# Atlas Web handoff — as of October 28, 2026

## Decision and authority
**Hold deployment and pilot opening.** 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. Theo is away October 30 morning and no backup is assigned, so the reserved October 30, 09:00 Pacific slot currently has no available authorized operator. A reservation is not approval. [inputs/approved-changes.md, CR-13; inputs/archive.md, MAIL-28]

## Final scope and superseded claims
Atlas **Web** includes **CSV import and account search only**, for at most **80 consented accounts**. Email alerts and SSO are excluded. October 30 is the earliest conditional target, not a committed launch date. CR-12 supersedes DEC-01’s October 20 target, 500-account limit and inclusion of email alerts. DEC-01’s SSO postponement does not authorize SSO in this release. [inputs/approved-changes.md, CR-12; inputs/archive.md, DEC-01]

EMAIL-19’s October 20 promise of SSO, alerts and unlimited accounts was a sales draft explicitly rejected by Maya; it is not scope or approval. Atlas Mobile is an unrelated experiment. The routine panel-copy drafts and “instant sync” language establish neither launch acceptance nor a measured service guarantee; their tests are internal-demo-only. TICKET-223 is a logged, unapproved customer request, not launch authority or permission to export customer data. [inputs/archive.md, EMAIL-19; NOTE-001–NOTE-060; TICKET-223]

## Evidence that exists
| Record | Evidence and boundary |
|---|---|
| TEST-07, October 12 | Theo reported build a17 staging passes: 12 positive CSV tests, 4 invalid-format tests and 8 search tests. Duplicate handling was untested; alerts failed 2 of 5 tests. No production smoke test or migration had run. |
| TEST-11, October 26 | Theo reported build a19 staging passes: duplicate handling 3/3, CSV regression 12/12 and search regression 8/8. This closes the earlier duplicate-test gap, but the search-dialog keyboard path fails. No signoff or production smoke test yet. |
| MAIL-28, October 28 | Nora reports the revised-scope support runbook ready and consent confirmed for 80 accounts. These are operational readiness reports, not release authorization. |

Sources: inputs/archive.md, TEST-07, TEST-11 and MAIL-28. The archive supplies test summaries, not underlying execution artifacts. The four invalid-format passes are evidenced on a17 only; TEST-11 does not explicitly establish that coverage on a19. Alert failures are historical evidence for an excluded feature, not an additional current-scope acceptance gate. [inputs/approved-changes.md, CR-12]

## Remaining gates and next action
1. **Accessibility:** Jules must fix the keyboard path and provide passing evidence by October 29, before signoff. The due date is not proof of completion. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]
2. **Rollback:** the required rollback plan is absent. CR-13 says it must be attached first; conservatively attach it to the acceptance package before signoff/deployment. Its author is not assigned in the supplied records. [inputs/approved-changes.md, CR-13]
3. **Authorization and staffing:** Maya’s written signoff remains outstanding. Name a trained backup for the morning slot or establish a later opportunity when Theo is available; no later slot or return time is evidenced. Maya’s signoff cannot substitute for an operator. [inputs/archive.md, TEST-11, MAIL-28; inputs/approved-changes.md, CR-13]
4. **Post-deployment gate:** perform and pass the production smoke test after authorized deployment and before opening pilot access. It is pending by design, not a test to run before deployment. The smoke-test owner is not explicitly assigned. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]

**Earliest defensible action now:** continue non-production readiness work—Jules’s fix and evidence, preparation/attachment of rollback documentation, and explicit operator assignment—rather than deploy. Then Maya reviews acceptance and issues written signoff; an eligible operator deploys no earlier than the conditional October 30 target; production smoke testing precedes pilot opening. October 30 at 09:00 is not presently defensible, and no exact launch time can be established from this archive. These are recommendations, not actions performed. [inputs/approved-changes.md, CR-12–CR-13; inputs/archive.md, MAIL-28]

## Interpretation limits
Requirements CSV owners marked “not specified” need assignment; engineering ownership alone is not evidence of a specific rollback or smoke-test assignment. No migration requirement is established: TEST-07 reports none run, without making migration an acceptance gate. No deployments, messages, exports or production access were performed.
