External validation demo

A previous ALLOW is not permission for the next action.

REHT authorizes the exact action against the current authority and state. After execution, Veritas records what actually happened. The next action must prove causal continuity with that verified outcome.

REHT authorizes action A

ALLOW

Identity, authority, scope, freshness and exact action binding are valid at the execution boundary.

Action: Release payment batch A
Permit: permit:a7f1…
Authority: ACTIVE

Gateway executes action A

EXECUTED

The gateway consumes the permit once and binds the execution receipt to the exact authorized action.

Permit consumed: YES
Receipt: receipt:4c91…
Status: SUCCEEDED

Veritas verifies observed outcome

VERIFIED

Observed external state matches the execution receipt and is appended to the immutable evidence chain.

WORM chain: VERIFIED
Observed state: MATCH
Authority granted by Veritas: NO

REHT evaluates action B now

ALLOW

The verified outcome remains consistent with the authorized state and authority is still active. Action B receives a new permit.

Prior ALLOW reused: NO
Current authority: ACTIVE
New permit: permit:b2d8…

What this proves

Authorization does not remain valid over time. Execution must prove causal continuity with the authorized state. A successful previous action cannot carry authority forward through changed reality or revoked authority.

REHT → Gateway → Veritas WORM → verified outcome → REHT