# §01 Part 3/6 — An AI Output Is Not an Act Canonical: https://blayneaina.com/01-an-ai-output-is-not-an-act/part-3/ | Raw Article: https://blayneaina.com/01.md | Next Part: https://blayneaina.com/01/part-4.txt ## The 2026 Action-Boundary Landscape: Composition, Not Erasure Between March and September 2026, academic and industry security engineering converged on a shared premise: prompt guardrails cannot govern execution, and agent runtimes need deterministic enforcement outside the model. AINA does not compete with those mechanisms by renaming single-point interception. It defines the end-to-end conjunctive lifecycle that prevents any one valid check from impersonating the complete standing decision. | 2026 work and status | Native contribution | Established overlap | What full-lifecycle standing additionally requires | |---|---|---|---| | **Approval Laundering** — [Wang `arXiv:2609.38983`](https://arxiv.org/abs/2609.38983), [Zhang et al. `arXiv:2609.28586`](https://arxiv.org/abs/2609.28586), September 2026 preprints | Six approval–execution failure classes and transitive effects beyond approved invocations. | Directly motivates why approving surface parameters is insufficient. | Controller-fixed `RequestedAct` with content and pre-state commitments, revalidated under a pinned handle inside the destination transaction. | | **ActGov** ([`arXiv:2609.24446`](https://arxiv.org/abs/2609.24446)) and **Authorization Architectures** ([`arXiv:2609.15906`](https://arxiv.org/abs/2609.15906), September 2026 preprints) | SMT-based counterexample policy validation and multi-hop principal-hierarchy enforcement. | Deterministic pre-action validation and explicit principal separation. | Policy validation does not itself seal evidence, adjudicate entity equivalence, hold kernel file exclusion, or govern post-effect receipt failure. | | **AcquireBound** ([`arXiv:2609.14744`](https://arxiv.org/abs/2609.14744), September 2026 preprint) | Identifies the post-fulfillment activation gap when agents acquire new resources, credentials, or sub-agents mid-task. | New capabilities cannot become active without a bound activation transaction. | Wake delivery, lease acquisition, and successor grants additionally bind to monotonic generation and control epochs. | | **AttriGuard** ([USENIX Security ’26](https://www.usenix.org/conference/usenixsecurity26/presentation/he-yu)) and **SARA** ([`arXiv:2608.27146`](https://arxiv.org/abs/2608.27146), August 2026) | Counterfactual shadow replay for causal attribution and separation of action induction from runtime authorization. | Tool-call shape and conversation history must not launder origin into authority. | Causal attribution is one origin/encounter input; it does not prove target pre-state, exclusive ownership, or terminal closure. | | **Field-Tier Minimization** ([`arXiv:2608.25474`](https://arxiv.org/abs/2608.25474), August 2026 preprint) | Separates disclosure minimization from authorization, reducing the fields exposed during agent action mediation. | Limiting what a model may see is distinct from deciding what its proposal may do. | Semantic Switch’s disclosure boundary must compose with sealed evidence, recognized acts, current standing, and fenced execution; field minimization alone cannot confer consequence authority. | | **Aegis** ([`arXiv:2608.16891`](https://arxiv.org/abs/2608.16891)) and **Mandato** ([`arXiv:2608.14074`](https://arxiv.org/abs/2608.14074), August 2026 preprints) | Server-side provenance, fail-closed quorum settlement, digitally signed mandates, and chained audit trails. | The model proposes while the runtime decides; signed pre-execution mandates and refusals are first-class. | AINA extends beyond proxy interception to LPAC document jails, pre-resume child inspection, and OS handle fencing across rename windows. | | **PCAA** ([`arXiv:2606.04104`](https://arxiv.org/abs/2606.04104)) and **CAVA** ([`arXiv:2607.13716`](https://arxiv.org/abs/2607.13716), June–July 2026 preprints) | Runtime-neutral action certificates spanning admissibility, approval, execution identity, receipts, and closure. | Portable action identity, approval binding, and explicit outcome closure. | AINA separates path enforcement, effect coverage, and implementation assurance, with closed EISA recognition and strict versus successor receipts. | | **SAB** ([`arXiv:2606.11632`](https://arxiv.org/abs/2606.11632)), **IGAC/OpenPort** ([`arXiv:2606.22916v3`](https://arxiv.org/abs/2606.22916)), and **OAP** ([`arXiv:2603.20953`](https://arxiv.org/abs/2603.20953), March–July 2026 preprints) | Certificate-bound admission rechecked by an execution broker, short-lived intent certificates, and synchronous pre-tool policy evaluation. | Deterministic pre-tool mediation and revocable admission artifacts are shared territory. | Admission certificates must compose with server-cut evidence, counterevidence checks, pre-write vaults, and durable unconfirmed-effect reconciliation. | This landscape is important for two reasons. First, the field is no longer debating whether execution needs an external boundary; the boundary has arrived. Second, **full-lifecycle transition standing** is the integration test: no one mechanism can borrow the assurance of the others without proving the complete path. ### A mature conventional stack is allowed to win The necessity claim has two separate falsifiers. A conventional deployment may already defeat the Lawful-Act Defect. Separately, AINA’s distinct value contracts if its common objects and cross-boundary composition add no reproducible assurance or diagnostic value over that deployment. A plausible mature composition might combine SPIFFE/SPIRE workload identity, OpenID AuthZEN or another policy decision/enforcement pair, JSON Schema or Protocol Buffers, content-addressed evidence manifests, etcd or PostgreSQL MVCC, isolated or attested execution such as AWS Nitro Enclaves, leases and fencing, and durable event and receipt ledgers such as SCITT. | Required lifecycle property | Candidate conventional implementation burden | AINA reference path | What equivalence must demonstrate | |---|---|---|---| | Proposal origin and actor eligibility | SPIFFE/SPIRE workload identity, native session binding, and an AuthZEN-style policy decision | Authenticated Room session, project territory, wake permit, and task binding | The same eligible origin cannot be substituted or replayed across actor, session, task, or epoch | | Sealed evidence world | Content-addressed source manifests, immutable revisions, and served-content receipts | Confined `doc_source`, JCS `ViewManifest`, `srv_` receipts, and `ev_` handles | A citation resolves to the same server-served matter, with drift and omissions visible | | Bounded act recognition | JSON Schema, Protocol Buffers, or another closed action grammar | Strict EISA parser, record-relative pointers, closed opcodes, comparators, and counterevidence law | Malformed, unsupported, or contradictory proposals fail before acquiring standing | | Current target and tenancy | etcd/PostgreSQL MVCC, leases, fencing tokens, and destination version predicates | `room.generation.v2`, typed leases, Win32 handle exclusion, and SQLite version fences | A stale or displaced holder is refused at the resource without changing the new state | | Release-ready execution | Isolated or attested execution, controller-approved payload, and current policy recheck | Pre-resume LPAC/token/handle inspection and a pinned controller-fixed `RequestedAct` | The executed payload and target equal the approved act at the authoritative ordering point | | Independent effect observation | Destination readback, artifact digest checks, and out-of-band divergence detection | Post-state observation, acceptance predicates, and Amber quarantine | `200 OK` is not accepted unless the actual post-state satisfies the declared predicates | | Honest terminal closure | Durable receipts and transparency ledgers such as SCITT, with explicit retry and reconciliation rules | Strict original receipts, successor grants, `effect_unconfirmed`, and break-glass carry-forward | No committed-but-unreceived effect is duplicated or relabeled as original-session completion | The bill of materials proves nothing by itself. Equivalence depends on whether those components bind one canonical transition through origin, act, evidence, actor, target, execution, occurrence, effect, and closure. If they demonstrate the same positive progressions and failure behavior, they have earned functional credit. ## Standards: What They Prove, and What They Cannot Carry for Us A second source of confusion is the belief that adopting a modern protocol automatically creates standing. Standards are valuable precisely because each has a bounded native property. They do not become stronger through proximity to one another. | Standard or specification | Maturity as of October 2026 | Native contribution | Boundary that remains | |---|---|---|---| | **IETF Transaction Tokens** ([`draft-ietf-oauth-transaction-tokens-11`](https://datatracker.ietf.org/doc/draft-ietf-oauth-transaction-tokens/)) | IETF OAuth Working Group Internet-Draft, July 2026 | Propagates short-lived, signed caller and request context across internal service call chains. | Does not prove model-turn origin, sealed evidence validity, target pre-state, or post-effect receipt closure. | | **OAuth Identity Chaining** ([`draft-ietf-oauth-identity-chaining-17`](https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-chaining/)) and **WIMSE** ([`draft-ietf-wimse-arch-08`](https://datatracker.ietf.org/doc/draft-ietf-wimse-arch/)) | IETF Working Group Internet-Drafts, 2026 | Preserves identity and authorization context across trust domains and multi-service workloads. | The destination domain must still re-establish local target authority, generation, and terminal closure. | | **OpenID Shared Signals (SSF 1.0) and CAEP 1.0** ([SSF](https://openid.net/specs/openid-sharedsignals-framework-1_0-final.html), [CAEP](https://openid.net/specs/openid-caep-1_0-final.html)) | OpenID Foundation Final Specifications | Asynchronous security-event streams for session, credential, and claim revocation. | Delivery latency cannot retroactively undo a committed write; synchronous epoch checks remain necessary at the mutation boundary. | | **OpenID AuthZEN Authorization API 1.0, COAZ-MCP, Obligations, and ARAP** ([AuthZEN 1.0](https://openid.net/specs/authorization-api-1_0.html), [COAZ-MCP](https://openid.github.io/authzen/authzen-coaz-mcp-binding-1_0.html)) | `AuthZEN 1.0` Final, January 2026; COAZ-MCP, Obligations, and ARAP Working Group Drafts, 2026 | Externalizes Subject–Action–Resource–Context decisions, MCP projections, mandatory obligations, and requestable-denial approval workflows. | An `allow` is one actor predicate; it does not establish act recognition, lawful encounter, execution readiness, or terminal disposition. | | **IETF SCITT Architecture** ([`RFC 9943`](https://www.rfc-editor.org/rfc/rfc9943.html)) and 2026 AI-agent SCITT drafts | `RFC 9943` Proposed Standard, June 2026; AI-agent profiles remain Individual Internet-Drafts | Registers signed statements, permits, action capsules, receipts, and refusal events in an append-only Transparency Service. | Registration proves statement integrity and log inclusion, not the substantive truth of the statement or absence of an unlogged crash. | | **Model Context Protocol `2026-07-28`** ([MCP Authorization](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization)) | Released protocol specification, July 28, 2026 | Stateless self-describing HTTP requests and OAuth 2.1 resource-server authorization using Protected Resource Metadata and PKCE. | Explicitly excludes the HTTP OAuth flow from `stdio` local transports and does not bind model-event origin, evidence handles, or destination pre-state. | The `stdio` exception matters for local multi-agent fleets. A local server should retrieve credentials from the environment rather than perform HTTP OAuth. It still needs an authenticated controller-brokered IPC path, per-worker ACLs, native conversation binding, and current task authority. Transport compatibility is not act authority.