# Atlas Web handoff — as of October 28, 2026

## Decision and launch authority
**Hold launch; do not deploy on the strength of the reservation.** 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; no backup is assigned. Thus the reserved October 30, 09:00 Pacific slot currently lacks an available authorized operator. No written signoff is evidenced in the supplied archive. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11, MAIL-28]

## Final scope and superseded claims
The approved pilot is **Atlas Web: CSV import and account search only**, limited to **80 consented accounts**. Email alerts and SSO are excluded. October 30 is the earliest target, conditional on acceptance, not a committed launch. CR-12 supersedes DEC-01's October 20 target, email-alert scope and 500-account limit. EMAIL-19's unlimited-account, SSO/email-alert October 20 promise is a rejected sales draft, not authority. [inputs/approved-changes.md, CR-12; inputs/archive.md, DEC-01, EMAIL-19]

Atlas Mobile is a separate experiment, not this release. The panel-copy drafts and “instant sync” wording are not approved scope or measured guarantees; their demo tests are not launch acceptance, and the routine notes grant no production approval. TICKET-223 is a logged, unapproved customer quotation: neither launch approval nor authorization to export customer data. [inputs/archive.md, NOTE-001–NOTE-060, TICKET-223]

## Acceptance evidence actually recorded
- **October 12, build a17:** Theo reports CSV import passing 12 positive and 4 invalid-format tests, and account search passing 8 tests. Duplicate handling was untested. Email alerts failed 2 of 5 tests, but alerts are now excluded. No production smoke test or migration had run. [inputs/archive.md, TEST-07; inputs/approved-changes.md, CR-12]
- **October 26, build a19:** Theo reports duplicate-account tests 3/3, CSV import regression 12/12 and account-search regression 8/8 passing. This closes the earlier duplicate-test gap. The search-dialog keyboard path fails. No signoff or production smoke test is recorded. The a19 entry does not explicitly repeat the four a17 invalid-format tests; do not claim they were rerun. [inputs/archive.md, TEST-11, TEST-07]
- **October 28 readiness:** Nora reports the revised-scope support runbook ready and consent confirmed for 80 accounts only. These are operational readiness reports, not substitutes for acceptance/signoff. [inputs/archive.md, MAIL-28]

## Blockers and gate order
1. **Before signoff:** Jules must fix the keyboard path and supply passing evidence, due October 29. The current failure is an explicit acceptance blocker. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]
2. **Before deployment:** obtain Maya's written signoff, attach the missing rollback plan, and provide Theo or an explicitly named trained backup. The register does not name a rollback-plan author or backup-assignment owner; these need assignment. For safety, interpret “attached first” as before deployment, not merely before pilot opening. [inputs/approved-changes.md, CR-13; inputs/archive.md, MAIL-28]
3. **After deployment, before pilot access:** complete the production smoke-test gate; none is evidenced yet. This is a later gate, not a test that can be represented as already passed or required to run before deployment. [inputs/approved-changes.md, CR-13; inputs/archive.md, TEST-11]

## Earliest defensible next action
**Now, October 28: continue pre-release remediation and readiness preparation, not launch.** Prioritize Jules's keyboard fix/evidence; in parallel prepare/attach rollback documentation and explicitly name a trained backup for the morning slot, or replan for Theo's availability. Then present the acceptance package to Maya for written signoff. October 29 is an evidence due date, not launch permission. October 30 remains the earliest conditional target; 09:00 is not defensible unless all prerequisites are met. Otherwise defer deployment; open access only after the post-deployment smoke gate. [inputs/approved-changes.md, CR-12, CR-13; inputs/archive.md, MAIL-28]

## Limits
This is a documentary assessment, not independent test execution. No underlying test artifacts, passing keyboard retest, rollback attachment, backup appointment or later signoff are supplied. No migration requirement is established by the current register; TEST-07's unrun migration is not promoted to a new release gate. Requirements owners marked unspecified are unresolved, not inferred assignments. No deployments, messages or production access were performed.
