ASIMOV State Directory Specification (SDS)

Living Standard, 26 June 2025

To the extent possible under law, the editors have waived all copyright and related or neighboring rights to this work. In addition, as of 26 June 2025, the editors have made this specification available under the Open Web Foundation Agreement Version 1.0, which is available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0. Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.

1. Introduction

The [ASIMOV] Platform is a polyglot development platform for trustworthy, neurosymbolic AI.

This specification defines the organization and management of ASIMOV state directories ($HOME/.asimov/), ensuring consistent data storage and retrieval mechanisms.

2. Examples

$ tree $HOME/.asimov
.
├── envs
├── libexec
│   ├── asimov-apify-fetcher
│   ├── asimov-apify-importer
│   ├── asimov-brightdata-cataloger
│   ├── asimov-brightdata-fetcher
│   ├── asimov-brightdata-importer
│   ├── asimov-jinja-runner
│   ├── asimov-jq-runner
│   ├── asimov-near-fetcher
│   ├── asimov-nexus-importer
│   ├── asimov-serpapi-fetcher
│   └── asimov-serpapi-importer
└── modules
    ├── apify.yaml
    ├── brightdata.yaml
    ├── jinja.yaml
    ├── jq.yaml
    ├── near.yaml
    ├── nexus.yaml
    └── serpapi.yaml

3. RDF Mapping

4. Security Considerations

5. IANA Considerations

This specification does not require any IANA registrations.

6. Acknowledgments

The editors would like to thank the ASIMOV Platform community for their contributions and feedback during the development of this specification.

7. Changes

This section will document changes between versions of this specification.

Conformance

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.