baya-monorepo/docs/status/index.md

Status — where the project actually is

Populated by phase 4 — not yet written. Phase 4 owns 149 of the 275 surveyed markdown files, by far the largest extraction job in the chain. Until then, open work is spread across five ledgers that do not reference each other.

Planned contents

File	Covers
implemented.md	The overlay: product/'s 14 business areas → build state. product/ itself stays untouched
backlog.md	Every open item as BL-###, triaged, each carrying its origin id
backlog-closed.md	Items confirmed done, with what closed them
decisions.md	The distilled decision log from the whole phase chain

The five ledgers phase 4 reconciles

Source	Size	Note
frontend/requests/for-backend.md	67 REQs, 104 K	Append-only; dispositions must be re-checked, not copied
hardening/issues.md	18 items	18 of 18 unticked, last touched 2026-07-17 — while four later chains shipped. Re-verify each against code (C-10)
reports/*.md "Follow-ups for later phases"	53 reports	Every report has one. Confirmed present in all 53
backend/handoff/*.md	22 files	Deferrals with pull-triggers
product/notes/open-questions.md + manual-testing/ ×2	—	Business questions and two raw human feedback notes

Plus mocks-registry.md (75 K) — the seam-by-seam mock/real status that implemented.md needs, and the only file that tracks it.

Where decisions come from

Every dev/phases/* prompt shares a fixed structure, and §5 "Critical rules you must not get wrong" is the section that states constraints not visible in the code. Verified present in all 32 prompts — that is the raw material for decisions.md. See the inventory.