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.

  • SaaS & hosted sync — domain plan retired 2026-09-06 (Convergence #3881): the local sync transport was removed and the hosted surface re-homed to the authoritative upstream repos (spec-kitty/zeitgeist, spec-kitty/saas); this repo consumes their clients. See 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- and program-scoped companions are the 3.2.x Open-Core Delivery Plan and the Glossary Doctrine Overhaul — Program Plan.
  • Packs extraction — Packs Extraction — Domain Plan: physically extracting the doctrine layer into the standalone spec-kitty-doctrine module — boundary definition, import-cycle break, strangler cutover, and repo split.
  • 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.

All four throughlines 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 strategy for the current cycle. These follow the distil-then-retire lifecycle and each links up to the domain throughline it serves.

  • 3.2.x Executive Overview — PO / C-suite synthesis: goals and progress since 3.2.4, framed as business outcomes; the top-level stakeholder entry point.
  • 3.2.x Open-Core Delivery Plan — PO-facing status re-read and the open-core breaking-change delivery strategy (charter-as-sole-door, built-in→module extraction). Supersedes the roadmap's "G2-is-the-blocking-spine" framing where they disagree.
  • 3.2.x Delivery Approach — cross-mission sequencing intent, stress-tested by a two-round dialectic squad. Doctrine-first confirmed.
  • 3.2.x Milestone Roadmap — the operator-facing execution roadmap for the current milestone; the durable declarations of intent it executes live in release goals.

Working collections (by area)

Subdirectories of the distil-then-retire surface, each with its own index.md cataloguing its contents. Roughly ordered by current activity:

  • Doctrine — doctrine layering, charter boundary, and artifact-selection planning.
  • Refactor — degod/unshim program and slice-landing planning.
  • 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.)
  • Initiatives — active architecture initiatives.
  • User journeys — end-to-end user-journey docs.
  • Research — research deliverables (era spikes/explorations).
  • Next-mission mappings — mapping notes for the mission-next compatibility surface.

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) and the 3.2 doc publication collection (IA, navigation, and the 3.2 publication checklist).

Edit this page