FAST 3-STEP SERIES DIGEST 3/3 — Digest 1 (§01–§03) · Digest 2 (§04–§06) · Digest 3 (§07–§09) · 1-Page Master Brief · All 9 Articles · Assurance · Proof
§07 — Defeating Approval Laundering: Act Pinning and Successor Grants
- URLs: 1-Call Brief (/07/brief/) · Full (/07-defeating-approval-laundering-act-pinning-and-successor-grants/) · Raw Markdown (/07.md) · Parts (3): P1 P2 P3
- Thesis & Scope: Problem: Approval for action A can become a different action A′ at execution, and a crash can separate commit from receipt. — Proves: Pre-resume confinement, controller-fixed RequestedAct, fenced SQLite, and non-fabricating successor grants preserve act and return continuity. — Scope: Use the Confinement, Act-Pinning & Crash-Straddling Continuity Challenge on one approved mutation.
- One Approved Mutation, Three Places to Fail: Suppose a policy approves raising one customer's credit limit from 10,000 to 25,000. The trusted controller first projects exactly that row and prepares the change. — Items: Before launch: the suspended worker's package SID, LPAC attribute, capabilities, Job membership, and current handle inventory are verified. A sentinel match or unclassified handle terminates the Job before instruction 0.
- 1. Pre-Resume Kernel Verification: Subtopics: Exhibit 7.1 — Pre-resume kernel audit; Exclusive identity and anti-reuse; Raw LPAC attribute verification; Handle-table object identity, not numeric equality; The native spawn gate — A confined process must be inspected before instruction 0. Once the worker runs, every later control is negotiating with an already-active environment. — Items:
TokenAppContainerSidmust equal the owned package SID; |TokenSecurityAttributesmust containWIN://NOALLAPPPKG; | the attribute must be integer kind2, count1, not disabled (flags & 0x10 == 0), and nonzero. - 2. Controller-Brokered Model Egress: Subtopics: Authenticated local channels; The controller owns the route; Journal before dispatch; never replay uncertainty; Exhibit 7.6 — Unresolved model egress — Confined workers have no general network capability. Model access is a separate controller-owned transition, not an ambient HTTP client. For LPAC workers, the controller exposes a per-worker
AF_UNIXendpoint with a restrictive ACL. — Items: exact HTTPS destination or isolated subscription CLI; | credential injection and fixed headers; | allowed models and output-token ceilings; | request/response byte limits and request budget; | project, agent, expiry, and control-epoch admission. - 3. Controller-Fixed
RequestedAct: Subtopics: Exhibit 7.2 —RequestedActlifecycle; Derivation; Durable fixation; Execution revalidation; Historical verification; Exhibit 7.4 — SanitizedRequestedActrecord; Exhibit 7.5 —requested_act_mismatch— The act is derived from exact projected bytes before the worker environment is issued. It is not re-read from live model prose at execution time. This is the strict confined-worker staging path. — Items: environment ID and worker; | staging actor and complete task binding; | exact source projection receipt; | source generation and source tenancy; | the controller-fixed destination. - 4. The Fenced SQLite Execution Window: Subtopics: Exhibit 7.3 — SQLite fenced execution flow; Exhibit 7.7 — Row-version refusal; Recovery capture is separate from the mutation; Exhibit 7.8 — Pre-write recovery capture —
destinations/records.rsexecutes the mutation inside one ordered window that joins lease authority, transaction isolation, act validation, recovery, and observation. - 5. Multi-Destination Capability Plans: A coordinated plan is not a distributed transaction. Each destination declares what its own write path can actually guarantee. A plan names required guarantees for each step. — Table Data:
sqlite.records; Declared guarantees:conditional_write,idempotent_retry,recovery_capture;cross_destination_atomic:false|goose.sessions.db; Declared guarantees:conditional_write,idempotent_retry,recovery_capture;cross_destination_atomic:false|opencode.http_api; Declared guarantees: Empty set; every fresh effect is held;… - 6. Non-Fabricating Successor Grants: Subtopics: The
ResultGrant; What a successor acknowledgement must prove; Exhibit 7.9 — Successor acknowledgement — A committed effect and its first receipt are different events. A crash can separate them permanently. A controller may issue aResultGrantfor one historical proposal to a new receiving task and environment. — Items: the original proposal ID and nested payload digest; | the whole immutable submission record digest; | the whole executor outcome digest and outcome class; | the receiving worker, task, environment, project, tenancy, and control epoch; | the issuer's current authenticated… - 7. Official Platform and Standards Crosswalk: The architecture uses existing platform primitives without pretending they are complete governance systems by themselves. The functional-equivalence concession remains: another stack that fixes the same exact act, confines its workers,… — Table Data: Microsoft AppContainer and LPAC security architecture; Native property: Package identity, capability restriction, and the
WIN://NOALLAPPPKGattribute can limit ambient package access.; How AINA composes it into execution standing: Fresh identity per launch, exact raw-token verification, exclusive grants, and anti-fallback native spawn refusal. - The Confinement, Act-Pinning & Crash-Straddling Continuity Challenge: The Confinement, Act-Pinning & Crash-Straddling Continuity Challenge uses one approved database mutation or worker result that could be replayed.
- The Fourteen Execution Claims: Table Data:
07-C01; Bounded claim: AppContainer profiles are single-launch and anti-reuse; Evidence and ceiling: Implemented and author-verified; existing identities fail withconfinement_identity_reused|07-C02; Bounded claim: Brokered hosts use deterministicS-1-9identities withSQADand 128 digest bits; Evidence and ceiling: Implemented and author-verified; no SAM account or ambient group authority is inherited |07-C03; Bounded claim: LPAC is verified directly from raw token attributes before resume; Evidence and ceiling: Implemented and author-verified for package, kind, count, flags, and nonzero value |07-C04; Bounded claim: Suspended handles are compared by… - The Article 07 Claim Card: Items: Mechanism: | AINA Execution Confinement, Act Fixation, Fenced Destination, | and Non-Fabricating Successor Continuity | (pre-resume token/handle inspection, spawn gate, model egress, | RequestedAct, SQLite IMMEDIATE, capability plans, ResultGrant) | Failure it governs: | Unclassified handles and ambient capabilities at launch; | approved A becoming a different A' at execution; | stale task/source/lease authority and out-of-band destination writes; | blind model-request replay and cross-destination atomicity…
- Approval Ends at the Destination, Not at the Prompt: The approved act cannot be allowed to drift between the prompt and the write. The controller therefore fixes it early, persists it immutably, and holds it open while the destination rereads current authority.
- Frequently Asked Questions: Subtopics: Why isn't numeric handle equality enough?; Why must the act be fixed before the worker environment exists?; Why use
BEGIN IMMEDIATEand a row-version predicate?; What happens if a destination commits but the worker crashes before receipt?; Does a successor grant complete the original return obligation?; Are multi-destination plans distributed transactions? — Handle values are process-local indices, not kernel object identities.CompareObjectHandlestests the underlying object. The pre-resume audit also checks expected provenance and a deliberate sentinel because numeric equality cannot prove… - Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: [Article 06 — Rollback Is Not Erasure: Dual-Tier Vaults and Ungated…
- Primary Platform References: Items: Microsoft
CompareObjectHandles— compare underlying kernel object identity | [MicrosoftCreateFileWand File-Sharing… - Publication Metadata: Title tag: Defeating Approval Laundering: Act Pinning and Successor Grants Meta description: Pre-resume kernel verification, controller-fixed RequestedAct, fenced SQLite execution, multi-destination holds, and non-fabricating…
§08 — The Sovereign Kill Switch: Break-Glass Epochs and the Conformance Gate
- URLs: 1-Call Brief (/08/brief/) · Full (/08-sovereign-kill-switch-break-glass-epochs-and-conformance-gate/) · Raw Markdown (/08.md) · Parts (4): P1 P2 P3 P4
- Thesis & Scope: Problem: A kill switch the agent can clear is not a boundary, and a green build does not prove the release enforces refusals. — Proves: Latch-first containment, scoped epochs, observed Job termination, in-doubt recovery, and the 45-case candidate gate close the loop. — Scope: Use the Break-Glass & Conformance Qualification Challenge on one containment or release requirement.
- One Stop, Three Races, No Invented All-Clear: Suppose a safety monitor engages a machine stop after an autonomous worker begins behaving anomalously. Three races now matter, and none can be resolved by a dashboard toggle: A project-scoped stop follows the same latch and… — Items: Containment races cleanup. The latch reaches durable storage before AINA attempts to terminate owned runs or cancel queued wakes. One worker termination remains unconfirmed; the latch still closes new effects.
- 1. Asymmetric Containment: Subtopics: Exhibit 8.1 — Stop versus recovery authority — The emergency interface deliberately gives stop and recovery different authority. Any admitted caller may invoke
engagebecause refusal to stop is the more dangerous default. A nonempty reason is mandatory. — Items: No MCP session. Ifsession::current()exists, recovery is refused. A model-connected tool session cannot satisfy the owner surface. | Explicit operator identity. The caller must supply--by operator; a worker or agent name is insufficient. - 2. Latch-First Containment: Subtopics: Exhibit 8.2 — Publication before cleanup; Exhibit 8.3 — Sanitized scoped latch record; Owned Jobs must be observed stopped; “Latched” is not the same as “fully reconciled” — An emergency stop must not depend on a database, a live server, a lease sweep, a successful process kill, or a final audit write. Those steps can fail precisely when containment is needed. The distinction matters. — Table Data:
KILLING: An affected owned Job is not yet observed quiescent, a Job census failed, or a live server does not implement the current break-glass observation protocol. |RECONCILING: Quiescence and protocol coverage are established, but an unresolved file, destination, or model operation remains—or its registry cannot be read. - 3. Control Epochs Revoke Authority, Not Just Processes: Subtopics: Exhibit 8.4 — Scoped revocation map; WAL before snapshot; Exhibit 8.5 — Sanitized epoch-advance record — A latch closes new-effect gates immediately. Control epochs handle a different problem: authority that was minted before the stop must not remain usable after the relevant boundary advances. — Table Data: Resource lease; Carried lineage:
Lease.control_epoch; Recheck at the boundary:validate_tenancychecks expiry, current generation, and matching scope revision | Room wake job; Carried lineage: sealedcontrol_epoch; Recheck at the boundary: Dispatch re-derives task/Room/project standing and refuses revoked lineage | Result-grant receiving tenancy; Carried… — Items: Reads the current epoch and per-scope revisions. | Computesnext = prior + 1, refusing integer exhaustion. | Appends anepoch_advancerecord tobreakglass.wal.jsonland flushes it. | Atomically rewritesepoch.jsonwith the new sequence and scope map. - 4. Managed Drain and In-Doubt Recovery: Subtopics: Recovery starts with a census, not amnesia; Exhibit 8.6 — Recovery intent preserves uncertainty; Stop beats recovery on a race; Exhibit 8.7 — Racing stop leaves
FROZEN_SAFE— Immediate engage is not the only controlled-stop mode.drainsupports a bounded window in which already durably prepared effects may finish. — Items:unresolved_file_operations()for protected file writes without an established outcome; |destinations::unresolved_operations()for nonterminal destination mutations; |model_egress::unresolved()for brokered model requests whose provider-side outcome is unsettled. - 5. The Candidate-Binary Publication Gate: Subtopics: Exhibit 8.8 — Candidate qualification sequence; The complete 45-case inventory — Containment architecture is only as credible as the binary that implements it. A green build proves compilation. It does not prove that the release artifact refuses stale generations, impersonation, cross-project reads, altered proposals,… — Table Data: 1; Emitted case ID:
impersonation_refused; What must hold: A bound session cannot act as another owner. | 2; Emitted case ID:altered_proposal_conflict; What must hold: Reusing an operation ID with a different payload is refused. | 3; Emitted case ID:stale_generation_refused; What must hold: An edit fencing an old ownership generation is rejected. - 6. What the Gate Proves—and What It Cannot: Subtopics: Exhibit 8.9 — Publication summary shape — The release gate closes an important bootstrapping hole. The candidate carries its own inventory and enforcement code, the surface receipt binds the expected harness and target image hashes, and the source digest is checked before and… — Table Data: Rust
IsTerminal/ console handles; What it establishes: Whether standard handles belong to a terminal; What AINA adds—and refuses to infer: Combines terminal detection with no MCP session, explicit operator identity, and OS confinement; terminal presence alone is not human identity. - The Break-Glass & Conformance Qualification Challenge: The Break-Glass & Conformance Qualification Challenge uses one AI workflow that needs emergency containment or release qualification.
- The Fourteen Containment and Assurance Claims: Table Data:
08-C01; Claim: Any admitted caller can engage a validated stop with a mandatory reason; Evidence and ceiling: Implemented and author-verified for machine, agent, and canonical project scopes |08-C02; Claim: The active latch is persisted before secondary cleanup; scoped latches use staging and hard-link publication; Evidence and ceiling: Implemented and author-verified; machine latches use direct final-path creation |08-C03; Claim: Cleanup, epoch, WAL, or signal failures after latching do not roll back containment; Evidence and ceiling: Implemented and author-verified through warnings and engaged receipts |08-C04; Claim: Drain and recovery require no MCP session,… - The Article 08 Claim Card: Items: Mechanism: | AINA Sovereign Containment and Candidate-Binary Assurance | (latch-first break-glass, scoped control epochs, owned-Job observation, | in-doubt recovery, interactive owner recovery, 45-case publication gate) | Failure it governs: | Agents or scripts clearing their own emergency stop; | stale authority surviving after a matching stop; | successful termination calls mistaken for observed quiescence; | uncertain operations erased or blindly replayed during recovery; | stop/recovery races and unqualified…
- A Stop Is a Transition, Not a Button: Trustworthy emergency control is not a red icon that calls
kill(). It is a sequence with asymmetric authority: the latch appears before fallible cleanup; new effects close immediately; old scoped authority is refused; owned Jobs are… - Frequently Asked Questions: Subtopics: Why can any admitted caller engage the stop?; Can an agent clear its own emergency stop through MCP or a script?; Does advancing
control_epochrevoke every lease on the host?; Does recovery resolve operations whose outcomes are unknown?; What happens if another stop arrives during recovery?; Do the 45 passing cases certify the system independently? — Stopping is the safe direction. Requiring elevated recovery authority before containment would create a dangerous delay. Engage still requires admission, a nonempty reason, and a valid machine, agent, or project scope. No. - Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: [Article 07 — Defeating Approval Laundering: Act Pinning and Successor…
- Primary Platform References: Items: Microsoft
GetConsoleMode— console input and screen-buffer mode inspection | Ruststd::io::IsTerminal— terminal/TTY detection and platform behavior… - Publication Metadata: Title tag: The Sovereign Kill Switch: Break-Glass Epochs and the Conformance Gate Meta description: Asymmetric emergency containment, scoped control-epoch revocation, in-doubt recovery, managed Job termination, and the 45-case…
§09 — Bring One Real Boundary: Technical Peer Review, Challenge Tracks & R&D Evaluation
- URLs: 1-Call Brief (/09/brief/) · Full (/09-bring-one-real-boundary-work-with-blayne/) · Raw Markdown (/09.md) · Parts (8): P1 P2 P3 P4 P5 P6 P7 P8
- Thesis & Scope: Problem: Writing code by hand is no longer the bottleneck. The bottleneck is formalizing the trust boundary, decomposing work across parallel AI agents without context collapse, catching plausible-but-wrong outputs, and proving that invalid transitions fail closed. — Proves: AINA is both a deterministic execution-governance runtime (squad.exe) and Exhibit A of a repeatable 9-IDE multi-agent engineering methodology grounded in 11+ years of production systems delivery. — Scope: Independent Technical Peer Review · Research & Funding Due Diligence · Bounded Boundary Challenges.
- How to Peer-Review & Evaluate AINA: The 5-Step Architecture & Runtime Verification Protocol: Whether you are a systems engineer, a formal-verification or AI-security researcher, or a technical evaluator for a research funding body, AINA is designed to be inspected as an operational machine rather than a slide deck. — Items: Threat model & operational boundary definition: How cleanly does the architecture separate untrusted probabilistic proposals from privileged OS process creation, file handles, and relational database commits? | Bounded slice decomposition (preventing context collapse):…
- Why AINA Is Grounded in 11+ Years of Production Systems Engineering: Every invariant in AINA was shaped by real operational failure modes encountered over more than a decade of enterprise systems integration and data migration: — Table Data: **2025–2026: AINA & SquadForge (BlayneAina.com · GitHub)**; The messy operational problem: Parallel AI coding agents overwriting shared files, fabricating document citations, and executing unapproved mutations.; The deterministic system delivered: Directed a 9-IDE agent fleet to build a deterministic…
- 1. Choose the Boundary, Not the Buzzword: Three Technical Evaluation Tracks: Subtopics: Exhibit 9.1 — Three challenge tracks; Track 1 — AI Workflow Standing & Confinement; Track 2 — Zero-Trust Document, Citation & EISA Adjudication; Track 3 — Protected Computation & Entity Resolution — A useful technical evaluation or R&D pilot starts with one narrow question and a clear acceptance contract. Three technical tracks provide that entrance: Evidence-route key (
AINA-E01–E09): Each track maps to concrete verification routes established across the architecture series: Who it fits: CTOs, CISOs, principal architects, and platform… — Table Data: Candidate recall: Fraction of known duplicate pairs included in nominated candidate blocks | Candidate precision: Size and noise level of candidate blocks delivered to adjudication | False merges: Distinct entities incorrectly combined into a single partition | False splits: Records representing the same entity left separated without review | Adjudication outcomes: Proportion of records merged, kept separate, or held explicitly unresolved | Field provenance: Verification that every surviving canonical field cites its exact source record and pointer | Privacy boundary: Verification that raw identifiers remain local while external… — Items:AINA-E01— Semantic Switch structure-preserving fictionalization, relation-isomorphism verification, and exact local restoration (§01, §03). |AINA-E02— LPAC-confined parsing, explicit omission surfaces, committed views, server-cutev_citations, and bounded-absence gates (§02). - 2. Acceptance Is a Contract, Not a Demo Video: Subtopics: Exhibit 9.2 — Demonstration and acceptance-contract template; Minimum acceptance evidence by track; Exhibit 9.3 — Sanitized challenge intake example — Before an accepted run, both sides write down what would count as success, refusal, and uncertainty. This prevents a positive anecdote from becoming proof of a different claim. — Table Data: 1 — Workflow standing; Positive predicate: The approved row reaches exactly the approved values and version +1, or the guarded file result matches the fixed proposal.; Required refusal or rejection: A changed act, stale tenancy, or superseded generation is refused without overwriting current state.; Uncertainty that must survive: A crash between destination commit and…
- 3. What the First Challenge Does Not Buy: Written qualification precedes scheduling. The initial discussion requires no confidential data and no platform commitment, but it must identify the question, handling constraints, participants, and decision owner. — Items: custom input conversion, schemas, connectors, adapters, or action profiles; | production ingestion, integration, or write-back; | enterprise-wide rollout or a new vertical deployment; | relationship-graph construction, enrichment, or lead generation; | unrestricted source…
- 4. Deployment: Small-Sufficient and Client-Controlled: Subtopics: Exhibit 9.4 — From bounded challenge to controlled deployment — A qualified deployment does not need to clone the author's full fleet or depend on a mandatory vendor-hosted AINA cloud. The reference deployment shape is an AINA Portable Deployment Node: a dedicated client-controlled… — Table Data: 1. Existing Windows reference implementation; Delivered capability: Reference runtime; Engagement role: Runs the bounded Track 1, Track 2, or Track 3 challenge on controlled fixtures and produces inspectable receipts and refusal records. | ****2. — Items: Software portability means the qualified package can be provisioned in the declared environment. | Authority is not portable. A copied lease, grant, approval, or Room identity does not automatically become valid at the destination.
- 5. Operating Reality: Maintenance Is Part of the System: Subtopics: Exhibit 9.5 — Deployment and requalification checklist — A governed deployment changes with its environment. Connectors and IDE adapters evolve. Provider APIs deprecate fields. Parser updates create new extraction identities. Schemas and destination policies change.
- 6. The Commercial Wedge: Duplicates to Defensible Relationships: Subtopics: Exhibit 9.6 — From duplicates to distribution — Entity resolution is a strong first wedge because duplicate records are common, consequential, and evidence-rich. The problem is easy to describe and difficult to fake: which records represent the same entity, which values should survive,…
- Why an Enterprise Integrator Built AINA: 11+ Years in the Data Trenches Before AI: AINA was not designed in an academic vacuum. Before spending 14 months architecting AINA, I spent 11+ years embedded inside enterprise operations—building inbound and outbound HubSpot and Salesforce data pipelines and deduplication…
- 7. Operator Credibility: Delivery Is the Commercial Proof Point: The architecture is recent. The customer-embedded delivery career underneath it is not. My operational record across enterprise integration, data migration, and field execution includes: <aside class="context-callout author-profile"… — Items: 11+ years of customer-embedded technical delivery across integration, data migration, workflow automation, launch readiness, operator training, and live production issue resolution; | Enterprise catalog, ERP, and multi-location systems (Jacuzzi Colorado / Spa Palace):…
- 8. Regulatory and Standards Crosswalk—Not Certification: A deployment can produce technical evidence for a governance program without becoming compliant by acquisition. The use case, jurisdiction, organization, processing, and assessment route still have to be established by the responsible… — Table Data: NIST AI Risk Management Framework 1.0 (
AI 100-1, with ongoing revision context); Technical evidence AINA can contribute: MAP: sealed cases, source bindings, declared limits. MEASURE: acceptance predicates and candidate conformance. — Items: Author-developed benchmarks vs. NIST NCCoE standards: TheR1–R3operation-continuity method andP01–P10failure catalog referenced across this series are author-developed evaluation artifacts created inside AINA; they are not NIST-issued test suites. - 9. Engagement Routes—and a Firewall Around Independent Review: Subtopics: Exhibit 9.8 — Commercial work and independent review are separate — Different readers need different next steps. All begin with a written, bounded request to
me@blayneaina.com. The initial request should identify the technical track and evaluation or engagement type, participants and decision owner,… — Items:[RESEARCH]— request method-scoped independent technical peer review, submit adversarialEISA/RequestedActtest vectors, or propose formal-verification collaboration outside the commercial ladder. - 10. The Complete Machine, Now With an Address: Subtopics: Deployment & Evaluation Claim Card; Fourteen Claims for the Capstone — The eight architecture papers and this commercial doorway form one continuous route from probabilistic proposal to governed consequence. The point is not to make probability sovereign. — Table Data: 01 — An AI Output Is Not an Act: Standing must be established for one exact transition; model confidence is not authority. | 02 — Zero-Trust Ingestion & Server-Cut Evidence: Hostile sources become committed views with explicit omissions and citations the server…
- Bring the Boundary: Bring one AI-proposed mutation, one hostile document, or one duplicate-record problem. Include the operating owner, the handling constraints, and the question you need answered.
- Frequently Asked Questions: Subtopics: What should I bring to an initial challenge?; Does a challenge include production integration or CRM write-back?; Does a client-controlled node mean the whole system is offline?; Why is entity resolution the commercial wedge?; Does a paid pilot buy independent validation?; Do the regulatory mappings establish compliance? — Bring one bounded transition, its decision owner, an authorized synthetic/redacted/existing sample, handling constraints, and the positive and negative outcomes you need to evaluate.
- Continue the Series: Items: Series index: From Proposal to Consequence: The AINA Transition-Governance Series | Previous: Article 08 — The Sovereign Kill Switch: Break-Glass Epochs and the Conformance Gate | **Start at the…
- Primary Framework and Regulatory References: Items: NIST AI Risk Management Framework Core — GOVERN, MAP, MEASURE, MANAGE | NIST NCCoE — Software and AI Agent Identity and Authorization | [ISO/IEC 42001:2023 — AI management…
- Publication Metadata: Title tag: Bring One Real Boundary: Technical Peer Review, Challenge Tracks & R&D Evaluation | Blayne Aina Meta description: Evaluate the AINA architecture and reference runtime through three bounded technical challenge tracks,…
FAST 3-STEP SERIES DIGEST 3/3 — Digest 1 (§01–§03) · Digest 2 (§04–§06) · Digest 3 (§07–§09) · 1-Page Master Brief · All 9 Articles · Assurance · Proof