Execution and reconciliation

Execution separates preparation, provider dispatch, observation, effect truth, and claim permission. Runtime supplies process-local orchestration around the identities and contracts; the host still owns the provider adapter, verifier, durable record, and operational recovery policy.

Acknowledgment is not effect truth

The provider adapter may return an acknowledgment, rejection, precondition failure, or uncertain result. An acknowledgment means the provider accepted or received the request; it does not establish that the authoritative system contains the intended effect. The independent verifier reads the authoritative system and returns bounded evidence such as PRESENT, ABSENT_FINAL, or INDETERMINATE.

PRESENT can support COMMITTED, ABSENT_FINAL can support DISPROVED, and unresolved evidence remains UNKNOWN. Preserve operation, effect, execution, and attempt identities so the original effect can be reconciled. Reconciliation may perform a verifier-only read; it must not create a second provider dispatch. Current Runtime evidence is process-local and does not prove restart-safe recovery or exactly-once execution.

See Results and errors, the Runtime API Reference, and reconciliation concepts.