Reading the public roadmap

The roadmap lives at feedback.tovio.dev/roadmap and groups posts by status: Planned, In progress, and Shipped.

There are no dates, and there will not be

Not a quarter, not a target, not a "soon". This is a deliberate constraint enforced in more than one place. No engineering issue or project linked to a post carries a due or target date, because the integration would sync that date onto the post and turn it into a promise; and the workspace configuration is published in the project repository, where a check refuses it if a date field appears anywhere.

TOVIO is pre-release and built by one person. A date on this roadmap would be a guess presented as a commitment, and a missed one costs more trust than the roadmap was ever going to earn.

What the statuses actually mean

• Planned — decided and ticketed. It has not been started.
• In progress — someone is working on it now. This is set from the engineering tracker, so it reflects real work rather than intent.
• Shipped — released, with release notes. Set by hand, per item, at release time.

There is no status between "in progress" and "shipped". Code being merged is not the same as a release you can install, so the roadmap does not move on a merge.

Following something

Upvote a post and you are on the list for the one notification it will send: the message when it ships. The moves before that — into Planned, and into In progress — are deliberately silent. In progress is the move that arrives automatically from the engineering tracker, and its upvoter notification is switched off on purpose: a stream of intermediate updates trains people to ignore the one that matters.

Voting requires a sign-in, because an anonymous vote can never be notified at all.

What is not on it

The roadmap shows customer-facing work that came from posts. It is not the project's engineering plan: the independent security audit, the scale and failure evidence, the packaging and publication work, and everything else with no post behind it live in the phase roadmap and the status documentation on the documentation site.