Concepts/Concept

Application context

A payroll agent receives “create the Singapore payroll group from last month’s template.” The model can interpret the request and explain the intended result. The runtime still needs a finite route, exact tenant and template identifiers, approval state, and a deterministic branch for failure. Free-form language and program control serve different consumers.

Definition

The narrative plane contains model-readable goals, observations, explanations, and summaries. The control plane contains bounded values that select program branches: intent enums, node states, policy decisions, approval status, retry state, and error codes. Narrative helps the model reason. Control determines what the runtime is allowed to do next.

Engineering mechanism

The model may propose a control value, but a parser validates it against a finite schema and maps invalid output to an explicit fallback. Tool responses enter mechanical state before a narrative summary is produced.

Boundary

This separation does not remove language from execution. It prevents prose from becoming the sole authority for routing, approval, and recovery. Content-only work can use a thinner control plane; external writes require explicit control values and recorded transitions.

Edit source · Published source · Review process