<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/4.x/2026-10-06-2-charter-offering-active-charter-and-activation-presets/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-10-06-2-charter-offering-active-charter-and-activation-presets/</id>
  <title>ADR: charter offering, active charter and activation presets</title>
  <updated>2026-10-06T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/4.x/2026-10-06-2-charter-offering-active-charter-and-activation-presets/"/>
  <summary>A Charter Pack bundles charter components with activation presets applied by charter activate; the doctrine names are cut over with no aliases or shims.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-10-06&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (repository owner).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/3732&quot;&gt;#3732&lt;/a&gt; (rename doctrine packs to charter packs), with &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5323&quot;&gt;#5323&lt;/a&gt; and &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4400&quot;&gt;#4400&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer or agent executing the #3732 rename, or changing pack loading, charter activation, the &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; CLI groups, or the shipped &lt;code dir=&quot;auto&quot;&gt;spk-*&lt;/code&gt; skills.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;PR #3791 settled two words for the rename of “doctrine pack”: &lt;strong&gt;Charter Pack&lt;/strong&gt; for the offered collection, and &lt;strong&gt;Pack Default Charter&lt;/strong&gt; for the older meaning of “charter pack”. Classifying every occurrence at &lt;code dir=&quot;auto&quot;&gt;b327f5bb&lt;/code&gt; showed that this was not enough to rename safely:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;“charter pack” has three meanings in the code, not two.&lt;/strong&gt; The config key &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt; and the directory &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; already mean the offered collection. &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack list|path|apply&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/packs/{default,minimal}.yaml&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;3.2.0rc35_default_charter_pack&lt;/code&gt; migration mean a ready-made activation set. &lt;code dir=&quot;auto&quot;&gt;CharterPackManager&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CharterPackConfigError&lt;/code&gt; and the error code &lt;code dir=&quot;auto&quot;&gt;CHARTER_PACK_CONFIG_INVALID&lt;/code&gt; mean a project’s own activation state. The contract had no word for the third meaning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI name was taken twice over.&lt;/strong&gt; Retiring &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; sends &lt;code dir=&quot;auto&quot;&gt;doctrine pack validate|assemble&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;charter pack&lt;/code&gt;, which already holds the activation-set commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The “default charter pack” is a drifted copy.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; says it lists every built-in artifact id; it lists about 200, and at &lt;code dir=&quot;auto&quot;&gt;b327f5bb&lt;/code&gt; it missed 91 shipped artifacts across seven kinds (matching each file by YAML &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; or filename stem; a stricter match finds about 100). Nothing regenerates it or compares it to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt;. The rc35 upgrade migration and &lt;code dir=&quot;auto&quot;&gt;charter pack apply default&lt;/code&gt; write it into &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, where a present &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key is an allowlist, so those projects silently lose every newer built-in (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5323&quot;&gt;#5323&lt;/a&gt;). Three activation-promotion callers narrow an absent key with the same file (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4400&quot;&gt;#4400&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The presets are not part of any pack.&lt;/strong&gt; They are registered in a hard-coded &lt;code dir=&quot;auto&quot;&gt;BUILTIN_PACKS&lt;/code&gt; map in &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; and live outside &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt;; the pack descriptor does not know them. Packs are going to ship from the spec-kitty public-packs sidecar repository, where a code-registered preset cannot exist.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-*&lt;/code&gt; skill family mixes two things.&lt;/strong&gt; Four skills are charter governance (charter, glossary, profile loading, the REASONS canvas); three are working practices unrelated to the charter (bulk-edit classification, semantic compression, show-me visuals). An older &lt;code dir=&quot;auto&quot;&gt;spec-kitty-*&lt;/code&gt; name layer still ships beside them and often holds the real content.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Earlier renames left compatibility layers with no end date.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; group, the &lt;code dir=&quot;auto&quot;&gt;doctrine.*&lt;/code&gt; config keys and the &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; read root each warn once and keep working, with no removal milestone, so in practice they are permanent.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/charter.md&lt;/code&gt; cites ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-2&lt;/code&gt; (§74, §76–77) for the earlier definitions, but that ADR is not in the repository. This ADR therefore states the vocabulary in full rather than amending it.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;1-the-model-charter-offering-and-active-charter&quot;&gt;1. The model: charter offering and active charter&lt;/h3&gt;
&lt;p&gt;The charter has two sides, matching the existing package split &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/&lt;/code&gt;:&lt;/p&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Term&lt;/th&gt;&lt;th&gt;Meaning&lt;/th&gt;&lt;th&gt;Replaces&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Charter offering&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Everything that is &lt;em&gt;offered&lt;/em&gt; to a project: the Charter Packs it can draw from.&lt;/td&gt;&lt;td&gt;“doctrine” as the name of the offer-side tier&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Charter Pack&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A distributable bundle of interconnected charter components (artifacts and their DRG edges) together with a set of &lt;strong&gt;activation presets&lt;/strong&gt;. An org pack may also enforce activations (&lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt;).&lt;/td&gt;&lt;td&gt;“doctrine pack”&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Activation preset&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A named set of activations that a Charter Pack ships, applied to a project by activating it.&lt;/td&gt;&lt;td&gt;“Pack Default Charter”, and the old meaning of “charter pack”&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Active charter&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;What a project has activated: its &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; keys and &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt;.&lt;/td&gt;&lt;td&gt;the third meaning of “charter pack” (&lt;code dir=&quot;auto&quot;&gt;CharterPackManager&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CHARTER_PACK_CONFIG_INVALID&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Charter Bundle&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Unchanged: the materialised &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; tree.&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;“Active” and “inactive” still describe a single artefact’s state (“an active directive”). The glossary guard that “active” never describes bundle state is amended: &lt;strong&gt;active charter&lt;/strong&gt; names the project’s activated set as a whole.&lt;/p&gt;
&lt;h3 id=&quot;2-applying-a-preset-is-an-activation&quot;&gt;2. Applying a preset is an activation&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;spec-kitty charter activate --pack &amp;#x3C;pack&gt; --preset &amp;#x3C;preset&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;&lt;code dir=&quot;auto&quot;&gt;--pack&lt;/code&gt; defaults to &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt;. The built-in pack ships two presets:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt;&lt;/strong&gt;: every built-in artifact, plus the built-in mission types. It is expressed as &lt;em&gt;no per-kind restriction&lt;/em&gt; (the per-kind keys stay absent, which already means “all built-ins”), never as a list of ids, so it cannot drift from the shipped inventory.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;minimal&lt;/code&gt;&lt;/strong&gt;: the curated small baseline (today’s &lt;code dir=&quot;auto&quot;&gt;minimal.yaml&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Skipping charter activation during &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; is the same as &lt;code dir=&quot;auto&quot;&gt;charter activate --pack built-in --preset default&lt;/code&gt;. Today’s fresh &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; already behaves this way for artifact kinds: it writes only &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; and leaves the per-kind keys absent. It reads that mission-type list from &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/packs/default.yaml&lt;/code&gt; and fails closed when the file is missing (&lt;code dir=&quot;auto&quot;&gt;provision_default_mission_type_activations&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DefaultCharterPackMissingError&lt;/code&gt;); that read moves with the preset, to the built-in pack’s &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; preset.&lt;/p&gt;
&lt;h3 id=&quot;3-presets-are-pack-data&quot;&gt;3. Presets are pack data&lt;/h3&gt;
&lt;p&gt;A preset lives inside its pack, next to the pack’s components, and is discovered from the pack, for the built-in pack and for any fetched or org pack alike. There is no code registry of presets. &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/packs/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;BUILTIN_PACKS&lt;/code&gt; are removed. The pack descriptor field &lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt;, which described a separate pack accompanying a doctrine pack, is retired: a pack carries its own presets.&lt;/p&gt;
&lt;h3 id=&quot;4-the-cli&quot;&gt;4. The CLI&lt;/h3&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Before&lt;/th&gt;&lt;th&gt;After&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;charter pack apply &amp;#x3C;name&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --pack &amp;#x3C;pack&gt; --preset &amp;#x3C;preset&gt;&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack list&lt;/code&gt; (presets only)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack list&lt;/code&gt;: packs and the presets each one ships&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack path &amp;#x3C;name&gt;&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack path &amp;#x3C;pack&gt;&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine pack validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine pack assemble&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter pack assemble&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a top-level &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; subcommand; it checks the active charter, not a pack&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine regenerate-graph&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine asset&lt;/code&gt;&lt;/td&gt;&lt;td&gt;a home under &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine mission-type list&lt;/code&gt;&lt;/td&gt;&lt;td&gt;already replaced by &lt;code dir=&quot;auto&quot;&gt;charter mission-type list --include-inactive&lt;/code&gt;; removed with the group&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; group&lt;/td&gt;&lt;td&gt;removed once its last command has moved&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack&lt;/code&gt; holds operations on Charter Packs (the offering). Activation operations, presets included, stay on &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;5-skills&quot;&gt;5. Skills&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Before&lt;/th&gt;&lt;th&gt;After&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;spk-doctrine-charter&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-charter-governance&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-glossary&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-charter-glossary&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-profile-load&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-charter-profile-load&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-spdd-reasons&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-charter-spdd-reasons&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-bulk-edit&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-practice-bulk-edit&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-semantic-compression&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-practice-semantic-compression&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-doctrine-show-me&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;spk-practice-show-me&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spk-practice-*&lt;/code&gt; is a new family for working practices that apply in any mission. The older &lt;code dir=&quot;auto&quot;&gt;spec-kitty-*&lt;/code&gt; skills (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter-doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-glossary-context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-bulk-edit-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-spdd-reasons&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ad-hoc-profile-load&lt;/code&gt;, and the rest of that layer) are folded into the &lt;code dir=&quot;auto&quot;&gt;spk-*&lt;/code&gt; skill they back and deleted. Each skill ends with one name.&lt;/p&gt;
&lt;h3 id=&quot;6-names-that-stay&quot;&gt;6. Names that stay&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine-daphne&lt;/code&gt;&lt;/strong&gt; agent profile keeps its id and name. It is a known persona already in use; “doctrine” there is part of a name, not the retired tier.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“Doctrine” as the governance content itself&lt;/strong&gt; (the substance of a directive or tactic) stays where it is written as content.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_039&lt;/code&gt; (named for a person) and every historical record (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, released changelog sections, ADRs, dated reports, the archive) are unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;7-full-cutover-no-aliases-no-shims&quot;&gt;7. Full cutover: no aliases, no shims&lt;/h3&gt;
&lt;p&gt;Earlier renames kept the old names working for backwards compatibility. The result is a mixed bag of naming and code structures: agents and human contributors meet two names for one thing, and users’ harnesses contradict themselves because one surface uses the old name while another uses the new one. This rename therefore does not repeat that approach. The old names are removed, not deprecated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;No alias commands, alias skills or redirecting stubs. An old command name fails as an unknown command.&lt;/li&gt;
&lt;li&gt;The existing compatibility layers are removed: the deprecated &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; group (after its commands move), the read-side fallbacks for the &lt;code dir=&quot;auto&quot;&gt;doctrine.org.packs&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;governance.doctrine.*&lt;/code&gt; config keys, and the &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; read-root fallback.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Persisted project state is rewritten once, not shimmed&lt;/strong&gt; (confirmed by the deciders: a one-time migration is not a compatibility layer). An upgrade migration rewrites legacy config keys and moves &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; during &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;. The same migration replaces a project’s &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; lists that equal the drifted &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; contents with the &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; preset’s meaning (key absent), so projects stop losing newer built-ins. After the migration there is no read-side compatibility. A project that has not been upgraded gets an error naming &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Good:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;One meaning per word on every surface: CLI, config, code, skills, docs.&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; preset cannot drift, because it lists nothing.&lt;/li&gt;
&lt;li&gt;Presets work for packs fetched from the public-packs sidecar repository, not only for the built-in one.&lt;/li&gt;
&lt;li&gt;Fixes #5323 and #4400 by construction instead of by re-listing ids.&lt;/li&gt;
&lt;li&gt;Removes four permanent compatibility layers instead of adding more.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Bad:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A breaking release for anyone who scripts &lt;code dir=&quot;auto&quot;&gt;charter pack apply&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine …&lt;/code&gt; or a renamed skill. The changelog carries a Before/After table, and the generated agent command and skill copies are regenerated in the same change.&lt;/li&gt;
&lt;li&gt;A project that skips &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; stops at the first command, with an error naming the fix.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Neutral:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/doctrine/&lt;/code&gt; module path and internal &lt;code dir=&quot;auto&quot;&gt;Doctrine*&lt;/code&gt; identifiers are renamed as internal refactors under the same occurrence map; they are not consumer contracts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;execution&quot;&gt;Execution&lt;/h2&gt;
&lt;p&gt;The rename runs as the #3732 governed mission. Its occurrence map is the classification ledger from the 2026-10-06 run (posted on #3732); this ADR is the naming contract the map binds to.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-10-06-rulings-from-the-mission-specification&quot;&gt;Amendment 2026-10-06: rulings from the mission specification&lt;/h2&gt;
&lt;p&gt;The #3732 mission specification (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/charter-pack-cutover-01M491G6/spec.md&lt;/code&gt;) surfaced ten further questions after its adversarial review. The deciders ruled on them the same day:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine_pack_id&lt;/code&gt; is renamed to &lt;code dir=&quot;auto&quot;&gt;charter_pack_id&lt;/code&gt;.&lt;/strong&gt; The upgrade migration rewrites project state; the &lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt; schema version is bumped and validation names the field to change in an org pack.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Packs that still carry &lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt; are rejected&lt;/strong&gt; with an error naming the field to delete. The public-packs sidecar repository receives a pull request. A validation message that names a replacement is not a compatibility layer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A removed command fails with the plain unknown-command error.&lt;/strong&gt; No hint, stub or hidden group; the changelog and the migration runbook carry the message.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;organisation_packs&lt;/code&gt; legacy key is removed&lt;/strong&gt; and migrated with the other legacy keys.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Compatibility residue unrelated to the doctrine vocabulary&lt;/strong&gt; (for example the &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt; no-op) is out of scope and tracked separately.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Applying a preset over customised activation lists is refused without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt;, with the per-key difference printed. The applied preset name is not persisted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;§5 is narrowed for this mission:&lt;/strong&gt; only the older skills that back the renamed &lt;code dir=&quot;auto&quot;&gt;spk-*&lt;/code&gt; skills (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter-doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-glossary-context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-bulk-edit-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-spdd-reasons&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ad-hoc-profile-load&lt;/code&gt;) are folded and deleted. The rest of the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-*&lt;/code&gt; layer follows in a separate mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt; becomes &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter consistency-check&lt;/code&gt;&lt;/strong&gt;, not &lt;code dir=&quot;auto&quot;&gt;charter check&lt;/code&gt;, to stay clear of &lt;code dir=&quot;auto&quot;&gt;validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lint&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;bundle validate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/doctrine/&lt;/code&gt; is split by meaning, not renamed.&lt;/strong&gt; It holds code only (no charter content). Pack model and tooling (descriptor, manifest, built-in manifest, lineage, validator, assembler) move to &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/packs/&lt;/code&gt;; org charter composition (&lt;code dir=&quot;auto&quot;&gt;org_charter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;org_charter_loader&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;config&lt;/code&gt;) moves to &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/&lt;/code&gt;; the fetch and scaffold adapters (&lt;code dir=&quot;auto&quot;&gt;sources/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;snapshot&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;template_render/&lt;/code&gt;) move to &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/charter_packs/&lt;/code&gt;. Layer-root and org-chain resolution moves into &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, and the architectural boundary exemption for the old package is deleted rather than carried over.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The cutover ships as one mission and one pull request&lt;/strong&gt;, because a cutover without compatibility layers cannot ship half.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The “Neutral” consequence above (“the &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/doctrine/&lt;/code&gt; module path … renamed as internal refactors”) is superseded by ruling 9.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-10-19-synthesized-tactics-and-activation-lists&quot;&gt;Amendment 2026-10-19: synthesized tactics and activation lists&lt;/h2&gt;
&lt;p&gt;The charter-governance-resolution Mission (#6404-#6408) settled four points about how activation lists treat synthesized tactics. They refine the activation model above without changing the absent-key default.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Synthesized “how we apply” tactics are reach-only (operator decision 2026-10-18, #6404).&lt;/strong&gt; A tactic that synthesis created and linked from its directive with &lt;code dir=&quot;auto&quot;&gt;directive --suggests--&gt; tactic&lt;/code&gt; is never a traversal root. It is delivered only while its directive is active, even when it appears in an explicit &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt; list. Hand-authored tactics and org-required tactics stay roots.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesis appends, and never creates the key.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt; append the tactic ids a run creates to a present &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt; list. They never create the key, so absent-key semantics are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An operator’s removal sticks (operator decision 2026-10-19).&lt;/strong&gt; A tactic the operator removed from &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt; is not silently re-added. Synthesis appends a tactic only the first time it creates it, and records every tactic it has created in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-tactics.yaml&lt;/code&gt;, also when the key is absent. A later run that regenerates the tactic, after a &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; or a deleted manifest, does not append it again. A removed tactic is also not delivered through its directive. Only the operator brings it back (&lt;code dir=&quot;auto&quot;&gt;charter activate tactic &amp;#x3C;id&gt;&lt;/code&gt;). Org-required (enforced) tactics stay in force regardless. If the record cannot be read, synthesis appends nothing and warns.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Narrowing is opt-in.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter activate --only&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter interview --narrow-activation&lt;/code&gt; (#6408) set a kind’s list to the selection plus org-required ids. The absent-key default and the preserve-don’t-narrow rule are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reach-only and removal-sticks cover synthesized styleguides (operator decision 2026-10-19, #6442).&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;testing_philosophy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;quality_gates&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;documentation_policy&lt;/code&gt; interview sections source their styleguide from a fixed directive (DIRECTIVE_034, DIRECTIVE_030 and DIRECTIVE_037). Synthesis links it with &lt;code dir=&quot;auto&quot;&gt;directive --suggests--&gt; styleguide&lt;/code&gt;, only when that directive is in the run’s DRG snapshot. Such a styleguide follows points 1 to 3 above: it is never a traversal root, it is delivered only while its directive is in force (also with an explicit &lt;code dir=&quot;auto&quot;&gt;activated_styleguides&lt;/code&gt; list or an absent key), it is appended to an explicit &lt;code dir=&quot;auto&quot;&gt;activated_styleguides&lt;/code&gt; list only the first time it is created, and an absent key stays absent. Unsourced styleguides (&lt;code dir=&quot;auto&quot;&gt;language_scope&lt;/code&gt;, hand-authored) keep today’s activation semantics, and org-required styleguides stay roots. The record is now the per-kind &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;created_tactics&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;created_styleguides&lt;/code&gt;). It also reads the unreleased tactic-only &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-tactics.yaml&lt;/code&gt;, which is never written again. If either record cannot be read, synthesis appends nothing for any kind and warns. A source-side &lt;code dir=&quot;auto&quot;&gt;styleguide --applies--&gt; X&lt;/code&gt; overlay edge on a synthesized styleguide is legacy: reconcile strips and reports it. Styleguides that already sit in the synthesis manifest are not appended on the first recording run (they were not created for the first time by it), so they stay as delivered today.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;amendment-2026-10-19-presets-and-synthesis-under-the-activation-ledger&quot;&gt;Amendment 2026-10-19: presets and synthesis under the activation ledger&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/&quot;&gt;ADR 2026-10-19-1&lt;/a&gt; refines how presets and synthesis treat a deactivated artifact. The absent-key default is unchanged.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;A preset without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; never touches deny keys.&lt;/strong&gt; A denied id the preset lists stays subtracted, and the preset warns and names it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset X --force&lt;/code&gt; clears exclusions&lt;/strong&gt; for the ids the preset lists, and the output names them. It is one of the four explicit choices that may change a deny-list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesis never re-adds a denied tactic or styleguide&lt;/strong&gt;, also on first creation. This adds to rulings 3 and 5 of Amendment 2026-10-19 above.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The created-artifacts record stays and is not an activation surface.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt; (and the legacy &lt;code dir=&quot;auto&quot;&gt;synthesized-tactics.yaml&lt;/code&gt; it still reads) records what synthesis created. It does not say what is in force, and the ledger does not read it.&lt;/li&gt;
&lt;/ol&gt;</content>
</entry>
