<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/</id>
  <title>ADR: Sequence Charter-Activation-Driven Mission-Type Availability Ahead of Mission-Type-as-ArtifactKind; Land It With Mission-Tree Resolution Unification as One Slice</title>
  <updated>2026-08-05T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/"/>
  <summary>Sequences charter-activation-driven mission-type availability ahead of mission-type-as-ArtifactKind, landed with mission-tree resolution unification as one slice.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;The end-state the epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2466&quot;&gt;#2466&lt;/a&gt;
(“Doctrine/Charter extensibility &amp;#x26; pack ecosystem”) calls &lt;strong&gt;fully doctrine-provided,
charter-loaded mission types&lt;/strong&gt; — a single canonical mission-type source where a type is
&lt;em&gt;offered&lt;/em&gt; iff the charter activation set says so, and &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; is an ordinary peer
doctrine type with no filesystem-position-implies-availability logic anywhere — has been
&lt;strong&gt;repeatedly deferred across successive missions&lt;/strong&gt;. &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/3204&quot;&gt;PR #3204&lt;/a&gt;
(mission &lt;code dir=&quot;auto&quot;&gt;doctrine-consumer-surface-missions-extraction&lt;/code&gt;, closes
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3091&quot;&gt;#3091&lt;/a&gt;) is the latest instance: it
landed the &lt;em&gt;physical&lt;/em&gt; relocation of built-in mission data to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt;
and deferred everything else by explicit spec constraint (C-002).&lt;/p&gt;
&lt;p&gt;This ADR records &lt;strong&gt;why&lt;/strong&gt; the deferral keeps happening and the sequencing decision that
breaks it, so the next slice is scoped correctly rather than re-bundling the whole endgame
and deferring again.&lt;/p&gt;
&lt;p&gt;The end-state decomposes into three technically independent pieces that prior scoping
treated as one:&lt;/p&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Piece&lt;/th&gt;&lt;th&gt;Nature&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;th&gt;Real blocker&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Relocate mission data → &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;file move&lt;/td&gt;&lt;td&gt;&lt;strong&gt;done&lt;/strong&gt; (#3204)&lt;/td&gt;&lt;td&gt;—&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Availability from the charter activation set&lt;/strong&gt; — &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2652&quot;&gt;#2652&lt;/a&gt; chain, delete &lt;code dir=&quot;auto&quot;&gt;specify_cli/missions/&lt;/code&gt;&lt;/td&gt;&lt;td&gt;runtime behaviour&lt;/td&gt;&lt;td&gt;deferred&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2657&quot;&gt;#2657&lt;/a&gt; provisioned default charter (unstarted)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; as a first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;&lt;/strong&gt; — &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt;&lt;/td&gt;&lt;td&gt;type system&lt;/td&gt;&lt;td&gt;deferred&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2467&quot;&gt;#2467&lt;/a&gt; keystone pack-split (L, high blast radius, unstarted)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The deferral is &lt;strong&gt;structural, not effort-related&lt;/strong&gt;: the visible “move mission types” work
is a leaf sitting on two unstarted foundations (#2467 and #2657). Every run that scopes the
leaf reaches one of these foundations, finds it absent, and defers the &lt;em&gt;whole&lt;/em&gt; chunk rather
than claiming a foundation.&lt;/p&gt;
&lt;p&gt;Two facts change the calculus and make the deferral fixable now:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The type-system piece (#2468) genuinely needs the keystone pack-split (#2467), &lt;em&gt;and&lt;/em&gt;
#3204 introduced a new sub-decision under it (the mission-type content lives &lt;strong&gt;nested&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/mission_types/&lt;/code&gt;, but every other built-in kind resolves through
the &lt;strong&gt;flat&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctrine.pack_paths.built_in_dir(kind)&lt;/code&gt; convention). That piece is
legitimately large and blocked.&lt;/li&gt;
&lt;li&gt;The availability piece (#2652 chain) does &lt;strong&gt;not&lt;/strong&gt; need the keystone. Its first child
#2658 (templates-as-config) is already &lt;strong&gt;closed&lt;/strong&gt;. The chain is now
&lt;code dir=&quot;auto&quot;&gt;#2658 ✅ → #2659 → #2660 → #2661&lt;/code&gt;, and #2659 is blocked by exactly &lt;strong&gt;one&lt;/strong&gt; unstarted
issue: #2657. The behaviour the user actually named — “charter-loaded mission types” —
is delivered by this chain, independent of the artifact-kind promotion.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Separately, #3204 left its own resolution debt as &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3210&quot;&gt;#3210&lt;/a&gt;:
two parallel &lt;code dir=&quot;auto&quot;&gt;get_package_asset_root&lt;/code&gt; implementations (&lt;code dir=&quot;auto&quot;&gt;src/kernel/paths.py&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/runtime/home.py&lt;/code&gt;) with &lt;code dir=&quot;auto&quot;&gt;_find_relocated_missions_ancestor&lt;/code&gt; byte-duplicated,
a false “re-exported by” docstring, and &lt;code dir=&quot;auto&quot;&gt;default_missions_root()&lt;/code&gt; ignoring
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; (an env split-brain where directives/styleguides honour the
override but missions silently do not). Nothing mis-resolves today, but this is &lt;em&gt;exactly&lt;/em&gt;
the kind of two-door mission-tree ambiguity that would confuse the availability rework built
on top of it.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Break the deferral by claiming a foundation, not the leaf.&lt;/strong&gt; As long as the work is
scoped as “relocate mission types,” it re-derives its blockers and defers. The scope must
name a foundation issue as its headline.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Separability of the two halves.&lt;/strong&gt; “Charter-loaded availability” (#2652/#2657) and
“mission-type as a doctrine kind” (#2468/#2467) are independent. Only the second needs the
keystone. Prior scoping conflated them and inherited the keystone’s weight unnecessarily.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deliver the behaviour the user named, on the shortest unblocked path.&lt;/strong&gt; The user’s phrase
maps to activation-driven availability, which is one unstarted issue (#2657) away — not the
L-sized keystone.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resolve the resolution seam before building on it.&lt;/strong&gt; #3210 is a precondition for trusting
a single mission-tree door; the availability rework (#2659) resolves availability &lt;em&gt;through&lt;/em&gt;
that door. Landing them together avoids repointing the same readers twice.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No silent contract reversal.&lt;/strong&gt; #2468 reverses a deliberate, tested “no silent fallback”
contract (R-009/CL-1, FR-032, pinned by &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_org_pack_augmentation.py&lt;/code&gt;) and
must carry its own decision record; it must not be smuggled into an availability slice.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Decouple the two mission-type threads and sequence the charter-activation-driven
availability thread first.&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The next slice is the resolution + availability foundation&lt;/strong&gt;, bundling &lt;strong&gt;#2657
(provisioned default charter)&lt;/strong&gt; and &lt;strong&gt;#3210 (mission-tree resolution unification)&lt;/strong&gt; into a
single mission:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3210&lt;/strong&gt; collapses the two-door &lt;code dir=&quot;auto&quot;&gt;get_package_asset_root&lt;/code&gt; into one authority, removes the
duplicated &lt;code dir=&quot;auto&quot;&gt;_find_relocated_missions_ancestor&lt;/code&gt;, corrects the false re-export docstring,
and makes &lt;code dir=&quot;auto&quot;&gt;default_missions_root()&lt;/code&gt; honour &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; — so there is &lt;em&gt;one&lt;/em&gt;
resolution door with consistent env-relocation semantics.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2657&lt;/strong&gt; retires the implicit “all four built-in types” fallback
(&lt;code dir=&quot;auto&quot;&gt;src/charter/mission_type_profiles.py:388-395&lt;/code&gt; and the analogous &lt;code dir=&quot;auto&quot;&gt;charter.pack_context&lt;/code&gt;
fallback) so the provisioned default charter (&lt;code dir=&quot;auto&quot;&gt;src/charter/packs/default.yaml&lt;/code&gt;, migration
&lt;code dir=&quot;auto&quot;&gt;m_3_2_0rc35_default_charter_pack&lt;/code&gt;) is the single authority for the activation set, with
fail-closed provisioning for both legacy-migration and fresh-init projects.&lt;/li&gt;
&lt;li&gt;These two are bundled because they are the &lt;em&gt;foundation the availability chain stands on&lt;/em&gt;:
#2659 resolves availability through the mission-tree door (#3210) using the activation set
as the single authority (#2657). Landing them together repoints the mission-tree readers
exactly once.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2659 → #2660 → #2661&lt;/strong&gt; (the remainder of the #2652 chain, delivering
activation-driven enumeration and the deletion of &lt;code dir=&quot;auto&quot;&gt;specify_cli/missions/&lt;/code&gt;) follow as
sequenced slices once this foundation is in, &lt;strong&gt;without&lt;/strong&gt; waiting on the keystone.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2468 (mission-type as &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;) stays parked behind #2467 (keystone pack-split)&lt;/strong&gt;
and is &lt;em&gt;not&lt;/em&gt; part of this or the immediately following slices. The runtime “charter-loaded”
behaviour does not depend on it.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Positive&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The behaviour the user named ships on the shortest unblocked path: after this slice, only
#2659–#2661 (already sequenced, no new foundations) stand between here and a single
activation-driven availability authority.&lt;/li&gt;
&lt;li&gt;The repeated-deferral pattern is closed at its cause: a foundation issue (#2657) is the
headline, so a run cannot reach it, find it missing, and defer.&lt;/li&gt;
&lt;li&gt;#3204’s own resolution debt is retired as part of the seam the availability work builds on,
rather than accreting as a separate never-scheduled cleanup.&lt;/li&gt;
&lt;li&gt;#3183 (the &lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; activated-vs-available vocabulary collision) is
resolved by #2657 making “activated” the single authority, rather than being inherited.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Negative / accepted trade-offs&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The type-system unification (#2468) remains deferred, so &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; continues to be
admitted via the &lt;code dir=&quot;auto&quot;&gt;_ORG_DRG_KIND_ALIASES[&quot;mission_types&quot;]&lt;/code&gt; side channel and
&lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt; stays raised until the keystone (#2467) lands. This is
intentional: it is the larger, keystone-blocked half and carries a tested-contract reversal
that needs its own decision record.&lt;/li&gt;
&lt;li&gt;Bundling #2657 (charter activation semantics) with #3210 (kernel/path resolution) crosses
two layers in one mission. Accepted because both converge on the single question “how is a
mission type resolved and offered,” and splitting them would repoint the same mission-tree
readers twice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Explicitly out of scope (deferred, not decided here)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;nested-vs-flat&lt;/strong&gt; mission-type path decision (#2468: flatten &lt;code dir=&quot;auto&quot;&gt;mission_types/&lt;/code&gt; to a
top-level pack dir to fit the &lt;code dir=&quot;auto&quot;&gt;built_in_dir&lt;/code&gt; convention, vs. teach &lt;code dir=&quot;auto&quot;&gt;built_in_dir&lt;/code&gt; a nested
&lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt; mission-tier exception). It belongs to the #2468 promotion and should get its own
short decision record when that slice is scoped. This ADR does &lt;strong&gt;not&lt;/strong&gt; bind it.&lt;/li&gt;
&lt;li&gt;The kernel↔doctrine &lt;strong&gt;schema&lt;/strong&gt; coupling follow-up flagged by #3204.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Epic: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2466&quot;&gt;#2466&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Availability thread: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2652&quot;&gt;#2652&lt;/a&gt;
(chain), &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2657&quot;&gt;#2657&lt;/a&gt;,
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2659&quot;&gt;#2659&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Resolution unification: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3210&quot;&gt;#3210&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Type-promotion thread (deferred): &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt;,
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2467&quot;&gt;#2467&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Landed relocation: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/3204&quot;&gt;PR #3204&lt;/a&gt;,
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3091&quot;&gt;#3091&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Coherence ADR this refines:
&lt;a href=&quot;/adr/3.x/2026-07-15-1-doctrine-offers-charter-activates-runtime-consumes/&quot;&gt;2026-07-15-1-doctrine-offers-charter-activates-runtime-consumes.md&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Wheel-cutover assessment (downstream consumer of a settled mission home):
&lt;a href=&quot;/adr/3.x/2026-08-02-1-charter-wheel-assessment/&quot;&gt;2026-08-02-1-charter-wheel-assessment.md&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;addendum-2026-08-05--3210-resolver-shape-sharpened-after-the-post-plan-review&quot;&gt;Addendum (2026-08-05) — #3210 resolver shape sharpened after the post-plan review&lt;/h2&gt;
&lt;p&gt;The post-plan review squad on mission &lt;code dir=&quot;auto&quot;&gt;resolution-activation-foundation-01KZ9FKG&lt;/code&gt; showed the original
“one resolution door via a thin re-export” framing was incomplete: &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions&lt;/code&gt; is
resolved by &lt;strong&gt;two&lt;/strong&gt; functions with disjoint caller bases — &lt;code dir=&quot;auto&quot;&gt;kernel.paths.get_package_asset_root&lt;/code&gt; (the
door) and &lt;code dir=&quot;auto&quot;&gt;doctrine.missions.repository.default_missions_root&lt;/code&gt; — and only the latter was being made
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt;-aware. Re-pointing &lt;code dir=&quot;auto&quot;&gt;home.py&lt;/code&gt; at the kernel door would have left the door and
its ~7 consumers env-blind, i.e. the split-brain would move, not die.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Operator decision (2026-08-05): unify the resolver. The &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt; pack — missions included — is
installed/available from the default- or env-supplied pack root (“PACKS_HOME” = &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt;).&lt;/strong&gt;
The mission-tree is &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;built-in-pack-root&gt;/missions&lt;/code&gt;, resolved through one primitive:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;kernel&lt;/strong&gt; floor owns a &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt;-aware built-in-pack-root resolver (kernel reading
an env var is layer-legal; it does not import doctrine). &lt;code dir=&quot;auto&quot;&gt;kernel.sibling_paths.resolve_installed_sibling&lt;/code&gt;
already exists as the env-agnostic algorithm; the env read moves to a kernel entry point.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine.pack_paths._resolve_built_in&lt;/code&gt; delegates to it (retiring the duplicate &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt;
read at &lt;code dir=&quot;auto&quot;&gt;pack_paths.py:204&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctrine.missions.repository.default_missions_root()&lt;/code&gt; becomes &lt;code dir=&quot;auto&quot;&gt;built_in_root() / &quot;missions&quot;&lt;/code&gt; — so it
inherits PACKS_ROOT-awareness by construction (the FR-003 fix by unification, not a bolt-on).&lt;/li&gt;
&lt;li&gt;The kernel door resolves the same &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;built-in-pack-root&gt;/missions&lt;/code&gt;, so door consumers honor PACKS_ROOT
uniformly. &lt;code dir=&quot;auto&quot;&gt;home.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;specify_cli/missions&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;dev_root&lt;/code&gt; legacy fallbacks are intentionally dropped —
fail-closed, not fall-through.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_TEMPLATE_ROOT&lt;/code&gt; retains its distinct role as the asset-copy/template override (it is used
across &lt;code dir=&quot;auto&quot;&gt;template/manager.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;asset_generator.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;init.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;bootstrap.py&lt;/code&gt;, and upgrade migrations);
precedence: &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; governs pack-root &lt;em&gt;location&lt;/em&gt; and wins when both are set. A
door-caller census confirms TEMPLATE_ROOT semantics are preserved for the copy path.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This also subsumes the sibling-pattern-literal duplication (three drifting &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions&lt;/code&gt;
constants collapse onto the kernel primitive + the existing &lt;code dir=&quot;auto&quot;&gt;missions&lt;/code&gt; leaf name). The mission’s spec,
plan, and contracts are revised accordingly; &lt;code dir=&quot;auto&quot;&gt;_find_relocated_missions_ancestor&lt;/code&gt; is &lt;strong&gt;logically&lt;/strong&gt;
duplicated (not byte-identical — the “byte-duplicated” wording earlier in this ADR is loose; the code
uses a constant in kernel and an inline literal in home.py).&lt;/p&gt;
&lt;h2 id=&quot;addendum-2026-08-07--dr-1-silent-parity-behaviour-superseded-misconfigured-spec_kitty_packs_root-now-warns-loudly&quot;&gt;Addendum (2026-08-07) — DR-1 silent-parity behaviour superseded: misconfigured &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; now warns loudly&lt;/h2&gt;
&lt;p&gt;The 2026-08-05 addendum above records DR-1 (mission &lt;code dir=&quot;auto&quot;&gt;resolution-activation-foundation-01KZ9FKG&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;post-plan-review-findings.md&lt;/code&gt;): unify the built-in pack resolver behind one kernel-floor primitive,
&lt;code dir=&quot;auto&quot;&gt;kernel.paths.get_built_in_pack_root&lt;/code&gt;. One consequence of that unification, carried over unchanged from
the pre-collapse resolver for behaviour-parity, was that a &lt;strong&gt;set-but-unresolvable&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; — the value is present, but &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;value&gt;/built-in&lt;/code&gt; does not exist as a directory —
resolved &lt;em&gt;silently&lt;/em&gt; to the installed/ancestor-walk sibling. The override lost the race, but nothing told
the operator it had.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Operator decision (2026-08-07): this silent parity is superseded.&lt;/strong&gt; It is cleaner to inform an
operator of a misconfigured environment than to silently load a possibly-unrelated doctrine/charter pack
on their machine. Resolution stays &lt;strong&gt;fail-open&lt;/strong&gt; — a broken override must not hard-break every command —
but the fallback is now &lt;strong&gt;loud&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;get_built_in_pack_root&lt;/code&gt; emits a &lt;code dir=&quot;auto&quot;&gt;UserWarning&lt;/code&gt; naming the misconfigured
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; value and the &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt; path it failed to resolve, before falling through to the
ancestor-walk-resolved installed sibling. This is a narrow amendment to DR-1’s fallback framing, not a
reversal of DR-1 itself: there is still exactly one resolution primitive, and it still does not raise on
the override — only the silence is removed. See &lt;code dir=&quot;auto&quot;&gt;src/kernel/paths.py::get_built_in_pack_root&lt;/code&gt; and its
regression coverage in &lt;code dir=&quot;auto&quot;&gt;tests/kernel/test_paths.py&lt;/code&gt;.&lt;/p&gt;</content>
</entry>
