# EAO release-candidate acceptance replay

**Replay date:** 10 October 2026  
**Source:** EAO platform commit `fae743c2db30e19711439322a9f83c50c0c44370`  
**Runtime:** Node.js 24.21.0 on an authorized IgniteX Ubuntu development host  
**Result:** Repository acceptance passed

This is a fresh, reproducible check of one exact EAO source revision. It is engineering evidence from a synthetic reference environment. It is not a customer case study, hosted CI result, security certification, production deployment, performance result or business-outcome claim.

## Gates executed

| Gate | Observed result |
|---|---|
| Foundation validation | Passed. Syntax checked across 330 modules. The validator reported 516 architecture, boundary and contract-identity checks. |
| Full repository tests | Passed. 802 tests: 797 passed, 5 skipped, 0 failed. |
| Focused governance tests | Passed. 32 tests, 0 failed. |
| Synthetic reference UAT | Passed. Four mission scenarios and one cross-tenant denial check completed. |

The focused governance set exercised the user-and-agent permission intersection, cross-tenant and cross-environment denial, identity assurance, resource scope, classification ceilings, explicit deny, expiry, read-only defaults, write grants, exact approvals, approval replay prevention, audit evidence and fail-closed behavior.

## Reference mission evidence

The synthetic UAT produced these final states:

- L1 support mission: `RESOLVED`, 17 trace events.
- Coding mission: `WAITING_HUMAN_REVIEW`, 15 trace events. The agent could prepare a draft change but could not merge or deploy it.
- Admission-support mission: `COMPLETED`, 7 trace events after the required staff approval.
- Paper-review mission: `COMPLETED`, 15 trace events after teacher review and approval.

The UAT also denied a cross-tenant mission read. Trace verification passed across 54 events with head digest `sha256:7d888092aa41902f0cb2b4c83ba57ed1ef714e82180f49ba33e2a273ed3ec5d9`.

## Evidence file

- [Download the machine-readable acceptance report](./eao-v1-acceptance-fae743c-2026-10-10.json)
- SHA-256: `79e9ab687d97a27075f8cd920292bd41a30c3f5d87cf72bd94b03e02b842bb24`

The JSON preserves the exact candidate revision, timestamps, gate results, durations, test summaries and the source tool's limitation statement.

## Limits

Environment preflight and staging tests were not included. This replay does not establish deployment readiness for a named environment, connector readiness, model quality, workload performance, resilience, regulatory compliance or customer acceptance. Those checks need the actual target environment, representative data, operating owners and agreed acceptance criteria.