<?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-13-1-mission-type-roster-layering-seam/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-08-13-1-mission-type-roster-layering-seam/</id>
  <title>ADR: Mission-Type Roster Layering Is the Availability Slice, Not the Kind-Promotion Slice</title>
  <updated>2026-08-13T00: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-13-1-mission-type-roster-layering-seam/"/>
  <summary>Adds a layered, pack-aware mission-type lookup and a flat org/project roster layout. Availability slice only: mission-type is not promoted to an ArtifactKind.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Mission &lt;code dir=&quot;auto&quot;&gt;up-mission-type-seam-01KZY1JB&lt;/code&gt; gives the mission-type roster a &lt;strong&gt;layered lookup&lt;/strong&gt; so a
non-built-in mission type declared in an org-tier doctrine pack resolves through &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;, and action-sequence projection end-to-end — not merely “loads
without crashing.” &lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository.default()&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/mission_type_repository.py:48-50&lt;/code&gt;,
a &lt;code dir=&quot;auto&quot;&gt;@classmethod&lt;/code&gt; decorated with &lt;code dir=&quot;auto&quot;&gt;@functools.cache&lt;/code&gt;, keyed on &lt;code dir=&quot;auto&quot;&gt;cls&lt;/code&gt; only) stays built-in-only and
unchanged; a new, separate, pack-aware factory is added alongside it.&lt;/p&gt;
&lt;p&gt;That work sits immediately downstream of a live sequencing decision recorded in
&lt;a href=&quot;/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion.md&lt;/code&gt;&lt;/a&gt;,
which deliberately decoupled two independent mission-type threads and sequenced the
charter-activation-driven &lt;strong&gt;availability&lt;/strong&gt; thread ahead of the &lt;strong&gt;mission-type-as-&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;&lt;/strong&gt;
promotion thread (issue &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt;, blocked
on the keystone pack-split &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2467&quot;&gt;#2467&lt;/a&gt;). That
ADR is explicit that the promotion thread “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.” It also
explicitly parks the org-pack mission-type directory &lt;strong&gt;layout&lt;/strong&gt; (nested vs. flat) as an
undecided sub-decision belonging to the promotion slice: “This ADR does not bind it.”&lt;/p&gt;
&lt;p&gt;This mission’s roster-layering work is exactly the availability/resolution slice that
sequencing ADR anticipated. The risk this ADR closes is conflation risk, not implementation
risk: a future reader auditing either ADR must be able to tell, without re-deriving it from the
diff, that this mission (1) does not do the promotion work, (2) is not a silent reversal of the
“no silent fallback” contract the promotion thread must reckon with, and (3) makes its own,
narrower, self-contained call on the one layout sub-decision the sequencing ADR left open for a
directory shape this mission actually needs today (the org/project roster location), without
pretending to settle the promotion thread’s broader nested-vs-flat question for &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt;.&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;No silent contract reversal.&lt;/strong&gt; The sequencing ADR requires the promotion thread (&lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt;) to
carry its own decision record rather than be smuggled into an availability slice; symmetrically,
this availability slice must not be misread as doing that thread’s work by omission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Honor a parked decision instead of silently resolving it.&lt;/strong&gt; The sequencing ADR left
nested-vs-flat mission-type layout open &lt;em&gt;for the promotion slice&lt;/em&gt;. This mission needs an
org/project roster layout &lt;em&gt;now&lt;/em&gt;, for a narrower purpose (where does a layered lookup scan for
non-built-in mission-type YAML), and must record that choice explicitly rather than let a
directory decision made here be mistaken for having settled the promotion thread’s question.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CHARTER_KIND_TOKENS&lt;/code&gt; boundary stays untouched.&lt;/strong&gt; Confirmed live (see below):
the enum has no &lt;code dir=&quot;auto&quot;&gt;MISSION_TYPE&lt;/code&gt; member, and the exception that keeps &lt;code dir=&quot;auto&quot;&gt;&quot;mission-type&quot;&lt;/code&gt; out of the
charter-activatable &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; vocabulary still exists and is unchanged by this mission
(spec C-002/C-003).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Correctness over convenience in the seam’s own shape (CL-001).&lt;/strong&gt; The layered lookup must not
be built by making the existing built-in-only &lt;code dir=&quot;auto&quot;&gt;default()&lt;/code&gt; project-dependent, even though that
would look like the smaller diff — see “Seam Shape” below.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;a-this-mission-does-not-promote-mission-type-to-a-first-class-artifactkind&quot;&gt;(a) This mission does not promote mission-type to a first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Confirmed live at this HEAD: &lt;code dir=&quot;auto&quot;&gt;src/doctrine/artifact_kinds.py:124-143&lt;/code&gt; defines
&lt;code dir=&quot;auto&quot;&gt;class ArtifactKind(StrEnum)&lt;/code&gt; with twelve members (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TACTIC&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;STYLEGUIDE&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;TOOLGUIDE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PARADIGM&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PROCEDURE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;AGENT_PROFILE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MISSION_STEP_CONTRACT&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TEMPLATE&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;ASSET&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ANTI_PATTERN&lt;/code&gt;) — &lt;strong&gt;no &lt;code dir=&quot;auto&quot;&gt;MISSION_TYPE&lt;/code&gt; member exists today.&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt; is defined at &lt;code dir=&quot;auto&quot;&gt;src/doctrine/artifact_kinds.py:40&lt;/code&gt; and is
re-exported by &lt;code dir=&quot;auto&quot;&gt;src/charter/kind_vocabulary.py&lt;/code&gt; (import at line 51, &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; entry at line 78).
Its purpose, per the module’s own kind-normalization contract, is to keep the operator-facing
token &lt;code dir=&quot;auto&quot;&gt;&quot;mission-type&quot;&lt;/code&gt; out of the charter-activatable &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; vocabulary while it remains
a &lt;code dir=&quot;auto&quot;&gt;CHARTER_KIND_TOKENS&lt;/code&gt; member — i.e. mission types are activatable but are deliberately &lt;strong&gt;not&lt;/strong&gt;
a doctrine artifact kind. This mission does not add a &lt;code dir=&quot;auto&quot;&gt;MISSION_TYPE&lt;/code&gt; enum member, does not touch
&lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt;, and does not widen &lt;code dir=&quot;auto&quot;&gt;ALLOWED_MISSION_TYPES&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/charter/activations.py:95&lt;/code&gt;, an import-time-constrained frozenset — spec C-003). Promoting
mission-type to a first-class &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; is the separate, larger, currently-unstarted
upstream effort tracked by the sequencing ADR: issue
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt;, blocked on the keystone pack-split
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2467&quot;&gt;#2467&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;b-relation-to-the-sequencing-adrs-no-silent-contract-reversal-driver&quot;&gt;(b) Relation to the sequencing ADR’s “no silent contract reversal” driver&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion.md&lt;/code&gt;&lt;/a&gt;
names &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt;’s promotion as reversing 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 requires that
reversal to carry its own decision record rather than be smuggled into an availability slice.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;This mission is that availability/resolution slice, and states plainly that it is not the
contract-reversing type-promotion slice.&lt;/strong&gt; Concretely: this mission adds a layered lookup +
&lt;code dir=&quot;auto&quot;&gt;PackContext&lt;/code&gt; projection + CLI-surface fixes for a mission type that has already been &lt;em&gt;activated&lt;/em&gt;
(charter-eligible) — it never widens what can be &lt;em&gt;activated&lt;/em&gt; in the first place (C-003, above).
It touches no code path guarded by &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_org_pack_augmentation.py&lt;/code&gt;, adds no
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; member, and leaves &lt;code dir=&quot;auto&quot;&gt;MissionTypeNotAnArtifactKind&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CHARTER_KIND_TOKENS&lt;/code&gt;
unchanged. A future reader auditing either ADR should read this section and the sequencing ADR’s
“No silent contract reversal” driver together as confirming, not conflicting: the sequencing ADR
sequenced this slice first &lt;em&gt;because&lt;/em&gt; it does not touch the contract the promotion slice must
reckon with; this ADR confirms that the slice landed as scoped.&lt;/p&gt;
&lt;h3 id=&quot;c-the-flat-org-pack-layout-cl-005--its-own-short-decision-record&quot;&gt;(c) The flat org-pack layout (CL-005) — its own short decision record&lt;/h3&gt;
&lt;p&gt;The sequencing ADR’s “Explicitly out of scope” section names the &lt;strong&gt;nested-vs-flat mission-type
path&lt;/strong&gt; as an open sub-decision it deliberately parks for the &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt; promotion slice: “This ADR
does not bind it.” This mission needs an org/project mission-type roster location for its own,
narrower purpose (where the new layered lookup scans for non-built-in mission-type definitions),
so it makes and records that call here, distinct from (a) and (b) above and without claiming to
settle the promotion slice’s broader question.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Decision: the layout is flat.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Org layer&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;pack_root&gt;/mission_types/*.yaml&lt;/code&gt;. This matches the sibling &lt;code dir=&quot;auto&quot;&gt;mission-steps/&lt;/code&gt;
convention already used at the org/project pack tier — confirmed live at
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/mission_step_repository.py:411&lt;/code&gt;, whose docstring states the pattern
&lt;code dir=&quot;auto&quot;&gt;{pack_root}/mission-steps/{mission_type_id}/{step_id}/step.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project layer&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/mission_types/*.yaml&lt;/code&gt;, scanned &lt;strong&gt;non-recursively&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Rejected alternative&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/mission_types/&lt;/code&gt;. That directory shape, scanned
recursively, would descend into a per-type subdirectory (e.g.
&lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/mission_types/&amp;#x3C;type&gt;/governance-profile.yaml&lt;/code&gt;) and mint a bogus available
mission type literally named &lt;code dir=&quot;auto&quot;&gt;governance-profile&lt;/code&gt;. This is a real trap in the live scanning code,
not a hypothetical one: &lt;code dir=&quot;auto&quot;&gt;CharterPackManager.list_available_detailed&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/charter/pack_manager.py:756&lt;/code&gt;) uses &lt;code dir=&quot;auto&quot;&gt;scan_dir.rglob(glob)&lt;/code&gt; universally for every
charter-activatable kind (the &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt; call itself is at &lt;code dir=&quot;auto&quot;&gt;src/charter/pack_manager.py:809&lt;/code&gt;), so
any subdirectory content matching the glob resolves as a top-level available artifact id.&lt;/p&gt;
&lt;p&gt;This mission’s flat CL-005 shape &lt;strong&gt;structurally avoids&lt;/strong&gt; the trap rather than fixing the
underlying &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt; behavior — &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/mission_types/&lt;/code&gt; holds only flat &lt;code dir=&quot;auto&quot;&gt;*.yaml&lt;/code&gt; files
with no per-type subdirectory, so &lt;code dir=&quot;auto&quot;&gt;rglob(&quot;*.yaml&quot;)&lt;/code&gt; and a hypothetical non-recursive &lt;code dir=&quot;auto&quot;&gt;glob&lt;/code&gt; are
behaviorally identical there. Changing &lt;code dir=&quot;auto&quot;&gt;list_available_detailed&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;glob&lt;/code&gt; would be
an unrelated, broader-blast-radius change affecting every other charter-activatable kind that
scans through the same method, and is explicitly out of scope for this mission (tracked as
follow-up scope in WP05’s own work-package prompt,
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/up-mission-type-seam-01KZY1JB/tasks/WP05-activate-layer-scan.md&lt;/code&gt;).&lt;/p&gt;
&lt;h2 id=&quot;seam-shape-backing-these-decisions-cl-001s-rejected-alternatives&quot;&gt;Seam Shape Backing These Decisions: CL-001’s Rejected Alternatives&lt;/h2&gt;
&lt;p&gt;The layered lookup itself (the mechanism (a)/(b)/(c) above describe as “the availability slice”)
was not the only shape considered. Recording the rejected alternatives here, not just the chosen
shape, is part of what makes this a decision record rather than a design summary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option (a) — make &lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository.default()&lt;/code&gt; itself project-dependent&lt;/strong&gt;, by threading
a &lt;code dir=&quot;auto&quot;&gt;PackContext&lt;/code&gt; into the existing, process-wide, &lt;code dir=&quot;auto&quot;&gt;cls&lt;/code&gt;-keyed &lt;code dir=&quot;auto&quot;&gt;@functools.cache&lt;/code&gt;. &lt;strong&gt;Rejected&lt;/strong&gt;:
a project-dependent value behind a project-blind cache is a correctness bug — the first project
resolved in a process would poison the cache for every later one resolved in that same process.
&lt;code dir=&quot;auto&quot;&gt;default()&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/mission_type_repository.py:48-50&lt;/code&gt;) therefore stays
built-in-only and untouched; the new lookup is a &lt;strong&gt;separate, module-level&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;@functools.cache&lt;/code&gt;-wrapped factory keyed on &lt;code dir=&quot;auto&quot;&gt;(mission_types_dirs, pack_context)&lt;/code&gt;, never a
classmethod cache.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option (b) — move the &lt;code dir=&quot;auto&quot;&gt;action_sequence&lt;/code&gt; projection out of
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/mission_type_repository.py&lt;/code&gt; into the charter layer.&lt;/strong&gt; &lt;strong&gt;Rejected,
measured, not guessed&lt;/strong&gt;: doing so would remove the only producer of the &lt;code dir=&quot;auto&quot;&gt;action_sequence&lt;/code&gt; slot
from the one directory tree (&lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt;) that
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_inert_schema_slots.py&lt;/code&gt;’s producer-scan walks, which reds the one
live assertion in that architectural gate — &lt;code dir=&quot;auto&quot;&gt;test_live_tree_has_no_new_inert_slots&lt;/code&gt;’s
&lt;code dir=&quot;auto&quot;&gt;assert new == []&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_inert_schema_slots.py:62-75&lt;/code&gt;, confirmed live at
this HEAD).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The new lookup instead imports the existing structural &lt;code dir=&quot;auto&quot;&gt;_PackContextLike&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;Protocol&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/mission_step_repository.py:41-61&lt;/code&gt;, confirmed live) from its sibling
module in the same package (&lt;code dir=&quot;auto&quot;&gt;doctrine.missions&lt;/code&gt;) — an intra-package import, not a new
cross-layer one; &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; still never imports &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;. This is why the mechanism qualifies as
“availability/resolution,” per (b) above: it is additive plumbing inside the existing
built-in/org/project layering, not a change to what counts as a doctrine artifact kind.&lt;/p&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;A future reader of either this ADR or the sequencing ADR can resolve, from either document
alone, whether a given piece of mission-type work is the availability slice or the promotion
slice — the conflation risk this ADR exists to close.&lt;/li&gt;
&lt;li&gt;The one org-pack layout question this mission actually needs answered (org/project roster
location) is decided and recorded, without overreaching into the promotion slice’s broader
nested-vs-flat question, which stays open for &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt; to answer when it is scoped.&lt;/li&gt;
&lt;li&gt;The rejected &lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository.default()&lt;/code&gt; project-dependent-cache option is on record, so a
future contributor tempted by the smaller-looking diff can see why it was rejected instead of
rediscovering the cache-poisoning bug by shipping it.&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;This ADR does not resolve the promotion slice’s own nested-vs-flat decision for &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt; — that
remains genuinely open, and &lt;code dir=&quot;auto&quot;&gt;#2468&lt;/code&gt;’s own future ADR must still make that call for the doctrine
artifact-kind path, independent of the roster-layout call made here.&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt;-vs-&lt;code dir=&quot;auto&quot;&gt;glob&lt;/code&gt; behavior in &lt;code dir=&quot;auto&quot;&gt;CharterPackManager.list_available_detailed&lt;/code&gt; is not fixed by
this mission; it is neutralized only for the flat directories this mission introduces. A future
per-type-subdirectory addition to a different charter-activatable kind under a recursively
scanned root would still hit the same class of trap.&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;&lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository.default()&lt;/code&gt; and its &lt;code dir=&quot;auto&quot;&gt;cls&lt;/code&gt;-keyed cache are unchanged; all built-in
mission-type resolution behavior is unaffected by this mission.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Sequencing ADR this relates to:
&lt;a href=&quot;/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-05-1-mission-type-availability-before-kind-promotion.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Promotion thread (deferred, separate ADR required): issue
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2468&quot;&gt;#2468&lt;/a&gt; (“mission-type as a first-class
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;”), blocked on keystone issue
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2467&quot;&gt;#2467&lt;/a&gt; (pack-split).&lt;/li&gt;
&lt;li&gt;Mission spec (binding decision records CL-001, CL-002, CL-005; constraints C-002, C-003):
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/up-mission-type-seam-01KZY1JB/spec.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Mission plan (Implementation Concern Map preamble stating WP01’s required contents):
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/up-mission-type-seam-01KZY1JB/plan.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Follow-up scope for the underlying &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;glob&lt;/code&gt; behavior:
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/up-mission-type-seam-01KZY1JB/tasks/WP05-activate-layer-scan.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
