Domain Throughlines — Catalog
Domain throughlines are the durable, version-spanning strategy for a domain. Each
holds the standing "why" — invariants, sub-areas, and cross-references — and points at
the release-scoped epics and roadmaps for the "what ships when" rather than duplicating
them. Unlike the distil-then-retire working notes elsewhere under
docs/plans/, a throughline does not retire when a milestone closes.
This page is the one-hop catalog of every throughline. Naming convention:
<domain>-domain-plan.md, filed here under domains/.
The throughlines
Three throughlines are live. A fourth, the former "SaaS & hosted sync" plan, is retired (listed last for the record).
- Doctrine & Charter — Domain Plan — the
governance substrate: charter lifecycle & sole-door access, pack extensibility,
activation-driven availability,
meta.jsonfail-closed reads, the stable public API surface, and glossary-as-doctrine. - Packs Extraction — Domain Plan — re-extracting
the doctrine layer from
src/charter/offering/andpacks/built-in/: the code boundary and wheel split, content provenance via open-packs, strangler discipline, and verified distribution. - 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.
- Team Kitty / hosted collaboration — retired here, owned upstream. The former
"SaaS & hosted sync" plan was retired on 2026-09-06 when the Convergence (#3881) removed the
local sync transport. Team Kitty over Zeitgeist is authored in the upstream
spec-kitty/zeitgeistandspec-kitty/saasrepos. See Team Kitty context and the convergence-retirement ADR.
See also
- Plans landing page — the full plans surface (throughlines plus the distil-then-retire working collections).