<?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-09-20-1-canonical-mission-type-source/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-09-20-1-canonical-mission-type-source/</id>
  <title>ADR: Org-aware mission-type loader + `path_conventions` doctrine slot (full charter convergence deferred to #2652)</title>
  <updated>2026-09-20T00: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-09-20-1-canonical-mission-type-source/"/>
  <summary>Makes the mission-type loader org-aware and adds an additive `path_conventions` charter doctrine slot; full convergence onto charter mission types is deferred to #2652.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;Spec Kitty resolves a mission’s &lt;em&gt;type&lt;/em&gt; through &lt;strong&gt;three&lt;/strong&gt; independent registries that
disagree (issues #3831, #4088):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Legacy template loader&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/mission.py&lt;/code&gt; loads a &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; from a
directory containing &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;_mission_path_by_name&lt;/code&gt;, consulting only two
tiers (&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;name&gt;&lt;/code&gt;, then packaged built-ins). It is &lt;strong&gt;org-blind&lt;/strong&gt; and
bypasses the six-tier resolver (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/runtime/resolver.py&lt;/code&gt;) that the
&lt;em&gt;command-template&lt;/em&gt; lookup already uses.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Org-tier governance resolver&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;charter.activation.mission_type_profiles. resolve_mission_type_context&lt;/code&gt; (+ &lt;code dir=&quot;auto&quot;&gt;MissionTypeRepository&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_org_dirs&lt;/code&gt;), which
&lt;em&gt;is&lt;/em&gt; org-aware.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt; resolver&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;runtime/next/runtime_bridge_io.py&lt;/code&gt;, org-aware,
owns the runtime step-DAG.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Because (1) never consults the org tier, an org-pack-activated custom mission type falls
through &lt;code dir=&quot;auto&quot;&gt;_mission_path_by_name&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;get_mission_for_feature&lt;/code&gt; swallows the
&lt;code dir=&quot;auto&quot;&gt;MissionNotFoundError&lt;/code&gt;, and the mission silently loads as &lt;strong&gt;software-dev&lt;/strong&gt; — carrying
software-dev’s path conventions and required/optional artifact sets instead of its own.
#4088 is the same function failing to consult a project override tier.&lt;/p&gt;
&lt;h3 id=&quot;re-scope-discovery-2026-09-21-the-two-sources-encode-different-concerns&quot;&gt;Re-scope discovery (2026-09-21): the two sources encode different concerns&lt;/h3&gt;
&lt;p&gt;This mission began as the #2652 “single canonical mission-type source” slice — converge
mission-type loading onto charter &lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType&lt;/code&gt; and retire the
&lt;code dir=&quot;auto&quot;&gt;specify_cli/mission.py&lt;/code&gt; resolver. Implementation surfaced a load-bearing fact the planning
had assumed away: &lt;strong&gt;the charter/doctrine tier does not carry built-in path/artifact data
equivalent to the legacy &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;, and the two encode different concerns.&lt;/strong&gt; Legacy
&lt;code dir=&quot;auto&quot;&gt;artifacts.required/.optional&lt;/code&gt; is a &lt;strong&gt;template-selection&lt;/strong&gt; list (what a mission template
offers); charter &lt;code dir=&quot;auto&quot;&gt;expected_artifacts.required_by_step&lt;/code&gt; is a &lt;strong&gt;runtime step-gate
completeness&lt;/strong&gt; spec. Their token sets diverge materially, and &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; is
unpopulated (&lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;) for all three built-ins. A wholesale “read everything from charter”
rewrite would therefore silently change built-in behavior (SC-004/NFR-001 regression), not
refactor it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Decision (operator, 2026-09-21): re-scope to the targeted, behavior-safe fix&lt;/strong&gt; — make the
loader org-aware (the fix #3831’s author originally proposed) and defer the full convergence
(retiring the resolver + reconciling/authoring built-in doctrine data as a two-concern
merge) to the &lt;strong&gt;#2652 epic&lt;/strong&gt;. The &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; slot and the charter &lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt;
home (below) are retained as the foundation that convergence will build on.&lt;/p&gt;
&lt;p&gt;This ADR is a companion to, not a reversal of, two earlier decisions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ADR 2026-07-14-2&lt;/strong&gt; (Doctrine → Charter → Core Mission-Type Resolution Unification)
already named the north-star — &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; should eventually be
deleted and &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; should be an ordinary built-in doctrine mission type fed
through the charter, with no hardcoded core knowledge of &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;. This mission
is a concrete step toward that north-star, specifically for the &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;
&lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissionConfig&lt;/code&gt; resolver (a &lt;em&gt;third&lt;/em&gt;, still-undecided surface that ADR
2026-07-14-2’s problem statement did not itself retire).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR 2026-07-15-1&lt;/strong&gt; (Doctrine offers, Charter activates, Runtime consumes) established
the layering this mission’s &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; slot lives inside: charter is the single
offering surface a doctrine artifact (a &lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt;) is authored against; runtime and
&lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; consume it, never author competing copies.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It &lt;strong&gt;reconciles ADR 2026-08-28-1&lt;/strong&gt; (a project &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; override precedes the
doctrine default). That ADR’s “doctrine default” side was, at the time, &lt;code dir=&quot;auto&quot;&gt;MissionConfig. paths&lt;/code&gt; sourced from &lt;code dir=&quot;auto&quot;&gt;specify_cli/mission.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; tier — the resolver this
mission makes org-aware (full retirement deferred to #2652). 2026-08-28-1’s &lt;em&gt;decision&lt;/em&gt; (project override remaps the resolved
directory; the accept-blocking policy from #3783 is unchanged; one canonical frozenset of
valid path keys, reused by both validation and the override reader) is preserved
unmodified; the &lt;em&gt;doctrine-default&lt;/em&gt; side of that precedence chain moves onto the charter
&lt;code dir=&quot;auto&quot;&gt;MissionType.path_conventions&lt;/code&gt; slot introduced here. &lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt; — the
“one canonical frozenset” 2026-08-28-1 already called for — is the concrete relocation
target: charter becomes its canonical home (Directive 044, single canonical authority),
per FR-004/FR-009 of this mission’s spec.&lt;/p&gt;
&lt;h3 id=&quot;the-mission-name-collision&quot;&gt;The &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; name collision&lt;/h3&gt;
&lt;p&gt;Two independent, unrelated classes are both named &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; in this codebase, and this
mission’s convergence makes the collision load-bearing rather than incidental:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.mission.Mission&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/mission.py&lt;/code&gt;) — the legacy
&lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;-backed domain object this ADR makes org-aware (&lt;code dir=&quot;auto&quot;&gt;MissionConfig&lt;/code&gt;-validated,
carries &lt;code dir=&quot;auto&quot;&gt;workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;artifacts&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;paths&lt;/code&gt;, etc.; full retirement deferred to #2652). This
is the resolver named in the Context section above.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter.offering.missions.models.Mission&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/missions/ models.py:151&lt;/code&gt;) — an unrelated &lt;strong&gt;schema-generation model&lt;/strong&gt; used only by
&lt;code dir=&quot;auto&quot;&gt;scripts/generate_schemas.py&lt;/code&gt; to emit &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/schemas/mission.schema.yaml&lt;/code&gt;
(a minimal &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;key&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;steps&lt;/code&gt; shape). It is explicitly &lt;strong&gt;not&lt;/strong&gt; the
runtime domain model (see its own docstring) and has no &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;MissionConfig&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; relationship at all.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Neither &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; class is renamed by this mission — that is out of scope here — but a
reader who greps &lt;code dir=&quot;auto&quot;&gt;class Mission&lt;/code&gt; and finds two hits, in two packages this mission is
actively moving authority &lt;em&gt;between&lt;/em&gt;, needs the disambiguation on record: &lt;strong&gt;the &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt;
this ADR concerns (makes org-aware; retirement deferred to #2652) is
&lt;code dir=&quot;auto&quot;&gt;specify_cli.mission.Mission&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;charter/offering/missions/models.py&lt;/code&gt; is untouched and unrelated.&lt;/strong&gt; The field this
mission &lt;em&gt;does&lt;/em&gt; add lives on a third, distinctly-named class in the same module —
&lt;code dir=&quot;auto&quot;&gt;charter.offering.missions.models.MissionType&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:234&lt;/code&gt;) — which is not &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; at all.
Future work that renames either &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; to resolve this collision should treat this ADR
as the reference for which one is which.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Org-aware mission-type loader (this mission).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;get_mission_by_name&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;specify_cli/mission.py&lt;/code&gt;) resolves &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; through the shared &lt;strong&gt;org-aware&lt;/strong&gt;
resolver &lt;code dir=&quot;auto&quot;&gt;specify_cli.runtime.resolver.resolve_mission&lt;/code&gt; (override → legacy → org →
global → package — the same chain command-template resolution already uses), and, when a
type is org-registered via a sparse &lt;code dir=&quot;auto&quot;&gt;mission_types/&amp;#x3C;type&gt;.yaml&lt;/code&gt; but ships no
&lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;, builds a &lt;strong&gt;neutral &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt;&lt;/strong&gt; (the org type’s &lt;code dir=&quot;auto&quot;&gt;display_name&lt;/code&gt; identity,
its own &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; or none, no software-dev conventions). &lt;code dir=&quot;auto&quot;&gt;get_mission_for_feature&lt;/code&gt;
preserves the typeless→software-dev &lt;em&gt;template&lt;/em&gt; default and now raises a visible
&lt;code dir=&quot;auto&quot;&gt;MissionNotFoundError&lt;/code&gt; for a typed-but-unknown type instead of warn-and-substituting.
This closes #3831 and #4088 without touching built-in behavior. The legacy &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;MissionConfig&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; resolver is &lt;strong&gt;retained&lt;/strong&gt; here — retiring it, and making
charter &lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType&lt;/code&gt; the &lt;em&gt;sole&lt;/em&gt; source, is the &lt;strong&gt;#2652 epic&lt;/strong&gt; (it requires the
two-concern merge + built-in doctrine-data authoring described in the Re-scope section).
Direction of dependency is unchanged: consumers depend downward onto charter, never the
reverse (C-001).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; — a new doctrine slot (FR-004).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt; gains an optional
&lt;code dir=&quot;auto&quot;&gt;path_conventions: dict[str, str] | None&lt;/code&gt; field (WP02, &lt;code dir=&quot;auto&quot;&gt;models.py&lt;/code&gt;). A mission type
that declares &lt;strong&gt;no&lt;/strong&gt; conventions (&lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;, the default) is a pure no-op for downstream
consumers — accept-path validation does not fall back to another type’s shape (e.g.
software-dev’s &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;) when a type is silent. This is the one genuinely new
schema this mission introduces; every other legacy &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; field migrates to an
existing charter/dossier home or is retired outright (see the mission’s &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;
consumer census).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt; relocates into charter (FR-004/FR-009, Directive 044).&lt;/strong&gt; The
frozenset of valid path-convention keys — &lt;code dir=&quot;auto&quot;&gt;{&quot;workspace&quot;, &quot;tests&quot;, &quot;deliverables&quot;, &quot;documentation&quot;, &quot;data&quot;}&lt;/code&gt; — is added to &lt;code dir=&quot;auto&quot;&gt;charter.offering.missions.models&lt;/code&gt; (WP02,
T011) as the &lt;strong&gt;canonical&lt;/strong&gt; home, together with a &lt;code dir=&quot;auto&quot;&gt;validate_path_conventions&lt;/code&gt; validator
that rejects (raises &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt;, fail-closed) any key outside that set. The historical
copy at &lt;code dir=&quot;auto&quot;&gt;specify_cli.mission.VALID_PATH_KEYS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission.py:159&lt;/code&gt;) is deliberately &lt;strong&gt;not&lt;/strong&gt;
deleted here — both copies carry the identical literal value, pinned by the WP02 test
suite (&lt;code dir=&quot;auto&quot;&gt;tests/charter/test_path_conventions_slot.py&lt;/code&gt;) so drift is caught. Deleting the
&lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; copy and repointing its importers (&lt;code dir=&quot;auto&quot;&gt;config/path_conventions.py&lt;/code&gt;) onto the
charter home is part of the &lt;strong&gt;#2652&lt;/strong&gt; convergence (originally WP04, now deferred with the
rest of the resolver retirement), not this slice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; name collision is documented, not resolved, here&lt;/strong&gt; (see above). No
rename is performed by this mission.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Positive.&lt;/strong&gt; Org-tier and project-override custom mission types resolve as themselves
instead of being warn-and-substituted with software-dev (#3831, #4088 closed by this
mission). A typed-but-unknown mission type now fails visibly instead of silently. Path
conventions get a doctrine-governed slot for org types to declare.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Built-ins byte-unchanged.&lt;/strong&gt; The loader special-cases the resolver’s PACKAGE tier back to
the historical &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&amp;#x3C;type&gt;/&lt;/code&gt; source, so built-in path conventions and
artifact sets are identical to before and stay consistent with &lt;code dir=&quot;auto&quot;&gt;discover_missions&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;list_available_missions&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;get_active_mission&lt;/code&gt; (which read the same source). The two
built-in package roots (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; vs the canonical
&lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt;) have pre-existing drift (e.g. &lt;code dir=&quot;auto&quot;&gt;documentation.paths.deliverables&lt;/code&gt;
&lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;docs/output/&lt;/code&gt;, and terminology); unifying them onto the canonical root and
deleting the &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; copy is the #2652 convergence, deliberately out of scope here so
this slice changes no built-in behavior. The &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; project tier now emits the
shared resolver’s &lt;code dir=&quot;auto&quot;&gt;run spec-kitty migrate&lt;/code&gt; deprecation nudge, consistent with
command-template resolution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cost / risk — standing dual-home until #2652.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt; exists in two places
(charter canonical + the retained &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; copy) until the #2652 convergence deletes
the legacy resolver. Both are value-pinned by tests so they cannot drift. This is a
scoped, documented exception to single-authority for the life of the deferral, not silent
duplication.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layering.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt; are added strictly &lt;em&gt;downward&lt;/em&gt;
into &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; — no new &lt;code dir=&quot;auto&quot;&gt;charter → specify_cli&lt;/code&gt; import is introduced (C-001). WP02 does
not touch &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; doctrine content or a doctrine-derived pack schema, so the
pack-manifest regen gate (&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph&lt;/code&gt;) is not triggered by
this WP; it remains in scope for whichever later WP first authors a built-in
&lt;code dir=&quot;auto&quot;&gt;mission_types/*.yaml&lt;/code&gt; entry with a &lt;code dir=&quot;auto&quot;&gt;path_conventions:&lt;/code&gt; key.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ATDD.&lt;/strong&gt; WP01 already landed red-first repros for #3831/#4088 through the pre-existing
entry point (ADR 2026-07-17-1 discipline); WP02’s &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt;
slot is covered by new, issue-pinned unit tests
(&lt;code dir=&quot;auto&quot;&gt;tests/charter/test_path_conventions_slot.py&lt;/code&gt;) rather than a repro, since the slot is
net-new rather than a defect fix.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;alternatives-considered&quot;&gt;Alternatives Considered&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Give &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; its own top-level YAML artifact / schema file distinct from
&lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt;.&lt;/strong&gt; Rejected: &lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt; is already the governed descriptor for a
built-in or extension mission type (one YAML file per type, &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;-keyed); a sibling
artifact would duplicate that identity and reintroduce a second registry to keep in
sync — exactly the class of defect this mission closes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Warn-and-continue on an unknown &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; key&lt;/strong&gt; (mirroring the historical
&lt;code dir=&quot;auto&quot;&gt;specify_cli.mission.MissionConfig&lt;/code&gt; behaviour, which used &lt;code dir=&quot;auto&quot;&gt;warnings.warn&lt;/code&gt;). Rejected:
charter’s &lt;code dir=&quot;auto&quot;&gt;MissionType&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissionStep&lt;/code&gt; models are &lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;, fail-closed models
throughout (see &lt;code dir=&quot;auto&quot;&gt;_validate_id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;validate_action_sequence&lt;/code&gt;); a silently-tolerated typo
in a path-convention key is exactly the “looks configured, isn’t enforced” failure mode
Directive 044 (single canonical authority, no silent drift) exists to prevent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rename one of the two &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; classes as part of this WP.&lt;/strong&gt; Rejected as out of
scope: WP02’s owned files are &lt;code dir=&quot;auto&quot;&gt;models.py&lt;/code&gt;, this ADR, and the new test file; a rename
touches every consumer of whichever class is renamed and belongs to a dedicated,
reviewed WP of its own.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Issues: #3831 (org-tier custom mission type invisible to the loader), #4088 (project
override tier never consulted), #2652 (single canonical mission-type source epic).&lt;/li&gt;
&lt;li&gt;Mission: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/mission-type-canonical-source-01M302V9/spec.md&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;.../plan.md&lt;/code&gt; (consumer census, WP sequencing).&lt;/li&gt;
&lt;li&gt;Related ADRs: &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-07-14-2-doctrine-to-core-mission-type-resolution-unification.md&lt;/code&gt;
(companion — names the north-star this mission advances),
&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-07-15-1-doctrine-offers-charter-activates-runtime-consumes.md&lt;/code&gt;
(companion — the layering &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; lives inside),
&lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-28-1-project-path-convention-override-precedes-doctrine.md&lt;/code&gt;
(reconciled — its override-precedence decision is preserved; its doctrine-default side
now points at &lt;code dir=&quot;auto&quot;&gt;MissionType.path_conventions&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; resolver is made
org-aware here, with full retirement deferred to #2652).&lt;/li&gt;
&lt;li&gt;Charter: Directive 044 (single canonical authority / no drifting duplicate lists), C-001
(&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; must never import &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;), C-005 (routing-safety coupling between the
path-convention value and the mission artifact-token vocabulary, unchanged by this ADR).&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
