Implementation: SHADOW (context compiler) · ENABLED (work-item context packs) · DESIGN (chunk store) · Exposure: INTERNAL. See status labels. Three things are kept apart on purpose: state is the truth about a run, memory is what can be retrieved later, and context is the projection one component sees for one step. Mixing them is how agents end up depending on transcript length.

​
Architecture contract

Rules that follow from this: context is always rebuildable from state; nothing lives only in context; retrieval results enter context as chunks with provenance and a trust class; and untrusted content is fenced, never merged into control instructions.

​
Current implementation

On main today the work runtime builds deterministic context packs to rehydrate a work item and fences untrusted text (a predecessor node’s output, ledger payloads) with a random per-render nonce. These are internal and predate the compiler contract. The context compiler, chunk store and shared retrieval snapshots are not on main. The compiler work (WP9) is in draft behind a flag that is off by default.

​
Availability

​
Developer relevance

Put anything that must survive a step into state, not into a prompt. Assume each step receives a right-sized projection, and that a component may be replaced between steps.