List view

• 1 — Nexus: Pre-Freeze (1.0 blockers)

  Critical path to the 1.0 freeze. Everything here must land BEFORE the freeze: it touches the public API or on-disk wire format, or is a remaining feature/example/doc on the 1.0 path. Merged from the former 'Feature-Complete' and 'Freeze Hardening' milestones — the 1/2 split was redundant (both were pre-freeze, with overlapping on-disk-format scope). Tier 0 = irreversible (on-disk format, stable-vs-nightly, per-row GlobalSeq); Tier 1 = breaking to change after external adoption. When this closes -> freeze -> build Agency.

  No due date

  •44/52 issues closed
  84% complete8 open44 closed

• 3 — Ongoing Improvements (1-off)

  Standalone, additive, non-API-breaking cards that make nexus incrementally better. Worked on in parallel and after the freeze. Not on the critical path.

  Due by September 15, 2026

  •1/12 issues closed
  8% complete11 open1 closed

• Tier 2: Production Hardening

  Features mature frameworks have. Expected for production adoption. Sagas, command routing, retry strategies, metadata enrichment, more store adapters.

  Due by August 1, 2026

  •7/8 issues closed
  87% complete1 open7 closed

• Tier 1: Table Stakes

  Features every serious ES framework has. Without these, nexus cannot be used for real projects. Snapshots, projections, subscriptions, and test fixtures.

  Due by July 15, 2026

  •12/12 issues closed
  100% complete0 open12 closed

• 4 — Research / Watch-list

  Exploratory evaluations and watch-list technologies (formal verification, simulation testing, loom). Not committed work.

  Due by November 1, 2026

  •1/7 issues closed
  14% complete6 open1 closed