You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Agent Memory Convention enforces ten foundational design principles to ensure project memory remains accurate, compact, and maintainable over time.1
The 10 Minimal Agent Guarantees
Persistent knowledge belongs in the OKF corpus: Conversations reset, but the knowledge/ bundle survives.
Search before write: Search existing concepts before authoring to prevent duplication.
Prefer update over duplication: Expand or revise matching concepts when new facts emerge.
No chain-of-thought storage: Store only durable facts and decisions; discard transient reasoning.
Preserve provenance: Track sources, URIs, and dates using standard OKF mechanisms.
Preserve meaningful history: Track changes via log.md and lifecycle metadata rather than silent overwrites.
Review knowledge after substantial work: Execute the review loop described in lifecycle.
Validate changes: Ensure bundle conformance using the tooling layer outlined in architecture/layers.
Never claim persistence unless confirmed: Report failures honestly if a disk write or validation fails.
Domain Neutrality
The convention intentionally avoids prescribing a fixed taxonomy. Projects may define custom semantic types (e.g. Fact, Decision, Client, Book, Runbook, Metric) as needed. This flexibility supports diverse domains as detailed in project/overview.