# Atlas Web handoff — as of October 28, 2026

## Decision and launch authority
**Hold deployment and pilot opening.** Maya owns release approval, but cannot operate deployment. Only Theo or an explicitly named, trained backup may deploy, and only after Maya’s **written signoff**. No signoff is recorded. 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 launch permission. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11, MAIL-28]

## Final scope and precedence
The approved release is **Atlas Web: CSV import and account search only**, for at most **80 consented accounts**. Email alerts and SSO are excluded. October 30 is the earliest target, conditional on acceptance—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 signoff/engineering ownership remains consistent with later records. [inputs/approved-changes.md, CR-12; inputs/archive.md, DEC-01]

EMAIL-19’s unlimited accounts, SSO, alerts and October 20 promise was a rejected sales draft, not approval. Atlas Mobile is a separate experiment, not this release. The recurring panel-copy notes and AT-101–AT-160 draft tickets do not expand scope: their tests concern internal demos, and “instant sync” is proposed copy, not a measured guarantee. TICKET-223 is an unapproved quoted customer request; it grants neither launch authority nor permission to export customer data. [inputs/archive.md, EMAIL-19, NOTE-001–NOTE-060, TICKET-223]

## Evidence available
| Record | Recorded result | Interpretation |
|---|---|---|
| inputs/archive.md, TEST-07 (October 12) | Build a17: CSV passed 12 positive and 4 invalid-format tests; search passed 8 tests. Duplicates untested; alerts failed 2 of 5. No production smoke or migration run. | Historical staging evidence. Alerts are now excluded, so those failures are not a current scope blocker. |
| inputs/archive.md, TEST-11 (October 26) | Build a19: duplicates 3/3, CSV regression 12/12, search 8/8 passed. Search-dialog keyboard path fails. No signoff or production smoke. | Closes the earlier duplicate-test gap; does not establish accessibility acceptance. The four invalid-format tests are not explicitly reported rerun on a19. |
| inputs/archive.md, MAIL-28 (October 28) | Nora reports revised-scope support runbook ready and consent confirmed for 80 accounts only. | Operational readiness evidence, not deployment approval. |

These are archive reports, not independently inspected test artifacts. No later migration evidence is supplied; migration is not stated as a separate approved launch gate. [inputs/archive.md, TEST-07, TEST-11; inputs/approved-changes.md, CR-12–CR-13]

## Blockers and earliest defensible next action
**Begin non-production readiness work now, October 28; do not wait for or automatically use the slot.** Recommended sequence:

1. Jules fixes the keyboard path and supplies passing evidence, due October 29. Passing accessibility is mandatory before signoff. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]
2. In parallel, arrange an explicitly named, trained backup for the morning slot, or replan for Theo’s confirmed availability. Assign preparation of the missing rollback plan and attach it before deployment. The archive specifies neither the backup-selection owner nor rollback author; proposed coordination by Maya/Theo is a recommendation, not an existing assignment. [inputs/approved-changes.md, CR-13; inputs/archive.md, MAIL-28]
3. Assemble the acceptance packet for Maya’s written signoff after the keyboard pass. Reconcile evidence to the intended release build, including whether invalid-format coverage needs rerunning; this is a recommended evidence check, not an invented approved gate. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-07, TEST-11]
4. No earlier than the October 30 target, the authorized available operator may deploy once prerequisites are satisfied. Run the production smoke test after deployment and before opening the capped, consented pilot. Smoke evidence is presently absent and remains a downstream opening gate, not a test that can be claimed completed before deployment. [inputs/approved-changes.md, CR-12–CR-13; inputs/archive.md, TEST-11, MAIL-28]

No exact launch time is defensible: accessibility, rollback attachment, written approval and operator coverage remain unresolved. Conservatively, “rollback plan must be attached first” is treated as pre-deployment. Smoke-test execution and pilot-opening ownership are not explicitly assigned. No deployment, message, export or production access was performed for this handoff.
