This appendix defines the normative execution lifecycle for a Constitutional Execution Infrastructure (CEI) runtime. Every consequential request progresses through explicit states with well-defined transition rules.
A governed runtime is not defined only by what it can execute, but by the states through which execution is permitted to evolve.
S0 DRAFT
│
▼
S1 VALIDATED
│
▼
S2 GOVERNED
│
▼
S3 ADMISSIBLE
│
▼
S4 EXECUTED
│
▼
S5 AUDITED
| State | Purpose | Entry Condition | Exit Condition |
|---|---|---|---|
| S0 Draft | Request received but not validated. | New execution request. | Validation begins. |
| S1 Validated | Syntax, identity, and mandatory fields verified. | Validation successful. | Governance evaluation starts. |
| S2 Governed | Authority, policy, and evidence evaluated. | Governance checks complete. | Admissibility decision requested. |
| S3 Admissible | Runtime authorizes execution. | Decision = GO. | Execution initiated. |
| S4 Executed | Consequential action completed. | Execution succeeds. | Audit recording completed. |
| S5 Audited | Replayable constitutional record finalized. | Ledger committed. | Terminal state. |
| Decision | Meaning | Transition |
|---|---|---|
| GO | Execution permitted. | S2 → S3 |
| DENY | Execution rejected. | S2 → Terminal |
| PAUSE | Await additional information. | S2 → Suspended |
| ESCALATE | Human review required. | S2 → Review Queue |
| OVERRIDE | Authorized exceptional path. | S2 → S3 (with recorded justification) |
| ID | Invariant |
|---|---|
| SI-001 | No execution before admissibility. |
| SI-002 | Every executed action has one immutable ledger entry. |
| SI-003 | Every audited action is replayable. |
| SI-004 | Authority is evaluated before consequence. |
| SI-005 | Terminal states cannot be modified in place. |
Replay reconstructs the ordered state transitions from immutable events. A conforming implementation should produce the same final state when provided with identical event history and policy versions.
events ↓ state reconstruction ↓ transition verification ↓ final constitutional state
if validate(request):
state = S1
if govern(request):
state = S2
if admissible(request):
state = S3
execute(request)
state = S4
audit(request)
state = S5
else:
deny(request)
The formal runtime state machine establishes a deterministic execution lifecycle for CEI implementations. By constraining execution to explicit states and controlled transitions, the runtime becomes auditable, replayable, and operationally predictable.
Next: Appendix D — Governance Decision Language.
This document forms part of the CEI publication record. Supporting evidence is organized through the engineering-evidence archive, specifications, architecture documentation and replay verification materials.