§09 PART 3/8 (12,535 chars · Sections: 2. Acceptance Is a Contract, Not a Demo Video; 3. What the First Challenge Does Not Buy; 4. Deployment: Small-Sufficient and Client-Controlled) — ← Part 2 · Part 4 → · 1-Call Brief · Full §09 · Raw .txt · All: P1 P2 P3 P4 P5 P6 P7 P8
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
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
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
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.
END OF §09 PART 3/8 — Next: https://blayneaina.com/09-bring-one-real-boundary-work-with-blayne/part-4/ · §09 1-Call Brief · Raw .md