Plans

Two kinds of document live here. Domain throughlines are durable and persist across releases. Everything else is the distil-then-retire working surface — investigations, research, initiatives, user journeys, and release-scoped plans that retire once distilled into durable architecture/reference docs (Mission B, FR-009).

Domain throughlines (version-spanning)

Domain throughlines are the standing strategy for a domain. They hold the durable "why" — invariants, sub-areas, cross-references — and point at the release-scoped epics and roadmaps for the "what ships when" rather than duplicating them. Epics are release/milestone-scoped tracking, not the throughline. Unlike the working notes below, a throughline does not retire when a milestone closes.

  • Team Kitty / hosted collaboration — retired here; owned upstream. The former "SaaS & hosted sync" domain plan was retired on 2026-09-06 when the Convergence (#3881) removed the local sync transport. The hosted surface (Team Kitty over Zeitgeist) is authored in the upstream spec-kitty/zeitgeist and spec-kitty/saas repos, and this repo consumes their clients. See Team Kitty context and the convergence-retirement ADR.
  • Doctrine & charter — Doctrine & Charter — Domain Plan: charter lifecycle & sole-door access, pack extensibility, activation-driven availability, meta.json fail-closed reads, the public API surface, and glossary-as-doctrine. Its release-scoped companion is the 4.0.0 Milestone Roadmap (the 3.2.x Open-Core Delivery Plan is the prior-cycle record); its program-scoped companions are the Glossary Doctrine Overhaul — Program Plan and the Charter-Resolution Program.
  • Packs extraction — Packs Extraction — Domain Plan: re-extracting the doctrine layer from src/charter/offering/ and packs/built-in/ into separately released units: the wheel split (#3101), open-packs re-vendoring (#3504) and verified distribution (#2539). None of it is 4.0.0 scope.
  • API & dashboard — API & Dashboard — Domain Plan: the stable application/mission-data API surface (#645) and the dashboard/UX consumers (#650), including retiring the Feature-labelled UI drift.

The three live throughlines (and the retired one) are catalogued one hop away in the domains catalog. Naming convention for throughlines: <domain>-domain-plan.md, filed under domains/.

Portfolio & milestone planning

Release-scoped plans follow the distil-then-retire lifecycle and each links up to the domain throughline it serves.

Active cycle (4.x)

  • 4.0.0 Milestone Roadmap — the operator-facing execution roadmap for 4.0.0 (rc-stage): the four goal themes (stability, maturity, extensibility, Team Kitty enablers), the epic dependency spine, per-theme progress, exit criteria, and watch items. Its declaration of intent is 4.0.0.md.
  • 4.x Executive Overview — the stakeholder summary for decision owners (CEO, CPO, CTO, PO): where 4.0.0 stands, what the release candidates delivered, what still gates GA, and the calls that need product ownership.

Prior cycle (3.2.x) — historical

Kept as a record of the 3.2.x line, which closed with 3.2.7 (2026-09-10). Do not act on their next steps; the 4.0.0 roadmap is the plan of record.

  • 3.2.x Milestone Roadmap — superseded. The prior-cycle execution roadmap; re-anchored on 2026-09-14 to hand authority to the 4.0.0 roadmap. The durable declarations of intent it executed live in release goals.
  • 3.2.x Executive Overview — superseded. PO / C-suite synthesis of 3.2.x goals and progress since 3.2.4, framed as business outcomes.
  • 3.2.x Open-Core Delivery Plan — superseded. PO-facing status re-read and the open-core breaking-change delivery strategy (charter-as-sole-door, built-in→module extraction).
  • 3.2.x Delivery Approach — superseded. Cross-mission sequencing intent, stress-tested by a two-round dialectic squad.

Programmes and status notes

Standalone plans and status notes that sit at the top of plans/ or in their own folder:

Working collections (by area)

Subdirectories of the distil-then-retire surface. These are working notes, not plans of record: each folder's own index.md says what in it is live and what is retired.

  • Doctrine — doctrine layering, charter boundary, and artifact-selection planning. The Charter-Resolution Program is a sibling folder in the same area.
  • Code quality — the SonarCloud baseline, quality-metric evolution, the smell/vulnerability cluster taxonomy, and targeted cleanup scoping.
  • Testing — mutation testing, acceleration, friction audit, and CI gate tuning.
  • Investigations — scope assessments, compatibility matrices, and RFC/endpoint research.
  • Engineering notes — the live remainder: architecture audits & reviews, mission notes, DRG/doctrine analyses, and maintenance/field-report briefs. (The runtime/state-overhaul, surface-resolution-cluster, and triage-log sub-clusters have been distilled and retired to deprecated; they remain on disk as archived provenance only.)
  • User journeys — the 2.x-era vision journeys (historical) plus the live init/doctrine flow walkthrough.
  • Research — research deliverables (era spikes/explorations).

Retired collections (distilled and closed out; their index.md is deprecated, kept on disk as archived provenance, not a live working surface): the Reviews collection (PR review resolution plans, test plans, execution reports), the 3.2 doc publication collection (IA, navigation, and the 3.2 publication checklist), the Initiatives collection (2.x-era architecture initiatives, retired 2026-09-30), the Refactor collection (the degod/unshim programme, executed; retired 2026-09-30), and the Next-mission mappings collection (both mapped gaps are now hard regression tests; retired 2026-09-30).

Edit this page