Implementation: ENABLED (memory services) · DESIGN (kernel retrieval snapshots) · Exposure: INTERNAL. See status labels. Memory is a store of things worth keeping. It is not state and it is not context. It feeds context through retrieval, under policy.

​
Architecture contract

  • Recalled content re-enters a run as chunks with provenance, a trust class and a sensitivity class. Recalled text is data, never instructions.
  • Sensitivity gates eligibility before utility: a chunk a component may not see is excluded before ranking.
  • Memory writes from a run are effects. They are policy-checked and leave a receipt like any other mutation.
  • A shared retrieval snapshot (one frozen retrieval result reused across steps) is a named concept in the contract set with no schema yet.

​
Current implementation

The memory services described in Memory Kernel and Memory Fabric are the current surface. The kernel-level rules on this page describe how they attach to the run model; the retrieval snapshot and chunk store are not on main.

​
Availability

​
Developer relevance

Never write secrets or unverified model claims into memory as fact. Store artifacts and evidence references, and let verification decide what is trusted.