Retired rebuild documents — how to read them
Migration headers, edge functions and a few source comments cite rebuild-era documents by name
(TABLE-TRIAGE.md, PHASE-8-NOTES.md decision #1, CAPABILITY-INVENTORY.md Contradiction 9,
DESIGN-A.md, PHASE-2-PROMPT.md Track B, ...). Those citations are deliberate provenance: they
record why a table or policy is shaped the way it is.
The documents themselves were retired from the working tree on 2026-09-03 — the rebuild they describe is finished, and 3,493 lines of phase-by-phase planning prose was drowning the docs that describe the current system. Nothing was lost: they are in git history, and the citations still resolve through it.
Do not "fix" a citation to one of these files by deleting it from a migration. Applied migrations are a historical record. The citation is correct; the file just isn't checked out.
Reading a retired document
# Find the commit that retired them
git log --diff-filter=D --name-only -- docs/history/
# Read any file as it was, one commit before that deletion
git show <that-commit>^:docs/history/TABLE-TRIAGE.md
git show <that-commit>^:docs/history/PHASE-8-NOTES.md
# Or restore one into the working tree temporarily (remember to delete it again)
git show <that-commit>^:docs/history/DESIGN-B.md > /tmp/DESIGN-B.md
What each one was
| File | Lines | What it held |
|---|---|---|
CAPABILITY-INVENTORY.md | 494 | Inventory of the pre-rebuild app's capabilities (CAP-###) and the numbered Contradictions with their owner rulings |
TABLE-TRIAGE.md | 366 | Per-table KEEP / RESHAPE / DROP verdict on every legacy table, with live read/row counts as of 2026-08-20 |
DESIGN-A.md | 451 | Track A design doc (coordination, audit, identity) |
DESIGN-B.md | 447 | Track B design doc (schema + RLS shape), including the deployments / project_violations vocabulary open questions |
MERGE-NOTES.md | 100 | Numbered items left open when Track A and Track B merged (item 6 = the field_execution collaborator grant) |
PHASE-2-PROMPT.md | 183 | Phase 2 build prompt, Track A / Track B split |
RUNG-6-PROMPT.md | 336 | Rung 6 build prompt — the ruling that phase is a label, not a gate |
PHASE-3-NOTES.md | 121 | Phase 3 completion notes |
PHASE-5-NOTES.md | 200 | Phase 5 (core UI) completion notes |
PHASE-6-NOTES.md | 215 | Phase 6 (field / XRF) completion notes, numbered gaps |
PHASE-7-NOTES.md | 264 | Phase 7 (documents & money) completion notes, owner-review flags |
PHASE-8-NOTES.md | 262 | Phase 8 (portal & white-label) completion notes — the numbered decisions #1–#9 cited from branding, email and portal migrations |
rebuild-web-README.md | 54 | The rebuild/web package README, from before it was promoted to the repo root |
Also retired the same day: docs/CLIENT_COMPLEX_PROJECT_WALKTHROUGH.md, cited from
20260828090000_project_order_decisions.sql, 20260829090000_document_orders.sql and
DESIGN-C.md. Its content was merged into
docs/PROJECT_LIFECYCLE_GUIDE.md (§14 carries the
five-orders-on-one-apartment scenario), so prefer that file over git history for it.
Still here, and still live
| File | Why it stayed |
|---|---|
CHANGE-LOG.md | The phase-by-phase completion record, pointed at from REQUIREMENTS.md and README.md |
DESIGN-C.md | A proposal, not history: candidate action-level preconditions that do not read phase. None have shipped — see ../domain/GATING.md |
For the current system, start at ../domain/. For what still needs doing, see
../LIFECYCLE_ASSESSMENT.md §8.