§01 PART 5/6 (13,953 chars · Sections: The Evidence Register: `AINA-E01`–`E09`; Bring One Real Boundary; The Article 01 Claim Card; Before the Green Check Mark) — ← Part 4 · Part 6 → · 1-Call Brief · Full §01 · Raw .txt · All: P1 P2 P3 P4 P5 P6
The Evidence Register: AINA-E01–E09
The implementation claims below are deliberately bounded. An evidence ID stabilizes citation; it is not an assurance grade.
Availability class for every entry: CONTROLLED. The underlying artifacts are available for qualified, method-scoped technical review rather than as an implied public download or unrestricted data release. Review access must be adequate to test the named claim and permits adverse findings; it does not itself constitute independent validation. The independent-review route is [RESEARCH] through Article 09.
| ID | Bounded implementation claim | Principal evidence surface and ceiling |
|---|---|---|
AINA-E01 — Relation survival |
On the declared 125-record, 25-positive-pair corpus, Semantic Switch preserved locally established relationships through an external computation path while declared prohibited direct identifiers were absent from inspected payloads. | Implemented, measured, author-verified. Not independent fuzzy-match discovery, superiority over stable tokenization, universal privacy, auxiliary-roster unlinkability, or population accuracy. |
AINA-E02 — Blocking witness proof |
Four retained historical forensic runs contained proof objects whose accepted public commitments matched the deterministic V2 witness under the declared Rust audit and STARK verification path. | Implemented and author-verified on retained artifacts. Not a current cryptographic-assurance benchmark, semantic truth of every edge, or proof of every standing center. |
AINA-E03 — Dedupe admission |
The contact-dedupe path binds candidate identity partitions to a sealed blocking run and rejects malformed, incomplete, incompatible, or source-unbound objects through a Rust/WASM contract. | Implemented and author-verified at named wiring/package gates. Does not guarantee that every admitted identity decision is worldly true. |
AINA-E04 — Field-level merge |
Canonical merge verifies field and element citations against sealed evidence, permits partial finality, and emits reversible patch plans with pre-state and post-state commitments. | Implemented and author-verified at named wiring/release gates. Not ambient mutation permission, source truth, or hardware-strengthened execution. |
AINA-E05 — Governed coordination and model access |
Room operationalizes typed actor/session identity, EISA-bound act recognition, native wake proof, credential-source resolution, leases with ownership-generation checks, pre-state capture, transition commitments, invariants, package admission, and resolution across a heterogeneous fleet. | Implemented, measured, author-verified for the publication release. Tier 1 software/OS evidence, not Tier 2 AINA operative standing, hardware interposition, universal adapters, HSM custody, or adversarial FNV collision resistance. |
AINA-E06 — Governed durable memory |
Honcho Portable provides local, scoped, lineage-bearing memory while Room and the standing path remain authoritative for current operational state. | Implemented and author-verified on the declared portable memory package. Memory remains advisory; it does not prove current locks, delivery, mutation, package identity, or terminal standing. |
AINA-E07 — Portable packaging and deployment topology |
The four-root publication collection packages folder-relative appliances, runtimes, browser surfaces, local state, relocation-aware bootstrap, sealed handoffs, and replayable portability receipts. | Implemented and author-verified for the named release. Portability is predicate-specific and does not include external model services, arbitrary hosts, undisclosed networks, or physical A2E. |
AINA-E08 — Authenticated Dedupe-to-Merge release handoff |
The qualified release carries a Dedupe result into Merge through a signed, receipt-last handoff bound to producer, source input, run, cluster, required artifacts, byte counts, hashes, and tree commitment; Merge validates intake before lower-level operation. | Implemented and author-verified for the publication release. Establishes the declared release handoff, not the worldly truth of the partition or every canonical field. |
AINA-E09 — Forward-only Shield ingress |
After the entity-resolution stack seals an L3 baseline, a later record passes pre-provider switching and leak scan, declared embedding quorum, exact-baseline-run retrieval, deterministic anchor gating, and one of three forward-only dispositions: DEFLECT, GROWTH, or ESCALATE as autonomous quarantine. No route mutates the sealed baseline in place. |
Implemented and author-verified for the publication release. Not universal ER accuracy, source truth, universal privacy, provider-side-channel elimination, control of undeclared ingress paths, or independent validation. |
The seven governing claims
AINA-C01— Output is proposal matter. A model can be useful, accurate, aligned, and authenticated while lacking authority for a consequence.AINA-C02— Shape is not standing. Schemas, enums, registries, confidence scores, and credentials answer necessary questions, not the complete act.AINA-C03— Standing is conjunctive. Act, actor, encounter, execution path, target, and terminal disposition must compose for this transition now.AINA-C04— The model proposes; the boundary disposes. Probabilistic systems may search and reason while deterministic surfaces own admission and force.AINA-C05— Authority does not travel automatically. Retrieved memory, remote consensus, signed packets, and authentic instructions may supply evidence, but any resulting transition must earn standing under the receiving domain’s current rules.AINA-C06— The boundary ends at effect. Authorization is incomplete until the actual target and release path are governed at the assurance tier the consequence requires.AINA-C07— Refusal is a result. Withheld, contested, downgraded, and non-action states deserve the same evidentiary seriousness as execution receipts.
Bring One Real Boundary
If your team is running an AI-proposed mutation whose green status currently depends on schema validation, a credential, or a 200 OK, the AI Workflow Standing Challenge is the direct next step. Bring one bounded transition. I will map which lifecycle predicates the current stack proves, which it assumes, and how an existing governed transition closes—or refuses to close—under inspection.
The challenge excludes custom enterprise taxonomy, production write authority, organization-wide rollout, and independent-validation claims. Deployment, pilots, distribution, principal mandates, and independent review follow the separate routes in Article 09: Bring One Real Boundary.
The Article 01 Claim Card
Mechanism:
AINA Transition-Governance Architecture and Constitutional Kernel
(doc_source, evidence, eisa, room, leases, vault, confine, destinations, enforce, task, invariants)
Failure it governs:
The Lawful-Act Defect — syntactically valid, authenticated, or confident AI proposals
becoming self-authorizing state transitions, forged tool-call origin, approval laundering,
and green statuses that do not verify a closed destination effect.
Positive path:
Protected Reality (doc_ / cap_ / ViewManifest)
→ Served Receipt (srv_) and Evidence Handle (ev_)
→ EISA Recognized Act (eisa_)
→ Room Session, Task, and Five-Gate Wake Permit (RequestPermit)
→ Monotonic Lease Generation (room.generation.v2)
→ Controller-Fixed RequestedAct
→ Fenced Destination Mutation (oshandle.rs / records.rs:699)
→ Independent Post-State Observation
→ Terminal Receipt (Strict or non-fabricating Successor).
Refusal / quarantine path:
Fail-closed refusal before mutation: strict duplicate-key refusal, typed EISA fault,
manufactured-reference refusal, stale wake refusal, tenancy/version refusal.
Post-effect evidence failure held as durable effect_unconfirmed.
Out-of-band file edits preserved as quarantine_ungated with released_with_ungated_content.
Evidence status:
Implemented, Measured, and Author-Verified across AINA-E01–AINA-E09,
October 6–8 P01–P06 evaluation runs, and the 45-case candidate-binary publication gate.
Not Independently Validated: zero external findings registered in this snapshot.
Verifier and artifacts:
squad-connector runtime verifiers: strict parser, EISA recognizer, wake authority,
RequestedAct validator, worker-receipt validator, invariant engine,
and the 45-case conformance runner in package/run_cmd/execute.rs:272-322.
Scope and claim ceiling:
Path enforcement:
Enforced on governed MCP, file, and SQLite routes mediated by squad-connector.
Effect coverage:
Scoped to declared project territories and connector-mediated destinations;
no physical hardware-interposition claim and no claim of stopping privileged host-admin bypass.
Implementation assurance:
Windows NTFS / Win32 / LPAC / Job Object reference embodiment.
Author-verified, not third-party certified or a legal compliance attestation.
Next stage in the machine:
Article 01 defines constitutional law and lifecycle.
Article 02 builds Stage Zero: confined document parsing and server-cut evidence.
Commercial doorway:
AI Workflow Standing Challenge — bring one AI-proposed mutation or tool workflow that
relies on schema validation and a green check mark; receive a predicate map and a live
replay of a governed transition end-to-end (Article 09 · me@blayneaina.com).
Before the Green Check Mark
Return to the opening merge.
The conventional system saw valid JSON, called a tool, and reported success. A consequence-governed system must tell a longer story.
Stage Zero sealed the source records, instructions, actor roster, active governance binding, and evidence coordinates. Semantic Switch then transformed declared native identifiers into structure-preserving fictional records before qBlock/Qdrant Edge or any later provider-exposed computation. Native rows, keys, and the private crosswalk stayed local while qBlock and Mesh committed the protected candidate universe, ensuring no participant could enlarge the case halfway through deciding it.
The model then nominated a possible relationship through a recognized EISA act. Its member identifiers and evidence references resolved. Its stage nonce matched the active instruction bundle. The proposing actor possessed nomination authority but no merge authority. Fracture tested the relationship through role-separated challenge and preserved both support and contradiction. Terminal Binding either established the identity boundary, refused it, or left it unresolved under declared rules.
Only then could Forge propose a canonical record, deciding field by field which values were supported, re-walking evidence coordinates, preserving provenance and dissent, rejecting unsupported values, and producing a reversible transition plan. Shield gave later records only forward dispositions—deflect, grow through a sealed branch, or isolate in autonomous quarantine—without rewriting the baseline.
Machine Force executed only the admitted plan under declared runtime and lock conditions. If the transition crossed a machine boundary, the receiving domain re-established standing rather than inheriting remote standing. At the actual target, the A2E action lane revalidated target standing and consequence assurance before releasing effect. The terminal record preserved not merely the winning values, but the reasons transitions acquired standing, what was refused, which alternatives lost, what executed, and which disposition became current.
The green check mark could then mean something more substantial than “the API returned 200.” It could mean:
- Protected reality was sealed before reasoning began.
- Active governance objects verified under the declared issuance and activation procedure.
- The candidate universe was committed.
- The proposed act was recognized and its evidence bound.
- Origin resolved to an eligible producer and source event.
- Actor authority was current under the active instruction bundle.
- All required standing results referred to the same transition and formed a disclosed acyclic dependency graph.
- Target derived from the declared target authority without fallback laundering.
- An eligible issuer admitted an occurrence-bound warrant, and the executor revalidated it at a single ordering point with current governance, revocation, time, and target state.
- Execution matched the admitted transition, target, path, obligations, composition law, and available assurance tier.
- The operating budget remained visible, and resource pressure did not widen authority or erase refusal.
- Path inventory identified no unresolved in-scope route to the claimed effect, with exclusions named explicitly.
- Terminal status, refusals, dissent, and non-actions were preserved, with one disposition current under the declared fork law.
This does not guarantee that the machine will never be wrong. It guarantees something more useful: a falsifiable requirement that fluency alone is insufficient to acquire authority, and that any release while a required predicate is false defeats the path-enforcement claim.
That is the route to trusting AI. Not faith in the model. Not another layer of prose. A machine that can say, for every proposed transition, exactly why it may—or may not—become real.
The AINA rule: no proposal may award itself force. The proposed transition must satisfy every required predicate on its declared path from sealed reality to governed effect.
END OF §01 PART 5/6 — Next: https://blayneaina.com/01-an-ai-output-is-not-an-act/part-6/ · §01 1-Call Brief · Raw .md