Architecture

A layered control model for consequential autonomous action.

Platform Overview

Architecture map

Seven planes. One proof obligation.

The owner, trust boundary, non-final states, and current evidence ceiling are explicit at every step.

Authority is not execution.Execution is not finality.Finality requires proof of the ending.

01Authority
02Action
03Execution
04Authoritative State
05Reconciliation
06Receipt
07Reopen if Reality Changes

Agent control stack

The control question changes as an action moves.

Each layer answers a different question. The Finality Gateway begins where execution systems stop: was the claimed ending established by an authoritative source?

01Identity
Who or what is acting?
02Authority
May it act for this purpose?
03Policy
Is this action permitted now?
04Execution
Was the action attempted?
05Outcome Finality
Did authoritative reality reach the required ending?
06Evidence
Can another party verify and reopen it?

Finality Gateway

Acknowledged is not authoritative. Authoritative is not final until reconciled.

01ACKNOWLEDGED
A runtime or tool reports completion.
02AUTHORITATIVE?
Read the source empowered to establish the outcome.
03RECONCILE
Compare required state, observed state, authority, contradictions, and obligations.
04FINAL / CONFLICT
Issue a Receipt only when the supportable state is explicit.
05REOPEN
Preserve lineage when governing reality changes.

Seven-plane control model

A reported action is not a proven ending.

Finality exists only when authorized action, execution evidence, authoritative reality, and reopen rules agree.

01
Authority planeControl owner · mandate issuer
Identity, delegation, purpose, limits, expiry, and revocation.
02
Decision planeControl owner · policy authority
Versioned rules determine whether the proposed consequence is permitted.
03
Execution planeControl owner · accountable operator
Only bounded adapters may attempt an authorized state transition.
04
Authoritative-state planeControl owner · system of record
Reality is read from the source empowered to establish the outcome.
05
Reconciliation planeControl owner · control function
Claims, receipts, and authoritative state are compared; contradictions stay open.
06
Evidence planeControl owner · evidence custodian
A portable Receipt binds lineage, classifications, hashes, and obligations.
07
Reopen loopControl owner · designated authority
New reality, revocation, correction, or contradiction supersedes prior closure.

Finality reconciled authoritative endingNot finality request, approval, or acknowledgement aloneTrust boundary external systems and assessorsEvidence state current public ceiling E3

Receipt

The ending becomes portable.

The public Receipt object shows the minimum explanatory anatomy without exposing protected buyer evidence.

Public product object · illustrative sample

Finality Receipt

A portable explanation of what was authorized, attempted, observed, reconciled, and reopened. Sample values are illustrative; no external transaction or attestation is represented.

E2 sample · locally verifiable

Action ID: act_demo_7f31
Authority reference: mandate_demo_v3
Decision lineage: policy_demo_12 → PERMIT
Execution acknowledgement: adapter_ack_demo
Authoritative state: RECONCILED
Evidence references: evidence_demo_01…04
Contradictions: none observed in sample
Obligations: retain · notify · reopen
Classification: ILLUSTRATIVE
Protocol version: outcome-finality.v2.0.0
Receipt hash: sha256: 9f2c…7a10
Reopen rule: new state or revoked authority
Supersession lineage: none in sample

authority linked policy linked state reconciled reopen rule present