Memory & Context
Give work durable context without making every memory globally visible.
Primitive supports managed memory, authorised context and provenance-preserving memory merge. Context is selected for an execution; memory is durable information that can be reused later.
Context is what is on the desk for this job. Memory is what can be kept in the filing cabinet for later. Primitive tries to put the right files on the desk without dumping the whole cabinet there.
Memory and context are separate because persistence and relevance are different problems. Durable information needs provenance and scope; an execution needs only the authorised subset relevant to its task. This boundary is critical for both quality and permissions.
Managed memory
Workspace includes managed memory with provenance-preserving merge, allowing durable information to be reconciled without silently losing source lineage.
Authorised context
Agent execution uses authorised context rather than treating all indexed information as automatically visible to every run.
Context Fabric direction
Primitive's broader context work treats context as a composed execution input spanning identity, task, memory, knowledge, source provenance and policy rather than as one large prompt string.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.