<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/context/orchestration/">
  <id>https://docs.spec-kitty.ai/context/orchestration/</id>
  <title>Context: Orchestration</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/context/orchestration/"/>
  <summary>Glossary context for orchestration: lifecycle and runtime orchestration semantics, including the repository, project, and mission-run terms.</summary>
  <content type="html">&lt;h2 id=&quot;context-orchestration&quot;&gt;Context: Orchestration&lt;/h2&gt;
&lt;p&gt;Terms describing lifecycle and runtime orchestration semantics.&lt;/p&gt;
&lt;p&gt;Mission topology terms (the four topologies, write checkout, repo-root lane, code lane, protected target, mission branch, lane work tip, absorbed lane) are defined in &lt;a href=&quot;/context/topology/&quot;&gt;Context: Topology&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;repository&quot;&gt;Repository&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The local git repository that a &lt;a href=&quot;#project&quot;&gt;Project&lt;/a&gt; is initialized from and executes within.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Use this term when the repository boundary itself matters, especially for repository-scoped identity.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#project&quot;&gt;Project&lt;/a&gt;, &lt;a href=&quot;#build&quot;&gt;Build&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;project&quot;&gt;Project&lt;/h3&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Entire repository initialized for Spec Kitty workflow execution.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-type&quot;&gt;Mission Type&lt;/h3&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Reusable workflow blueprint that configures the mission’s steps (actions), their templates, and guardrails.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;build&quot;&gt;Build&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;One checkout or worktree execution context inside a &lt;a href=&quot;#repository&quot;&gt;Repository&lt;/a&gt;, identified by machine and build-scoped runtime identity.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Use this term when distinguishing per-worktree or per-machine runtime context from the repository boundary itself.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#repository&quot;&gt;Repository&lt;/a&gt;, &lt;a href=&quot;#mission-run&quot;&gt;Mission Run&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission&quot;&gt;Mission&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A unit of governed delivery: the concrete tracked item, stored under the Mission’s own spec directory and linked to exactly one Mission Type, that carries one piece of work from agreed intent to a verified result.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;This is the generic tracked-item noun across software, research, planning, and documentation work.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the reusable workflow blueprint the Mission is an instance of — use &lt;a href=&quot;#mission-type&quot;&gt;Mission Type&lt;/a&gt;. The concept is one runtime execution of the Mission’s step loop — use &lt;a href=&quot;#mission-run&quot;&gt;Mission Run&lt;/a&gt;. Never use the retired alias “Feature” for the Mission domain object (Terminology Canon).&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-run&quot;&gt;Mission Run&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;One runtime execution of a Mission’s step loop, keyed by &lt;code dir=&quot;auto&quot;&gt;run_id&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Scoping rule&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Runtime events should be scoped by the run’s &lt;code dir=&quot;auto&quot;&gt;run_id&lt;/code&gt; where available&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the tracked unit of work itself — use &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;. Avoid “mission session”.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;feature&quot;&gt;Feature&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Retired alias for a &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt; whose mission type is &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;deprecated&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; (historical)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Prohibited for the Mission domain object in active surfaces (Terminology Canon). Use &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;. Generic “feature” in the product-capability sense, and the Gherkin keyword, are unaffected. Legacy machine keys such as &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt; are still emitted alongside the canonical &lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt; as legacy output aliases (#5206), not read-only survivors.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;work-package&quot;&gt;work package&lt;/h3&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Executable slice of work inside a mission plan, typically represented as &lt;code dir=&quot;auto&quot;&gt;WPxx&lt;/code&gt; tasks.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-action&quot;&gt;Mission Action&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Outer lifecycle action for a mission, 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;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-type&quot;&gt;Mission Type&lt;/a&gt;, &lt;a href=&quot;#step-contract&quot;&gt;step contract&lt;/a&gt;, &lt;a href=&quot;/context/charter/#procedure&quot;&gt;Procedure&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;step-contract&quot;&gt;step contract&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Structured contract for one mission action, including step sequencing, guard evaluation, prompt binding, and delegation hooks.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-action&quot;&gt;Mission Action&lt;/a&gt;, &lt;a href=&quot;#mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/a&gt;, &lt;a href=&quot;/context/charter/#procedure&quot;&gt;Procedure&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;workflow&quot;&gt;Workflow&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Umbrella prose term for the overall flow of work.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical (generic prose only)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Rule&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Use &lt;a href=&quot;#mission-type&quot;&gt;Mission Type&lt;/a&gt;, &lt;a href=&quot;#mission-action&quot;&gt;Mission Action&lt;/a&gt;, &lt;a href=&quot;#step-contract&quot;&gt;step contract&lt;/a&gt;, or &lt;a href=&quot;/context/charter/#procedure&quot;&gt;Procedure&lt;/a&gt; when precision matters.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;workpackage-alias&quot;&gt;WorkPackage (Alias)&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Legacy lexical variant of &lt;a href=&quot;#work-package&quot;&gt;work package&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Canonical entry&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#work-package&quot;&gt;work package&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;lane&quot;&gt;Lane&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Status lane: a work package’s state position in the canonical lifecycle FSM. The nine canonical lanes are &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;. The happy path is &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; is reachable from every non-terminal lane and &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; from every lane. Alias: &lt;code dir=&quot;auto&quot;&gt;doing&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Other sense&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Execution lane&lt;/strong&gt;: a group of work packages that &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; computes into &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, which runs in one place. A code lane has its own lane branch and &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; lane worktree; the &lt;code dir=&quot;auto&quot;&gt;lane-planning&lt;/code&gt; lane has no lane branch and resolves to the &lt;a href=&quot;/context/topology/#write-checkout&quot;&gt;write checkout&lt;/a&gt;, normally the repository root checkout. Defined in &lt;a href=&quot;/context/topology/#code-lane&quot;&gt;Context: Topology&lt;/a&gt; (&lt;a href=&quot;/context/topology/#code-lane&quot;&gt;code lane&lt;/a&gt;, &lt;a href=&quot;/context/topology/#repo-root-lane&quot;&gt;repo-root lane&lt;/a&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Never write bare “lane” when the sense matters: say “status lane” for the lifecycle position defined here, and “execution lane”, “code lane”, “lane branch” or “lane worktree” for where work runs.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Configuration file (&lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt;) that defines a mission type’s step graph, action ordering, dependencies, and prompt-template bindings.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-type&quot;&gt;Mission Type&lt;/a&gt;, &lt;a href=&quot;#step-dependency&quot;&gt;Step Dependency&lt;/a&gt;, &lt;a href=&quot;#step-contract&quot;&gt;step contract&lt;/a&gt;, &lt;a href=&quot;#command-template&quot;&gt;Command Template&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;step-dependency&quot;&gt;Step Dependency&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A declared relationship saying “this step cannot start until that step finishes.” Defined in mission-runtime YAML to enforce ordering.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/a&gt;, &lt;a href=&quot;#step-sequence&quot;&gt;Step Sequence&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;step-sequence&quot;&gt;Step Sequence&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The order in which mission steps execute, determined by the step list and dependency graph in mission-runtime YAML.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#step-dependency&quot;&gt;Step Dependency&lt;/a&gt;, &lt;a href=&quot;#mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;command-template&quot;&gt;Command Template&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A markdown file that provides the prompt for a specific mission action. Located in the mission type’s template directory and loaded at runtime based on mission type and agent configuration.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#template-resolution&quot;&gt;Template Resolution&lt;/a&gt;, &lt;a href=&quot;#mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;template-resolution&quot;&gt;Template Resolution&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The process of finding and loading the correct command template for a given mission action, considering which mission type is active and which agent is running.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#command-template&quot;&gt;Command Template&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-discovery&quot;&gt;Mission Discovery&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;How the runtime finds and loads mission-type definition files (&lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt;) from configured mission-pack roots at startup.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-type&quot;&gt;Mission Type&lt;/a&gt;, &lt;a href=&quot;#mission-runtime-yaml&quot;&gt;Mission-Runtime YAML&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;command-envelope&quot;&gt;Command Envelope&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Standard JSON wrapper around the output of every &lt;code dir=&quot;auto&quot;&gt;spec-kitty orchestrator-api&lt;/code&gt; command: &lt;code dir=&quot;auto&quot;&gt;contract_version&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;command&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;timestamp&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;correlation_id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;data&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;make_envelope&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/orchestrator_api/envelope.py&lt;/code&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#orchestrator-api&quot;&gt;Orchestrator API&lt;/a&gt;, &lt;a href=&quot;#contract-version&quot;&gt;Contract Version&lt;/a&gt;, &lt;a href=&quot;/context/technology-foundations/#json&quot;&gt;JSON&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;contract-version&quot;&gt;Contract Version&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Version number on the orchestrator API that tells consumers whether the API has changed in a breaking way.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#orchestrator-api&quot;&gt;Orchestrator API&lt;/a&gt;, &lt;a href=&quot;#command-envelope&quot;&gt;Command Envelope&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;orchestrator-api&quot;&gt;Orchestrator API&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;JSON-based interface that lets external orchestration tools drive Spec Kitty operations programmatically: the &lt;code dir=&quot;auto&quot;&gt;spec-kitty orchestrator-api&lt;/code&gt; command group, whose commands answer in the &lt;a href=&quot;#command-envelope&quot;&gt;Command Envelope&lt;/a&gt; instead of human-facing output.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#command-envelope&quot;&gt;Command Envelope&lt;/a&gt;, &lt;a href=&quot;/context/technology-foundations/#api&quot;&gt;API&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;decision&quot;&gt;Decision&lt;/h3&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A structured choice presented to the Human-in-Charge (HiC) or their delegated agent during the next-command loop. Each decision describes what needs to happen next and offers options to advance the mission. In event-backed runtimes, a pending Decision is tracked until answered, then closed.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Lifecycle&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;In event-backed runtimes, opened by &lt;a href=&quot;#decision-input-request&quot;&gt;Decision Input Request&lt;/a&gt;; closed by &lt;a href=&quot;#decision-input-answer&quot;&gt;Decision Input Answer&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Former SaaS projection&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Before the hosted surfaces were removed from open-core (#6164), the hosted product materialised a Decision as a &lt;code dir=&quot;auto&quot;&gt;DecisionInboxItem&lt;/code&gt; (pending → answered) in the TeamSpace. Open-core no longer sends it there.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Not to be confused with&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;SaaS &lt;code dir=&quot;auto&quot;&gt;Decision&lt;/code&gt; (an immutable recorded past collaboration choice); SaaS &lt;code dir=&quot;auto&quot;&gt;DecisionPoint&lt;/code&gt; (a first-class team-consultation entity that can be widened, deferred, or resolved independently of the loop).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#decision-kind&quot;&gt;Decision Kind&lt;/a&gt;, &lt;a href=&quot;#decision-input-request&quot;&gt;Decision Input Request&lt;/a&gt;, &lt;a href=&quot;#decision-input-answer&quot;&gt;Decision Input Answer&lt;/a&gt;, &lt;a href=&quot;/context/identity/#human-in-charge-hic&quot;&gt;Human-in-Charge (HiC)&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;decision-kind&quot;&gt;Decision Kind&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The type of choice being presented — for example, selecting which step to run next, resolving a conflict, or assigning a work package to an agent. In the &lt;code dir=&quot;auto&quot;&gt;spec-kitty next --json&lt;/code&gt; contract this is carried as the top-level &lt;code dir=&quot;auto&quot;&gt;kind&lt;/code&gt; field; &lt;code dir=&quot;auto&quot;&gt;DecisionInputRequested&lt;/code&gt; events are emitted only for &lt;code dir=&quot;auto&quot;&gt;decision_required&lt;/code&gt; choices and do not repeat that field.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;, &lt;a href=&quot;#decision-input-request&quot;&gt;Decision Input Request&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;decision-input-request&quot;&gt;Decision Input Request&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The event emitted by the runtime when it opens a &lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt; and requires a response from the HiC or a delegated agent. Carries the question text, candidate options, step context, and a unique &lt;code dir=&quot;auto&quot;&gt;decision_id&lt;/code&gt;. Opening a Decision Input Request is what makes a Decision “pending”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Event type&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DecisionInputRequested&lt;/code&gt; (in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Former SaaS effect&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Before #6164, created a &lt;code dir=&quot;auto&quot;&gt;DecisionInboxItem&lt;/code&gt; row with &lt;code dir=&quot;auto&quot;&gt;state=pending&lt;/code&gt; in the hosted product. Open-core no longer sends it there.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;, &lt;a href=&quot;#decision-input-answer&quot;&gt;Decision Input Answer&lt;/a&gt;, &lt;a href=&quot;#mission-run&quot;&gt;Mission Run&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;decision-input-answer&quot;&gt;Decision Input Answer&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The event emitted when the HiC or a delegated agent answers a pending &lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;. Carries the chosen answer, the actor identity, and the originating &lt;code dir=&quot;auto&quot;&gt;decision_id&lt;/code&gt;. Answering closes the Decision; the loop continues.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Event type&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;DecisionInputAnswered&lt;/code&gt; (in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Former SaaS effect&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Before #6164, updated the matching &lt;code dir=&quot;auto&quot;&gt;DecisionInboxItem&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;state=answered&lt;/code&gt; in the hosted product. Open-core no longer sends it there.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;, &lt;a href=&quot;#decision-input-request&quot;&gt;Decision Input Request&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;runtime-bridge&quot;&gt;Runtime Bridge&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The adapter that connects the CLI’s decision loop to the mission execution engine. It translates internal runtime decisions into the format the HiC or agent sees while keeping mission identity separate from mission-run identity.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;, &lt;a href=&quot;/context/identity/#human-in-charge-hic&quot;&gt;Human-in-Charge (HiC)&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;mission-state-derivation&quot;&gt;Mission State Derivation&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The process of figuring out where a mission currently stands by reading filesystem artifacts and event logs, so the system can determine what mission actions are available next.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission-run&quot;&gt;Mission Run&lt;/a&gt;, &lt;a href=&quot;#decision&quot;&gt;Decision&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;base-branch&quot;&gt;base branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Overloaded key with two distinct scopes. (1) At the &lt;strong&gt;mission level&lt;/strong&gt; (branch-context JSON output): alias for &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; — the branch the mission is rooted in; &lt;code dir=&quot;auto&quot;&gt;base_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; carry the same value in branch-context output. (2) At the &lt;strong&gt;worktree/WP level&lt;/strong&gt; (WP prompt frontmatter): the specific git branch from which the individual lane worktree was created; this may be a lane branch (e.g. &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-lane-a&lt;/code&gt;) rather than the target branch itself. JSON key: &lt;code dir=&quot;auto&quot;&gt;base_branch&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#planning-base-branch&quot;&gt;Planning base branch&lt;/a&gt;, &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;branch-strategy-gate&quot;&gt;branch strategy gate&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The mission-create guard for PR-bound missions that requires an explicit operator or agent decision before planning artifacts are written on a primary branch. Interactive callers may confirm at the prompt; non-interactive callers record the already-made decision with &lt;code dir=&quot;auto&quot;&gt;--branch-strategy already-confirmed&lt;/code&gt;. When the recommended feature-branch path is chosen, pass &lt;code dir=&quot;auto&quot;&gt;--start-branch&lt;/code&gt; so the CLI switches before scaffold writes.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#pr-bound-mission&quot;&gt;pr-bound mission&lt;/a&gt;, &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;, &lt;a href=&quot;#feature-branch&quot;&gt;feature branch&lt;/a&gt;, &lt;a href=&quot;#start-branch&quot;&gt;start branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;current-branch&quot;&gt;current branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The git branch checked out in the repository root checkout at the moment a workflow command is invoked. Read ephemerally from the working tree; never persisted in any mission artifact. Exposed as &lt;code dir=&quot;auto&quot;&gt;current_branch&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CURRENT_BRANCH&lt;/code&gt; in branch-context JSON output. Since WP07 (FR-012), spec-kitty does &lt;strong&gt;not&lt;/strong&gt; use &lt;code dir=&quot;auto&quot;&gt;current_branch&lt;/code&gt; to derive the mission target — it reads &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; instead, so the branch contract is stable regardless of which branch the operator is on.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#base-branch&quot;&gt;base branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;topic-branch&quot;&gt;topic branch&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A short-lived branch carrying one change to a pull request.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the repository’s default integration branch — use &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;. The concept is the ref a mission’s code must ultimately land on — use &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;. Avoid the aliases “feature branch” and “PR branch”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#feature-branch&quot;&gt;feature branch&lt;/a&gt;, &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#pr-bound-mission&quot;&gt;pr-bound mission&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;feature-branch&quot;&gt;feature branch&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Alias of topic branch: a short-lived branch carrying one change to a pull request. Prefer “topic branch” in canonical and operator-facing language.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;deprecated&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Prefer the canonical &lt;a href=&quot;#topic-branch&quot;&gt;topic branch&lt;/a&gt; in new code, prose and operator-facing text. The machine value &lt;code dir=&quot;auto&quot;&gt;feature-branch&lt;/code&gt; (for example the &lt;code dir=&quot;auto&quot;&gt;recommended_strategy&lt;/code&gt; branch-strategy value) is unchanged and is not this alias.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#topic-branch&quot;&gt;topic branch&lt;/a&gt;, &lt;a href=&quot;#pr-bound-mission&quot;&gt;pr-bound mission&lt;/a&gt;, &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;, &lt;a href=&quot;#start-branch&quot;&gt;start branch&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;gate-binding&quot;&gt;gate binding&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A versioned doctrine declaration attaching a named gate handler to a status-transition edge (&lt;code dir=&quot;auto&quot;&gt;{on_transition, handler, handler_kind, schema_version, fail_open, provenance}&lt;/code&gt;), authored on the review &lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt;. A binding is a field/relationship, not a standalone artifact. Do NOT confuse with the five pre-existing &lt;code dir=&quot;auto&quot;&gt;*gate*&lt;/code&gt; senses (branch strategy gate / diff compliance gate / dependency gate / merge dependency gate / sonar quality gate) — those are unrelated one-off guards, not doctrine-resolved lane-edge checks.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#gate-handler&quot;&gt;gate handler&lt;/a&gt;, &lt;a href=&quot;#transition-gate&quot;&gt;transition gate&lt;/a&gt;, &lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;gate-handler&quot;&gt;gate handler&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A named, dispatchable check registered in &lt;code dir=&quot;auto&quot;&gt;GATE_REGISTRY&lt;/code&gt;; the Spec-Kitty pre-review engine is the first handler, keyed to the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; edge. Registry membership is the callable source; activation decides whether it runs. Do NOT confuse with the five pre-existing &lt;code dir=&quot;auto&quot;&gt;*gate*&lt;/code&gt; senses (branch strategy gate / diff compliance gate / dependency gate / merge dependency gate / sonar quality gate) — those are unrelated one-off guards, not doctrine-resolved dispatch callables.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#gate-binding&quot;&gt;gate binding&lt;/a&gt;, &lt;a href=&quot;#transition-gate&quot;&gt;transition gate&lt;/a&gt;, &lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;merge-target-branch&quot;&gt;Merge target branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The branch where completed work-package code must ultimately land. Stored in every WP prompt’s frontmatter (alongside &lt;code dir=&quot;auto&quot;&gt;planning_base_branch&lt;/code&gt;) to give implementing agents an explicit landing destination. In &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;: legacy alias for &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, read as a fallback by &lt;code dir=&quot;auto&quot;&gt;resolve_planning_branch_from_meta()&lt;/code&gt; for pre-WP03 missions. In 3.x and 4.x all three — &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;planning_base_branch&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt; — carry the same value; the separation makes intent explicit in agent-facing prompts and prevents the “prep branch leak” (pre-WP07 pattern). Here “merge” means landing the work on its target (the &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration&lt;/a&gt; sense), not lane consolidation. JSON key: &lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#planning-base-branch&quot;&gt;Planning base branch&lt;/a&gt;, &lt;a href=&quot;#work-package&quot;&gt;work package&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;planning-base-branch&quot;&gt;Planning base branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The branch a work package’s planning is rooted on, written into every WP prompt’s frontmatter by &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; sets it to the Mission’s resolved planning branch, which is the &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; read from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (an owned checkout uses its write branch; the &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; override is how a legacy PR-bound Mission names its planning branch, #2938), never the branch the operator happens to be on (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/agent/mission_finalize_bootstrap.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_finalize_branch_contract.py&lt;/code&gt;). The branch-context JSON reports the same value (&lt;code dir=&quot;auto&quot;&gt;mission_branch_context.py&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; does not store it: it records &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt;. Introduced alongside &lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt; to close the “prep branch leak” bug (pre-WP07): when &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; ran from a temporary &lt;code dir=&quot;auto&quot;&gt;prep/...&lt;/code&gt; branch, that branch leaked into WP frontmatter and crashed lane-worktree allocation once the prep branch was deleted. JSON key: &lt;code dir=&quot;auto&quot;&gt;planning_base_branch&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;, &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;, &lt;a href=&quot;#work-package&quot;&gt;work package&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;primary-branch&quot;&gt;primary branch&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The repository’s default integration branch, normally resolved from &lt;code dir=&quot;auto&quot;&gt;origin/HEAD&lt;/code&gt; and commonly named &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;master&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt;. The specify branch-context output exposes this value as &lt;code dir=&quot;auto&quot;&gt;primary_branch&lt;/code&gt; only for branch-strategy recommendation; it is not automatically the mission’s &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; once &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; has been persisted in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. This is &lt;code dir=&quot;auto&quot;&gt;primary&lt;/code&gt; &lt;strong&gt;Sense B&lt;/strong&gt; — the canonical term is “primary branch” (kept per operator decision D1); the wire keys &lt;code dir=&quot;auto&quot;&gt;primary_branch&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;current_is_primary&lt;/code&gt; are unchanged.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the artifact-kind partition — use &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;. The concept is the repository-root working copy versus a lane worktree — use &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;. The concept is the ref planning artifacts commit to — use &lt;a href=&quot;#target-ref--commit-target&quot;&gt;Target Ref / Commit Target&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#current-branch&quot;&gt;current branch&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#feature-branch&quot;&gt;feature branch&lt;/a&gt;, &lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;, &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;, &lt;a href=&quot;#target-ref--commit-target&quot;&gt;Target Ref / Commit Target&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;pr-bound-mission&quot;&gt;pr-bound mission&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A mission expected to land through a pull request rather than direct work on the primary branch. During mission create, &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt; activates the branch strategy gate so the branch choice is explicit before planning artifacts are written.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;, &lt;a href=&quot;#feature-branch&quot;&gt;feature branch&lt;/a&gt;, &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;start-branch&quot;&gt;start branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The branch passed to mission create with &lt;code dir=&quot;auto&quot;&gt;--start-branch&lt;/code&gt;. The CLI creates or switches to this branch before writing mission scaffolding, and it must match &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; when both options are supplied so mission metadata and the checked-out branch describe the same planning branch.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#feature-branch&quot;&gt;feature branch&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;target-branch&quot;&gt;target branch&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The git branch on which a mission’s code, planning artifacts, and status events must ultimately land. Persisted in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; under the key &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; at &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; time and never overwritten. Read by &lt;code dir=&quot;auto&quot;&gt;resolve_planning_branch_from_meta()&lt;/code&gt; as the canonical key; &lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt; is its legacy alias in older &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; fixtures. Since WP07 (FR-012), all downstream commands — &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; — derive the branch contract from this stored value, not from &lt;code dir=&quot;auto&quot;&gt;current_branch&lt;/code&gt; at invocation time. In branch-context JSON output, &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;base_branch&lt;/code&gt; carry the same value at the mission level.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#base-branch&quot;&gt;base branch&lt;/a&gt;, &lt;a href=&quot;#planning-base-branch&quot;&gt;Planning base branch&lt;/a&gt;, &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;, &lt;a href=&quot;#current-branch&quot;&gt;current branch&lt;/a&gt;, &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;transition-gate&quot;&gt;transition gate&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A check that must pass before a work-package status-transition edge (e.g. &lt;code dir=&quot;auto&quot;&gt;in_progress-&gt;for_review&lt;/code&gt;) is allowed. Resolved from the repo’s active doctrine and dispatched through the inverted move-task hook (&lt;code dir=&quot;auto&quot;&gt;_mt_run_transition_gates&lt;/code&gt;); the flagship handler is the scoped pre-review regression check. Do NOT confuse with the five pre-existing &lt;code dir=&quot;auto&quot;&gt;*gate*&lt;/code&gt; senses (branch strategy gate / diff compliance gate / dependency gate / merge dependency gate / sonar quality gate) — those are unrelated one-off guards, not doctrine-resolved lane-edge checks.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#gate-handler&quot;&gt;gate handler&lt;/a&gt;, &lt;a href=&quot;#gate-binding&quot;&gt;gate binding&lt;/a&gt;, &lt;a href=&quot;#branch-strategy-gate&quot;&gt;branch strategy gate&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;tracker-connector&quot;&gt;Tracker Connector&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Outbound integration boundary that projects host lifecycle state to external tracker systems without transferring lifecycle authority.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#orchestrator-api&quot;&gt;Orchestrator API&lt;/a&gt;, &lt;a href=&quot;/context/system-events/#wpstatuschanged&quot;&gt;WPStatusChanged&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;tracker-connector-boundary-alias&quot;&gt;Tracker Connector Boundary (Alias)&lt;/h3&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Architecture-facing alias for &lt;a href=&quot;#tracker-connector&quot;&gt;Tracker Connector&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Canonical entry&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#tracker-connector&quot;&gt;Tracker Connector&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;primary-partition&quot;&gt;PRIMARY partition&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The artifact-kind partition that holds stable planning artifacts — spec, plan, work-package outlines, and &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; — as distinct from the &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt; that holds the lifecycle artifacts (status events, notes, trace, issue-matrix, acceptance-matrix, review cycles, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;). A partition is an artifact-kind &lt;em&gt;placement routing&lt;/em&gt; concept: it decides which &lt;a href=&quot;#topology-surface&quot;&gt;topology surface&lt;/a&gt; an artifact kind is written to. It is &lt;strong&gt;not&lt;/strong&gt; a git branch. Missions with no coordination topology (&lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;LANES&lt;/code&gt;) route every artifact kind to PRIMARY. This is &lt;code dir=&quot;auto&quot;&gt;primary&lt;/code&gt; &lt;strong&gt;Sense A&lt;/strong&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the repository’s default integration branch — use &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;. The concept is the repository-root working copy versus a lane worktree — use &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;. The concept is the ref that planning artifacts commit to — use &lt;a href=&quot;#target-ref--commit-target&quot;&gt;Target Ref / Commit Target&lt;/a&gt;. The concept is the physical tree the routed artifact lands in — use &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;. Never write bare “primary” for the partition; always say “PRIMARY partition”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;, &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt;, &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;, &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;, &lt;a href=&quot;#target-ref--commit-target&quot;&gt;Target Ref / Commit Target&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;target-ref--commit-target&quot;&gt;Target Ref / Commit Target&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The git ref that a mission’s planning artifacts and status events are committed against — the “commit target” the resolver writes to. In current code this resolves to the mission’s &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;. It is distinct from the artifact-kind partition (which decides &lt;em&gt;which surface&lt;/em&gt; an artifact is written to) and from the repository’s default integration branch. This is &lt;code dir=&quot;auto&quot;&gt;primary&lt;/code&gt; &lt;strong&gt;Sense D&lt;/strong&gt;; the retired alias phrases “primary target” and “primary ref” describe this sense.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the artifact-kind partition — use &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;. The concept is the repository’s default integration branch — use &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;. The concept is the branch the mission’s code must ultimately land on — use &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;. Avoid the bare aliases “primary target” and “primary ref”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;, &lt;a href=&quot;#base-branch&quot;&gt;base branch&lt;/a&gt;, &lt;a href=&quot;#current-branch&quot;&gt;current branch&lt;/a&gt;, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;lane-consolidation&quot;&gt;Lane Consolidation&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The lane step of &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (the command was renamed from the former &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; command by #3080): LOCAL consolidation of completed lane branches into the mission branch, with &lt;strong&gt;no&lt;/strong&gt; push to any remote. Realized by the internal helper &lt;code dir=&quot;auto&quot;&gt;consolidate_lane_into_mission&lt;/code&gt;. This is &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; &lt;strong&gt;Sense 1&lt;/strong&gt; — the first of three distinct “merge” operations. The step stops at the local mission branch. The same command then performs &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration&lt;/a&gt; locally (&lt;code dir=&quot;auto&quot;&gt;integrate_mission_into_target&lt;/code&gt;), and publishes only when the operator passes &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; (see &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Canonical term (2026-07-30, renamed 2026-09 by #3080)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;consolidation&lt;/code&gt; is the &lt;strong&gt;canonical word&lt;/strong&gt; for this sense (ADR &lt;a href=&quot;/adr/3.x/2026-07-30-1-consolidated-write-surface-and-consolidate-terminology/&quot;&gt;2026-07-30-1&lt;/a&gt;). The bare word “merge” for lane consolidation is now a &lt;strong&gt;legacy alias&lt;/strong&gt;: pre-#3080 occurrences are grandfathered, but NEW code, new symbols, and touched prose must say “consolidate” / “consolidation” for this sense (boyscouting, C-012). The full #3080 rename has landed: the CLI command is &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; now exits with a migration-error stub), the state class is &lt;code dir=&quot;auto&quot;&gt;ConsolidationState&lt;/code&gt;, and the package is &lt;code dir=&quot;auto&quot;&gt;specify_cli.consolidation&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; (the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; wire-key) and &lt;code dir=&quot;auto&quot;&gt;consolidate_lane_into_mission&lt;/code&gt;’s own name are unaffected — they were frozen KEEPs, not part of the rename.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt; that integrates the mission branch into its target branch — use &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/a&gt;. The concept is publishing the landed work to &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt; — use &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;. Never write bare “merge”; name the operation. In NEW code or prose, prefer “consolidate” / “consolidation” over “merge” for this sense — see &lt;strong&gt;Canonical term&lt;/strong&gt; above; a CI drift-ratchet guard (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_legacy_terminology.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_LANE_CONSOLIDATION_FORBIDDEN_PHRASES&lt;/code&gt;) blocks the specific legacy lane-plus-merge-verb phrasings from growing beyond their grandfathered baseline (FR-016).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/a&gt;, &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;, &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;, &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;, &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt; operation that integrates the mission branch into its target branch. Realized by the internal helper &lt;code dir=&quot;auto&quot;&gt;integrate_mission_into_target&lt;/code&gt;. This is &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; &lt;strong&gt;Sense 2&lt;/strong&gt; — branch-to-branch integration, distinct from local lane consolidation and from publishing to origin. The &lt;code dir=&quot;auto&quot;&gt;MergeStrategy&lt;/code&gt; literals (&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;squash&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;rebase&lt;/code&gt;) select &lt;em&gt;how&lt;/em&gt; this integration is performed and are unchanged serialized contracts.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;’s local lane consolidation — use &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;. The concept is publishing the landed work to &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt; — use &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;, &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;publish-to-originmain&quot;&gt;Publish to origin/main&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The operator-only act of publishing the landed mission work to &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt;. In this repository it always goes through a pull request — never a direct push. Represented in the consolidation flow by &lt;code dir=&quot;auto&quot;&gt;push_requested&lt;/code&gt;. By default &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; does &lt;strong&gt;not&lt;/strong&gt; perform this step: it stops at the local landing. Its opt-in &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; flag runs &lt;code dir=&quot;auto&quot;&gt;git push origin &amp;#x3C;target branch&gt;&lt;/code&gt; after the local integration (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/consolidation/phase_finalize.py&lt;/code&gt;); this repository’s workflow forbids using it for &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. This is &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; &lt;strong&gt;Sense 3&lt;/strong&gt; — the publish operation, sometimes called “operator merge”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;’s local lane consolidation — use &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;. The concept is the &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt; branch-integration step — use &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/a&gt;, &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;branch-relative-provenance&quot;&gt;Branch-relative provenance&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The meaning of a commit SHA a Mission dossier records (&lt;code dir=&quot;auto&quot;&gt;merged_commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept_commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accepted_from_commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lane_head&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;base_commit&lt;/code&gt;, and any SHA cited in hand-authored evidence such as &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;evidence_ref&lt;/code&gt;): it names a commit on the branch the Mission was built on, as that branch stood when the value was written. After the pull request lands by rebase it may resolve only through the pull request’s head ref, or not at all, and it is never repointed. The only exception is a field classified &lt;code dir=&quot;auto&quot;&gt;LANDED&lt;/code&gt; (today &lt;code dir=&quot;auto&quot;&gt;pr_merge_commit&lt;/code&gt;), whose writer verifies the commit is on the target branch. The classification lives in &lt;code dir=&quot;auto&quot;&gt;DOSSIER_SHA_FIELDS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_dossier_sha_provenance.py&lt;/code&gt;); ADR &lt;a href=&quot;/adr/4.x/2026-11-07-1-dossier-commit-shas-are-branch-relative-provenance/&quot;&gt;2026-11-07-1&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the commit that landed a Mission on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;: that is &lt;code dir=&quot;auto&quot;&gt;pr_merge_commit&lt;/code&gt; where it was recorded, or the pull request’s landed commit. Do not call an unreachable branch-relative SHA “stale” or “corrupt”, and never ask for an archive-freeze exception to correct one.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;, &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#evidence-gate&quot;&gt;Evidence gate&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;work-package-window&quot;&gt;Work-package window&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The span of lane history one approved work package is accountable for: from its &lt;a href=&quot;#window-open-sha&quot;&gt;window-open SHA&lt;/a&gt; (exclusive) to its newest approval stamp (inclusive). A work package with a &lt;a href=&quot;#window-gap&quot;&gt;window gap&lt;/a&gt; gets a degraded window from the claim base to its approval stamp. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the canceled-content implementation and review windows of a mixed lane (&lt;code dir=&quot;auto&quot;&gt;WorkWindow&lt;/code&gt;): that is a &lt;a href=&quot;#named-window-variant&quot;&gt;named window variant&lt;/a&gt;, never “work-package window”. Do not write “work window” or “WP range” for this sense.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#window-open-sha&quot;&gt;Window-open SHA&lt;/a&gt;, &lt;a href=&quot;#window-opener&quot;&gt;Window opener&lt;/a&gt;, &lt;a href=&quot;#window-gap&quot;&gt;Window gap&lt;/a&gt;, &lt;a href=&quot;#exemption-anchor&quot;&gt;Exemption anchor&lt;/a&gt;, &lt;a href=&quot;#named-window-variant&quot;&gt;Named window variant&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;window-open-sha&quot;&gt;Window-open SHA&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The lane head recorded under &lt;code dir=&quot;auto&quot;&gt;policy_metadata.wp_window.open_sha&lt;/code&gt; on the status event of a non-migration move into &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;. The window opens at the one recorded on the &lt;a href=&quot;#window-opener&quot;&gt;window opener&lt;/a&gt;. It is &lt;a href=&quot;#branch-relative-provenance&quot;&gt;branch-relative provenance&lt;/a&gt;, valid for one consolidation attempt. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the approval stamp (&lt;code dir=&quot;auto&quot;&gt;lane_head&lt;/code&gt; on the newest approval transition): that is the window’s closing edge. Do not write “open stamp”, “base SHA” or “fork point” for this sense.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;, &lt;a href=&quot;#window-opener&quot;&gt;Window opener&lt;/a&gt;, &lt;a href=&quot;#window-gap&quot;&gt;Window gap&lt;/a&gt;, &lt;a href=&quot;#branch-relative-provenance&quot;&gt;Branch-relative provenance&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;window-opener&quot;&gt;Window opener&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The opening event a work package’s window binds to: the first non-migration move into &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; after the work package last returned to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; from a non-review status lane (a review rejection does not reset it), skipping leading &lt;code dir=&quot;auto&quot;&gt;lane_branch_missing&lt;/code&gt; openers, with the openers of that cycle ordered by lane topology and by event-log order when their SHAs are unrelated (FR-021). ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the closed-world lane anchor, where &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; also counts as an opener (&lt;code dir=&quot;auto&quot;&gt;first_governed_open_stamp&lt;/code&gt;): that is a &lt;a href=&quot;#named-window-variant&quot;&gt;named window variant&lt;/a&gt;. Do not write “first claim”; it is no longer exact.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#window-open-sha&quot;&gt;Window-open SHA&lt;/a&gt;, &lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;, &lt;a href=&quot;#named-window-variant&quot;&gt;Named window variant&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;window-gap&quot;&gt;Window gap&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The explicit, typed absence of a recorded window for a work package: “not recorded” (no value on the opener), “capture failed” (with the recorded cause), “lane branch missing” (every opener of the cycle recorded that the lane branch did not exist yet) or “not on lane” (the SHA is not an ancestor of the lane tip, or does not resolve in this clone). A gap never refuses by itself: the work package is judged by the approval-stamp bound and listed in the &lt;a href=&quot;#gap-report&quot;&gt;gap report&lt;/a&gt;. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is a missing approval stamp: that is &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt;, a different refusal. Do not write “missing stamp” for a window gap.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#gap-report&quot;&gt;Gap report&lt;/a&gt;, &lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;, &lt;a href=&quot;#window-open-sha&quot;&gt;Window-open SHA&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;gap-report&quot;&gt;Gap report&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The part of the &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; output (fresh run, resume and forecast; &lt;code dir=&quot;auto&quot;&gt;window_gaps&lt;/code&gt; in the JSON) that lists every work package judged by the fallback approval-stamp bound, with its &lt;a href=&quot;#window-gap&quot;&gt;window gap&lt;/a&gt; reason. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is a refusal or a warning about the work itself: a gap report lists the weaker check a work package got, and refuses nothing. Do not write “warning list”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#window-gap&quot;&gt;Window gap&lt;/a&gt;, &lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;exemption-anchor&quot;&gt;Exemption anchor&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A commit whose reach exempts lane commits from the window refusal: the closed-world anchors (dependency-lane tips of lanes that are not fully canceled, the target’s pre-consolidation tip) and the approval stamps of &lt;strong&gt;other&lt;/strong&gt; bounded lanes. A lane’s own approval stamps are not exemption anchors on the window path. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is an approval stamp of the lane under check, which does not exempt on the window path. Do not write “stamp anchor” without naming the lane.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;, &lt;a href=&quot;#claim-inputs&quot;&gt;Claim inputs&lt;/a&gt;, &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;claim-inputs&quot;&gt;Claim inputs&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;ClaimInputs&lt;/code&gt;: the one frozen value the consolidation gate’s claim is built from, with one constructor and three sources (&lt;code dir=&quot;auto&quot;&gt;LIVE&lt;/code&gt; for the forecast, &lt;code dir=&quot;auto&quot;&gt;LIVE_THEN_SAVED&lt;/code&gt; for a fresh run, &lt;code dir=&quot;auto&quot;&gt;SAVED&lt;/code&gt; for a resume). It holds the target base, the coordination base, the frozen lane tips, the frozen dependency anchors, the dependency pins, the excluded canceled work packages, the strategy and the status directory read. ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the target branch’s tip before the run mutated anything (the claim base), which is one field of the claim inputs. Do not write “claim args” or “gate params”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#exemption-anchor&quot;&gt;Exemption anchor&lt;/a&gt;, &lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;named-window-variant&quot;&gt;Named window variant&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A deliberate difference between window definitions that ADR &lt;a href=&quot;/adr/4.x/2026-11-08-2-work-package-windows-are-recorded-at-the-opening-transition/&quot;&gt;2026-11-08-2&lt;/a&gt; records by name instead of unifying: “lane anchor” (&lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; opens), “canceled-content windows” (&lt;code dir=&quot;auto&quot;&gt;WorkWindow&lt;/code&gt;), “owned-file evidence”, and the &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; authorship window.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is an accident or an unrecorded difference between two checks: a named variant is recorded and has a reason. Do not write “exception” or “special case”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#work-package-window&quot;&gt;Work-package window&lt;/a&gt;, &lt;a href=&quot;#window-opener&quot;&gt;Window opener&lt;/a&gt;, &lt;a href=&quot;#exemption-anchor&quot;&gt;Exemption anchor&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;evidence-gate&quot;&gt;Evidence gate&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A command that turns a Mission’s local status or code into a durable verdict: review workspace preparation (&lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;accept-mission&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate-mission&lt;/code&gt; forms. Each one runs the &lt;a href=&quot;#origin-freshness-check&quot;&gt;origin freshness check&lt;/a&gt; before it trusts a local branch. Enforced by &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_evidence_gates_check_origin.py&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the end of a Mission’s life — “terminus” already names that, so never “terminus gate”. The concept is the reconciliation gate that verifies a consolidation landed approved content (&lt;code dir=&quot;auto&quot;&gt;MergeOutcomeVerifier&lt;/code&gt;) — that is one step &lt;em&gt;inside&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, not the gate itself. The concept is the comparison against the remote — use &lt;a href=&quot;#origin-freshness-check&quot;&gt;origin freshness check&lt;/a&gt;; never “origin reconciliation” or “sync”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#origin-freshness-check&quot;&gt;origin freshness check&lt;/a&gt;, &lt;a href=&quot;#status-evidence-branch&quot;&gt;status evidence branch&lt;/a&gt;, &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;origin-freshness-check&quot;&gt;Origin freshness check&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Refreshing the remote’s view of a branch in the current invocation and classifying the local branch against it. The verdict is one of &lt;code dir=&quot;auto&quot;&gt;up_to_date&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;behind&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ahead&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;diverged&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;local_missing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote_missing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unreachable&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;no_remote&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote_ambiguous&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;compare_failed&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;not_checked&lt;/code&gt; is recorded when the check is &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; and nothing was contacted (&lt;code dir=&quot;auto&quot;&gt;FreshnessState&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/git/origin_freshness.py&lt;/code&gt;). A landing-path gate (&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, the two &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; gates) refuses on &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_REMOTE_AMBIGUOUS&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;ORIGIN_COMPARE_FAILED&lt;/code&gt; unless the operator passes &lt;code dir=&quot;auto&quot;&gt;--origin-check warn&lt;/code&gt; (default &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; contacts nothing and accepts stale evidence. &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_DIVERGED&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; only, which has no flag: only &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=warn&lt;/code&gt; lifts it. Owned by &lt;code dir=&quot;auto&quot;&gt;specify_cli.git.origin_freshness&lt;/code&gt;; every remote read (listing, fetch, clone, &lt;code dir=&quot;auto&quot;&gt;remote show&lt;/code&gt;) belongs to &lt;code dir=&quot;auto&quot;&gt;kernel.git.remote&lt;/code&gt;, while push is excluded (FR-015, #5858). See ADR &lt;a href=&quot;/adr/4.x/2026-10-06-3-evidence-gates-check-origin-freshness/&quot;&gt;2026-10-06-3&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the check that a push will be accepted (&lt;code dir=&quot;auto&quot;&gt;is_safe_to_push&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;) — that is push safety, which this check does not replace. The concept is the consolidation reconciliation gate — use &lt;a href=&quot;#evidence-gate&quot;&gt;Evidence gate&lt;/a&gt; and name the gate; do not say “origin reconciliation”. The retired transport vocabulary (“sync”, “in sync”) is never used for this: say &lt;code dir=&quot;auto&quot;&gt;up_to_date&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#evidence-gate&quot;&gt;Evidence gate&lt;/a&gt;, &lt;a href=&quot;#status-evidence-branch&quot;&gt;status evidence branch&lt;/a&gt;, &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;status-evidence-branch&quot;&gt;Status evidence branch&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The branch whose copy of a Mission’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; an &lt;a href=&quot;#evidence-gate&quot;&gt;evidence gate&lt;/a&gt; reads: the coordination branch for a coordination topology, the write branch for &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;kitty/mission-...&lt;/code&gt; for a protected target, the target itself with &lt;code dir=&quot;auto&quot;&gt;--commit-to-target&lt;/code&gt;), and the target branch for &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;. The origin freshness check judges it only on commits that change this Mission’s status log, under every directory alias of the Mission. A gate never moves it; it refuses and names the pull command.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt; (a placement rule over artifact kinds), or “coord” generally: a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission has no coordination branch but still has a status evidence branch. The concept is a lane’s code branch — use &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#evidence-gate&quot;&gt;Evidence gate&lt;/a&gt;, &lt;a href=&quot;#origin-freshness-check&quot;&gt;origin freshness check&lt;/a&gt;, &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt;, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;coord-partition&quot;&gt;COORD partition&lt;/h3&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The artifact-kind partition that holds a mission’s lifecycle/coordination artifacts — status events, notes, trace, issue-matrix, acceptance-matrix, review cycles, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; — as distinct from the &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt; that holds stable planning artifacts. Like the PRIMARY partition it is an artifact-kind &lt;em&gt;placement routing&lt;/em&gt; concept, &lt;strong&gt;not&lt;/strong&gt; a git branch and &lt;strong&gt;not&lt;/strong&gt; a directory: it decides which surface a kind is written to. Only missions whose stored topology routes through coordination (&lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;LANES_WITH_COORD&lt;/code&gt;) have a materialised COORD surface; &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;LANES&lt;/code&gt; missions route every kind to PRIMARY. Realized in code as the &lt;code dir=&quot;auto&quot;&gt;_PLACEMENT_ARTIFACT_KINDS&lt;/code&gt; frozenset in &lt;code dir=&quot;auto&quot;&gt;mission_runtime/artifacts.py&lt;/code&gt;, whose partition-invariant P-1 (disjoint and jointly exhaustive with &lt;code dir=&quot;auto&quot;&gt;_PRIMARY_ARTIFACT_KINDS&lt;/code&gt;) is asserted at the placement seam.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is the physical tree an artifact resolves to — use &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;. The concept is a coordination &lt;em&gt;branch&lt;/em&gt; or &lt;em&gt;worktree&lt;/em&gt; — say “coord branch” / “coord worktree” explicitly. Never write bare “coord” for the partition; always say “COORD partition”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;, &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;, &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;, &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;target-owned-bookkeeping&quot;&gt;Target-owned bookkeeping&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A tracked file at the project root that Spec Kitty fully generates, marks “do not edit”, and that no work package authors, declared &lt;code dir=&quot;auto&quot;&gt;StateSurface.target_owned&lt;/code&gt; in the state contract (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/state/contract.py&lt;/code&gt;; today only &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;). Its authoritative copy is the one on the &lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;. When two branches of one Mission carry different copies, each integration site resolves the conflict to a fixed side without asking: the copy closer to the merge target branch wins, and between two lane branches the receiving lane branch keeps its own until consolidation. The per-site table is in ADR &lt;a href=&quot;/adr/4.x/2026-10-04-4-upgrade-writes-project-global-state-once/&quot;&gt;2026-10-04-4&lt;/a&gt;. The code identifiers &lt;code dir=&quot;auto&quot;&gt;target_owned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;is_target_owned_path&lt;/code&gt; and the rule id &lt;code dir=&quot;auto&quot;&gt;R-TARGET-OWNED-BOOKKEEPING&lt;/code&gt; carry this sense.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;candidate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Describing why &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, review start, implement resume or a lane sync did not refuse on a conflict in &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;, or which copy of it survived.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The file is operator-editable (&lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;): those are never target-owned, and a conflict on them still refuses. The concept is where a Mission artifact is stored: use &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;; &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; is not a Mission artifact and has no partition. The concept is “the repository root checkout’s copy”: no site computes that. Do not call it “primary-owned”: that earlier name suggested the PRIMARY partition or the &lt;a href=&quot;#primary-branch&quot;&gt;primary branch&lt;/a&gt;, and the merge target branch need not be the primary branch.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#merge-target-branch&quot;&gt;Merge target branch&lt;/a&gt;, &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane consolidation&lt;/a&gt;, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;, &lt;a href=&quot;/context/execution/#integrating-worktree&quot;&gt;integrating worktree&lt;/a&gt;, &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;topology-surface&quot;&gt;Topology Surface&lt;/h3&gt;













































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The physical tree (working copy / checkout location) that a mission artifact resolves to for reading and writing. This is &lt;code dir=&quot;auto&quot;&gt;surface&lt;/code&gt; &lt;strong&gt;Sense 2&lt;/strong&gt; — the mission-topology sense. Modeled by the &lt;code dir=&quot;auto&quot;&gt;TopologySurface&lt;/code&gt; enum in &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py&lt;/code&gt;, carried on &lt;code dir=&quot;auto&quot;&gt;MissionArtifactHome&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;read_surface&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;write_surface&lt;/code&gt;, and returned by &lt;code dir=&quot;auto&quot;&gt;artifact_home_for&lt;/code&gt;. Members with production callers today: &lt;code dir=&quot;auto&quot;&gt;PRIMARY&lt;/code&gt; — the repository-root planning tree; &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; — the mission’s coordination tree. Also declared, together with the surface→filesystem translation seam that makes each resolvable (&lt;code dir=&quot;auto&quot;&gt;translate_surface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/resolution.py&lt;/code&gt;): &lt;code dir=&quot;auto&quot;&gt;LANE&lt;/code&gt; — a per-work-package lane worktree under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED&lt;/code&gt; — the tree after lane branches have been consolidated into the mission branch; &lt;code dir=&quot;auto&quot;&gt;TEMP&lt;/code&gt; — an ephemeral scratch tree with no durable home. These three have no production caller yet, but every member maps to a real location and the seam’s totality test (&lt;code dir=&quot;auto&quot;&gt;assert_surface_totality&lt;/code&gt;) exercises each, so none is a phantom. Renamed from &lt;code dir=&quot;auto&quot;&gt;Surface&lt;/code&gt; (whose members were &lt;code dir=&quot;auto&quot;&gt;PRIMARY&lt;/code&gt; | &lt;code dir=&quot;auto&quot;&gt;PLACEMENT&lt;/code&gt;, with a &lt;code dir=&quot;auto&quot;&gt;str&lt;/code&gt; mixin and an &lt;code dir=&quot;auto&quot;&gt;ArtifactSurface&lt;/code&gt; back-compat alias, both retired) per ADR &lt;a href=&quot;/adr/3.x/2026-07-23-1-surface-vocabulary-two-domains-and-topology-surface-rename/&quot;&gt;2026-07-23-1&lt;/a&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;A topology surface is a &lt;em&gt;location&lt;/em&gt;; a partition is a &lt;em&gt;placement-routing rule over artifact kinds&lt;/em&gt;. The two vocabularies coincide only on the &lt;code dir=&quot;auto&quot;&gt;PRIMARY&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; values — the &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt; routes its kinds to the &lt;code dir=&quot;auto&quot;&gt;PRIMARY&lt;/code&gt; topology surface and the &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt; to the &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; topology surface. &lt;code dir=&quot;auto&quot;&gt;LANE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;TEMP&lt;/code&gt; are locations with no partition of their own. Prose also uses “surface” as an ungoverned generic modifier (“command surface”, “API surface”, “doc surface”) meaning “the outward face of X”; that usage is not governed here, but it must always carry its modifier — bare “surface” always means one of the two governed senses.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note (naming vs conditioning)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Naming a surface &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; does &lt;strong&gt;not&lt;/strong&gt; violate the rule against conditioning behavior on topology. Naming a real surface is correct; &lt;em&gt;branching&lt;/em&gt; on it — &lt;code dir=&quot;auto&quot;&gt;if surface is COORD: ...&lt;/code&gt; in place of a resolved read/write path — is what is forbidden. The prior member name &lt;code dir=&quot;auto&quot;&gt;PLACEMENT&lt;/code&gt; avoided the &lt;em&gt;word&lt;/em&gt; while keeping the &lt;em&gt;concept&lt;/em&gt;; explicitness is preferred.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note (&lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;MERGED&lt;/code&gt;)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The post-consolidation surface is named &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED&lt;/code&gt; because &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; is itself a three-sense overloaded term in this codebase — &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#branch-integration--git-merge&quot;&gt;Branch Integration / Git Merge&lt;/a&gt;, and &lt;a href=&quot;#publish-to-originmain&quot;&gt;Publish to origin/main&lt;/a&gt;. A member named &lt;code dir=&quot;auto&quot;&gt;MERGED&lt;/code&gt; would not say which of the three had happened. &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED&lt;/code&gt; names exactly one: the surface that exists after &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;. This is the same disambiguation discipline already applied to &lt;code dir=&quot;auto&quot;&gt;primary&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;base&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The concept is a tool-visible artifact or configuration entry Spec Kitty installs for a concrete execution tool — use &lt;a href=&quot;/context/execution/#tool-surface&quot;&gt;Tool Surface&lt;/a&gt; (&lt;code dir=&quot;auto&quot;&gt;surface&lt;/code&gt; &lt;strong&gt;Sense 1&lt;/strong&gt;). The concept is the artifact-kind placement-routing rule rather than the location — use &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt; or &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt;. The concept is the repository-root working copy versus a lane worktree as an operator-facing checkout — use &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;. Never write bare “surface” in governed prose; name the sense (“topology surface” / “tool surface”).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;/context/execution/#tool-surface&quot;&gt;Tool Surface&lt;/a&gt;, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;, &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt;, &lt;a href=&quot;#lane&quot;&gt;Lane&lt;/a&gt;, &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;/context/execution/#repository-root-checkout&quot;&gt;repository root checkout&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;routing&quot;&gt;Routing&lt;/h3&gt;













































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;“Routing” has no single meaning in this codebase — it is an umbrella word covering at least six &lt;strong&gt;live governed&lt;/strong&gt; decisions, one &lt;strong&gt;retired&lt;/strong&gt; governed sense retained here as a named referent, plus several &lt;strong&gt;infrastructural&lt;/strong&gt; ones that are explicitly out of scope here. This entry extends, not restates, &lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt; / &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt; / &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt; above, which already frame the &lt;strong&gt;placement&lt;/strong&gt; sense; naming an exclusion is disambiguation, silence is not.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Governed senses&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Placement routing&lt;/strong&gt; — mapping a &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; + mission topology to a &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;. Owning module: &lt;code dir=&quot;auto&quot;&gt;mission_runtime/resolution.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;PlacementSeam&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;placement_seam&lt;/code&gt;). Full explanation: &lt;a href=&quot;/architecture/artifact-placement-seam/&quot;&gt;The Artifact Placement Seam&lt;/a&gt;. &lt;em&gt;Do NOT use when&lt;/em&gt; the question is which git &lt;strong&gt;branch&lt;/strong&gt; a commit lands on — that is branch-target routing, below. — &lt;strong&gt;Branch-target routing&lt;/strong&gt; — which git branch (lane / coordination / target) a category of change commits to. Owning doc: &lt;a href=&quot;/architecture/branch-target-routing/&quot;&gt;Branch-Target Routing&lt;/a&gt;. &lt;em&gt;Do NOT use when&lt;/em&gt; the question is which physical &lt;strong&gt;tree&lt;/strong&gt; an artifact kind resolves to — that is placement routing, above. — &lt;strong&gt;Commit routing&lt;/strong&gt; — the git-commit mechanics inside &lt;code dir=&quot;auto&quot;&gt;coordination/commit_router.py::commit_for_mission&lt;/code&gt;: given an already-resolved placement, whether the coordination worktree must be materialised before staging and committing. &lt;em&gt;Do NOT use when&lt;/em&gt; the question is which surface a kind resolves to (placement routing) or which branch a category lands on (branch-target routing) — commit routing consumes both answers, it does not compute either. — &lt;strong&gt;Dispatch/profile routing&lt;/strong&gt; — matching an ad-hoc natural-language request to an agent profile + action. Owning module: &lt;code dir=&quot;auto&quot;&gt;specify_cli/invocation/router.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ActionRouter&lt;/code&gt;). &lt;em&gt;Do NOT use when&lt;/em&gt; the subject is mission artifact placement or git branches. — &lt;strong&gt;Model/task routing&lt;/strong&gt; — assigning a model or delegation target to a unit of work; the highest-collision sense in agent-authored prose because “route this to the right agent” reads as dispatch/profile routing but is a distinct decision. Owning surface: &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/model_task_routing/&lt;/code&gt;. &lt;em&gt;Do NOT use when&lt;/em&gt; the subject is profile selection for an ad-hoc request (dispatch/profile routing) or mission artifact placement. — &lt;strong&gt;Scope routing&lt;/strong&gt; — resolving which configuration/auth/sync scope (repo-level vs global) an operation applies at. Its former owning module, the hosted auth transport, was removed with the hosted surfaces in #6164; no current module is named as its owner. &lt;em&gt;Do NOT use when&lt;/em&gt; the subject is artifact placement, branches, or model/agent assignment.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Retired governed sense&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Sync fan-out routing&lt;/strong&gt; — per-checkout opt-in/opt-out for SaaS sync delivery. It was owned by the sync transport’s routing module; the whole sync package was deleted with the sync transport (issue #115) and this is no longer a live governed decision. Retained here as a named referent, not as a live sense, so historical prose (“sync routing decides only &lt;em&gt;whether&lt;/em&gt; a checkout participates in sync fan-out, never where anything is stored”) still resolves.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Explicitly out of scope (infrastructural senses, named not silenced)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Event routing&lt;/strong&gt; — dispatching an emitted event to its handler(s) inside the event/runtime-bridge machinery. &lt;strong&gt;HTTP request routing&lt;/strong&gt; — mapping an inbound request path to a handler in a web-serving layer. &lt;strong&gt;Significance routing bands&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;make_routing_bands&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;runtime/next/_internal_runtime/significance.py&lt;/code&gt;, which buckets a decision’s scored significance into a band; a scoring concept, not a placement or dispatch decision. None of these three is governed by this entry; if a caller needs one disambiguated further, name it explicitly in prose rather than writing bare “routing”.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Never write bare “routing” in governed prose without naming which of the senses above (or an explicitly out-of-scope one) is meant.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#primary-partition&quot;&gt;PRIMARY partition&lt;/a&gt;, &lt;a href=&quot;#coord-partition&quot;&gt;COORD partition&lt;/a&gt;, &lt;a href=&quot;#topology-surface&quot;&gt;Topology Surface&lt;/a&gt;, &lt;a href=&quot;#target-branch&quot;&gt;target branch&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;hr&gt;
&lt;h3 id=&quot;the-drain&quot;&gt;The drain&lt;/h3&gt;













&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;“The drain” is retired historical terminology on this line. It previously named three distinct flows — the &lt;strong&gt;dispatch-selection drain&lt;/strong&gt; (in the delivery subsystem), the &lt;strong&gt;body drain&lt;/strong&gt; (the sync transport’s background body-queue sender), and the &lt;strong&gt;queue-backed event drain&lt;/strong&gt; (the sync transport’s batch sender, removed upstream by #3167) — all of which were deleted with the &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;delivery&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;event_journal&lt;/code&gt; subsystems (spec-kitty#5 / PR #114). The entry is retained as a named referent so historical prose, commit messages and issue threads that say “the drain” stay resolvable. Bare use is not resolvable from context; in new prose, name the concrete current operation instead.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;| &lt;strong&gt;Context&lt;/strong&gt; | Orchestration |
| &lt;strong&gt;Status&lt;/strong&gt; | canonical |
| &lt;strong&gt;Applicable to&lt;/strong&gt; | &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt; |
| &lt;strong&gt;Governed senses&lt;/strong&gt; | All three senses are historical on this line: &lt;strong&gt;the dispatch-selection drain&lt;/strong&gt; (the delivery subsystem’s selection step, feeding its dispatcher), &lt;strong&gt;the body drain&lt;/strong&gt; (the sync transport’s background sender, backed by its body queue), and &lt;strong&gt;the queue-backed event drain&lt;/strong&gt; (the sync transport’s batch sender, removed upstream by #3167 before the subsystem deletion). None has a successor mechanism in open-core. A reader resolving a historical “the drain” mention consults this entry, not current code. |&lt;/p&gt;
&lt;p&gt;| &lt;strong&gt;Note (why this entry exists)&lt;/strong&gt; | The overload was load-bearing, not cosmetic. #3167’s own first-draft specification asserted that a &lt;strong&gt;true&lt;/strong&gt; docstring was false — it read the sync runtime module’s claim that “the drain” walks the per-project consent chain as referring to the batch sender (which walked a different chain) instead of to the dispatch-selection step (which did walk it). The proposed correction would have rewritten correct documentation and, in the natural rewrite, claimed consent coverage for a module that had no production caller — manufacturing exactly the false-pointer class that mission existed to remove. A false pointer is how an auditor concludes a gate exists. |
| &lt;strong&gt;Do NOT use when&lt;/strong&gt; | Never write bare “the drain” in governed prose or in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; docstrings. Write “the dispatch-selection drain”, “the body drain”, or “the retired queue-backed drain” — or link this entry. Also do not use “the drain” for the &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt; or status-event flush paths; those are not drains and have their own terms. |
| &lt;strong&gt;Related terms&lt;/strong&gt; | &lt;a href=&quot;#routing&quot;&gt;Routing&lt;/a&gt; (the retired sync fan-out sense decided &lt;em&gt;whether&lt;/em&gt; a checkout participates, never what “the drain” means), &lt;a href=&quot;#lane-consolidation&quot;&gt;Lane Consolidation&lt;/a&gt;, &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt; |&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id=&quot;residue&quot;&gt;Residue&lt;/h3&gt;









































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;“Residue” names a &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; child directory that is not a Mission — but it has no single rule. Three live code senses each answer “is this folder a Mission?” differently for their own surface, and each is justified in its owning docstring. This entry extends, not restates, &lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;; naming the senses is disambiguation, silence is not (the same footgun class as &lt;a href=&quot;#routing&quot;&gt;Routing&lt;/a&gt; above, issue #6759).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Context&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Orchestration&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Status&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;canonical&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Applicable to&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;4.x&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Governed senses&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Write-seam residue&lt;/strong&gt; — whether an upgrade or migration write seam must leave the folder untouched. Owning symbol: &lt;code dir=&quot;auto&quot;&gt;is_kitty_specs_residue&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/context/mission_resolver.py&lt;/code&gt;, #6627 / #6668). A &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on disk keeps a folder out of write-seam residue, so the upgrade sweep can still repair it. &lt;em&gt;Do NOT use when&lt;/em&gt; the surface reads or audits the folder: a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;-only folder is never selectable, and the audit engine reports it too until its &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; is tracked — those are the read-side and audit-engine senses below. — &lt;strong&gt;Audit-engine residue&lt;/strong&gt; — a directory that fails &lt;code dir=&quot;auto&quot;&gt;is_mission_dir&lt;/code&gt;, reported as one INFO &lt;code dir=&quot;auto&quot;&gt;RESIDUE_DIRECTORY&lt;/code&gt; finding and not classified. Owning symbol: &lt;code dir=&quot;auto&quot;&gt;RESIDUE_DIRECTORY&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/audit/models.py&lt;/code&gt;, emitted by &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/audit/engine.py&lt;/code&gt;, #5812). The engine keeps this looser rule deliberately (issue #5875): a tracked &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, or any marker on a non-git root, still makes a Mission there, so its findings must not disappear. &lt;em&gt;Do NOT use when&lt;/em&gt; the question is whether Mission selection lists the folder (read-side residue is stricter) or whether a write seam may repair it (write-seam residue is looser). — &lt;strong&gt;Read-side / &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; residue&lt;/strong&gt; — a folder Mission selection never lists: no &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; on disk; a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that carries no &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; and that git does not back with a tracked marker (in a git repository); or a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that is unreadable or not a JSON object when git tracks no marker (a Mission otherwise, which &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; then classifies as &lt;code dir=&quot;auto&quot;&gt;orphan&lt;/code&gt; — as read-side residue it carries the &lt;code dir=&quot;auto&quot;&gt;corrupt_meta&lt;/code&gt; reason with the read error). Owning symbol: &lt;code dir=&quot;auto&quot;&gt;not is_selectable_mission_dir&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/context/mission_resolver.py&lt;/code&gt;, consumed by &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/identity_audit.py&lt;/code&gt;, #5875 operator ruling 2026-10-27). &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; reports each with its reason and remedy. &lt;em&gt;Do NOT use when&lt;/em&gt; the question is whether a write seam may touch the folder (a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;-only folder is read-side residue but never write-seam residue) or what the audit engine reports (audit-engine residue).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Note (why three rules)&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;The strictness order is deliberate, not drift: the write seam must not destroy repairable work (so a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on disk shields the folder), selection must not offer non-Missions to the operator (so it demands a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and identity or a tracked marker), and the audit engine reports rather than classifies (so it keeps the &lt;code dir=&quot;auto&quot;&gt;is_mission_dir&lt;/code&gt; rule its findings were written against). A folder holding only a &lt;strong&gt;tracked&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; is read-side residue and an audit-engine Mission; untracked, the audit engine reports it as &lt;code dir=&quot;auto&quot;&gt;RESIDUE_DIRECTORY&lt;/code&gt; too — but tracked or not it is never write-seam residue, because a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on disk is all the write seam asks. The code is the source of truth for each rule; this entry only names and links them.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Do NOT use when&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;Never write bare “residue” in governed prose or in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; docstrings when the sense matters; name it (“write-seam residue” / “audit-engine residue” / “read-side residue”) or link this entry. Also do not use “residue” for toolchain leftovers outside &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; (for example the status files a rolled-back consolidation may leave in a coordination worktree — “toolchain residue” is a different, ungoverned concept), or for the retired-vocabulary sense of leftover identifiers (&lt;a href=&quot;/context/team-kitty/&quot;&gt;Team Kitty&lt;/a&gt;).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;strong&gt;Related terms&lt;/strong&gt;&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;#mission&quot;&gt;Mission&lt;/a&gt;, &lt;a href=&quot;#routing&quot;&gt;Routing&lt;/a&gt;, &lt;a href=&quot;#the-drain&quot;&gt;The drain&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;</content>
</entry>
