docs: a public roadmap, including what we have NOT built - #469
Merged
Merged
Conversation
Public-facing, so accuracy matters more than ambition. No dates: we would rather be honest about order than wrong about timing. Three things it deliberately does: Says what is NOT shipped, in the same voice as what is. Multi-device sync is listed as in-progress with an explicit "do not rely on it until this line moves", because the producers only just landed and two real machines have not been verified. LAN sync says pairing works and data does not converge yet — the 0.11.0 post claimed that capability early once and this file is where that stops happening. The marketplace says the code exists and nothing is hosted, which is the actual state. Carries a Known gaps section that is not roadmap at all. The Journal data loss predating 0.13.0 is unrecoverable and users deserve to read that somewhere other than a release note they may have skipped. States what we will never build (web version, accounts, ads/tracking) so the question stops being asked and the positioning is unambiguous. Also names the near-term app work in user language rather than iteration ids: Database gets charts/calendar/gallery/timeline plus saved views, Graph gets layouts beyond the single force-directed one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
First pass buried the point. The value of a public roadmap is letting people see what is being added, and that had shrunk to four bullets under a pile of caveats. "What's coming" is now the bulk of the file, broken out per app with the reasoning that makes each item legible — why hierarchical layout is the one we most want (force-directed hides direction), why charts are close (the aggregation engine already computes the numbers), what saved views actually buy. Seven sections covering Graph, Database, Notes/editor, Tasks/Calendar/ Files, Whiteboard/Books/Bookmarks, Agent/automations, and platform. The status sections stay because they are cheap and someone deciding whether to install still needs them, but they are no longer the shape of the page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Public-facing, so accuracy matters more than ambition. No dates — we would rather be honest about order than wrong about timing.
What it deliberately does
Says what is not shipped, in the same voice as what is.
Carries a "Known gaps" section that is not roadmap at all. The Journal data loss predating 0.13.0 is unrecoverable, and users deserve to read that somewhere other than a release note they may have skipped.
States what we will never build — web version, accounts, ads/tracking — so the question stops being asked and the positioning is unambiguous.
Near-term app work, in user language
Database gets charts / calendar / gallery / timeline plus saved views; Graph gets layouts beyond its single force-directed one. Both come from the inventory in harness #246, translated out of iteration ids.
Why this file rather than a Projects board
A board tracks tasks; this answers "should I install this, and what will bite me". It also lives next to the code, so it is reviewable and its history is auditable.
🤖 Generated with Claude Code