Snapshot date: 2026-10-28. This is the living public migration summary; dated phase-by-phase migration reports are not the source of new technical decisions.
Source-transfer completion
The OLD-to-NEW migration workflow has ended. Historical orchestration scripts have been retired; this does not independently establish complete runtime parity, cross-service integration or production acceptance.
The live database schema migration owner and Alembic revisions remain necessary for future product updates and were deliberately preserved.
Historical source-only scorecard
| Evidence class | Recorded status |
|---|---|
| Eligible original non-Markdown paths | 878 |
| NEW owner behaviors historically verified from code/test evidence | 664 of 878 |
| Independently reviewed original non-Markdown paths | 784 of 878 |
| Additional independent reviews required | 94 |
| Independently proven full OLD/NEW file equivalence | 0 |
| Blocked jobs in the last paused QA queue | 0 |
These are historical source classifications, not fresh runtime tests, a production certificate, or evidence that all unreviewed files represent missing functionality.
Remaining engineering work
- Security and authority: review sensitive roles, credentials, peer identities and authorization boundaries with the correct owner.
- Financial correctness: prove atomic ledger and hold/dispatch behavior against the intended YSQL role boundaries, including uncertain provider results.
- Provider control/data separation: independently verify the host-lifecycle boundary, scoped API recipients and method-level mTLS authorization.
- Backups and recovery: distinguish health checks from signed restore readiness and real off-host durability.
- Cross-service contracts: establish real interface compatibility, schema versioning, idempotency and negative-path tests.
- Deployment: verify TLS, rollback, live dependencies and operational readiness separately from source-only claims.
Historical report retirement
After consolidation, 622 historical Markdown QA and migration reports were deleted: 482 unreferenced, 99 obsolete progress reports, and 41 technical reports whose enduring design invariants and unresolved implementation gates have been transferred into the relevant service’s Engineering Gates page.
Two nonpublic integration-test/clearance reports remain because existing test/data fixtures directly depend on their paths. Neither is a public design specification; their security boundaries are also summarized in the owner Docs.
Machine-readable migration ledgers and agent state remain internal; neither these nor raw reports are public web assets. Obsolete migration automation that expects removed historical reports is unsupported until separately updated.
Retired migration scripting
The migration cleanup removed 416 obsolete files: 194 old agent scripts, 216 root-level migration utilities and six historical code snapshots. A nonpublic hash manifest records all paths. A general test-ownership checker, current service source, Alembic schema migrations and the living Docs platform remain intact. Former migration automation must not be restarted as an ongoing development workflow.
Development decision rules
- Look for existing behavior in the owning NEW service before adding code; record concrete evidence.
- Prioritize demonstrated behavior gaps over old file counts.
- Make the smallest safe owner-local change and update that service’s docs.
- Keep proposed design, approved design, implemented code, verified test evidence and deployed production state distinct.
- Update the decision register and interface map when a cross-service decision changes. Do not create new per-phase progress reports.
Authorization and limits
Source-only review does not authorize new tests, real payments, provider calls or live application deployment. Later work needs an explicit scope and relevant owner approval.
Continue with Architecture, Interfaces, Decisions and Readiness.