<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/architecture/org-doctrine-layer/">
  <id>https://docs.spec-kitty.ai/architecture/org-doctrine-layer/</id>
  <title>Understanding the Org Layer of the Charter Offering</title>
  <updated>2026-10-19T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/architecture/org-doctrine-layer/"/>
  <summary>How the three-layer charter offering resolves built-in, org, and project artifacts, how provenance tracking works, and how org charter policy composes with the project charter.</summary>
  <content type="html">&lt;span id=&quot;understanding-the-org-layer-of-the-charter-offering&quot;&gt;&lt;/span&gt;
&lt;p&gt;Spec Kitty resolves governance doctrine through the three layers of the &lt;strong&gt;charter offering&lt;/strong&gt;:
the &lt;strong&gt;built-in&lt;/strong&gt; Charter Pack shipped with the CLI, an optional &lt;strong&gt;org&lt;/strong&gt; layer of Charter Packs
fetched from one or more remote sources, and the &lt;strong&gt;project layer&lt;/strong&gt; maintained in the
repository’s own &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;. This document
explains the model, the resolution rules, the provenance tags you will see in tooling
output, and the architectural boundary that keeps the three layers cleanly separated.&lt;/p&gt;
&lt;p&gt;For step-by-step instructions on producing a pack, see &lt;a href=&quot;/guides/how-to/governance/create-an-org-doctrine-pack/&quot;&gt;How to create an org Charter
Pack&lt;/a&gt;. For migration guidance from a local
overlay, see &lt;a href=&quot;/migrations/doctrine-local-overlay-to-org-layer/&quot;&gt;Migrating shared doctrine to the org layer&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-three-layer-model&quot;&gt;The three-layer model&lt;/h2&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;┌────────────────────────────────────────────────────────────┐&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 layer:   .kittify/charter-packs/                  │  ← highest precedence&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-local artifacts and exceptions)                  │&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;├────────────────────────────────────────────────────────────┤&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 layer:       configured packs (e.g. ~/.kittify/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;│  (company-wide directives, profiles, 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 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 style=&quot;--0:#d6deeb;--1:#403f53&quot;&gt;│  Built-in layer:  shipped with the spec-kitty package      │  ← lowest precedence&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;│  (sane defaults for every spec-kitty project)              │&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;└────────────────────────────────────────────────────────────┘&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Each layer is a structured set of YAML artifacts — directives, tactics, styleguides,
toolguides, paradigms, procedures, agent profiles, mission step contracts, and DRG
graph extensions. Layers share the same schemas. Their only difference is &lt;strong&gt;where they
live&lt;/strong&gt; and &lt;strong&gt;how they are produced&lt;/strong&gt;.&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Layer&lt;/th&gt;&lt;th&gt;Source&lt;/th&gt;&lt;th&gt;Owned by&lt;/th&gt;&lt;th&gt;Activation&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Built-in&lt;/td&gt;&lt;td&gt;spec-kitty package&lt;/td&gt;&lt;td&gt;CLI maintainers&lt;/td&gt;&lt;td&gt;Always active&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Org&lt;/td&gt;&lt;td&gt;Remote pack(s) declared in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Org governance teams&lt;/td&gt;&lt;td&gt;Opt-in per project&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Project&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; in the repository&lt;/td&gt;&lt;td&gt;Project maintainers&lt;/td&gt;&lt;td&gt;Always active when present&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The org layer is &lt;strong&gt;purely additive&lt;/strong&gt;. Projects that do not declare an org pack are
unaffected by this feature — the built-in plus project model continues to work exactly
as it did before.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;why-the-org-layer-exists&quot;&gt;Why the org layer exists&lt;/h2&gt;
&lt;p&gt;Before the org layer, an organisation that wanted to share governance across many
projects had two unattractive options:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Fork the CLI&lt;/strong&gt; to embed company-specific directives into the built-in layer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Copy/paste&lt;/strong&gt; governance artifacts into every project’s &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Both approaches drift over time. Fork maintenance is painful; copy/paste means each
project carries a stale snapshot of the policy.&lt;/p&gt;
&lt;p&gt;The org layer solves this by giving organisations a versioned, PR-governed,
independently-released home for their doctrine that any number of projects can consume
without per-project bookkeeping. A security team can ship &lt;code dir=&quot;auto&quot;&gt;security-v2.1.0&lt;/code&gt;, an
architecture team can ship &lt;code dir=&quot;auto&quot;&gt;architecture-v1.4.0&lt;/code&gt;, and a project consumes both by
listing them in its config.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;precedence-and-resolution&quot;&gt;Precedence and resolution&lt;/h2&gt;
&lt;p&gt;When resolution traverses the three layers, it walks them in order — built-in first,
then each configured org pack in declaration order, finally project — and applies
&lt;strong&gt;full-replace semantics on ID collision&lt;/strong&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Full-replace means&lt;/strong&gt;: if an artifact ID exists in a higher-precedence layer, that
artifact entirely replaces the lower-precedence one. There is no field-level merging
across layers. The higher-layer artifact stands or falls on its own.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;within-the-org-layer&quot;&gt;Within the org layer&lt;/h3&gt;
&lt;p&gt;If you configure multiple org packs, declaration order determines precedence within
the org layer. The &lt;strong&gt;last entry has the highest precedence&lt;/strong&gt; — the convention is
“later wins.”&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;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;charter_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&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;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;name&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;architecture&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;# lower precedence&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:#ECC48D;--1:#3B61B0&quot;&gt;~/.kittify/org/architecture/&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;name&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;security&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;# higher precedence (declared later)&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:#ECC48D;--1:#3B61B0&quot;&gt;~/.kittify/org/security/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;If both packs define &lt;code dir=&quot;auto&quot;&gt;acme-001-secret-handling&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;security&lt;/code&gt; pack’s version wins.&lt;/p&gt;
&lt;p&gt;The same rule holds for every dependency-graph (DRG) node an org pack declares in
&lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;, whether or not the node also exists in the built-in pack: the
later-declared pack’s node replaces the earlier pack’s. A relationship (edge) both
packs declare is kept once, with the later pack’s provenance and &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;. Each
replacement is logged as a warning naming both packs. When the merge also refuses
the packs for another reason, the replacement is listed among the reported conflicts
as a &lt;code dir=&quot;auto&quot;&gt;node_override&lt;/code&gt; whose &lt;code dir=&quot;auto&quot;&gt;conflicting_layers&lt;/code&gt; names the overridden pack first.
Edges are additive: replacing a node does not remove the edges an earlier pack
declared from it. (Before 4.0.0rc8 the first-declared pack’s node won for a node the
built-in pack does not ship; see the changelog.)&lt;/p&gt;
&lt;h3 id=&quot;across-layers&quot;&gt;Across layers&lt;/h3&gt;
&lt;p&gt;Project beats org. Org beats built-in. The project layer is always free to override
an org artifact for legitimate exceptions. When a project artifact has the same ID as
a higher layer (org or built-in), &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint&lt;/code&gt; surfaces an advisory so
the team can confirm the override is intentional.&lt;/p&gt;
&lt;h4 id=&quot;activation-tokens-a-file-name-beats-a-declared-id&quot;&gt;Activation tokens: a file name beats a declared ID&lt;/h4&gt;
&lt;p&gt;An activation token (an entry of an &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; list in
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;) is matched against file names (stems) first,
across every layer, and only then against declared IDs. So a file named &lt;code dir=&quot;auto&quot;&gt;foo&lt;/code&gt; in
any layer wins over another artifact that declares &lt;code dir=&quot;auto&quot;&gt;id: foo&lt;/code&gt;, regardless of which
layer is higher: a project file &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024.directive.yaml&lt;/code&gt; that declares
&lt;code dir=&quot;auto&quot;&gt;id: DIRECTIVE_901&lt;/code&gt; takes the token &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024&lt;/code&gt;, and the built-in directive that
declares &lt;code dir=&quot;auto&quot;&gt;id: DIRECTIVE_024&lt;/code&gt; is not admitted by it. The reverse holds too: a
lower-layer file name beats a higher-layer declared ID. Layer order decides between
two artifacts with the same ID, not between a file name and a declared ID.&lt;/p&gt;
&lt;p&gt;When two layers’ files share a file name but declare different IDs, writers refuse
the colliding ID (its file name would select the other artifact); rename the org or
project file (a built-in file cannot be renamed).&lt;/p&gt;
&lt;p&gt;This behaviour is pinned by
&lt;code dir=&quot;auto&quot;&gt;tests/charter/activation/test_stem_first_gating_6459.py&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;tests/charter/activation/test_identity_index.py::test_lookup_is_stem_first_across_layers_then_declared_id&lt;/code&gt;
(#6459).&lt;/p&gt;
&lt;h4 id=&quot;field-level-merge-not-artifact-level-full-replace&quot;&gt;Field-level merge, not artifact-level full replace&lt;/h4&gt;
&lt;p&gt;When a higher layer declares an artifact ID that already exists in a lower layer,
the higher layer &lt;strong&gt;takes ownership&lt;/strong&gt; of the resolved artifact: its &lt;code dir=&quot;auto&quot;&gt;provenance&lt;/code&gt;
becomes that layer. But the merge is &lt;strong&gt;field-level&lt;/strong&gt;, not artifact-level full
replace:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fields &lt;strong&gt;present&lt;/strong&gt; in the higher layer’s YAML replace same-named fields in
the lower layer.&lt;/li&gt;
&lt;li&gt;Fields &lt;strong&gt;absent&lt;/strong&gt; from the higher layer fall through to the lower layer’s value.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;So an org override file that contains only &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;enforcement&lt;/code&gt;
inherits everything else (intent, scope, examples, …) from the built-in
definition. This keeps override YAML short and focused on what actually
changes. The trade-off is that operators must understand which fields are
inherited and which are overridden.&lt;/p&gt;
&lt;h4 id=&quot;collision-warnings-artifactlayercollisionwarning&quot;&gt;Collision warnings (&lt;code dir=&quot;auto&quot;&gt;ArtifactLayerCollisionWarning&lt;/code&gt;)&lt;/h4&gt;
&lt;p&gt;Because field-merge is silent by default, the resolver emits a
&lt;code dir=&quot;auto&quot;&gt;ArtifactLayerCollisionWarning&lt;/code&gt; whenever a higher layer shadows a lower-layer
artifact. The warning text records the artifact ID, the higher and lower
layers, and how many fields were replaced vs inherited:&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;Artifact override: directive DIRECTIVE_018 from project shadowed builtin&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;(3 field(s) replaced; 9 field(s) inherited).&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;These warnings are categorized as &lt;code dir=&quot;auto&quot;&gt;ArtifactLayerCollisionWarning&lt;/code&gt; (a
&lt;code dir=&quot;auto&quot;&gt;UserWarning&lt;/code&gt; subclass), so operators who maintain heavy overrides can
filter them via standard Python &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; machinery if desired.&lt;/p&gt;
&lt;h4 id=&quot;auditing-collisions-via-spec-kitty-doctor-charter-packs&quot;&gt;Auditing collisions via &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt;&lt;/h4&gt;
&lt;p&gt;To audit the full set of override collisions across the resolved charter
offering without parsing warning streams, run:&lt;/p&gt;
&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:#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;doctor&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;charter-packs&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The output includes a &lt;code dir=&quot;auto&quot;&gt;Collisions&lt;/code&gt; section that lists every shadowed
artifact (kind, ID, higher layer, lower layer, field counts), or reports
&lt;code dir=&quot;auto&quot;&gt;none — every artifact resolves from a single layer.&lt;/code&gt; when no overrides
are in play. The same data is available as a &lt;code dir=&quot;auto&quot;&gt;collisions&lt;/code&gt; array under
&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;See &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics.md&quot;&gt;ADR 2026-05-16-1&lt;/a&gt;
for the rationale behind this design.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;per-mission-type-governance-override&quot;&gt;Per-mission-type governance override&lt;/h2&gt;
&lt;p&gt;The same three-layer overlay stack is what carries &lt;strong&gt;per-mission-type governance
customisation&lt;/strong&gt; — the charter “activate and customise” step for a mission type.&lt;/p&gt;
&lt;p&gt;A project override for a mission type’s governance lives at:&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;.kittify/charter-packs/mission_types/&amp;#x3C;type&gt;/governance-profile.yaml&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Because it sits under &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;, it is an ordinary &lt;strong&gt;project-layer&lt;/strong&gt;
artifact resolved through the existing &lt;code dir=&quot;auto&quot;&gt;charter/offering/base.py&lt;/code&gt; overlay loader, giving it
the same three behaviours as every other overlaid artifact:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Builtin → org → project ordering.&lt;/strong&gt; The shipped mission-type governance is the
builtin layer; an org pack may layer on top; the project override wins last.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Field-level merge.&lt;/strong&gt; Fields present in the override replace same-named fields;
absent fields fall through from the lower layer — so an override that adjusts a
single selection need not restate the whole profile.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ArtifactLayerCollisionWarning&lt;/code&gt;.&lt;/strong&gt; The resolver emits the same collision
warning when the override shadows a lower layer, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt;
audits it alongside every other override.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Reusing the overlay stack is deliberate — it avoids duplicating the layer-merge
contract — but it is &lt;strong&gt;not zero-cost plumbing&lt;/strong&gt;. The &lt;code dir=&quot;auto&quot;&gt;base.py&lt;/code&gt; overlay loader keys
project artifacts on an &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; field and skips files that lack one, whereas
&lt;code dir=&quot;auto&quot;&gt;governance-profile.yaml&lt;/code&gt; keys on &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;. Wiring the profile onto the stack
therefore requires an adapter: either giving &lt;code dir=&quot;auto&quot;&gt;MissionTypeProfile&lt;/code&gt; an &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; and a
&lt;code dir=&quot;auto&quot;&gt;BaseArtifactRepository&lt;/code&gt; subclass, or a small explicit field-merge in the resolver.
That adapter is owned, tested work — not a free ride. Modulo that adapter, per-type
governance layering reuses rather than reinvents the merge contract in
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics.md&quot;&gt;ADR 2026-05-16-1&lt;/a&gt;.
Mission-type governance itself resolves through a single charter-mediated seam
keyed off &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;; this override is the project-tier customisation layer of
that seam. For the whole resolution model — the two governance grains, the reserved
slots for templates and gates, and the leak-closure invariant — see
&lt;a href=&quot;/architecture/mission-type-resolution/&quot;&gt;Mission-Type Resolution&lt;/a&gt; and
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/docs/adr/3.x/2026-07-14-2-doctrine-to-core-mission-type-resolution-unification.md&quot;&gt;ADR 2026-07-14-2&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;drg-composition&quot;&gt;DRG composition&lt;/h2&gt;
&lt;p&gt;The doctrine reference graph (DRG) is the typed graph that the runtime traverses to
select context for a given action. Each layer can contribute graph &lt;strong&gt;fragments&lt;/strong&gt;, and
they merge additively:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Built-in DRG nodes and edges are always present.&lt;/li&gt;
&lt;li&gt;Org packs contribute additional nodes and edges via &lt;code dir=&quot;auto&quot;&gt;drg/*.graph.yaml&lt;/code&gt; fragments.&lt;/li&gt;
&lt;li&gt;Project DRG fragments compose on top.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;DRG fragments from the org layer are &lt;strong&gt;additive only&lt;/strong&gt; — they may add new nodes and
new edges, but they must not remove or modify nodes from a lower layer. &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack validate&lt;/code&gt; enforces this and rejects packs whose DRG references dangle
or whose extensions try to delete built-in graph state.&lt;/p&gt;
&lt;p&gt;This rule is what keeps the three-layer composition safe: org packs cannot
silently weaken the built-in graph, and projects cannot accidentally weaken org
graph state without a visible override.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;source-attribution-provenance&quot;&gt;Source attribution (provenance)&lt;/h2&gt;
&lt;p&gt;Every artifact and DRG node carries a &lt;code dir=&quot;auto&quot;&gt;source&lt;/code&gt; tag once it is resolved:&lt;/p&gt;





















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Tag&lt;/th&gt;&lt;th&gt;Meaning&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;builtin&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Shipped with the CLI&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;org&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Loaded from a configured org pack&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;project&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Loaded from &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; in the repository&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Provenance shows up in two places you can inspect directly:&lt;/p&gt;
&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;# Per-action charter context (shows which artifacts apply)&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;uv&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;run&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&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;charter&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;context&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--action&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;implement&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--json&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&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;# Pack inventory (shows what is installed and where it came from)&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;uv&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;run&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&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;doctor&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;charter-packs&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--json&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;When you see an artifact tagged &lt;code dir=&quot;auto&quot;&gt;source: org&lt;/code&gt;, it tells you the artifact resolved
from one of the packs in your &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt; config — not from the project
overlay or the built-in defaults. That signal is what lets a team lead audit “is our
security directive actually live in this project?” without having to grep file trees.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;org-charter-composition&quot;&gt;Org charter composition&lt;/h2&gt;
&lt;p&gt;In addition to artifacts and DRG fragments, an org pack may include an
&lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt; at its root. This is a small, structured policy document that
composes with the project charter at interview time.&lt;/p&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt; schema has three meaningful fields:&lt;/p&gt;





















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Field&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;interview_defaults&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Pre-fill answers for the project charter interview. The user can still override during the interview.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;required_directives&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Directive IDs that the project charter is expected to honour. Surfaced as advisories during lint.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;governance_policies&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Free-form policy entries (e.g. minimum test coverage). Advisory-only in this release.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The merge across multiple packs follows the same “later wins” rule as artifacts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;interview_defaults&lt;/code&gt;: dict update; later packs overwrite earlier values.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;required_directives&lt;/code&gt;: union, preserving first-seen order.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;governance_policies&lt;/code&gt;: concatenated and deduplicated by &lt;code dir=&quot;auto&quot;&gt;(field, value)&lt;/code&gt;, keeping
the last occurrence.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Empty packs (no &lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt;) contribute no policy — they carry artifacts only.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Enforcement note&lt;/strong&gt;: In this release, &lt;code dir=&quot;auto&quot;&gt;enforcement&lt;/code&gt; values on
&lt;code dir=&quot;auto&quot;&gt;governance_policies&lt;/code&gt; are read but treated uniformly as advisory. Only the literal
string &lt;code dir=&quot;auto&quot;&gt;&quot;advisory&quot;&lt;/code&gt; is honoured today; other values parse and surface as advisories.
Future releases may add stronger enforcement modes; pack authors should write
&lt;code dir=&quot;auto&quot;&gt;enforcement: advisory&lt;/code&gt; explicitly to remain forward-compatible.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id=&quot;the-fetch-model&quot;&gt;The fetch model&lt;/h2&gt;
&lt;p&gt;Org packs are not resolved over the network at runtime. The &lt;code dir=&quot;auto&quot;&gt;charter fetch&lt;/code&gt; command
downloads or refreshes a &lt;strong&gt;local snapshot&lt;/strong&gt; under each pack’s configured &lt;code dir=&quot;auto&quot;&gt;local_path&lt;/code&gt;,
and every subsequent resolution reads from that snapshot.&lt;/p&gt;
&lt;p&gt;This shape was chosen deliberately:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI/CD safety&lt;/strong&gt;: pipelines do not depend on remote availability or auth.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Determinism&lt;/strong&gt;: a project produces the same context on every machine that has
fetched the same ref.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auditability&lt;/strong&gt;: the on-disk snapshot is the record of “what governance ran here.”&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter fetch&lt;/code&gt; is an explicit install/update step, not a background operation. If
your org publishes a new ref, you re-run &lt;code dir=&quot;auto&quot;&gt;charter fetch&lt;/code&gt; (or your IT system does)
to pick it up. This is the same shape as &lt;code dir=&quot;auto&quot;&gt;npm install&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;pip install&lt;/code&gt; — fetch is
the install step; resolution is offline.&lt;/p&gt;
&lt;p&gt;For git-managed packs, the local path is a normal working tree of the git clone
(&lt;code dir=&quot;auto&quot;&gt;.git/&lt;/code&gt; present). For HTTPS bundles and HTTP APIs, the snapshot is an atomic
replace of the directory with a &lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; recording the fetched version.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;architectural-boundary&quot;&gt;Architectural boundary&lt;/h2&gt;
&lt;p&gt;The org layer respects a strict layer rule:&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;kernel  ←  charter  ←  specify_cli&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; package implements DRG composition (&lt;code dir=&quot;auto&quot;&gt;load_validated_graph&lt;/code&gt;) and accepts
an explicit &lt;code dir=&quot;auto&quot;&gt;org_root&lt;/code&gt; argument when present. It must not import from
&lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;. The config-aware resolution — reading &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;
and turning it into a list of pack paths — lives in
&lt;code dir=&quot;auto&quot;&gt;charter.offering.drg.org_pack_config.resolve_org_roots&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;To preserve the boundary, &lt;code dir=&quot;auto&quot;&gt;charter.activation._drg_helpers._resolve_org_root()&lt;/code&gt; is an &lt;strong&gt;inert
stub&lt;/strong&gt; that always returns &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;. Real callers resolve the path
themselves and pass it explicitly. This pattern is documented in the source and
enforced by &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_layer_rules.py&lt;/code&gt; so that no future change can
silently introduce a circular dependency.&lt;/p&gt;
&lt;p&gt;If you encounter &lt;code dir=&quot;auto&quot;&gt;_resolve_org_root&lt;/code&gt; in the codebase and wonder why it is empty:
that is the intentional design. The real logic lives in &lt;code dir=&quot;auto&quot;&gt;resolve_org_roots&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;breaking-change-mission-b-missing-packs-hard-fail&quot;&gt;Breaking change (mission B): missing packs hard-fail&lt;/h2&gt;
&lt;p&gt;Prior to mission &lt;code dir=&quot;auto&quot;&gt;charter-mediated-doctrine-selection-01KRTZCA&lt;/code&gt;, an org pack
configured in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; whose &lt;code dir=&quot;auto&quot;&gt;local_path&lt;/code&gt; did not exist on disk was
silently skipped — resolution would degrade to the built-in + project layers
without surfacing the misconfiguration. This made stale pack entries and typoed
paths invisible until a missing artifact tripped a downstream lookup.&lt;/p&gt;
&lt;p&gt;As of this mission (FR-015), missing packs cause &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context&lt;/code&gt; and
every downstream command (including &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;) to fail loudly with a
message naming the pack and the missing path:&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;Org pack &apos;very-serious-developers&apos; configured at&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;&apos;/home/alice/.kittify/org/very-serious-developers&apos; not found. Either fetch the 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;(`spec-kitty charter fetch --pack &amp;#x3C;name&gt;`) or remove the entry from `.kittify/config.yaml`.&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The diagnostic is intentionally actionable — operators are given two concrete
remediation steps, and the error is raised by &lt;code dir=&quot;auto&quot;&gt;OrgPackMissingError&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/drg/org_pack_loader.py&lt;/code&gt;) so callers can catch and report it
in their own UIs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Migration&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; to enumerate configured packs and their
on-disk status.&lt;/li&gt;
&lt;li&gt;For each missing pack, either:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter fetch --pack &amp;#x3C;name&gt;&lt;/code&gt; to populate the snapshot, or&lt;/li&gt;
&lt;li&gt;Remove the entry from &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; to confirm a clean state before the next
&lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; build.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This behaviour is non-negotiable: silent fallback risked teams unknowingly
running without the governance their charter assumed. There is no opt-out flag.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;frequently-asked-questions&quot;&gt;Frequently asked questions&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Can I have multiple org layers?&lt;/strong&gt;
Yes — list any number of packs in &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt;. Within the org layer,
declaration order determines precedence (later wins).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Can a project override an org artifact?&lt;/strong&gt;
Yes. The project layer always wins. Use the override when you have a genuine
project-level exception; &lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt; will surface an advisory so the
override remains visible.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What if the org snapshot is missing on disk?&lt;/strong&gt;
As of mission &lt;code dir=&quot;auto&quot;&gt;charter-mediated-doctrine-selection-01KRTZCA&lt;/code&gt; (FR-015), this is a
&lt;strong&gt;hard error&lt;/strong&gt;. Earlier releases silently fell back to built-in + project; that
behaviour was hiding misconfigured packs and stale paths. See the breaking-change
section below for the migration path. &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; reports every
configured pack and flags any that are missing.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Is it safe to gitignore the snapshot directory?&lt;/strong&gt;
Yes — and that is the recommended pattern. &lt;code dir=&quot;auto&quot;&gt;charter fetch&lt;/code&gt; is the install step;
treating the snapshot as cache rather than source-controlled artifacts keeps the
repository small and ensures all consumers pull the same way.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Does the org layer change how the built-in Charter Pack is loaded?&lt;/strong&gt;
No. The built-in layer is unchanged. The org layer composes on top.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Where do I see which layer an artifact came from?&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;uv run spec-kitty charter context --action &amp;#x3C;action&gt; --json&lt;/code&gt; lists every resolved
artifact with its &lt;code dir=&quot;auto&quot;&gt;source&lt;/code&gt; tag. &lt;code dir=&quot;auto&quot;&gt;uv run spec-kitty doctor charter-packs --json&lt;/code&gt; lists
installed pack contents.&lt;/p&gt;
&lt;hr&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/how-to/governance/create-an-org-doctrine-pack/&quot;&gt;How to create an org Charter Pack&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/migrations/doctrine-local-overlay-to-org-layer/&quot;&gt;Migrating shared doctrine to the org layer&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/guides/how-to/governance/setup-governance/&quot;&gt;How to set up project governance&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/charter-synthesis-drg/&quot;&gt;Understanding Charter: Synthesis, DRG, and Governed Context&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/mission-type-resolution/&quot;&gt;Mission-Type Resolution&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
