Context Block

10-Second Overview

The Context Block is the structured execution context assembled by Context Layer before every model invocation. Given identical inputs and session state, the Context Block is identical across executions.

Why the Context Block Exists

Unstructured prompt construction produces inconsistent execution behavior. Context varies across steps, deployments, and invocations. Rules present in one invocation may be absent in another.

The Context Block centralizes context assembly under enforced rules. Every invocation receives a consistent, structured context built from declared inputs.

What the Context Block Guarantees

Deterministic Assembly

For identical session state, constraints, and user input, the Context Block is identical across executions. Context Layer does not introduce variation during assembly.

Constraint Persistence

Active constraints are always included in the assembled context. Constraints are never trimmed regardless of context size.

Memory Priority

When context size is limited, retrieved context is trimmed first. Summaries are preserved. Constraints are always preserved.

Version-Bound Behavior

Context assembly behavior is bound to the Runtime Contract version active at session creation.

Flow vs Pulse

In Flow mode, context carries forward execution state across steps. Each step receives context built from the current session state including prior step outputs.

In Pulse mode, context is assembled per message within the session scope.

Non-Claims