The roadmap moved out here
The list of what is built used to be a dialog inside the app, shown to somebody who had opened it to write a novel. That was the wrong reader.
The application had a Roadmap button in its status bar. Pressing it opened every feature the thing is meant to have — eight areas, forty-seven items, a hundred and sixty-five steps — marked built, in progress or planned.
It was a good page in the wrong building.
Who was actually reading it
A writer opens a manuscript application to write. The roadmap answers a question they are not asking: how far along is this? is a question you ask before you commit to something, not after you have forty thousand words in it. Worse, the honest answer today is “about a third”, and a writer three chapters into a draft does not need to be told that the tool holding it is a third finished.
The people who genuinely want that list are the ones watching it get built. So it moved to where they are, and the button came out of the status bar.
What that cost
One thing, and it is worth naming rather than quietly losing.
Every step marked built carries the paths in the repository that prove it, and a test asserted that each of those paths existed. It is the only thing standing between a public progress bar and a lie: without it, a step goes on being marked built long after the code behind it was deleted, and the bar keeps counting it.
Those paths point into a different repository now, so no test on this site can
check them. What replaced it is a script that runs against a local clone —
bun run verify:evidence ../untitled — and gets run before a roadmap change is
published. It is weaker, because nothing forces it. It is written down here so
that when the bar and the application eventually disagree, the reason is on the
record.
The number
Fifty-three of a hundred and sixty-five steps, which is 32%.
That number will move, and it will also move backwards as a percentage, because the roadmap gets longer. Thirty new planned steps take 32% to 27% without a line of code being deleted. That is not a bug in the list, and it is the exact reason nothing here computes a version number from it.