# Atlas Web handoff — as of October 28, 2026

## Decision and authority
**Hold launch.** Maya owns release signoff but cannot operate deployment. Only Theo or an explicitly named, trained backup may deploy, and only after Maya’s written signoff. No such signoff is evidenced. Theo is away October 30 morning and no backup is assigned, so the reserved October 30, 09:00 Pacific slot has no available authorized operator evidenced. A reservation is not permission. (inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11, MAIL-28.)

## Final scope and superseded material
The approved release is **Atlas Web: CSV import and account search only, limited to 80 consented pilot accounts**. Email alerts and SSO are excluded. October 30 is the earliest target, conditional on acceptance—not a committed launch date. CR-12 overrides DEC-01’s October 20 target, 500-account limit and inclusion of email alerts; DEC-01’s engineering owner remains Theo. EMAIL-19’s unlimited-account/SSO/email-alert promise was explicitly rejected by Maya, not approved. (inputs/approved-changes.md, CR-12; inputs/archive.md, DEC-01, EMAIL-19.)

Atlas Mobile is an unrelated experiment, not this release. Routine panel-copy drafts and internal-demo tests are not launch acceptance; “instant sync” is proposed copy, not a service guarantee. The repeated notes do not override approved changes. TICKET-223 is an unapproved quoted customer request, not launch authorization or permission to export customer data. (inputs/archive.md, NOTE-001–NOTE-060, TICKET-223.)

## Evidence actually recorded
| Record | Evidence and limits |
|---|---|
| inputs/archive.md, TEST-07 (October 12) | On a17, CSV import passed 12 positive and 4 invalid-format tests; account search passed 8. Duplicate handling was untested. Email alerts failed 2 of 5, but alerts are now excluded by CR-12. No production smoke test or migration had run. |
| inputs/archive.md, TEST-11 (October 26) | On a19, duplicates passed 3/3, CSV regression 12/12 and search 8/8. This closes the earlier duplicate-test gap for a19. Keyboard navigation fails on the search dialog. No signoff or production smoke test yet. |
| inputs/archive.md, MAIL-28 (October 28) | Nora reports the revised-scope support runbook ready and consent confirmed for 80 accounts. These are operational readiness reports, not deployment approval. |

These are archive summaries, not independently inspected test logs or attached runbooks. The four invalid-format passes are evidenced on a17 only; TEST-11 does not explicitly report their rerun on a19. No later migration evidence appears, and the register does not specify migration as a launch gate. Do not infer either completion or an additional mandatory gate. (inputs/archive.md, TEST-07, TEST-11; inputs/approved-changes.md, CR-12–CR-13.)

## Remaining gates and earliest defensible action
1. **Act now on preparation, not deployment:** Jules should fix the keyboard path and attach passing evidence by October 29. This is required before signoff. (inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11.)
2. In parallel, obtain and attach the missing rollback plan and arrange an explicitly named, trained backup for the reserved morning slot—or establish a later window with Theo. The archive names neither a rollback-plan owner nor the person empowered to assign the backup; resolve those assignments rather than assume them. (inputs/approved-changes.md, CR-13; inputs/archive.md, MAIL-28.)
3. Present the completed acceptance package to Maya for written signoff. Recommended conservative sequencing is to attach the rollback plan before that review; at minimum it must be attached before deployment. Then an eligible operator may deploy, no earlier than the conditional October 30 target. (inputs/approved-changes.md, CR-12–CR-13.)
4. Perform the production smoke test **after deployment and before opening pilot access**. It is a pending post-deployment gate, not a test that can already have passed in staging. Keep access closed until that gate is satisfied. (inputs/approved-changes.md, CR-13.)

**No defensible exact launch time can yet be promised.** October 30, 09:00 Pacific is only a conditional opportunity if all pre-deployment gates and staffing are resolved; pilot access must wait for the subsequent smoke test. (inputs/approved-changes.md, CR-12–CR-13; inputs/archive.md, MAIL-28.)

## Interpretation and limits
Requirements.csv uses local tracking IDs, not source ticket IDs. Theo’s engineering ownership supports feature ownership; unassigned operational duties are marked unspecified. Nora is identified as the readiness reporter, not assumed to authorize launch. This is a document-only assessment: no tests, messages, exports, deployments or production access were performed.
