Anchor — project roadmap v3
Goals
- Build the unified knowledge workspace for deep work.
- Support writing, code, reading, and thinking on the same primitives.
- Design for clarity, density, and keyboard-first navigation.
- Earn density through populated panels, never decorative chrome.
Milestones
| Milestone | Focus | Status | Target |
|---|---|---|---|
| M1 | Canvas, elements, command palette, status bar | complete | 2026-02-28 |
| M2 | Browse, tag-based filesystem, recent flyout | complete | 2026-03-21 |
| M3 | Linking, graph, cross-references | in progress | 2026-04-30 |
| M4 | Code editor, Architect agent, syntax pipeline | in progress | 2026-05-15 |
| M5 | Publishing pipeline + a327ex.com renderer | queued | 2026-06-15 |
| M6 | Writing mode, Editor agent, prose tools | queued | 2026-07-01 |
Next up
Finalize the link-graph element. The graph view should render inside any canvas as a first-class element type — same selection chrome, same handles, same metadata. The crucial constraint is that it stays readable when shrunk to 240×120 inside another document.
Once that lands, ship M3 and start the code-editor work in parallel.
Open question
Whether to allow nested canvases — a canvas-as-element. Hard to draw the line between embedded view and full nest. Defer until M5 forces the decision.
"The whole point of the brief is earned density, which you can't judge from one canvas alone." — design diary, 2026-03-19
Risk · scoped out for now
- Multi-monitor layout grammar — defer past M5 (single-screen has to settle first).
- Light mode — defer until web rendering needs it.
- Per-element AI conversation — committed to global right-side panel for v1.