# Spec Kitty Documentation

Spec Kitty is the current documentation set for the Spec Kitty CLI, Charter governance model, AI harness integration, mission runtime, and project upgrade workflows. The docs are organized into a single 13-section Common Docs structure under one entry point.

## Current Version Stance

- Current docs: https://docs.spec-kitty.ai/
- Current overview: https://docs.spec-kitty.ai/context/
- Current runtime model: Charter-era Spec Kitty
- Current project governance source: `.kittify/charter/charter.md`
- Current mission loop command: `spec-kitty next --agent <name> --mission <slug>`
- Historical 1.x and 2.x pages are archived under `/archive/` and are not the starting point for new projects.

## Best Entry Points

- Single entry point: https://docs.spec-kitty.ai/
- New users and guided workflows: https://docs.spec-kitty.ai/guides/
- API, CLI, schema, and environment reference: https://docs.spec-kitty.ai/api/
- Configuration: https://docs.spec-kitty.ai/configuration/
- Charter, governance, glossary, and audiences: https://docs.spec-kitty.ai/context/
- Architecture and living design: https://docs.spec-kitty.ai/architecture/
- Architecture decision records: https://docs.spec-kitty.ai/adr/
- Upgrading projects: https://docs.spec-kitty.ai/migrations/
- Historical archive: https://docs.spec-kitty.ai/archive/

## Documentation Sections

The docs are a single 13-section Common Docs structure:

- `context/` — glossary human narrative, audiences, and the Charter-era governance model.
- `architecture/` — unified, unversioned living design.
- `adr/` — architecture decision records by era (1.x, 2.x, 3.x).
- `plans/` — user journeys, investigations, and traces (distil-then-retire).
- `api/` — exact CLI, file, schema, and environment behavior.
- `configuration/` — configuration files, flags, and environment variables.
- `integrations/` — AI harness and external-system integration.
- `security/` — security posture, credentials, and secrets handling.
- `guides/` — task-oriented guides and guided learning workflows.
- `operations/` — operational and developer-workflow guides.
- `migrations/` — version migrations, upgrade paths, and shim rules.
- `changelog/` — release history.

## Intent Routing

When the question is about X, read Y first (each section has its own `index.md` landing page):

- Getting started or first project — read `guides/index.md`.
- Installing or upgrading the CLI or a project — read `guides/index.md`, then the migration notes under `migrations/index.md`.
- Running a specific task (spec, plan, tasks, implement, review, merge) — read `guides/index.md`.
- An exact command, flag, file, schema, or environment variable — read `api/index.md`.
- Configuration files and environment variables — read `configuration/index.md`.
- AI harness support and external integrations — read `integrations/index.md`.
- Security, credentials, or secrets handling — read `security/index.md`.
- Why something works the way it does (mental model, architecture, tradeoffs) — read `architecture/index.md`.
- A specific architectural decision and its rationale — read `adr/index.md`.
- Governance, Charter, doctrine, glossary, or agent profiles — read `context/index.md`.
- Upgrading from 1.x or 2.x, or finding archived behavior — read `migrations/index.md`, then `archive/index.md`.
- Recovering from a failed or interrupted operation — read `operations/index.md`.
- Roadmap, investigations, or research traces — read `plans/index.md`.
- Release history — read `changelog/index.md`.