<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/explanation-index/">
  <id>https://docs.spec-kitty.ai/architecture/explanation-index/</id>
  <title>Explanation</title>
  <updated>2026-10-08T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/architecture/explanation-index/"/>
  <summary>Understanding-oriented background on Spec Kitty: spec-driven development, the mission system, execution lanes, git workflow, and multi-agent orchestration.</summary>
  <content type="html">&lt;span id=&quot;explanation&quot;&gt;&lt;/span&gt;
&lt;p&gt;Understanding-oriented pages that explain &lt;em&gt;why&lt;/em&gt; Spec Kitty works the way it does. Start
here when you want the mental model behind a capability rather than step-by-step instructions.&lt;/p&gt;
&lt;h2 id=&quot;key-pages&quot;&gt;Key pages&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/spec-driven-development/&quot;&gt;Spec-driven development&lt;/a&gt; — the core methodology.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/mission-system/&quot;&gt;Mission system&lt;/a&gt; — how missions and work packages relate.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/mission-type-resolution/&quot;&gt;Mission-type resolution&lt;/a&gt; — the doctrine → charter → core seam that resolves per-mission-type behaviour.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/execution-lanes/&quot;&gt;Execution lanes&lt;/a&gt; and &lt;a href=&quot;/architecture/git-worktrees/&quot;&gt;git worktrees&lt;/a&gt; — the parallel execution model.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/git-workflow/&quot;&gt;Git workflow&lt;/a&gt; — what git operations the runtime owns versus the agent.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/multi-agent-orchestration/&quot;&gt;Multi-agent orchestration&lt;/a&gt; — coordinating work across agents.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/kanban-workflow/&quot;&gt;Kanban workflow&lt;/a&gt; and &lt;a href=&quot;/architecture/runtime-loop/&quot;&gt;runtime loop&lt;/a&gt; — the mission control loop.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/ai-agent-architecture/&quot;&gt;AI agent architecture&lt;/a&gt; — how supported agents integrate.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/doctrine-kinds/&quot;&gt;Doctrine artifact kinds&lt;/a&gt; — what each of the eight doctrine artifact kinds is for.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/spdd-reasons/&quot;&gt;SPDD and the REASONS Canvas&lt;/a&gt; — the opt-in structured-prompt-driven-development artifact set.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/status-model/&quot;&gt;Status model&lt;/a&gt; and &lt;a href=&quot;/architecture/mission-gates/&quot;&gt;mission transition gates&lt;/a&gt; — how lane state is recorded and guarded.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/event-ledger-writers-and-readers/&quot;&gt;Event ledger writers and readers&lt;/a&gt; — who writes and reads each event log today, and the gaps against the event ADRs.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/post-merge-partition-authority/&quot;&gt;Post-merge partition authority&lt;/a&gt; — which bytes win after consolidation, and which surface readers trust.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The full list is in the &lt;a href=&quot;/architecture/&quot;&gt;architecture index&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/guides/tutorials/&quot;&gt;Tutorials&lt;/a&gt; — learning-oriented walkthroughs.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/&quot;&gt;How-to guides&lt;/a&gt; — task-oriented instructions.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/api/&quot;&gt;Reference&lt;/a&gt; — authoritative specifications.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
