Roadmap
Committed next steps, in dependency order. Anything not here is in BACKLOG.md; rejected directions are in SCOPE.md. The reasoning behind each shape is in DECISIONS.md.
The ordering rule: each phase must produce an observable result on its own. The alternative - building the container parser, the address space, and the GPU layer before anything can be run - is how a project reaches month six with nothing to show and no way to tell which of three layers is wrong.
Phases 1-6 are a strict chain, with 1b and 2b hanging off 1. Phases
0b through 0e are independent of everything and of each other.
This table is generated. Edit an item under
roadmap/, then run
tools/split-doc.sh --index orbistoun ROADMAP 2 roadmap.
| item | status | |
|---|---|---|
| ⚪ | Where this actually stands (2026-08-24) | no marker |
| ⚪ | Phase 0 - Synthetic fixtures | no marker |
| 🟢 | Phase 0b - ABI spike | done |
| 🟢 | Phase 0c - Structural seams | done |
| 🟢 | Phase 0d - Test corpus tooling | done |
| 🟢 | Phase 0e - Observability substrate | done |
| 🟢 | Phase 1 - Container wrapper and dynamic segment | done |
| 🟢 | Phase 1b - Corpus-wide survey report | done |
| 🟢 | Phase 2 - Symbol resolution | done |
| 🟢 | Phase 2b - GUI shell and library | done |
| 🟢 | Phase 3 - Address space | done |
| 🟢 | Phase 4 - Worker, placement, relocation, protection, stubs, entry; thread pointer, trace sink | done |
| 🟡 | Phase 5 - Threading and synchronisation | begun |
| ⚪ | Phase 6 - First pixel | no marker |
| ⚪ | Phase 6's contents, built ahead of it | no marker |
| ⚪ | Running alongside | no marker |
| ⚪ | Stretch | no marker |
| ⚪ | Not on the roadmap | no marker |
| ⚪ | Answering Prosperous | no marker |
| meaning | |
|---|---|
| 🟢 | done |
| 🟡 | begun |
| 🔴 | open, or explicitly not done |
| ⚪ | deferred, not planned, or carrying no marker either way |