Archive notice: This page documents historical Spec Kitty behavior and is not the current 3.2 workflow. Start with Spec Kitty 3.2 for current docs.

2.x Documentation (Archive)

Archive Notice: This section documents Spec Kitty 2.x behavior. It is preserved for historical reference only. For current 3.2 documentation, see Spec Kitty 3.2 current overview.

2.x was the architecture track centered on doctrine-backed governance, living glossary semantics, and runtime-owned mission execution. These pages are archived so existing projects and contributors can understand older behavior; current projects should use the 3.2 docs.

Key 2.x Shifts

1. Doctrine artifacts are typed and schema-validated under src/doctrine/.
2. Charter generation uses interview answers plus doctrine catalog selection.
3. Glossary is context-owned (glossary/contexts/*.md) and integrated into mission execution through glossary hooks.
4. Runtime loop and mission discovery are driven by canonical next and runtime precedence rules.

Start Here

1. Doctrine and Charter
2. Glossary System
3. Runtime and Missions
4. Orchestration and API Boundary
5. ADR Coverage

Current replacement

• For new projects: start with Spec Kitty 3.2 documentation.
• For upgrades: use Migration to Spec Kitty 3.2.
• For old behavior lookup: use this 2.x archive only for historical context.

Architecture Repository Layout

• 2.x domain map: architecture/2.x/README.md#domain-breakdown
• 2.x C4 docs: architecture/2.x/01_context/, architecture/2.x/02_containers/, architecture/2.x/03_components/
• 2.x ADRs: architecture/2.x/adr/
• 2.x user journeys: architecture/2.x/user_journey/
• architecture personas: architecture/audience/