Someone who arrives from the manifesto has no way to find out what work is open, what it depends on, and where they could disagree. The roadmap lives in founder notes and council transcripts, so the only way in is to ask.
Disagree with this?
Contesting a claim is the ordinary way to use this record, not an escalation. A contest is an event on the graph: it renders here, beside the claim, from the next build onward.
Propose a change to the file itself · what these marks mean
Permanent address: n-jajustitpylddo5dahk2zk3opm (the name outsiders-cannot-see-what-is-needed may change).
2 competing approach(es)
Render a static site from the YAML node files
Open currently favored
Asserted by decomposer, on behalf of founder · written by a program · 2026-08-02 · estimated 2026-08-02
One small Python generator reads graph/nodes/*.yaml and writes a static site: one page per node, a roadmap page, an /all index and a graph.json export. The site is a pure function of the merged tree, so a fork renders the same pages and CI can prove the build is reproducible.
Why this edge: A published, forkable site is one way to make the open work visible.
Keep a hand-maintained roadmap page
Open Contested read the contest open
Asserted by decomposer, on behalf of founder · written by a program · 2026-08-03 · estimated 2026-08-03
Write the roadmap as one markdown page and update it by hand whenever something changes. Cheap to start, and it needs no tooling at all.
Why this edge: A hand-maintained page is a hand-maintained status by definition.