Project chart · 2026-10-17
Roadmap and progress
Live milestone snapshot for 969 issues (174 open, 795 closed). Every issue has a history or delivery milestone. 52 open issues are delivery work; 122 are catalog anchors.
Project management docs →History
795
closed issues grouped by era
Delivery
52
open delivery work
Catalog
122
requirement anchors, not agent work
Delivery sequence
| Train | Open |
|---|---|
| Catalog · Requirements & use cases | 112 |
| Backlog · Unscheduled | 22 |
| v0.5 · Quality & traceability (2027-01) | 18 |
| v0.3 · Hexagonal core & security (2026-11) | 14 |
| v0.6 · Platform & operability (2027-02) | 4 |
| v0.4 · Product completeness (2026-12) | 3 |
| v1.0 · GA: legacy-free (2027-03) | 1 |
How the project was organized
Closed cohorts preserve the path from the first issue to the current delivery plan. Curated phase buckets remain distinct from date cohorts.
- H · 2026 Q2 cohort: foundations & API80
- H · 2026 Q3 cohort: product build & UI/UX179
- H1 · Revival & foundations (2026-03–2026-04)6
- H2 · REST API migration (2026-05)15
- H3 · Platform & observability (2026-06)5
- H4 · Web frontend slice (2026-07)3
- H5 · Web frontend wave (2026-07–2026-08)15
- H6 · Production slice (2026-08–2026-09)2
- H7 · Swing deprecation start (2026-09)2
- H8 · Pre-release hardening (2026-09–2026-10)67
Requirements catalog
122 RF, CU, and RNF anchors remain open for traceability. They have dedicated Project views and are never picked as implementation work.
Parallel lanes
Lanes are derived from area and type labels. Cross work blocks backend and frontend; security also blocks backend. Catalog and epic lanes are not claimable.
- catalog122
- backend16
- quality12
- platform8
- frontend6
- security4
- epic4
- cross2