Definitions
Context Layer terminology
Standard vocabulary used to describe runtime-governed LLM systems.
Core primitives
Context Layer
Context Layer is a runtime execution boundary between your application and the model provider.
It controls how every LLM request is executed, not just what is sent.
It governs:
- whether execution proceeds
- what context the model receives
- how execution evolves over time
Execution boundary
The execution boundary is the point where control shifts from the application to the runtime.
Inside the boundary:
- execution rules are enforced
- context is constructed
- model invocation is controlled
Outside the boundary:
- the application decides intent
- the model generates output
Execution
An execution is a single controlled unit of runtime behavior.
Execution is governed from start to finish.
Session
A session is the runtime container that holds execution state over time.
It maintains:
- constraint context
- execution history
- authority state
All executions occur within a session.
The session defines continuity. Without it, execution is isolated.
Constraint
A constraint is an enforceable rule that affects execution behavior.
Constraints define:
- what is allowed
- what must be satisfied
- what cannot occur
They are applied by the runtime, not inferred by the model.
Constraints persist across execution steps.
Context
Context is the full input the model receives during execution.
It includes:
- user input
- prior execution state
- constraints
- retrieved or derived information
Context is not assembled implicitly. It is constructed by the runtime.
System behavior
Determinism
Determinism refers to the stability of execution behavior.
Given:
- the same input
- the same session state
- the same constraints
The runtime produces the same execution input.
Determinism applies to execution, not model output.
Execution lifecycle
Execution is governed as a complete lifecycle.
The runtime controls how execution begins, how it proceeds, and how it is validated.
Authority
Authority defines how the runtime controls execution.
It determines:
- whether execution proceeds
- how constraints are applied
- how outcomes are validated
Execution Authority
Execution Authority enforces authority within the runtime.
It performs:
- admission checks
- constraint enforcement
- lifecycle validation
- continuation decisions
It ensures execution follows defined rules at all times.
Runtime constructs
Context block
The context block is the runtime representation of context used during execution.
It is constructed by the runtime and includes:
- current objective
- prior execution state
- constraints
- relevant context
The model does not decide what it sees. The runtime does.
Authority snapshot
The authority snapshot is the runtime state that defines execution authority for a session.
It captures:
- execution identity
- execution mode
- constraint context
- runtime state
It remains consistent for the duration of the session.
Authority contract
The authority contract defines how execution is enforced.
It specifies:
- how constraints are applied
- how execution is validated
- how decisions are made during execution
Execution behavior is bound to a declared version.
Behavior does not change implicitly.
Execution models
Execution mode
Execution mode defines how execution behaves over time.
It determines:
- whether execution is bounded or continuous
- how state persists
- how lifecycle rules apply
Execution mode is fixed for a given runtime context.
Flow
Flow is a bounded execution mode for multi-step workflows.
Execution:
- progresses step by step
- shares state across steps
- must terminate explicitly
Pulse
Pulse is a persistent execution mode for conversational interaction.
Execution:
- continues across interactions
- maintains evolving state
- does not require explicit termination
Pulse is designed for ongoing interaction without losing control over constraints.
Outputs and artifacts
Authority report
An authority report is the final record of a completed Flow execution.
It summarizes:
- how execution proceeded
- how constraints were applied
- how the system behaved across the workflow
It provides evidence of execution under runtime control.
Execution receipt
An execution receipt is a per-step record of execution.
It captures:
- execution outcome
- constraint evaluation
- verification results
- runtime decisions
Receipts allow inspection of how each step executed.
Session rules
Session rules are constraints accumulated during execution.
They:
- persist across steps
- remain visible to the model
- are enforced when relevant
They allow the system to maintain awareness of requirements over time without enforcing them prematurely.