# §09: Bring One Real Boundary: Technical Peer Review, Challenge Tracks & R&D Evaluation
> Canonical: https://blayneaina.com/09-bring-one-real-boundary-work-with-blayne/ | 1-Call Brief: https://blayneaina.com/09/brief/ | Parts: 8
# Bring One Real Boundary: Technical Peer Review, Challenge Tracks & R&D Evaluation
*Evaluating AINA's deterministic execution-governance architecture through bounded acceptance contracts, reproducible refusal proofs, and independent research review.*
**By Blayne Aina · Principal Systems Architect and creator of AINA · October 31, 2026**
---
## 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.
Writing code by hand is no longer the primary bottleneck in systems engineering; the bottleneck is formalizing the trust boundary, decomposing work across parallel agents without context collapse, catching plausible-but-wrong outputs, and proving that invalid transitions fail closed without mutating target state.
**Researchers and technical evaluators can audit both the AINA architecture and the 9-IDE multi-agent methodology used to build it across five concrete dimensions:**
1. **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?
2. **Bounded slice decomposition (preventing context collapse):** How are complex specifications decomposed into independent, strictly typed work slices (`RequestedAct`, `EISA` envelopes, `LeaseDeclarations`) that parallel agent lanes can execute without corrupting shared state?
3. **Dependency, state & lease fencing:** How do monotonic generation tokens, Win32 share-mode exclusion (`FILE_SHARE_READ`), and SQLite optimistic concurrency (`WHERE version = expected`) stop stale workers at the resource?
4. **Adversarial & negative-path verification:** Plausible code and JSON can pass superficial checks while hiding TOCTOU races, silent data drops, or approval laundering. Every AINA mechanism is tested against adversarial fault classes (`requested_act_mismatch`, `stale_lease_generation`, `evidence_bad_selector_refused`).
5. **Deterministic verification & refusal proof (`PCNA`):** Every refused transition emits a tamper-evident receipt binding the RFC 8785 JCS-canonicalized proposal to byte-identical pre-attempt and post-refusal destination SHA-256 digests (`python3 proof/verify_refusal_proof.py`).
**Plus a 15–45 minute live `squad.exe` runtime evaluation:** Alongside the static public proof bundle, I conduct live technical screen-share sessions for peer reviewers and R&D grant evaluators—running `squad.exe` against ad-hoc transitions, demonstrating `requested_act_mismatch` and `stale_lease_generation` refusals live, and walking openly through the Rust crate architecture, formal tradeoffs, and the proposed Linux/POSIX and Lean 4 research roadmap.
The eight architecture papers ([§01](/01-an-ai-output-is-not-an-act/) through [§08](/08-sovereign-kill-switch-break-glass-epochs-and-conformance-gate/)) are the technical specifications for that evaluation: per-transition standing, sealed evidence, protected computation and deterministic EISA adjudication, Room coordination, fenced ownership, forensic recovery, act pinning, crash continuity, emergency containment, and candidate-binary qualification.
## 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:
| Era & environment | The messy operational problem | The deterministic system delivered |
| :--- | :--- | :--- |
| **2025–2026: AINA & SquadForge** ([BlayneAina.com](https://blayneaina.com/) · [GitHub](https://github.com/SquadForge/blayne.aina)) | Parallel AI coding agents overwriting shared files, fabricating document citations, and executing unapproved mutations. | Directed a 9-IDE agent fleet to build a deterministic governance runtime (`squad.exe`), Four-Gate EISA state machine, kernel file fencing, and 45-case conformance gate ([refusal proof](/refusal-proof/)). |
| **2022–2025: Agile Education Marketing** (enterprise EdTech data & CRM) | High-volume multi-source education datasets with duplicate records, schema drift, and synchronization failures between HubSpot and Salesforce. | Architected automated ETL/ELT validation pipelines, Insycle deduplication recipes, and bi-directional HubSpot/Salesforce lifecycle workflows. |
| **2019–2022: TCompanies—DrayMaster & Photector** (intermodal logistics & evidence) | Six years of fragmented data across seven companies and **800+ intermodal logistics carriers** at DrayMaster (acquired by Envase), plus unverified carrier photo workflows at Photector (integrated with Hirschbach TMS). | Migrated six years of carrier data into a custom CRM with conditional onboarding forms and facilitated daily whiteboarding to define deterministic stage-gate state machines for Photector. |
| **2015–2018: Jacuzzi Colorado / Spa Palace** (multi-location retail & ERP) | Six locations operating legacy point-of-sale and fragmented infrastructure with 15,000+ disconnected product SKUs. | Executed the six-location infrastructure cutover, migrated 15,000+ SKUs, built a centralized Drupal intranet, and integrated custom mobile apps with Vonage, HubSpot, and QuickBooks POS. |
## 1. Choose the Boundary, Not the Buzzword: Three Technical Evaluation Tracks
A useful technical evaluation or R&D pilot starts with one narrow question and a clear acceptance contract. Three technical tracks provide that entrance:
### Exhibit 9.1 — Three challenge tracks
```text
TRACK 1: AI WORKFLOW STANDING & CONFINEMENT
one AI-proposed file or SQLite mutation
→ wake authority → typed lease → guarded write → RequestedAct
→ fenced execution → original/successor receipt → break-glass
evidence route: AINA-E05–E07 · Articles 01, 04–08
TRACK 2: ZERO-TRUST DOCUMENT, CITATION & EISA ADJUDICATION
one hostile document, evidence-heavy workflow, or diagram relation
→ confined parsing → explicit omissions → immutable views
→ server-cut citations → bounded absence → deterministic EISA verdict
evidence route: AINA-E02–E04 · Articles 02–03
TRACK 3: PROTECTED COMPUTATION & ENTITY RESOLUTION
one bounded contact, company, product, or other duplicate-record problem
→ Semantic Switch → qBlock / Qdrant Edge → EISA Fracture
→ EISA Forge → local exact restoration → Shield
evidence route: AINA-E01, E03, E04, E08, E09 · Article 03
```
**Evidence-route key (`AINA-E01`–`E09`):** Each track maps to concrete verification routes established across the architecture series:
- `AINA-E01` — Semantic Switch structure-preserving fictionalization, relation-isomorphism verification, and exact local restoration ([§01](/01-an-ai-output-is-not-an-act/), [§03](/03-eisa-four-gate-verdict-machine-and-entity-resolution/)).
- `AINA-E02` — LPAC-confined parsing, explicit omission surfaces, committed views, server-cut `ev_` citations, and bounded-absence gates ([§02](/02-zero-trust-document-ingestion-and-server-cut-evidence/)).
- `AINA-E03` — EISA strict parsing, sealed cases, record-relative RFC 6901 pointers, and Four-Gate deterministic adjudication ([§03](/03-eisa-four-gate-verdict-machine-and-entity-resolution/)).
- `AINA-E04` — Parser-committed PDF integer geometry (`CONNECTS`) and EISA Fracture/Forge partition and field-provenance compilation ([§03](/03-eisa-four-gate-verdict-machine-and-entity-resolution/)).
- `AINA-E05` — Room authority, sealed wake envelopes, typed leases, monotonic generations, and kernel write exclusion ([§04](/04-the-room-why-git-and-chat-are-not-coordination-planes/), [§05](/05-expiry-is-not-fencing-typed-leases-and-kernel-write-exclusion/)).
- `AINA-E06` — Dual-tier vault recovery (Primary and Amber) and ungated-divergence quarantine ([§06](/06-rollback-is-not-erasure-dual-tier-vaults-and-ungated-quarantine/)).
- `AINA-E07` — Controller-fixed `RequestedAct`, fenced SQLite execution, honest original-versus-successor receipts (`satisfies_original_return: false`), break-glass epochs, and the 45-case conformance gate ([§07](/07-defeating-approval-laundering-act-pinning-and-successor-grants/), [§08](/08-sovereign-kill-switch-break-glass-epochs-and-conformance-gate/)).
- `AINA-E08` & `AINA-E09` — Authenticated `release_inventory` verification (`SS08`) and Shield forward-only (`DEFLECT`, `GROWTH`, `ESCALATE`) baseline defense ([§03](/03-eisa-four-gate-verdict-machine-and-entity-resolution/)).
### Track 1 — AI Workflow Standing & Confinement
**Who it fits:** CTOs, CISOs, principal architects, and platform owners running coding, operational, or database agents whose authority currently depends on tool schemas, advisory locks, Git branches, or a green tool result.
**The asset:** one AI-proposed file or SQLite mutation that can be reproduced in a controlled fixture.
**The demonstration:** sealed wake authority, current typed tenancy, monotonic generation fencing, guarded file replacement, a controller-fixed `RequestedAct`, fenced SQLite execution, recovery evidence, original-versus-successor receipt handling, and scoped break-glass behavior.
**The boundary:** the Windows reference path and declared destinations. The challenge does not grant production write authority, claim universal adapter or operating-system coverage, promise exactly-once external effects, or turn author-controlled evidence into independent validation.
### Track 2 — Zero-Trust Document, Citation & EISA Adjudication
**Who it fits:** legal, compliance, finance, research, and engineering teams ingesting untrusted documents, evidence-heavy material, or spatial diagrams.
**The asset:** one hostile or contentious document, one bounded evidence question, or one diagram connection claim with an authorized source.
**The demonstration:** LPAC-confined parsing, explicit omission and failure surfaces, immutable canonical views, server-cut `ev_` citations, bounded absence claims with acknowledged gaps, and a sealed EISA case judged by deterministic gates.
**The boundary:** declared formats and extraction profiles. A citation proves what the server served from a committed view; it does not prove that the source is true. The track does not claim complete-document comprehension, universal format support, absence without acknowledged gaps, or legal interpretation as a warranty.
### Track 3 — Protected Computation & Entity Resolution
**Who it fits:** enterprise data, RevOps, CRM, product-data, and integration leaders with duplicate contacts, companies, products, confidential identifiers, fragmented hierarchies, or unsupported canonical values.
**The asset:** one bounded contact, company, product, or other duplicate-record problem, or access to an existing replayable run. Initial scoping can use synthetic, redacted, or already authorized data; confidential production data is not required to start the conversation.
**The demonstration:** the privacy-first pipeline and its local return path:
- **Semantic Switch** transforms native values into structure-preserving fictional records before any provider-exposed computation. Native rows, keys, and the private crosswalk remain under client control.
- **qBlock / Qdrant Edge** consumes the protected records and nominates candidate blocks without declaring identity.
- **EISA Fracture** adjudicates those candidate partitions with explicit support, counterevidence, and preserved dissent.
- **EISA Forge** compiles canonical fields with source provenance rather than treating identity equivalence as permission to merge.
- **Local exact restoration** maps authorized field-source references back to native values through the private crosswalk; no model reproduces the originals.
- **Shield** handles later records through forward-only `DEFLECT`, `GROWTH`, or `ESCALATE` dispositions without rewriting the sealed baseline.
Semantic Switch is an experimental alpha relational-confinement module. The retained synthetic executions account for 2,750 inputs, 50 complete blocks, 2,704 fictionalized records, and 27,040 exact original-field restorations. Relation-isomorphism verification adds 20/20 relabeling-invariance blocks, 23/23 exact native edit relations, 53/53 records and 529/529 field values verified per run, 14/14 batch cases, and 10/10 transformation cases. These measurements establish **transport and relation fidelity on declared synthetic fixtures**—not population matching accuracy, anonymity, successful production merges, universal tokenizer preservation, or independent validation.
When evaluating entity resolution on a prospective customer's admitted dataset during a scoped pilot, transport fidelity is paired with explicit **matching-quality acceptance criteria**:
| Evaluation dimension | What a pilot measures |
|---|---|
| **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 computation receives only protected fictional records |
**The boundary:** an existing implementation profile and acceptance run. The initial challenge excludes custom schema engineering, production CRM ingestion or write-back, lead-list generation, enterprise graph construction, and universal privacy or matching-accuracy claims.
Physical actuation, defense systems, and other high-consequence control surfaces do not enter a general-purpose focused challenge. They require separately scoped diligence and an environment appropriate to the consequence class.
## 2. Acceptance Is a Contract, Not a Demo Video
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.
### Exhibit 9.2 — Demonstration and acceptance-contract template
```text
1. ENGAGEMENT AND DECISION OWNER
Track, participants, technical owner, business decision owner, and authority to proceed.
2. ADMITTED INPUTS, PROVENANCE, AND HANDLING
Synthetic/redacted/customer-supplied asset; who created the fixture and established expected
positive, refusal, and unresolved outcomes before execution; source classification;
permitted location; retention, network, credential, redaction, and return constraints.
3. EXACT TRANSITION
Starting state → proposed act → governed execution or adjudication → terminal result.
Name the implementation profile, destination, and evidence boundary.
4. PREDECLARED POSITIVE PREDICATES
Observable conditions that must hold, such as exact readback, complete input accounting,
expected citation resolution, or a forward-only baseline disposition.
5. PREDECLARED REFUSAL PREDICATES
Hostile or stale cases that must fail, the expected typed refusal where applicable,
and the destination state that must remain unchanged.
6. UNRESOLVED STATES TO PRESERVE
Conditions that must remain in-doubt, carried forward, quarantined, or non-operative
rather than being forced into success or failure.
7. ARTIFACTS RETURNED
Agreed manifests, replay identifiers, receipts, view/case digests, refusal records,
and any permitted recovery or conformance evidence, with redaction rules.
8. OPERATING BURDEN
Latency, storage, availability, refusal, recovery, operator-load, and requalification
observations relevant to this profile.
9. ACCEPTANCE RESULT AND CLAIM CEILING
Satisfied / Failed / Unsupported / Not exercised / Inconclusive for each predicate;
author-controlled vs. customer-supplied fixture provenance; explicit exclusions and owner duties.
10. NEXT DECISION
Stop, narrow, repeat under the same scope, commission a paid pilot, or seek
independent evaluation. No automatic production expansion.
```
This is an engineering acceptance template, not a claim that a demonstration is a legal service-level agreement or independent audit. Recording **fixture and ground-truth provenance** before execution ensures a reviewer can distinguish an author-constructed benchmark from a customer-blind test set and verify that expected results were fixed prior to the run. The returned artifacts are digest-linked and inspectable; a SHA-256 digest is not represented as a digital signature.
A failed predicate remains failed. An unresolved effect remains unresolved. A system that refuses every legitimate call has not passed a useful security test, so the contract includes both the permitted positive path and the hostile negative path.
### Minimum acceptance evidence by track
The generic contract becomes concrete before execution. The exact predicates are tailored to the admitted fixture, but a non-vacuous starting matrix is:
| Track | Positive predicate | Required refusal or rejection | Uncertainty that must survive | Minimum agreed evidence |
|---|---|---|---|---|
| **1 — Workflow standing** | The approved row reaches exactly the approved values and version +1, or the guarded file result matches the fixed proposal. | A changed act, stale tenancy, or superseded generation is refused without overwriting current state. | A crash between destination commit and receipt remains in doubt; a successor does not fabricate the original return. | `RequestedAct` digest, tenancy/generation evidence, recovery capture, exact readback, operation and reconciliation receipts. |
| **2 — Evidence and EISA** | Each citation resolves to its intended committed node and repeated evaluation preserves the expected verdict identity. | Drift, view tamper, invalid selectors, and false typed predicates receive their declared refusals. | Omissions and unknown coverage block unsupported absence; dissent and non-operative acts remain visible. | Source/view/case digests, omission inventory, served-content receipts, `ev_` handles, EISA submission and verdict records. |
| **3 — Entity resolution** | Every input is accounted for; an accepted replay restores the selected original fields exactly; later dispositions remain forward-only. | Altered release inventory, incomplete partitions, and unsupported field selections are rejected. | Unresolved records remain unresolved; candidate nomination is not identity proof and a graph path is not authorization. | Block manifests, release inventory, input/restoration counts, EISA lineage, canonical-field provenance, and Shield dispositions. |
These are **candidate predicates for scoping**, not a promise that every artifact applies to every run. The accepted contract names the actual subset and adds any profile-specific condition before the fixture executes.
**Technical acceptance is not a business-value measurement.** A fenced write does not prove revenue impact, and exact fictionalized transport does not prove matching accuracy. If a pilot has a commercial objective, write a separate value contract: baseline, metric and formula, population and observation window, data owner, decision threshold, and measurement owner. Without a baseline, the result is **Not measured**, not an inferred return on investment.
### Exhibit 9.3 — Sanitized challenge intake example
```text
To: me@blayneaina.com
Subject: [CHALLENGE] Track 1 — Fenced SQLite mutation
Participants: platform architect, security owner, workflow owner
Decision owner: VP of platform engineering
Bounded question:
Can a proposed single-row update be fixed before worker launch, rejected when
the approved payload or tenancy changes, and observed exactly once before commit?
Sample and handling:
One synthetic SQLite fixture and a declared row/version pair.
Run in a client-controlled Windows reference environment.
No production credentials, customer data, or external destination.
Requested evidence:
RequestedAct digest, changed-payload refusal, stale-tenancy refusal,
pre-commit readback, and the operation/reconciliation receipt.
Initial exclusions:
No production write authority, custom connector, external exactly-once claim,
enterprise rollout, or independent-validation claim.
```
## 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.
A focused commercial challenge covers only the accepted existing path, preparation, operation, and explanation named in the written scope. It does not silently include:
- 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 access, repository transfer, or protected-material disclosure;
- independent validation, endorsement, praise, or a guaranteed conclusion.
Those are separate scopes. Customization and deployment belong to a paid pilot or implementation mandate. Independent evaluation follows the separate research route described below.
The article and ebook remain free. Commercial sessions, implementation, customization, deployment, and support are paid and privately scoped after qualification. There is no public fixed-price or fixed-duration promise because the admitted surfaces and acceptance obligations determine the work. Payment never purchases proof, an evidence-status upgrade, a favorable finding, or outcome control.
A commercial case record may remain confidential. If both sides agree in advance to publish a redacted, method-scoped record, it can report a positive, negative, refused, or unresolved result. Permission to publish is not a testimonial or endorsement.
**Evidence availability and measurement boundary:** implementation artifacts, accepted challenge packets, and supporting delivery records are `CONTROLLED` for qualified, method-scoped review, subject to source, customer, credential, and confidentiality limits. They are not unrestricted public downloads or independent validation. Latency, throughput, storage, availability, operator load, matching quality, and business value must be measured on the admitted profile; this article promises no universal performance envelope or return on investment.
## 4. Deployment: Small-Sufficient and Client-Controlled
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 small-form-factor computer or an on-site Windows reference environment, provisioned for the admitted transition.
Deployment is organized as four capability layers:
| Deployment layer | Delivered capability | Engagement role |
|---|---|---|
| **1. Existing Windows reference implementation** | **Reference runtime** | Runs the bounded Track 1, Track 2, or Track 3 challenge on controlled fixtures and produces inspectable receipts and refusal records. |
| **2. Repeatable deployment & qualification procedure** | **Release qualification** | Defines how a candidate binary, local ledger, and destination plan are provisioned, rebound, and checked against the 45-case conformance gate. |
| **3. Customer-provisioned Portable Deployment Node** | **Customer-controlled profile** | Adapts the smallest-sufficient reference profile to a specific customer's admitted hardware or VM, credentials, schemas, and target workflows. |
| **4. Supported customer-operated lifecycle** | **Operating lifecycle** | Establishes ongoing monitoring, connector-drift handling, `rsa_` reassessment workflows, and client-operated, founder-supported, or joint operations. |
There is no universal hardware specification. The smallest-sufficient profile follows the workload, evidence retention, provider dependencies, and consequence surface.
### Exhibit 9.4 — From bounded challenge to controlled deployment
```text
qualified asset and acceptance contract
→ existing-path demonstration and inspectable result
→ separately scoped paid pilot
local dependency and credential rebinding
smallest-sufficient IDEs, providers, schemas, workflows, and destinations
affected-path replay and acceptance evidence
→ client-controlled Portable Deployment Node or on-site environment
launch + local bindings + retained receipts + operating handoff
→ client-operated, founder-supported, or joint-support lifecycle
→ optional vertical package or distribution agreement
```
The destination profile includes only admitted IDEs, subscriptions, APIs, local models, schemas, workflows, and consequence surfaces. Credentials, authority, targets, and effect paths are rebound for the destination. Controller-brokered model access keeps provider credentials outside the worker, while local state and artifacts remain under the client's custody.
Portability is deliberately bounded:
- **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.
- **State currency is not portable.** Local ledgers, generations, source views, and unresolved operations must be rebound and verified.
- **Network independence is not automatic.** Local execution can avoid a vendor-hosted AINA cloud, but an external model or destination still requires its declared provider route and terms.
- **Effect coverage is not portable.** Every new destination and alternate mutation path requires its own admission and evidence.
Deployment completion is not the arrival of files or the passage of a day. It means launch, local dependency binding, satisfaction of the written acceptance predicates, retained receipts, declared exclusions, and an operating owner. A narrow node may be brought up during a concentrated on-site engagement; there is no universal one-day deployment claim.
## 5. Operating Reality: Maintenance Is Part of the System
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. New source views can require reassessment of earlier findings.
The operating model therefore includes monitoring, staging, affected-path replay, and requalification—not silent auto-upgrade.
### Exhibit 9.5 — Deployment and requalification checklist
```text
[ ] Destination authority, credentials, targets, and project roots rebound
[ ] Admitted model/provider routes and external dependencies declared
[ ] Source revisions, parser profiles, and view supersession rules recorded
[ ] Reassessment flags (`rsa_`) assigned to affected dependent findings/tasks
[ ] Connector/schema changes reflected in versioned destination plans
[ ] Alternate effect paths and new consequence surfaces admitted or excluded
[ ] Positive, refusal, unresolved, and recovery predicates replayed
[ ] Candidate source/image identity verified and 45-case gate passed before promotion
[ ] Latency, storage, availability, refusal, recovery, and operator load observed
[ ] Receipts, unresolved operations, exclusions, and recovery duties handed to an owner
[ ] Support model selected: client-operated, founder-supported, or joint
```
A source or requirement revision does not launder an old conclusion into a new context. Evidence-linked `rsa_` flags keep dependent findings and tasks marked for reassessment. A new parser identity creates a new view; historical handles remain tied to their historical view. Runtime changes require the candidate-binary publication gate again.
The client's responsibilities remain explicit: credential and key custody, protected local storage, provider entitlements, backup and retention policy, destination authorization, operating escalation, and any organizational control outside the software. Support can be client-operated, founder-supported, or joint, but it is not maintenance-free.
## 6. The Commercial Wedge: Duplicates to Defensible Relationships
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, and what evidence justifies each decision?
The commercial expansion follows a disciplined chain.
### Exhibit 9.6 — From duplicates to distribution
```text
duplicate records
→ defensible identity substrate
→ canonical values with field-level provenance
→ evidence-linked relationships
→ inspectable graph paths
→ authorized read-only vertical pilot
→ repeatable vertical package
→ deployment, distribution, and principal mandates
```
The wedge is not generic “AI safety.” It is **entity resolution and evidence-linked state**. A resolved contact or company becomes more useful when deals, activities, tickets, addresses, parent organizations, and other associations can retain their provenance. HubSpot is one concrete CRM topology; Salesforce, Dynamics, NetSuite, and custom systems may present different authorized schemas and are not assumed to be identical.
An evidence-linked relationship graph retains source coordinates, relation type, scope, freshness, authority, and status for its nodes and edges. Unsupported paths remain candidate or unresolved. A configured search may include six-hop paths, but six hops are a **query horizon**, not proof of familiarity, influence, willingness to introduce, consent, or business value.
A graph path does not authorize outreach, disclosure, enrichment, mutation, or a CRM write. Those require separate authority and, where applicable, a controller-fixed destination act. Production graph ingestion and lead generation are separately paid scopes, not gifts hidden inside the initial challenge.
This creates a credible distribution path. A founding deployment partner can fund vertical customization. A distribution partner can contribute domain knowledge, qualified client access, and a repeatable channel. Neither label means sponsor, equity cofounder, or independent validator. Licensing, exclusivity, revenue sharing, support, data responsibility, and runtime rights require separate agreements.
The architectural differentiator is the common transition grammar—the layer that compiles organizational authority into per-transition technical standing so that evidence, actor, act, target, execution, effect, and closure remain bound even as model providers and adapters rotate. Client-controlled Windows execution is a differentiated deployment niche, not a claim that other platforms or a conventional composition cannot achieve equivalent properties. A mature stack that demonstrates the same bindings and failure behavior earns functional credit.
## 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 workflows at Agile Education Marketing (2022–2025), migrating six years of operational data across seven operating companies and **800+ intermodal transportation, logistics, and supply chain carriers** for DrayMaster's intermodal drayage rate-management and carrier-onboarding platform (2019–2022), designing deterministic stage-gate state machines for photographic evidence capture at Photector, and migrating six retail/distribution locations and 15,000+ SKUs from legacy ecommerce infrastructure at Jacuzzi Colorado (2015–2018).
At Photector, I facilitated daily architectural whiteboarding sessions with a distributed team to define edge-case scenario criteria and deterministic state-machine workflows for a patent-pending blockchain photographic evidence application. That work was workflow and scenario architecture, not a claim of authorship over Photector's patent.
Every mechanism in AINA—from server-cut provenance to lease fencing and quarantine vaults—exists because I have seen firsthand how unverified merges, race conditions, and silent rollbacks corrupt production enterprise databases.
## 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:
- **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):** systems and catalog architecture supporting **six retail/distribution locations and more than 15,000 products**;
- **Multi-entity logistics & CRM migration (TCompanies / DrayMaster):** migration, carrier compliance, and CRM/onboarding consolidation involving **800+ intermodal transportation, logistics, and supply chain carriers across a seven-business group**, encompassing six years of operating data;
- **Cross-platform enterprise integration:** hands-on implementation across **HubSpot, Salesforce, Microsoft Dynamics, NetSuite, Marketo, Zoho**, operational SQL databases, warehouses, and custom applications;
- **700+ production digital deliverables:** websites, applications, databases, ecommerce properties, and automation workflows delivered through independent practices, alongside **technology and marketing teams trained across 13 U.S. states**; and
- **U.S. Marine Corps service:** **Combat Correspondent, Photojournalist, and Northern Bureau Chief**, coordinating field reporting and public-affairs operations across Northern Okinawa under strict evidentiary discipline.
That operational history matters for technical due diligence and R&D execution because the hardest part of systems governance is rarely writing a conceptual whitepaper. It is identifying field ownership, resolving conflicting records, defining deterministic state transitions, enforcing pre/post state invariance, and making the system operable under real failure conditions.
It is not independent validation of AINA. AINA is founder-led and self-funded research and development, with work beginning in August 2025. AI-assisted coding and critique have contributed to the development process; I retain responsibility for the architecture, implementation integration, technical review, validation, and release decisions. Solo authorship establishes accountability and provenance, not production separation of duties.
All background provisional filings and implementation artifacts are documented with explicit claim ceilings so research evaluators, peer reviewers, and pilot partners can inspect exactly what has been demonstrated and what remains proposed research.
## 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 owners and their advisers.
Two explicit boundary notes govern how this crosswalk is read:
1. **Author-developed benchmarks vs. NIST NCCoE standards:** The `R1`–`R3` operation-continuity method and `P01`–`P10` failure catalog referenced across this series are **author-developed evaluation artifacts created inside AINA**; they are not NIST-issued test suites. They are mapped as engineering comparison points alongside the NIST NCCoE February 2026 concept paper (*Accelerating the Adoption of Software and AI Agent Identity and Authorization*) and emerging standards work (`Transaction Tokens`, `OAuth identity chaining`, `SSF/CAEP`, `AuthZEN`, and `SCITT`).
2. **Adjacent banking guidance (`SR 26-2` Scope Note 3):** The Federal Reserve, FDIC, and OCC interagency guidance on model risk management (`SR 26-2`, April 17, 2026) is primarily relevant to banking organizations with $30 billion or more in assets, and **Scope Note 3 explicitly excludes generative and agentic AI models** from its traditional quantitative scope. It appears below as adjacent governance context for financial institutions designing internal transition controls—not as a prescriptive agentic standard or banking certification.
Exhibit 9.7 — Engineering crosswalk and residual organizational duties (click to collapse/expand)
| Framework or instrument | Technical evidence AINA can contribute | What remains outside the software artifact |
|---|---|---|
| **NIST AI Risk Management Framework 1.0 (`AI 100-1`, with ongoing revision context)** | MAP: sealed cases, source bindings, declared limits. MEASURE: acceptance predicates and candidate conformance. MANAGE: refusals, quarantine, recovery, and break-glass. | GOVERN and the voluntary framework as a whole: organizational accountability, risk decisions, policies, review procedures, and authority to act. NIST AI RMF 1.0 is voluntary (and undergoing revision for generative/agentic systems); this is not certification. |
| **NIST NCCoE agent identity concept paper (Feb 2026) & adjacent standards** | AINA's author-developed `R1`–`R3` continuity method and `P01`–`P10` failure catalog evaluate operation continuity, scope limits, and accepted-population accounting. Transaction Tokens, OAuth identity chaining, SSF/CAEP, AuthZEN, and SCITT serve as architectural comparison points. | `R1`–`R3` and `P01`–`P10` are AINA internal methods; NIST did not commission, approve, or endorse the method or runs. Draft and final specifications have different maturities; no complete standards-stack claim follows. |
| **ISO/IEC 42001:2023** | Implementation records, acceptance results, limitations, change evidence, and operating procedures can contribute evidence to an AI management system. | ISO/IEC 42001 specifies requirements for establishing, operating, and continually improving an organization's management system. AINA does not establish or certify that system. |
| **EU AI Act, Articles 11, 12, and 43** | Source/version bindings, technical documentation inputs, event and decision logs, validation results, and limitations may support Article 11 documentation and Article 12 record-keeping for an applicable high-risk system. | Use-case classification, provider/deployer duties, jurisdiction, and the Article 43 conformity-assessment route are separate. Logs are not “turnkey compliance.” |
| **UK Data (Use and Access) Act 2025, Section 80** | Decision explanations, evidence links, intervention and escalation routes, and contestable records can support safeguards under UK GDPR Articles 22A–22D. | The controller must determine meaningful human involvement, significant decisions, restrictions, and safeguards. Article 22C includes information, representations, human intervention, and contest rights; technical receipts alone do not satisfy them. |
| **Federal Reserve SR 26-2 and interagency MRM guidance (adjacent context)** | Transition evidence, acceptance results, inventory, monitoring, and independent-review boundaries can inform an institution's chosen internal controls for agentic workflows. | Expected to be most relevant to banking organizations over $30B, and **Scope Note 3 excludes generative and agentic AI models**. Does not set enforceable standards for agentic AI; the institution determines appropriate governance. AINA claims no banking certification. |
| **AICPA SOC 2** | Access boundaries, change records, availability/recovery evidence, and processing-integrity receipts may support an agreed examination scope. | A SOC 2 report requires a CPA examination of service-organization controls and, where relevant, operation over an examination period. Application receipts are not a SOC 2 report. |
| **Data protection impact assessment (DPIA)** | Data-flow maps, minimization choices, local-custody boundaries, retention rules, access records, and residual-disclosure documentation supply assessment inputs. | The controller determines whether processing is likely to create high risk and completes the DPIA before such processing. Integrity checks and fictionalization do not decide necessity or eliminate risk. |
RequestedAct before the worker environment exists. The worker is spawned suspended inside a restricted Job Object; the pre-resume audit observes its token, image and handle inventory before instruction 0. requested_act::validate re-resolves current task, source, tenancy, destination and act identity at execution. A mismatch such as requested_act_mismatch or an unclassified pre-resume capability fails closed; no resume or destination mutation occurs.
Proof: §07 Act Pinning · actual refused-substitution receipt and unchanged SQLite digest
FILE_SHARE_READ and without write/delete sharing. If another process already holds a compatible writable handle, the kernel rejects the coordinator's open with ERROR_SHARING_VIOLATION (os error 32). Acquisition fails closed, no generation token is issued, and the territory remains contested until the foreign handles are closed and the baseline is re-verified. The gate does not pretend that a clock expiry revoked a handle the OS still holds open.
Proof: §05 Kernel Write Exclusion · os_lock_conflict in leases/oshandle.rs
UPDATE ... WHERE version = expected. A drift produces preimage_hash_mismatch or record_version_changed rather than an overwrite. Where candidate file bytes exist, divergence is preserved for forensic review rather than silently laundering it into a clean baseline. Quarantine is mechanism-specific, not a claim that every refused API call creates Amber bytes.
Proof: §03 Deterministic judgment · §05 fencing · §07 fenced SQLite
result_read_only grant to inspect the historical outcome after its tenancy, grant, source, delivery, and receipt bindings validate. The successor does not re-execute the mutation and does not fabricate the original worker's first receipt: satisfies_original_return: false and resolves_original_obligation: false.
Proof: §07 crash continuity and successor grants · result_grant_* refusal family
Proof: §03 production EISA core and alpha module · synthetic invariance testbed
Proof: published fixtures, harnesses, and alpha claim ceiling
Proof: §01 machine standing · §06 forensic history · public refusal exhibit
Proof: fresh execution timing and candidate attestation · §08 assurance boundary
Proof: this deployment boundary · local candidate evidence and its stated ceiling
The smallest practical enterprise deployment is a single CRM/database mutation gate wrapping §01 (proposal versus act), §03 (deterministic EISA checks), and §06 (pre-image and forensic vaulting). An existing model or subagent interacting with HubSpot, Salesforce, SQLite, or another relational store is placed behind one MCP tool boundary. The gate validates the controller-fixed RequestedAct, checks optimistic row versions, journals the pre-attempt state, and requires unapproved substitutions to fail closed with zero database effects. The whole nine-module architecture is not a prerequisite.
Proof: §01 output boundary · §06 dual-tier recovery · Case C SQLite refusal proof
Operational gate latency and full-lifecycle test duration are different measurements:
<5 ms figure is claimed.Proof: binary composition and timing note · candidate attestation
AINA keeps enterprise delivery history separate from the unified reference runtime:
squad.exe Windows NT supervisor, the 45-case conformance battery, and the refusal receipts were engineered during 14 months of independent work on a single workstation. They are not represented as a unified external customer production deployment.Proof: this production boundary · offline verification bundle
Verification has two tiers:
aina-refusal-proof-pack-v1.zip and run python verify_refusal_proof.py locally without internet access to audit all four refusal records, 12 schemas, and the 45-case manifest against published SHA-256 digests.Proof: Refusal proof pack · Schedule a live boundary walkthrough (me@blayneaina.com)