← SES-020 — Formal Semantic Execution Data Model · Standard Index · SES-022 — Transport-Neutral Wire Protocol →
Status: Draft 1.0 — Normative target.
SES is not only a pipeline. Retries, reauthorization, cancellation, approvals, stale policy, provider failure, and partial mutation create state transitions. A conforming implementation MUST model these transitions explicitly.
Required states:
Received -> Resolved -> Authorized -> Planned -> Verified -> Executing -> Completed
Terminal failure states MUST include at least Rejected, Expired, Cancelled, ResourceExhausted, ProviderIncompatible, and Failed.
Resolved -> Authorized MUST occur only after whole-graph authorization.Authorized -> Planned MUST preserve authority.Planned -> Verified MUST verify provenance, freshness, IR integrity, and provider requirements.Verified -> Executing MUST NOT occur if any required proof is stale or invalid.A retry MUST NOT implicitly recreate authority. Implementations MUST define whether the retry reuses, refreshes, or invalidates authorization provenance.
Mutations MUST additionally model Prepared, Committed, Compensating, and Compensated where the selected mutation profile permits partial failure.
Cancellation MUST be represented as a semantic event, not merely a transport disconnect. Providers MUST report whether cancellation was observed before, during, or after side effects.
Define a formal transition table, state/event/error registry, distributed execution lineage, human approval transitions, and recovery semantics.
Fault-injection tests MUST demonstrate that every reachable security-context change, timeout, cancellation, retry, and partial-failure path either preserves the stated invariant or terminates without unauthorized execution.
← SES-020 — Formal Semantic Execution Data Model · Standard Index · SES-022 — Transport-Neutral Wire Protocol →