<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/plans/doctrine/layered-doctrine-resolution-design/">
  <id>https://docs.spec-kitty.ai/plans/doctrine/layered-doctrine-resolution-design/</id>
  <title>Layered Doctrine Resolution — Design Blueprint</title>
  <updated>2026-09-30T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/plans/doctrine/layered-doctrine-resolution-design/"/>
  <summary>Design blueprint (approved 2026-05-15) for layered doctrine resolution across issues #832/#883/#1013: how doctrine layers compose and resolve.</summary>
  <content type="html">&lt;span id=&quot;layered-doctrine-resolution--design-blueprint&quot;&gt;&lt;/span&gt;
&lt;p&gt;Status: approved for mission planning, 2026-05-15&lt;br&gt;
Related issues: #832, #883, #1013&lt;br&gt;
Depends on: Phase 7 schema versioning (#469), landed in 3.2.x&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;problem&quot;&gt;Problem&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;Written 2026-05-15. The org layer this blueprint proposes has since shipped (the three-layer
built-in → org → project model; see the retired &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/archive/plans/doctrine/391-doctrine-usage-test.md&quot;&gt;#391 doctrine usage test&lt;/a&gt;),
so read this section as the problem as it stood then.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The spec-kitty doctrine resolution stack had two layers at the time: &lt;strong&gt;shipped&lt;/strong&gt; (bundled with the
CLI) and &lt;strong&gt;project&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt;). This is sufficient for individual project governance,
but it leaves a structural gap for organisations that adopt spec-kitty across multiple teams.&lt;/p&gt;
&lt;p&gt;Today those organisations face one of three unacceptable options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Fork the CLI&lt;/strong&gt; to hard-code org governance into the shipped layer. Forks diverge from upstream
and become a maintenance liability.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Repeat configuration&lt;/strong&gt; in every project’s &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt;. Each new project re-derives
org standards from scratch; drift accumulates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Leave org governance out&lt;/strong&gt; of spec-kitty entirely and maintain a parallel initialisation
system. Two systems means two onboarding paths and no shared governance model.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Two secondary gaps compound the problem:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission-type bleed-through.&lt;/strong&gt; All missions — software-dev, documentation, research — receive
the same governance context, which leans on &lt;code dir=&quot;auto&quot;&gt;software-dev-default&lt;/code&gt; assumptions. A documentation
mission should not inherit test-first coding doctrine.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;External doc opacity.&lt;/strong&gt; A project may have an authoritative governance document (a public
constitution, a security policy, an architecture decision record) that agents should read. There
is no first-class way to declare these references in the charter so that &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;
includes them.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;user-journeys&quot;&gt;User Journeys&lt;/h2&gt;
&lt;p&gt;The following journeys describe the intended end-to-end experience once both missions land.
They are ordered from authoring (upstream) to consumption (downstream).&lt;/p&gt;
&lt;h3 id=&quot;journey-1--security-policy-lead-authoring-an-org-doctrine-pack&quot;&gt;Journey 1 — Security Policy Lead: authoring an org doctrine pack&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“Our security team has an exhaustive discovery process and a set of required security directives
that every engineering team must follow. I need to encode these once and have them automatically
available in every project that uses spec-kitty — without asking project teams to copy anything.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; Security Policy Lead (doctrine author), spec-kitty CLI&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; a spec-kitty release with org-layer support installed (org packs shipped during 3.2.x; the 3.3.x line named here originally was retired and never shipped); org has adopted spec-kitty for project workflow&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The lead initialises a new git repository: &lt;code dir=&quot;auto&quot;&gt;security-policies-doctrine&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;She authors directives, tactics, and toolguides in spec-kitty YAML schema under the pack
directory layout:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;directives/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;sec-001-threat-modelling.directive.yaml&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;sec-002-dependency-scanning.directive.yaml&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;tactics/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;security-discovery-tactic.tactic.yaml&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;toolguides/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;sast-pipeline.toolguide.yaml&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;graph-extensions.yaml   ← additive DRG edges linking new nodes to shipped nodes&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;She runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack validate .&lt;/code&gt; to confirm schema compliance and DRG edge
consistency against the shipped graph.&lt;/li&gt;
&lt;li&gt;She tags a release (&lt;code dir=&quot;auto&quot;&gt;v1.0.0&lt;/code&gt;) and publishes the repository (private git or internal registry).&lt;/li&gt;
&lt;li&gt;She documents the pack’s versioning policy in &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; A versioned, self-contained doctrine pack that passes CLI validation and is ready
to distribute.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;journey-2--enterprise-doctrine-maintainer-assembling-the-org-distributable&quot;&gt;Journey 2 — Enterprise Doctrine Maintainer: assembling the org distributable&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“We have several domain-specific doctrine packs — security, compliance, architecture standards.
I need to aggregate them into a single org distributable that ships to every developer alongside
the spec-kitty CLI.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; Doctrine Maintainer, IT/Platform team&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; Domain packs (&lt;code dir=&quot;auto&quot;&gt;security-policies-doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;compliance-doctrine&lt;/code&gt;, etc.) are
published and validated&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The maintainer creates an &lt;code dir=&quot;auto&quot;&gt;org-doctrine-distributable&lt;/code&gt; repository.&lt;/li&gt;
&lt;li&gt;She declares all domain packs as versioned dependencies in an &lt;code dir=&quot;auto&quot;&gt;org-doctrine.yaml&lt;/code&gt; manifest:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;schema_version&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;1&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;org_name&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;acme-corp&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;packs&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;- &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;source&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;url&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;git@internal.example.com:security/security-policies-doctrine.git&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;ref&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;v1.0.0&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;- &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;source&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;url&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;git@internal.example.com:architecture/arch-doctrine.git&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;ref&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;v2.1.0&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;She authors a &lt;strong&gt;baseline charter fragment&lt;/strong&gt; — shared charter policy elements (review
expectations, human-in-command policy, publication authority) that all projects inherit. These
reference org-layer doctrine artifacts by URN so &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; can traverse them.&lt;/li&gt;
&lt;li&gt;She runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack assemble .&lt;/code&gt; to merge domain packs into a single validated
local snapshot and confirm no DRG edge conflicts.&lt;/li&gt;
&lt;li&gt;She tags and publishes the distributable. The distributable is the single installation artifact
that IT will push to all developer machines.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; One versioned artifact that aggregates all org governance. Domain pack owners update
their packs independently; the maintainer cuts new distributable releases on their schedule.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;journey-3--itplatform-enforcing-org-doctrine-installation&quot;&gt;Journey 3 — IT/Platform: enforcing org doctrine installation&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“We distribute spec-kitty to all engineers via our internal toolchain. We want the org doctrine
pack to be installed alongside the CLI with no manual step required from each developer.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; IT/Platform team, company installation policy&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; org-doctrine-distributable published; spec-kitty org-layer support landed&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;IT adds the distributable installation to the company toolchain alongside the spec-kitty CLI
install:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# company install script (conceptual)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;pipx&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;install&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;spec-kitty-cli&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# any release with org-layer support&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;doctrine&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;fetch&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;\&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--source&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;git&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;\&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--url&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;git@internal.example.com:platform/org-doctrine-distributable.git&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;\&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--ref&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;stable&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#F78C6C;--1:#AA0982&quot;&gt;\&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--target&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;~/.kittify/org/acme-corp/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;The org source is registered in the global user config (&lt;code dir=&quot;auto&quot;&gt;~/.kittify/config.yaml&lt;/code&gt;):
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;yaml&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;doctrine&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;org&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;    &lt;/span&gt;&lt;span style=&quot;--0:#7FDBCA;--1:#111111&quot;&gt;local_path&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;~/.kittify/org/acme-corp/&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;IT publishes the install script and policy in the company developer portal. New starters run
one command; existing developers receive the update through the standard toolchain refresh.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; lists the registered org-layer artifacts and their versions at any time,
giving IT an audit surface.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; Every developer machine has the org doctrine pack installed at a known path. No
project-level bootstrap is needed. The org layer is invisible until invoked — it just works.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;journey-4--developer-starting-a-new-project-with-zero-org-layer-configuration&quot;&gt;Journey 4 — Developer: starting a new project with zero org-layer configuration&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“I just installed spec-kitty and the org toolkit. When I start a new project, I expect our
security and architecture standards to be automatically available — I should not need to set
anything up.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; Developer&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; Journeys 1–3 complete; developer machine has org doctrine installed&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The developer creates a new project repository and runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;She runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview&lt;/code&gt; to produce the project charter. The interview surfaces
org-layer directives, tactics, and agent profiles alongside shipped defaults. She selects the
ones relevant to her project; org-layer selections are tagged with &lt;code dir=&quot;auto&quot;&gt;source: org&lt;/code&gt; in the
compiled charter.&lt;/li&gt;
&lt;li&gt;She runs a mission (&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement WP01&lt;/code&gt;). The agent context includes org-layer security
directives without any project-level configuration. She does not know or care that they came
from the org layer — they are just part of governance.&lt;/li&gt;
&lt;li&gt;She adds a project-local override for one directive (&lt;code dir=&quot;auto&quot;&gt;sec-002-dependency-scanning&lt;/code&gt;) to use a
different scanner: she drops an override YAML in &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/directive/&lt;/code&gt; and the
project layer takes precedence as usual.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status&lt;/code&gt; shows the resolved governance stack: shipped → org → project,
with source attribution for each artifact.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; Zero org-layer configuration at the project level. Project-local overrides still
work. The resolution order is transparent on demand.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;journey-5--developer-mission-type-governance-in-practice&quot;&gt;Journey 5 — Developer: mission-type governance in practice&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“I’m running a documentation mission. I don’t want software-dev coding doctrine cluttering my
agent context. And I want the org’s documentation standards — audience, plain language,
accessibility — to apply automatically.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; Developer, agent running the mission&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; Journey 4 complete; org pack includes documentation governance profile&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The developer starts a documentation mission (&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;). The mission type recorded
in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter context --action write&lt;/code&gt; resolves governance in mission-type-aware order:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;project charter&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ shipped documentation governance profile&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ org documentation governance overrides (if present in org pack)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ mission-instance addendum (if declared in mission meta)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;The agent context does &lt;strong&gt;not&lt;/strong&gt; include test-first coding doctrine, CLI interface requirements,
or code-review assumptions. It does include audience targeting, Divio type requirements,
plain-language directives, and accessibility guidelines.&lt;/li&gt;
&lt;li&gt;If the project charter also declares &lt;code dir=&quot;auto&quot;&gt;governance_references&lt;/code&gt;, those external docs (e.g.
&lt;code dir=&quot;auto&quot;&gt;docs/style-guide.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec/writing-standards.md&lt;/code&gt;) are included as bounded excerpts in the
context.&lt;/li&gt;
&lt;li&gt;Running the same mission on another project in the same org automatically picks up the org
documentation governance profile — no per-project setup.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; Mission-type governance is zero-config and compositional. The correct governance
scope is derived from the mission type, not inferred from template selection.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;journey-6--developer-declaring-governance-references-in-the-charter&quot;&gt;Journey 6 — Developer: declaring governance references in the charter&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;“We have a public project constitution at &lt;code dir=&quot;auto&quot;&gt;spec/constitution.md&lt;/code&gt; and a company architecture
decision record at &lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt;. I want agents to read these when doing governed actions — but
I don’t want to copy them into &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;.”&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;Actors:&lt;/strong&gt; Developer&lt;br&gt;
&lt;strong&gt;Preconditions:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; exists; referenced documents exist in the repository&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The developer adds a &lt;code dir=&quot;auto&quot;&gt;governance_references&lt;/code&gt; block to the project charter:
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;markdown&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82B1FF;--1:#3B61B0&quot;&gt;## Governance References&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; path: spec/constitution.md&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;description: &quot;Public project governance constitution&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;-&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; path: docs/adr/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;description: &quot;Architecture decision records&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter context --action implement&lt;/code&gt; includes bounded excerpts from the referenced paths in
the rendered context block.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; confirms the references resolve correctly. If &lt;code dir=&quot;auto&quot;&gt;spec/constitution.md&lt;/code&gt; is later
deleted or moved, &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; emits an actionable warning (not a silent omission).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate --force&lt;/code&gt; does not overwrite &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; if it is a symlink pointing outside
the expected charter bundle path — an error is emitted with a remediation hint.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Outcome:&lt;/strong&gt; External authoritative documents are first-class references in the charter, surfaced
in agent context without duplication or enforcement of content equality.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;architecture-blueprint&quot;&gt;Architecture Blueprint&lt;/h2&gt;
&lt;h3 id=&quot;current-resolution-stack&quot;&gt;Current resolution stack&lt;/h3&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;shipped  (.../site-packages/doctrine/)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;↕ field-level merge&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;project  (.kittify/doctrine/)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h3 id=&quot;target-resolution-stack&quot;&gt;Target resolution stack&lt;/h3&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;shipped  (.../site-packages/doctrine/)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;↕ full-replace on ID collision (org overrides shipped)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;org      (~/.kittify/org/&amp;#x3C;pack-name&gt;/)      ← new&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;↕ full-replace on ID collision (project overrides org)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;project  (.kittify/doctrine/)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Precedence: &lt;code dir=&quot;auto&quot;&gt;shipped &amp;#x3C; org &amp;#x3C; project&lt;/code&gt;. Project teams retain full override authority.
Org-layer overrides of shipped artifacts surface as advisory warnings in &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt;, never hard errors.&lt;/p&gt;
&lt;h3 id=&quot;drg-layer-model&quot;&gt;DRG layer model&lt;/h3&gt;
&lt;p&gt;The DRG (&lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt;) gains the same three-layer treatment. Additionally, the shipped and org
graphs support &lt;strong&gt;multi-file loading&lt;/strong&gt;: a &lt;code dir=&quot;auto&quot;&gt;doctrine/drg/&lt;/code&gt; directory of &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; fragments
is merged before the layer merge, replacing the current single-file constraint.&lt;/p&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;shipped graph fragments  →  merge  →  shipped DRGGraph&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;org graph-extensions.yaml           →  additive layer&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;project graph-extensions.yaml       →  additive layer&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;                                    &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;=  resolved DRGGraph&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;h3 id=&quot;mission-type-governance-resolution&quot;&gt;Mission-type governance resolution&lt;/h3&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;project charter policy&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ shipped mission-type profile  (src/doctrine/mission_type_profiles/&amp;#x3C;type&gt;.profile.yaml)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ org mission-type override     (org layer, if present)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span class=&quot;indent&quot;&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;  &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;+ mission-instance addendum     (kitty-specs/&amp;#x3C;mission&gt;/governance-addendum.yaml, if present)&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Selection key: &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/meta.json&lt;/code&gt;.
No fallback to &lt;code dir=&quot;auto&quot;&gt;software-dev-default&lt;/code&gt; for non-software missions.&lt;/p&gt;
&lt;h3 id=&quot;governance-references&quot;&gt;Governance references&lt;/h3&gt;
&lt;p&gt;Charter metadata gains an optional &lt;code dir=&quot;auto&quot;&gt;governance_references&lt;/code&gt; list. Each entry is a repo-root-scoped
path (file or directory). &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; includes referenced content as bounded excerpts.
Missing paths produce a warning in &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;; they do not block resolution.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;key-design-decisions&quot;&gt;Key design decisions&lt;/h2&gt;













































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Decision&lt;/th&gt;&lt;th&gt;Choice&lt;/th&gt;&lt;th&gt;Rationale&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Org-layer slot type&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;org_root: Path | None&lt;/code&gt; in config; &lt;code dir=&quot;auto&quot;&gt;org_roots: list[Path]&lt;/code&gt; internally&lt;/td&gt;&lt;td&gt;Exposes single-org UX; internally generalisable to multi-org without API break&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;ID collision semantics&lt;/td&gt;&lt;td&gt;Full-replace (org replaces shipped; project replaces org)&lt;/td&gt;&lt;td&gt;Simpler authoring contract than field-level merge; authors need to substitute, not patch&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Remote fetch model&lt;/td&gt;&lt;td&gt;Pull-once → validate → write local snapshot; no runtime remote calls&lt;/td&gt;&lt;td&gt;Deterministic in CI/CD; offline-safe&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Multi-file DRG&lt;/td&gt;&lt;td&gt;Directory of &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; fragments merged before layer merge&lt;/td&gt;&lt;td&gt;Scoped diffs; enables token-efficient partial loading&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Mission-type key&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, not inferred from &lt;code dir=&quot;auto&quot;&gt;template_set&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Explicit; removes software-dev bleed-through&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Governance references&lt;/td&gt;&lt;td&gt;Path-list in charter; bounded excerpts in context&lt;/td&gt;&lt;td&gt;No copy requirement; no equality enforcement&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Symlinked charter.md&lt;/td&gt;&lt;td&gt;Guard on &lt;code dir=&quot;auto&quot;&gt;charter generate --force&lt;/code&gt;; error + remediation hint&lt;/td&gt;&lt;td&gt;Explicit over silent&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id=&quot;mission-structure&quot;&gt;Mission structure&lt;/h2&gt;
&lt;p&gt;This capability is delivered in two chained missions.&lt;/p&gt;
&lt;h3 id=&quot;mission-a--layered-doctrine-resolution-infrastructure&quot;&gt;Mission A — Layered Doctrine Resolution (infrastructure)&lt;/h3&gt;
&lt;p&gt;Closes #832. Prerequisite for Mission B.&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;WP&lt;/th&gt;&lt;th&gt;Scope&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;WP01&lt;/td&gt;&lt;td&gt;Multi-file DRG loading: &lt;code dir=&quot;auto&quot;&gt;load_graph(path_or_dir)&lt;/code&gt; + update 8 &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; call sites in &lt;code dir=&quot;auto&quot;&gt;charter/&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP02&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;BaseDoctrineRepository&lt;/code&gt; three-layer loading: &lt;code dir=&quot;auto&quot;&gt;_apply_org_overrides()&lt;/code&gt; between shipped and project&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP03&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DoctrineService&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;org_roots: list[Path]&lt;/code&gt;; all repository properties updated&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP04&lt;/td&gt;&lt;td&gt;Config model: &lt;code dir=&quot;auto&quot;&gt;doctrine.org&lt;/code&gt; block in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine fetch&lt;/code&gt; command&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP05&lt;/td&gt;&lt;td&gt;Observability: &lt;code dir=&quot;auto&quot;&gt;&quot;source&quot;: &quot;org&quot;&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; lists org artifacts; &lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt; advisory warning on org-overrides-shipped&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;mission-b--governance-aware-context-application-layer&quot;&gt;Mission B — Governance-Aware Context (application layer)&lt;/h3&gt;
&lt;p&gt;Closes #883 and #1013. Depends on Mission A.&lt;/p&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;WP&lt;/th&gt;&lt;th&gt;Scope&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;WP01&lt;/td&gt;&lt;td&gt;Shipped mission-type governance profiles (&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;) as &lt;code dir=&quot;auto&quot;&gt;*.profile.yaml&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP02&lt;/td&gt;&lt;td&gt;Mission-type resolution in &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;: key off &lt;code dir=&quot;auto&quot;&gt;meta.json mission_type&lt;/code&gt;; no software-dev fallback for non-software missions&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP03&lt;/td&gt;&lt;td&gt;Charter &lt;code dir=&quot;auto&quot;&gt;governance_references&lt;/code&gt;: schema field, context injection, missing-path warning in &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WP04&lt;/td&gt;&lt;td&gt;Charter write guards: symlinked &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; detection in &lt;code dir=&quot;auto&quot;&gt;charter generate --force&lt;/code&gt;; legacy-path cleanup (&lt;code dir=&quot;auto&quot;&gt;constitution&lt;/code&gt;-era paths removed from current runtime checks)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h2 id=&quot;non-goals&quot;&gt;Non-goals&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;CLI plugin system for runtime behaviour (doctrine scopes agent evaluation, not CLI execution).&lt;/li&gt;
&lt;li&gt;Multi-org layers (company + business-unit config UX) — structurally supported by the
&lt;code dir=&quot;auto&quot;&gt;org_roots: list&lt;/code&gt; internal model but deferred.&lt;/li&gt;
&lt;li&gt;External-authoritative charter path (configured alternate path for &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;) — deferred
per ADR &lt;code dir=&quot;auto&quot;&gt;2026-05-08-1-charter-governance-center-and-external-governance-docs&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Content-equality enforcement between governance references and &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Automatic org-layer upgrade (version pinning and upgrade are explicit operator actions).&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
