<?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-07-15-1-doctrine-offers-charter-activates-runtime-consumes/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-07-15-1-doctrine-offers-charter-activates-runtime-consumes/</id>
  <title>ADR: Doctrine Offers, Charter Activates, Runtime Consumes Only Activated (default-charter provisioning)</title>
  <updated>2026-07-15T00: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-07-15-1-doctrine-offers-charter-activates-runtime-consumes/"/>
  <summary>Doctrine packs stay pure catalogues, charter activation becomes one mechanism covering mission types, gates and assets, and the loop consumes only activated artefacts.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;/adr/3.x/2026-07-14-2-doctrine-to-core-mission-type-resolution-unification/&quot;&gt;ADR 2026-07-14-2&lt;/a&gt;
(shipped as #883 slice 1) made the doctrine &lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt; artefact load-bearing
for &lt;strong&gt;governance&lt;/strong&gt; through one charter-mediated seam. This ADR states the
&lt;strong&gt;general governing rule&lt;/strong&gt; that seam is an instance of, and closes the places it
is not yet true.&lt;/p&gt;
&lt;p&gt;The operator-stated mechanism (binding):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Doctrine (packs) OFFER&lt;/strong&gt; a catalogue — mission types, step contracts, gates,
and (when supported) explicit checks / &lt;code dir=&quot;auto&quot;&gt;assets&lt;/code&gt;. Doctrine only offers; it does
not decide what is active.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A charter ACTIVATES&lt;/strong&gt; doctrine elements. The charter may be user-level or
predefined from a higher tier (org / project / team). Activation is the &lt;strong&gt;same
mechanism for every artefact kind&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The runtime execution loop consumes ONLY activated elements.&lt;/strong&gt; It holds no
hardcoded per-type knowledge; unactivated doctrine is invisible to the loop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prompt and WP templates are PART OF a mission type&lt;/strong&gt; — configuration
elements carried by doctrine, not core parts of the Spec Kitty engine.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;“What is active by default?” must be revised.&lt;/strong&gt; Pinning the default to “all
built-in doctrine” is no longer viable. There must be a &lt;strong&gt;default charter&lt;/strong&gt;,
provisioned when the customer/user has not created one.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A three-lens grounding pass (architecture, availability-split-brain, doctrine
mechanism) on &lt;code dir=&quot;auto&quot;&gt;design/mission-type-activation-coherence&lt;/code&gt; (post-#883) found that
the rule &lt;strong&gt;holds for the eight DRG-backed artifact kinds but breaks for mission
types and templates&lt;/strong&gt;, and that “active by default” is a fail-open code constant.&lt;/p&gt;
&lt;h3 id=&quot;grounded-status-of-the-five-claims&quot;&gt;Grounded status of the five claims&lt;/h3&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;#&lt;/th&gt;&lt;th&gt;Claim&lt;/th&gt;&lt;th&gt;Status&lt;/th&gt;&lt;th&gt;Root evidence (file:line)&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;Doctrine OFFERS&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Holds for 8 kinds; asymmetric&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;DRG node census of &lt;code dir=&quot;auto&quot;&gt;src/doctrine/graph.yaml&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; have &lt;strong&gt;0 nodes&lt;/strong&gt;. Only the 8 kinds are truly offer→activate→consume through the graph.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;Charter ACTIVATES uniformly&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Holds&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;One &lt;code dir=&quot;auto&quot;&gt;YAML_KEY_MAP&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;pack_manager.py:120-122&lt;/code&gt;, mission-type first-class), one plan/commit engine (&lt;code dir=&quot;auto&quot;&gt;activation_engine.py:194-282&lt;/code&gt;), one consume-side filter (&lt;code dir=&quot;auto&quot;&gt;drg.py:256-343&lt;/code&gt;). Two narrow special-cases: cascade is a no-op for mission-type (no DRG node → &lt;code dir=&quot;auto&quot;&gt;activate.py:88-90,319-321&lt;/code&gt;); one warning branch (&lt;code dir=&quot;auto&quot;&gt;activate.py:134&lt;/code&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;3&lt;/td&gt;&lt;td&gt;Runtime consumes ONLY activated&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Breaks&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;_dn_bootstrap&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;runtime_bridge.py:1199&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;get_or_start_run&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;runtime_bridge_io.py:469&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;_runtime_template_key&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;io.py:322-360&lt;/code&gt;) resolve &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;/templates by &lt;strong&gt;filesystem discovery tiers with no activation consultation&lt;/strong&gt;. The activated &lt;code dir=&quot;auto&quot;&gt;action_sequence&lt;/code&gt; is only an advisory routing predicate and &lt;strong&gt;degrades on exception&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;runtime_bridge_composition.py:180-195,316-327&lt;/code&gt;). An unactivated type whose &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; is on disk is fully runnable.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;Templates are config&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Partial (~80%)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;template_set&lt;/code&gt; fields exist on all four &lt;code dir=&quot;auto&quot;&gt;mission_types/*.yaml&lt;/code&gt;; templates are DRG nodes (16) and pack-carried. But the &lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType.template_set&lt;/code&gt; slot is &lt;strong&gt;unwired&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_type_profiles.py:470&lt;/code&gt; hardcodes &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;), and the mission_type→template link is an unbacked filename string because mission_type is not a DRG node.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;Default charter&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Breaks at init; fail-open&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Absent config → &lt;code dir=&quot;auto&quot;&gt;_load_config&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;{}&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;pack_context.py:230-231&lt;/code&gt;) → hardcoded &lt;code dir=&quot;auto&quot;&gt;_BUILTIN_*&lt;/code&gt; constants activate &lt;strong&gt;everything&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;pack_context.py:253-271&lt;/code&gt;). A real default charter ships (&lt;code dir=&quot;auto&quot;&gt;src/charter/packs/default.yaml&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;load_default_pack_activation_ids&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;merge_defaults&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;pack_manager.py:703&lt;/code&gt;), but &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; never provisions it&lt;/strong&gt; and &lt;strong&gt;no read-time fallback consumes it&lt;/strong&gt; — it reaches config only via a version-guarded migration. The default is &lt;strong&gt;triple-sourced&lt;/strong&gt; (constants, &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge_defaults&lt;/code&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;the-two-disconnected-availability-authorities&quot;&gt;The two disconnected availability authorities&lt;/h3&gt;
&lt;p&gt;Availability of mission types is answered by &lt;strong&gt;two parallel authorities&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Activation authority (intended):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;PackContext.activated_mission_types&lt;/code&gt; →
&lt;code dir=&quot;auto&quot;&gt;existing_mission_types()&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_type_profiles.py:362-398&lt;/code&gt;, self-declared
FR-018 single source) → &lt;code dir=&quot;auto&quot;&gt;resolve_mission_type_context&lt;/code&gt;, and the DRG filter
&lt;code dir=&quot;auto&quot;&gt;filter_graph_by_activation&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Filesystem-glob authority (activation-blind):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;list_available_missions&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;mission.py:489-509&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;discover_missions&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission.py:806-842&lt;/code&gt;),
&lt;code dir=&quot;auto&quot;&gt;_packaged_missions_dir&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission.py:70&lt;/code&gt;), and the runtime discovery in
&lt;code dir=&quot;auto&quot;&gt;runtime_bridge_io.py:302-360&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_internal_runtime/discovery.py:139-176&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;On top of this, the &lt;strong&gt;identity of the four built-ins is hardcoded in ~9
independent lists, two of which have already drifted&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;runtime/show_origin.py:72&lt;/code&gt; is missing &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;; migration &lt;code dir=&quot;auto&quot;&gt;m_0_6_7:29&lt;/code&gt; lists only
two). And there are &lt;strong&gt;two physical mission trees&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt;
v0-schema copies vs &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/&lt;/code&gt;), reachable from either side because
&lt;code dir=&quot;auto&quot;&gt;get_package_asset_root&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;kernel/paths.py:88-95&lt;/code&gt;) lists both as candidates.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Adopt the operator’s rule as binding, and make it true end-to-end by structural
change rather than assertion.&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Doctrine packs stay pure catalogues&lt;/strong&gt; — no activation state (already true;
preserved by the C-001 layer ratchet).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation is one mechanism for every kind.&lt;/strong&gt; Extend it to &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; by giving them &lt;strong&gt;first-class DRG
nodes&lt;/strong&gt;, so their availability runs through &lt;code dir=&quot;auto&quot;&gt;filter_graph_by_activation&lt;/code&gt; like
every other kind. This also fixes the cascade no-op for mission-type.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The runtime loop resolves mission-type context, action-sequence, AND
template/DAG selection through the activation-gated &lt;code dir=&quot;auto&quot;&gt;resolve_mission_type_context&lt;/code&gt;
seam.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;_runtime_template_key&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;get_or_start_run&lt;/code&gt; filesystem path is
&lt;strong&gt;subordinated to (gated by)&lt;/strong&gt; the activation set, not run in parallel to it.
Deactivation must make a type unrunnable, not merely governance-silent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prompt/WP templates become activation-scoped mission-type config.&lt;/strong&gt; Wire the
&lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType.template_set&lt;/code&gt; slot to select template files; retire the
parallel discovery-tier template resolution and the &lt;code dir=&quot;auto&quot;&gt;software-dev-default&lt;/code&gt;
template magic. Templates are configuration carried by the mission type, not
engine-baked knowledge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retire “active by default = all built-in doctrine” as a code constant.&lt;/strong&gt; The
shipped &lt;code dir=&quot;auto&quot;&gt;src/charter/packs/default.yaml&lt;/code&gt; becomes the &lt;strong&gt;single default-activation
authority&lt;/strong&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(a) Read-time fallback:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;PackContext.from_config&lt;/code&gt; resolves an absent
activation key from &lt;code dir=&quot;auto&quot;&gt;load_default_pack_activation_ids()&lt;/code&gt; (data, not the
&lt;code dir=&quot;auto&quot;&gt;_BUILTIN_*&lt;/code&gt; constants).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(b) Provision at init:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; writes the explicit activation
set from &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;merge_defaults&lt;/code&gt;, so a fresh project’s config is
self-describing and auditable.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(c) Layer-0 tier:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; is the lowest charter tier; org /
project / team charters overlay it through the existing &lt;code dir=&quot;auto&quot;&gt;pack_roots&lt;/code&gt; overlay
(&lt;code dir=&quot;auto&quot;&gt;DoctrineLayerCollisionWarning&lt;/code&gt;, &lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;ADR 2026-05-16-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;Delete &lt;code dir=&quot;auto&quot;&gt;_BUILTIN_MISSION_TYPE_IDS&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_BUILTIN_ARTIFACT_KINDS&lt;/code&gt; as a &lt;em&gt;fallback
source&lt;/em&gt; (keep only as a derived or drift-checked cross-reference).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;fail-policy-made-explicit&quot;&gt;Fail policy (made explicit)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Absent activation key&lt;/strong&gt; → resolve the default charter pack. The pack’s
content is permissive today (it enumerates all built-ins), but availability is
now &lt;strong&gt;data, versioned, and layerable&lt;/strong&gt; — an org can ship a restrictive default.
The permissiveness is a property of the pack’s content, not hardcoded behaviour.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Explicit empty list&lt;/strong&gt; → fail-closed &lt;code dir=&quot;auto&quot;&gt;frozenset()&lt;/code&gt;; never re-expand to the
default (otherwise deactivation is meaningless). Honoured today at
&lt;code dir=&quot;auto&quot;&gt;pack_context.py:268-271&lt;/code&gt; — preserved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Absent config file&lt;/strong&gt; → resolve the default charter pack (backward-compat for
legacy / newly-&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;ed projects).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Corrupt/malformed config&lt;/strong&gt; → hard error. The existing fail-closed contract
(&lt;code dir=&quot;auto&quot;&gt;pack_context.py:223-241&lt;/code&gt;, “activation filters must not fail open”) is preserved.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Backward compatibility&lt;/strong&gt; — legacy projects with no activation keys must keep
working (default-pack fallback preserves this; the upgrade migration already
materialises the same keys).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fail-closed, not fail-open&lt;/strong&gt; — the default-pack fallback is a narrow exception
scoped to &lt;em&gt;absent key / absent file&lt;/em&gt;, never to &lt;em&gt;corrupt config&lt;/em&gt; or &lt;em&gt;explicit
deactivation&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Single source of truth&lt;/strong&gt; — collapse the triple-sourced default and the ~9
hardcoded built-in lists onto the doctrine registry + &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deactivation must bite&lt;/strong&gt; — the rule is worthless if the ungated runtime path
still runs a deactivated type (Claim 3).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hot-path budget (NFR-001, 100ms)&lt;/strong&gt; — cache the default-pack load; keep
&lt;code dir=&quot;auto&quot;&gt;template_set&lt;/code&gt; resolution lazy like &lt;code dir=&quot;auto&quot;&gt;expected_artifacts&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;step_contracts&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;Positive:&lt;/strong&gt; one availability authority; deactivation actually removes a type
from the runtime; templates become uniform activation-scoped config; the default
becomes explicit, versioned, and overridable per org/project; the ~9 drift-prone
hardcoded lists collapse to the registry.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Negative / cost:&lt;/strong&gt; modelling &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;step_contract&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;
as DRG nodes is non-trivial (gates are currently engine-baked condition strings,
assets have no offer surface); gating the runtime template path touches the hot
&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; loop and must not regress NFR-001; the work spans several dependent slices
(below) and cannot land atomically.&lt;/p&gt;
&lt;h2 id=&quot;implementation-slices-sequenced-by-dependency&quot;&gt;Implementation slices (sequenced by dependency)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;S0 — mission_type (+ mission_step_contract) as first-class DRG nodes.&lt;/strong&gt;
Unblocks cascade and graph-based gating for S3/S4. &lt;em&gt;(Belongs with #2651/#2652.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;S1 — &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; provisions the default charter&lt;/strong&gt; via &lt;code dir=&quot;auto&quot;&gt;merge_defaults&lt;/code&gt;. Smallest;
independent of #2652; ships first. &lt;em&gt;(New default-charter issue.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;S2 — collapse the read-time fallback&lt;/strong&gt; onto &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; via
&lt;code dir=&quot;auto&quot;&gt;load_default_pack_activation_ids&lt;/code&gt;; delete the &lt;code dir=&quot;auto&quot;&gt;_BUILTIN_*&lt;/code&gt; default source;
reconcile the kind-count (8 vs 10) into the existing triple-guard. &lt;em&gt;(Same issue.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;S3 — gate &lt;code dir=&quot;auto&quot;&gt;_runtime_template_key&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;get_or_start_run&lt;/code&gt;&lt;/strong&gt; through the activation
seam so the runtime consumes only activated types. &lt;em&gt;(After #2652 canonicalises
enumeration; closes Claim 3.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;S4 — wire the &lt;code dir=&quot;auto&quot;&gt;template_set&lt;/code&gt; slot&lt;/strong&gt; so templates are activation-scoped config;
retire the discovery-tier template path. &lt;em&gt;(After S3; closes Claim 4.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Later / separate epics&lt;/strong&gt; — gates-as-DRG-artefacts; an assets offer surface.
Both are net-new artefact modelling, out of scope for the #2651/#2652 chain.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;guards-to-land-with-the-work&quot;&gt;Guards to land with the work&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;G1&lt;/strong&gt; — single availability seam (&lt;code dir=&quot;auto&quot;&gt;existing_mission_types()&lt;/code&gt;); architectural
test forbids a filesystem glob answering “available” outside it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G2&lt;/strong&gt; — the built-in ID list is &lt;strong&gt;derived&lt;/strong&gt; from &lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository.default()&lt;/code&gt;;
a drift test catches the &lt;code dir=&quot;auto&quot;&gt;show_origin.py:72&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;m_0_6_7&lt;/code&gt; divergence.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G3&lt;/strong&gt; — the default charter is one artefact; the “key absent → all” branches are
deleted; a test asserts an empty repo resolves exactly the default-pack set.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G4&lt;/strong&gt; — retire the &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; type-dir dark copy; collapse
&lt;code dir=&quot;auto&quot;&gt;get_package_asset_root&lt;/code&gt; to the doctrine tree only. &lt;em&gt;(This is #2652.)&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G5&lt;/strong&gt; — move the &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_io.py:347-350&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; tier special-case
into &lt;code dir=&quot;auto&quot;&gt;MissionType.template_set&lt;/code&gt; config.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;G6&lt;/strong&gt; — extend the kind-count triple-guard to include &lt;code dir=&quot;auto&quot;&gt;packs/default.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;related&quot;&gt;Related&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-07-14-2-doctrine-to-core-mission-type-resolution-unification/&quot;&gt;ADR 2026-07-14-2 — Doctrine → Charter → Core Mission-Type Resolution Unification&lt;/a&gt; (#883 slice 1)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-05-16-1-doctrine-layer-merge-semantics/&quot;&gt;ADR 2026-05-16-1 — Doctrine Layer Merge Semantics&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issues: #883, #461, #901, #2651, #2652, and the new default-charter provisioning issue (S1/S2).&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
