# Atlas Web handoff — as of October 28, 2026

## Decision and launch authority
**Hold launch.** 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 permission. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11, MAIL-28]

## Final scope and superseded statements
The approved Atlas Web pilot includes **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. [inputs/approved-changes.md, CR-12]

CR-12 supersedes DEC-01’s October 20 target, 500-account limit and inclusion of email alerts. DEC-01’s Maya/Theo ownership remains consistent with later records; its postponed SSO is now explicitly excluded from this release. EMAIL-19’s promise of SSO, alerts and unlimited accounts was a sales draft expressly rejected by Maya, not an approved commitment. [inputs/archive.md, DEC-01, EMAIL-19; inputs/approved-changes.md, CR-12, CR-13]

Atlas Mobile is an unrelated experiment, not part of Atlas Web. Routine NOTE-001–NOTE-060 entries concern draft copy and internal-demo tests, not launch acceptance or production approval; “instant sync” is not a measured guarantee. TICKET-223 is an unapproved quoted customer request, neither launch authorization nor 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) | Build a17: CSV passed 12 positive and 4 invalid-format tests; search passed 8 tests. Duplicates were untested. Email alerts failed 2 of 5 tests; alerts are now excluded by CR-12. No production smoke test or migration had run. |
| inputs/archive.md, TEST-11 (October 26) | Build a19: duplicates passed 3/3, CSV regression 12/12, search regression 8/8. This closes the earlier duplicate-test gap on a19. Search-dialog keyboard accessibility fails. 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 only. These are operational readiness statements, not release signoff. |

These are archive reports, not independently inspected test artifacts. TEST-11 does not explicitly report rerunning a17’s four invalid-format cases; do not assume those passed on a19. No later migration evidence appears, but the approved register does not establish migration as a separate launch gate. [inputs/archive.md, TEST-07, TEST-11; inputs/approved-changes.md, CR-12, CR-13]

## Blockers and earliest defensible next action
**The next action is readiness work now, not deployment.** Recommended sequence:

1. Jules fixes the keyboard path and supplies passing evidence, due October 29. Passing is mandatory before signoff; a due date is not completion evidence. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]
2. In parallel, arrange an explicitly named trained backup for the reserved slot, or plan around Theo’s confirmed availability. Prepare and attach the missing rollback plan. Its author is unspecified; assign one rather than assuming ownership. Conservatively attach it before deployment and include it in the signoff packet. [inputs/archive.md, MAIL-28; inputs/approved-changes.md, CR-13]
3. Present the evidence for Maya’s written signoff. Only then may an eligible operator deploy, no earlier than the October 30 target. A production smoke test follows deployment and precedes opening pilot access; do not treat staging passes as that test. [inputs/approved-changes.md, CR-12, CR-13]

**No exact launch time is defensible yet:** accessibility, rollback documentation, written approval and operator coverage remain unresolved; production smoke evidence is a subsequent access-opening gate. Backup availability, Theo’s return time, rollback author and smoke-test owner are not supplied. The October 30 slot remains conditional, not automatically usable. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11, MAIL-28]

No deployments, messages, exports or production access were performed for this handoff. Requirements IDs in the companion CSV are local tracking IDs; unspecified owners are explicitly marked rather than invented.
