Protocol Examples

Autonomous Payment

Initial observation: payment.release for USD 186,400. Credential VERIFIED; authority UNRESOLVED. Policy decision: ESCALATE. Added authority evidence verifies a USD 250,000 limit. Updated state permits policy re-evaluation while preserving the first decision.

Tool Invocation

A runtime asserts intent, a gateway observes the request, and the tool records execution. APP preserves three observations rather than treating the request as proof of execution.

Delegated Authority Failure

An authenticated actor presents no sufficient delegation evidence. Identity may be VERIFIED while authority remains UNRESOLVED and policy denies execution.

Authority Revocation

Previously verified authority becomes REVOKED. Current policy state changes while the earlier valid interval remains in the evidence trail.

Conflicting Evidence

Two trusted sources disagree about principal or authority. APP marks the claim CONFLICTED and retains both sources for review.

Cross-System Correlation

A runtime activity and provider execution are CORROBORATED by independent identifiers and timing without being represented as deterministically linked.

Unknown External Agent

At an Outside-In boundary the actor may remain UNRESOLVED while credential, action and local policy are available.

Inside-Out + Outside-In

Runtime intent and gateway observation strengthen the same activity representation while preserving separate trust domains.

Human Escalation

Policy requests human review when evidence is insufficient. The review outcome becomes a new observation, not a rewrite of the original state.

Execution Mismatch

The requested action and provider-reported execution differ. APP preserves the discrepancy and marks the outcome claim CONFLICTED.

Policy-Regime Difference

The same evidence can lead to different local decisions in different policy domains without changing the underlying evidence state.