<?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-04-04-2-mission-type-mission-and-mission-run-terminology-boundary/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-04-04-2-mission-type-mission-and-mission-run-terminology-boundary/</id>
  <title>Mission Type, Mission, and Mission Run Terminology Boundary</title>
  <updated>2026-04-04T00: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-04-04-2-mission-type-mission-and-mission-run-terminology-boundary/"/>
  <summary>Separates three colliding nouns: Mission Type is the reusable blueprint, Mission is the tracked item under kitty-specs, Mission Run is the persisted runtime session.</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 currently carries multiple conflicting ontologies for the same set of
objects.&lt;/p&gt;
&lt;p&gt;The main collisions are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; sometimes means the reusable workflow blueprint (&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; sometimes means the concrete tracked item under
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; already exists in runtime/state code as the persisted
execution/session instance under &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/&lt;/code&gt;, but parts of the
ongoing rename effort also use &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt; to mean the tracked item.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; is still the dominant tracked-item term in large parts of the
CLI, API, dashboard, docs, tutorials, skills, and website language even
though that noun only fits software delivery naturally.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;phase&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;step contract&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; are used
interchangeably in places where they should describe different layers.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Issue &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/241&quot;&gt;#241&lt;/a&gt; surfaced the
first concrete collision: &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; was proposed to become &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;, but
&lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; already meant mission blueprint/type selection.&lt;/p&gt;
&lt;p&gt;PR &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/348&quot;&gt;#348&lt;/a&gt; moved the system
toward &lt;code dir=&quot;auto&quot;&gt;mission type&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt;, but the branch still leaves one
critical ambiguity unresolved: &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt; is already a runtime/session term
in the codebase.&lt;/p&gt;
&lt;p&gt;Epic &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/364&quot;&gt;#364&lt;/a&gt; and design
spike &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/367&quot;&gt;#367&lt;/a&gt; make the
deeper architectural requirement explicit: Spec Kitty needs one noun per layer,
not a rotating set of aliases.&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;One noun, one layer&lt;/strong&gt; — each canonical term must name exactly one object
in the domain model.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Support all mission types&lt;/strong&gt; — the core tracked-item term must work for
software development, research, documentation, and future mission types.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Preserve runtime clarity&lt;/strong&gt; — runtime/session identity must remain distinct
from planning/delivery identity.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration tractability&lt;/strong&gt; — existing &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission-run&lt;/code&gt;
compatibility surfaces must be migratable without breaking every script at
once.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;API and event safety&lt;/strong&gt; — persisted fields and command flags must not reuse
the same noun for different entities.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Option 1:&lt;/strong&gt; Keep &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; as the canonical tracked item, use
&lt;code dir=&quot;auto&quot;&gt;Mission Type&lt;/code&gt; for the blueprint, and reserve &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; for runtime.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 2:&lt;/strong&gt; Generalize &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; to the canonical tracked item, use
&lt;code dir=&quot;auto&quot;&gt;Mission Type&lt;/code&gt; for the blueprint, reserve &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; for runtime/session
instances, and keep &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; only as a compatibility alias for
software-dev missions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Option 3:&lt;/strong&gt; Use &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; as the canonical tracked item and rename the
runtime/session concept to something else.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: Option 2&lt;/strong&gt;, because it gives Spec Kitty one portable tracked
item noun across all mission types while preserving &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt; for the
runtime/session layer where it already exists.&lt;/p&gt;
&lt;h3 id=&quot;core-terminology-model&quot;&gt;Core Terminology Model&lt;/h3&gt;























































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Canonical term&lt;/th&gt;&lt;th&gt;Layer&lt;/th&gt;&lt;th&gt;Definition&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;Mission Type&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Reusable blueprint&lt;/td&gt;&lt;td&gt;A reusable workflow definition that specifies lifecycle actions, guards, templates, artifacts, action indices, and default doctrine bindings.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Concrete tracked item&lt;/td&gt;&lt;td&gt;The concrete thing being planned, executed, reviewed, and integrated in a repository. Stored under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission-slug&gt;/&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Runtime/session instance&lt;/td&gt;&lt;td&gt;One persisted runtime execution instance for a mission. Stored under &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/&lt;/code&gt; and identified by &lt;code dir=&quot;auto&quot;&gt;mission_run_id&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Work Package&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Planning/review slice&lt;/td&gt;&lt;td&gt;One decomposed slice of work inside a mission.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Action&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Outer lifecycle node&lt;/td&gt;&lt;td&gt;A public lifecycle action such as &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Step Contract&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Action contract&lt;/td&gt;&lt;td&gt;A structured contract that decomposes one mission action into internal steps and delegation hooks.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Procedure&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Reusable subworkflow&lt;/td&gt;&lt;td&gt;A doctrine-level reusable playbook that a step contract may delegate to.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Tactic&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Technique&lt;/td&gt;&lt;td&gt;A smaller reusable technique applied within a procedure or step contract.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;Directive&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Constraint&lt;/td&gt;&lt;td&gt;A rule or policy that constrains behavior.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;specific-naming-rules&quot;&gt;Specific Naming Rules&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Type&lt;/code&gt; is the only canonical name for the reusable blueprint layer.
Use &lt;code dir=&quot;auto&quot;&gt;mission type&lt;/code&gt;, not plain &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;, when the subject is
&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;, or another reusable template.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; is the only canonical name for the concrete tracked item currently
represented by &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;, work package
status, acceptance, and integration.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; is reserved exclusively for the runtime/session instance.
It MUST NOT be used to name the tracked item, directory slug, or top-level
planning scope.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; is not a canonical architecture noun anymore. It remains an
allowed compatibility alias for a &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; whose &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; is
&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Workflow&lt;/code&gt; is an umbrella prose term only. It is not a primary tracked
object. When precision matters, use &lt;code dir=&quot;auto&quot;&gt;mission type&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission action&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;step contract&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Phase&lt;/code&gt; is allowed as explanatory prose for high-level lifecycle discussion,
but technical contracts, APIs, events, docs, and help text should prefer
&lt;code dir=&quot;auto&quot;&gt;mission action&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;step&lt;/code&gt; when referring to concrete runtime nodes.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;command-api-and-state-naming-rules&quot;&gt;Command, API, and State Naming Rules&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--mission-type&lt;/code&gt; is the canonical selector for the reusable blueprint.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; is the canonical selector for the concrete tracked mission.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--mission-run&lt;/code&gt; is reserved for runtime/session selectors only.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; is a compatibility alias for &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; on software-dev
legacy surfaces during migration.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt; is a compatibility field name only. The canonical tracked
item identifier is &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_run_id&lt;/code&gt; is the canonical runtime/session identifier and must never
alias a tracked mission slug.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;compatibility-and-migration-policy&quot;&gt;Compatibility and Migration Policy&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Existing user-facing and machine-facing surfaces may dual-read and dual-write
legacy names during migration.&lt;/li&gt;
&lt;li&gt;Canonical docs, glossary entries, architecture docs, and new APIs MUST use
the terminology in this ADR immediately.&lt;/li&gt;
&lt;li&gt;Compatibility aliases must be explicitly labeled as aliases or deprecated
surfaces. They must not be presented as co-equal canonical terms.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; may remain in examples, tutorials, and public marketing copy only
when the text is specifically about software delivery outcomes, not when
describing the generic product model.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;decision-on-step-contracts-and-procedures&quot;&gt;Decision on Step Contracts and Procedures&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Mission Type&lt;/code&gt; defines the outer lifecycle and the available mission
actions.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Step Contract&lt;/code&gt; is the executable action contract for one mission action.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Procedure&lt;/code&gt; is a reusable doctrine playbook used by a step contract to
supply structured guidance for part of an action.&lt;/li&gt;
&lt;li&gt;A procedure is not a mission, not a mission action, and not a mission run.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;decision-on-existing-technical-artifact-names&quot;&gt;Decision on Existing Technical Artifact Names&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt; remains an established technical filename for the
mission-type runtime DAG. It is not a &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; artifact and must not be
described that way in docs or code comments.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;positive&quot;&gt;Positive&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The tracked-item noun now works across software, research, documentation, and
future mission types.&lt;/li&gt;
&lt;li&gt;Runtime/session identity stays cleanly separate from planning/delivery
identity.&lt;/li&gt;
&lt;li&gt;Step contract and procedure language can be defined without overloading
&lt;code dir=&quot;auto&quot;&gt;workflow&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Public docs can explain the system without forcing every non-software use
case into the word &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;negative&quot;&gt;Negative&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Some of PR #348’s &lt;code dir=&quot;auto&quot;&gt;mission-run&lt;/code&gt; tracked-item naming will need to be reversed
or deprecated.&lt;/li&gt;
&lt;li&gt;CLI, API, dashboard, tutorial, and website copy will all require coordinated
updates.&lt;/li&gt;
&lt;li&gt;Event/API compatibility fields such as &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt; will need a deprecation
plan instead of an ad-hoc drift.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;neutral&quot;&gt;Neutral&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Existing legacy files, commands, and docs may temporarily preserve old names
as compatibility wrappers while the migration runs.&lt;/li&gt;
&lt;li&gt;Public marketing copy may still use ordinary English words like &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt;
when describing software outcomes, so long as it does not redefine the
product model.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;This decision is validated when all of the following are true:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;No canonical doc or glossary entry uses &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt; to mean the tracked
mission under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;No canonical CLI help text or API contract uses &lt;code dir=&quot;auto&quot;&gt;--mission-run&lt;/code&gt; to select a
tracked mission slug.&lt;/li&gt;
&lt;li&gt;Runtime/state code uses &lt;code dir=&quot;auto&quot;&gt;mission_run_id&lt;/code&gt; only for execution/session identity.&lt;/li&gt;
&lt;li&gt;The generic product model in docs and website copy says
&lt;code dir=&quot;auto&quot;&gt;Mission Type -&gt; Mission -&gt; Mission Run&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; clearly marked as a
software-dev compatibility alias.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;Step Contract&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;Procedure&lt;/code&gt; are described consistently across doctrine,
runtime, docs, skills, and public explanations.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;option-1-keep-feature-as-the-canonical-tracked-item&quot;&gt;Option 1: Keep &lt;code dir=&quot;auto&quot;&gt;Feature&lt;/code&gt; as the canonical tracked item&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lowest short-term migration cost.&lt;/li&gt;
&lt;li&gt;Matches current 2.x filesystem and many existing docs.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Makes research and documentation missions sound like software features.&lt;/li&gt;
&lt;li&gt;Keeps the product model biased toward one mission type.&lt;/li&gt;
&lt;li&gt;Leaves the broader terminology problem only partially solved.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-2-generalize-mission-as-the-canonical-tracked-item&quot;&gt;Option 2: Generalize &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; as the canonical tracked item&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Gives one generic tracked-item noun across all mission types.&lt;/li&gt;
&lt;li&gt;Preserves &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; for runtime/session identity where it already exists.&lt;/li&gt;
&lt;li&gt;Makes issue #367’s outer-lifecycle model easier to explain cleanly.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Requires a larger rename and compatibility program.&lt;/li&gt;
&lt;li&gt;Forces explicit migration rules for &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission-run&lt;/code&gt; legacy
surfaces.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;option-3-use-mission-run-as-the-canonical-tracked-item&quot;&gt;Option 3: Use &lt;code dir=&quot;auto&quot;&gt;Mission Run&lt;/code&gt; as the canonical tracked item&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Avoids renaming the tracked item back away from some of PR #348’s current
help text.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Directly collides with the existing runtime/session use of &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Forces a second rename for &lt;code dir=&quot;auto&quot;&gt;mission_run_id&lt;/code&gt;, runtime state, and run-index
files.&lt;/li&gt;
&lt;li&gt;Makes the domain model less precise, not more.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Related Issues:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/241&quot;&gt;#241&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/364&quot;&gt;#364&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/367&quot;&gt;#367&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Related Pull Request:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/348&quot;&gt;#348&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Related ADRs:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;2026-02-17-1-canonical-next-command-runtime-loop.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;2026-02-17-2-runtime-owned-mission-discovery-loading.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;2026-04-03-1-execution-lanes-own-worktrees-and-mission-branches.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;2026-04-03-3-feature-acceptance-runs-on-the-integrated-mission-branch.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
