Everything else that used to live in product/, docs/, and the old archive/ has been consolidated under archive/ as historical/reference material. It is not required reading to answer "what's next" — these three files are:

File	Answers
test-flows.md	"How do I manually test that X works?" — plain-language, click-by-click walkthroughs of every user journey, no engineering knowledge required.
blockers.md	"What has to be fixed before this is a real product?" — what's broken today, and what must happen before real money/real users touch it.
forgotten-features.md	"What's missing that we haven't clearly scheduled?" — planning gaps that don't show up as an app bug, plus a short list of things already deliberately cut so they don't get re-litigated by accident.
fix-plan.md	"How do I actually fix each blocker?" — an engineering-facing companion to blockers.md: exact root cause (file:line), proposed fix, and any business-rule decision flagged rather than guessed, per item. Nothing in it has been applied yet.

Last verified: 2026-08-02.