A draft, open to change
Open Memories starts with one question: what is the smallest useful contract that lets different tools read the same memory?
Draft 0.1 is a starting proposal. Field names, discovery rules, and update behavior can change before a stable release. No standards body or tool vendor endorsement is claimed.
Review with a real example
Use the test-command record in the specification. Try to represent it in an existing tool without losing its identity, scope, or origin.
For a proposed change, describe:
- The memory and tool involved.
- The behavior the current draft cannot express.
- A concrete record or manifest that shows the change.
- Effects on existing readers and local or remote sources.
- Trust, privacy, and removal requirements.
Questions that need evidence
- Which metadata can existing tools preserve without loss?
- How should personal and project scopes interact?
- What should happen when two approved sources disagree?
- Which update and deletion rules need to cross source boundaries?
- Does a remote source need signatures in addition to HTTPS?
Read, keep, and share
Each page has a Read Markdown link. The document index lists all pages for tools and readers. Keep a copy, annotate a proposal, and share it with an implementer.
The specification documents use Creative Commons Attribution 4.0. Code in this website uses the MIT License. This project has no published adapter or conformance suite yet.