plan-master.md misstates Phases 10, 13 and 14 and the store listing #73

New issue

Closed

opened 2026-09-21 18:07:08 +01:00 by cruelacid · 1 comment

cruelacid commented

2026-09-21 18:07:08 +01:00

Owner

Part of #37. Highest-value of the documentation corrections.

The problem

CLAUDE.md tells readers to check phase status in docs/plan-master.md rather
than from memory, and docs/positioning.md says to check feature claims against
its phase status specifically so that nothing is claimed that is not shipped.
So a stale table there is not untidy — it is actively misleading, and it misled
this planning session before git log corrected it.

What is wrong

Says	Actually
Phase 13 "next, designed 9 September" — not built	Complete
Phase 14 "hosted half built 18 September"	Complete
Phase 10 "in progress", community-store submission not done	Listed and live. `git log` shows `Release 0.1.2: pass the directory review` through `0.1.5: the last of the winnable review warnings`; manifest is at `0.1.5`
"No real users"	Accumulating downloads

The last one matters most: several decisions in this backlog were priced on
"pre-release, back-compat not binding". That is no longer true.

Also

docs/launch-readiness.md already carries the right warning about itself —
"Gates A, B and C have not been re-checked against the code since they were
written, and are known to understate what exists". The same discipline now
applies to plan-master.md.

What to do

Correct the status lines, add Phases 15-20 pointing at this backlog, and record
the store-listing date. Per that document's own standard: do not tick anything
from memory.

Part of #37. **Highest-value of the documentation corrections.** ## The problem `CLAUDE.md` tells readers to check phase status in `docs/plan-master.md` rather than from memory, and `docs/positioning.md` says to check feature claims against its phase status *specifically so that nothing is claimed that is not shipped*. So a stale table there is not untidy — it is actively misleading, and it misled this planning session before `git log` corrected it. ## What is wrong | Says | Actually | |---|---| | Phase 13 "next, designed 9 September" — not built | Complete | | Phase 14 "hosted half built 18 September" | Complete | | Phase 10 "in progress", community-store submission not done | **Listed and live.** `git log` shows `Release 0.1.2: pass the directory review` through `0.1.5: the last of the winnable review warnings`; manifest is at `0.1.5` | | "No real users" | Accumulating downloads | The last one matters most: several decisions in this backlog were priced on "pre-release, back-compat not binding". That is no longer true. ## Also `docs/launch-readiness.md` already carries the right warning about itself — *"Gates A, B and C have not been re-checked against the code since they were written, and are known to understate what exists"*. The same discipline now applies to `plan-master.md`. ## What to do Correct the status lines, add Phases 15-20 pointing at this backlog, and record the store-listing date. Per that document's own standard: do not tick anything from memory.

cruelacid added this to the Backlog - unscheduled milestone

2026-09-21 18:07:08 +01:00

cruelacid added the

area:docs

label

2026-09-21 18:07:08 +01:00

cruelacid modified the milestone from Backlog - unscheduled to Phase 15 - Retention and enrolment

2026-09-21 18:07:45 +01:00

cruelacid added the

parity

label

2026-09-21 18:08:29 +01:00