Goals, requirements and tasks are a single hierarchy held together by GitHub sub-issue links. Each view below reads that hierarchy a different way — coverage, proportion, detail, and everything the hierarchy misses.
One square per open issue, grouped by goal, sorted by board stage. This is the whole roadmap at its true size — and it is the only view where the unclaimed block is impossible to scroll past.
An icicle read left to right: goal, then its requirements and direct tasks, then their tasks. Every band's height is the number of open issues underneath it, so the picture is proportional — a goal with one member is one row tall, and the unclaimed block is as tall as the work it holds. Closed issues are excluded here; the point is what is live.
The whole graph as an indented, collapsible list — including closed issues if you ask for them. This is also the table view: every fact the colored views encode is written out here in text. Filter by goal, repo or state; search matches titles and issue numbers.
Forty-five open issues roll up to no goal. They are not a pile — they fall into five groups with clean edges. Two of the groups belong under goals that already exist; three describe workstreams the current goals were never written to hold. Part 2 turns those three into draft goals.
Open issues by goal and board stage. "Off board" means the issue is not an item on the obot Roadmap project, so it renders in no lane on the public roadmap page.