Expand description
Canonical Context execution contracts.
Context has three deliberately different representations:
ContextStateis the semantic state from which a context is selected;ContextPlanis the admitted runtime optimisation decision;ContextExecutionInputis the frozen identity of one provider execution input.
Provider request bytes remain host evidence. None of these objects is a provider request serializer, and none of them carries token projections as semantic message fields.
Structs§
- Cache
Prefix Boundary - Context
Candidate - Kernel-owned facts frozen in a provider effect. Host route and native count do not exist when the kernel emits this candidate; the host binds them before dispatch through core.
- Context
Dispatch Preparation - Evidence is returned with its canonical identity so storage adapters can persist every referenced body. This is host evidence; the kernel’s immutable candidate remains in the effect.
- Context
Dispatch Request - Context
Entry Ref - A stable reference to one addressable semantic item in ContextState.
- Context
Execution Input - The frozen identity of one provider execution input.
- Context
Plan - A deterministic runtime decision. It is not a mutable copy of ContextState.
- Context
Preparation - The non-authoritative result returned by the preparation boundary. The provider adapter keeps the projection transient and records the execution-input identity alongside host evidence.
- Context
Preparation Request - Facts supplied by the runtime at the preparation boundary. The renderer remains a kernel projection; provider adapters add their protocol-specific evidence after this call.
- Context
Prompt Measurement - The host count names fingerprinted request material under the route’s declared scope.
- Context
Selection - Context
State - Canonical Context state used to prepare one execution input.
Enums§
- Context
Contract Error - Context
Entry Source - The semantic area from which an entry came. This is provenance, not a provider role.
- Context
Plan Action - The action the runtime admitted for one Context entry.
Constants§
Functions§
- prepare_
context_ dispatch - prepare_
context_ dispatch_ json - Single canonical bridge shared by all SDK mirrors; no SDK owns selection or digest rules.
- verify_
context_ dispatch - Rebind recorded host evidence to the replayed kernel effect and compare all derived objects. A self-consistent record from a different effect, route or request is not equivalent.
- verify_
context_ dispatch_ json