System state
Review supported execution state, failures, and blocked actions without mistaking the interface for authority.
Control gives operators one place to review supported execution state, decision outcomes, receipts, and causal lineage. It can initiate supported governed workflows; Runtime alone decides whether an effect is authorized.
Control organizes the evidence an operator needs to move from visible state to the decision and recorded cause behind it.
Review supported execution state, failures, and blocked actions without mistaking the interface for authority.
Read Runtime outcomes — allowed, denied, or governed review — in the same operator context.
Move from a decision outcome to its supporting receipt and evidence references.
Control displays recorded receipt and lineage relationships. It does not infer missing links or turn interface narrative into proof.
Supported state appears with its recorded source and status.
The decision outcome anchors the operator review.
The supporting receipt remains primary over summaries or UI narrative.
Recorded predecessor and correlation links show how the state evolved.
A supported operator workflow begins in Control, crosses the same governed boundary as any other actor, and cannot produce an effect until Runtime authorizes it.
Control initiates. Runtime decides. Receipts remain the record.
The public Control demo is a labeled static preview. Runtime remains the place to inspect how authorization governs effects.