---
type: "Architecture"
title: "Explanation"
description: "Understanding-oriented background on Spec Kitty: spec-driven development, the mission system, execution lanes, git workflow, and multi-agent orchestration."
status: "stable"
generated:
  by: "process:dockitty-export"
  at: "2026-10-08T00:00:00Z"
---

# Explanation

Understanding-oriented pages that explain *why* Spec Kitty works the way it does. Start
here when you want the mental model behind a capability rather than step-by-step instructions.

## Key pages

- [Spec-driven development](/architecture/spec-driven-development.md) — the core methodology.
- [Mission system](/architecture/mission-system.md) — how missions and work packages relate.
- [Mission-type resolution](/architecture/mission-type-resolution.md) — the doctrine → charter → core seam that resolves per-mission-type behaviour.
- [Execution lanes](/architecture/execution-lanes.md) and [git worktrees](/architecture/git-worktrees.md) — the parallel execution model.
- [Git workflow](/architecture/git-workflow.md) — what git operations the runtime owns versus the agent.
- [Multi-agent orchestration](/architecture/multi-agent-orchestration.md) — coordinating work across agents.
- [Kanban workflow](/architecture/kanban-workflow.md) and [runtime loop](/architecture/runtime-loop.md) — the mission control loop.
- [AI agent architecture](/architecture/ai-agent-architecture.md) — how supported agents integrate.
- [Doctrine artifact kinds](/architecture/doctrine-kinds.md) — what each of the eight doctrine artifact kinds is for.
- [SPDD and the REASONS Canvas](/architecture/spdd-reasons.md) — the opt-in structured-prompt-driven-development artifact set.
- [Status model](/architecture/status-model.md) and [mission transition gates](/architecture/mission-gates.md) — how lane state is recorded and guarded.
- [Event ledger writers and readers](/architecture/event-ledger-writers-and-readers.md) — who writes and reads each event log today, and the gaps against the event ADRs.
- [Post-merge partition authority](/architecture/post-merge-partition-authority.md) — which bytes win after consolidation, and which surface readers trust.

The full list is in the [architecture index](/architecture/index.md).

## See also

- [Tutorials](/guides/tutorials/index.md) — learning-oriented walkthroughs.
- [How-to guides](/guides/index.md) — task-oriented instructions.
- [Reference](/api/index.md) — authoritative specifications.

## Related

- [AI Agent Architecture Explained](/architecture/ai-agent-architecture.md)
- [Execution Lanes](/architecture/execution-lanes.md)
- [Git Workflow: Who Does What](/architecture/git-workflow.md)
- [Git Worktrees Explained](/architecture/git-worktrees.md)
- [Kanban Workflow Explained](/architecture/kanban-workflow.md)
- [The Mission System Explained](/architecture/mission-system.md)
- [Mission-Type Resolution — the doctrine → charter → core seam](/architecture/mission-type-resolution.md)
- [Multi-Agent Orchestration](/architecture/multi-agent-orchestration.md)
- [The Runtime Loop Explained](/architecture/runtime-loop.md)
- [Spec-Driven Development Explained](/architecture/spec-driven-development.md)

## Audience

- [Stakeholder Persona: Lead Developer](/context/audience/internal/lead-developer.md) - Written for the Lead Developer reader.
