<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/2x/doctrine-and-charter/">
  <id>https://docs.spec-kitty.ai/changelog/2x/doctrine-and-charter/</id>
  <title>2.x Doctrine and Charter</title>
  <updated>2026-06-03T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/2x/doctrine-and-charter/"/>
  <summary>Historical Spec Kitty 2.x archive page for 2.x Doctrine and Charter; use Spec Kitty 3.2 docs for current Charter-era workflows.</summary>
  <content type="html">&lt;blockquote&gt;
&lt;p&gt;Archive notice: This page documents historical Spec Kitty behavior and is not the current 3.2 workflow. Start with &lt;a href=&quot;/context/&quot;&gt;Spec Kitty 3.2&lt;/a&gt; for current docs.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;span id=&quot;2x-doctrine-and-charter&quot;&gt;&lt;/span&gt;
&lt;p&gt;The charter is the single authoritative governance document for your project. It captures policy decisions — testing standards, quality gates, branching rules, deployment constraints — and feeds them into every workflow action. Agents never invent governance on the fly; they read what the charter says and comply.&lt;/p&gt;
&lt;p&gt;In 2.x, the charter workflow is fully command-driven. You answer an interview, generate machine-readable config, and sync it whenever policy changes. The extracted config is injected into agent prompts automatically, so governance is enforced without manual intervention.&lt;/p&gt;
&lt;h2 id=&quot;the-3-layer-model&quot;&gt;The 3-Layer Model&lt;/h2&gt;
&lt;p&gt;Governance is organized into three layers. Only the first is human-edited; the rest are derived.&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Layer&lt;/th&gt;&lt;th&gt;File&lt;/th&gt;&lt;th&gt;Edited By&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;1. Charter&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Human (via interview or direct edit)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2. Extracted Config&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Auto-generated (never edit)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3. Doctrine References&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;library/*.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Auto-generated (never edit)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The flow is always top-down: edit the charter, then run sync to regenerate everything below it.&lt;/p&gt;
&lt;h2 id=&quot;doctrine-artifact-model&quot;&gt;Doctrine Artifact Model&lt;/h2&gt;
&lt;p&gt;2.x doctrine artifacts are repository-native and typed:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Directives: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/directives/*.directive.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Tactics: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/tactics/*.tactic.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Styleguides: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/styleguides/**/*.styleguide.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Toolguides: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/toolguides/*.toolguide.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Schemas: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/schemas/*.schema.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Mission assets/templates: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/**&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Artifact integrity is enforced by:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_schema_validation.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_artifact_compliance.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_tactic_compliance.py&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;the-interview-generate-sync-workflow&quot;&gt;The Interview-Generate-Sync Workflow&lt;/h2&gt;
&lt;p&gt;The typical governance workflow follows three steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Interview&lt;/strong&gt; — answer questions about your project’s policies (testing, deployment, quality gates). This produces &lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt; and a draft &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Generate&lt;/strong&gt; — derive machine-readable config (&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;) and doctrine library files from the charter. This step is deterministic: same charter always produces the same output.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync&lt;/strong&gt; — after manually editing the charter, re-derive all config to pick up changes. The &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; file tracks the charter hash so drift detection can warn you when config is stale.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This cycle repeats whenever project policies evolve.&lt;/p&gt;
&lt;h2 id=&quot;charter-lifecycle&quot;&gt;Charter Lifecycle&lt;/h2&gt;
&lt;p&gt;The charter flow is command-driven through five subcommands:&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Command&lt;/th&gt;&lt;th&gt;Purpose&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Capture policy decisions interactively (or &lt;code dir=&quot;auto&quot;&gt;--defaults&lt;/code&gt; for CI)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Produce YAML config and doctrine library from the charter&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;action&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Inject governance into a workflow step (specify, plan, implement, review)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Show current sync state and detect drift&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Re-derive all config from the charter after manual edits&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The interview supports two profiles:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;minimal&lt;/strong&gt; (8 questions) — project intent, languages, testing, quality gates, review policy, performance targets, deployment constraints, and branching rules.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;comprehensive&lt;/strong&gt; (11 questions) — everything in minimal plus paradigm selection, doctrine references, and advanced tooling preferences.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Use &lt;code dir=&quot;auto&quot;&gt;--defaults&lt;/code&gt; for non-interactive bootstrapping or CI pipelines.&lt;/p&gt;
&lt;h2 id=&quot;charter-paths&quot;&gt;Charter Paths&lt;/h2&gt;
&lt;p&gt;Current bundle location:&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Path&lt;/th&gt;&lt;th&gt;Contents&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;The authoritative policy document&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/interview/answers.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Structured interview responses&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/references.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Doctrine reference selections&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/library/*.md&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Generated guidance documents&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Legacy compatibility is still handled for projects with older layout, but 2.x documentation treats &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; as canonical.&lt;/p&gt;
&lt;h2 id=&quot;available-directives-and-paradigms&quot;&gt;Available Directives and Paradigms&lt;/h2&gt;
&lt;p&gt;Directives are numbered project rules extracted from your charter. Each has:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Severity&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; (blocks workflow) or &lt;code dir=&quot;auto&quot;&gt;warning&lt;/code&gt; (advisory)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Action scope&lt;/strong&gt; — which workflow actions the directive applies to (e.g., &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Paradigms are higher-level development philosophies your charter can select:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;TEST_FIRST&lt;/strong&gt; — tests must be written before implementation code&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;LIBRARY_FIRST&lt;/strong&gt; — prefer existing libraries over custom implementations&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DOCS_ADJACENT&lt;/strong&gt; — documentation lives alongside code, not in a separate tree&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The charter interview prompts you to select paradigms; they are then embedded in the governance config and referenced during &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;runtime-template-resolution&quot;&gt;Runtime Template Resolution&lt;/h2&gt;
&lt;p&gt;When resolving templates and mission assets, 2.x uses ordered precedence:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Project override&lt;/li&gt;
&lt;li&gt;Project legacy location&lt;/li&gt;
&lt;li&gt;User-global mission-specific location&lt;/li&gt;
&lt;li&gt;User-global location&lt;/li&gt;
&lt;li&gt;Packaged doctrine mission defaults&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Implementation references:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/runtime/resolver.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/runtime/home.py&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Primary implementation:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/charter.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/charter/compiler.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/charter/context.py&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&quot;learn-more&quot;&gt;Learn More&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Step-by-step setup&lt;/strong&gt;: &lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to Set Up Project Governance&lt;/a&gt; — full walkthrough of interview, generate, and sync&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent management&lt;/strong&gt;: &lt;a href=&quot;/guides/how-to/collaboration/manage-agents/&quot;&gt;How to Manage Agents&lt;/a&gt; — configure which agents receive governance context&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission system&lt;/strong&gt;: &lt;a href=&quot;/architecture/mission-system/&quot;&gt;The Mission System Explained&lt;/a&gt; — how governance integrates with mission workflows&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI reference&lt;/strong&gt;: &lt;a href=&quot;/api/cli-commands/&quot;&gt;CLI Commands Reference&lt;/a&gt; — complete &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; subcommand details&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
