<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/4.x/2026-11-06-2-one-status-read-contract/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-11-06-2-one-status-read-contract/</id>
  <title>ADR: One status read contract</title>
  <updated>2026-11-11T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/4.x/2026-11-06-2-one-status-read-contract/"/>
  <summary>Every status read resolves through one door to one declared source per topology and coordination state; never a lane checkout, a missing path or a silent fallback.</summary>
  <content type="html">&lt;h2 id=&quot;one-status-read-contract&quot;&gt;One status read contract&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Proposed (2026-11-06). The operator accepts it by merging the pull request that carries it. Amended 2026-11-08 (below).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-11-06&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7277&quot;&gt;#7277&lt;/a&gt; (S1 of epic &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7276&quot;&gt;#7276&lt;/a&gt;): one read contract for Mission status.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/6466&quot;&gt;#6466&lt;/a&gt; and &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7198&quot;&gt;#7198&lt;/a&gt;: commands report different WP states for one Mission.&lt;/li&gt;
&lt;li&gt;PR &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/pull/6884&quot;&gt;#6884&lt;/a&gt; (branch &lt;code dir=&quot;auto&quot;&gt;issue-6466-lane-status-shadow&lt;/code&gt;): a lane root is never a status surface. Its contract is &lt;code dir=&quot;auto&quot;&gt;kitty-specs/lane-worktree-status-shadow-authority-01M68JFG/contracts/status-read-root.md&lt;/code&gt; on that branch.&lt;/li&gt;
&lt;li&gt;Mission &lt;code dir=&quot;auto&quot;&gt;lane-worktree-model-hardening-01M6QY1M&lt;/code&gt;: FR-001 to FR-007, FR-043, FR-061, NFR-001, Rules and Invariants 1 and 2.&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;What was ruled and what is derived.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ruled by the operator (2026-11-06, Decision Moments of the Mission).&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Ruling 8 (DM &lt;code dir=&quot;auto&quot;&gt;01M6QY3S1H6G5N853PJAPJS7CE&lt;/code&gt;): “The resolved status surface is the only source of truth; a lane worktree’s own status files never count (#6466, #6884).”&lt;/li&gt;
&lt;li&gt;Ruling 3 restated (DM &lt;code dir=&quot;auto&quot;&gt;01M6QY3XQJ5NAYVF3GMZ7ZPPRE&lt;/code&gt;): readers never read lane status files. This ADR carries the reader half; the checkout and writer halves are in the amendment of &lt;a href=&quot;/adr/3.x/2026-07-29-1-lane-base-recorded-planning-commit/&quot;&gt;ADR 2026-07-29-1&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;PRIMARY placement of a default Mission (DM &lt;code dir=&quot;auto&quot;&gt;01M6R0QJVPVZG2QT8MWQD4NXJR&lt;/code&gt;): “Topic branch until consolidate … explicit —topology Missions keep today’s placement … one read door (S1) carries it.”&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Derived&lt;/strong&gt; (plan and research R-1, R-2, R-4): the source names, the ref reader’s result type, fail-closed root normalization, and the precedence of the consolidated state over the coordination probe. Points the rulings leave open are listed under “Open points” with a recommendation.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;A Mission’s status lives in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; (with the derived &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;). Where that file is
read from depends on the topology and on the state of the coordination worktree. Nine adapters make
that choice today, and for one state, an unmaterialized coordination worktree, they give four answers
(research R-1):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the write side (&lt;code dir=&quot;auto&quot;&gt;status_transition._read_contract_from_transaction_target&lt;/code&gt;) reads the committed
coordination branch;&lt;/li&gt;
&lt;li&gt;the surface resolver’s loud fallback reads the repository root checkout’s stale copy
(&lt;a href=&quot;/adr/3.x/2026-06-19-1-coord-empty-surface-fallback/&quot;&gt;ADR 2026-06-19-1&lt;/a&gt;, amendment of 2026-06-21);&lt;/li&gt;
&lt;li&gt;the placement seam raises &lt;code dir=&quot;auto&quot;&gt;CoordinationWorktreeUnmaterialized&lt;/code&gt;
(&lt;a href=&quot;/adr/3.x/2026-09-24-2-coord-read-fail-closed/&quot;&gt;ADR 2026-09-24-2&lt;/a&gt;);&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;read_event_log(COORDINATION_BRANCH_REF)&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; on any &lt;code dir=&quot;auto&quot;&gt;git show&lt;/code&gt; failure, so a broken ref
reads as genesis.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A command run from inside a lane checkout can also read that lane’s inherited copy, which is #6466.
The result is wrong verdicts at exit 0: &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; can disagree about the same WP.&lt;/p&gt;
&lt;p&gt;The unmaterialized state is about to become normal, not rare. Lane checkouts become short-lived
(ruling 5, the S3 records) and the S9 write service commits to the coordination branch without a
worktree (C-1, below). A contract that breaks or reads stale data when no coordination worktree is on
disk breaks every reader.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Ruling 8: one source of truth, and a lane copy never counts.&lt;/li&gt;
&lt;li&gt;Rule 1: a read has exactly one declared source; it is never a lane checkout, never a path that does
not exist, and never a silent fallback.&lt;/li&gt;
&lt;li&gt;Liveness without a coordination worktree on disk (ruling 5, S9).&lt;/li&gt;
&lt;li&gt;A broken ref must never read as an empty history (FR-004).&lt;/li&gt;
&lt;li&gt;Cost: reading from a ref must stay cheap (NFR-001).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A. One door with a declared source per topology and state; an empty or unmaterialized coordination
worktree reads the committed coordination branch.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;B. Keep the loud repository-root fallback for an empty coordination worktree&lt;/strong&gt; (the 2026-06-21
amendment of ADR 2026-06-19-1, kept by &lt;code dir=&quot;auto&quot;&gt;coord-artifact-single-home-01M3V4BE&lt;/code&gt; C-002).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C. Materialize the coordination worktree on read.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;D. Raise on an unmaterialized coordination worktree&lt;/strong&gt; (the placement seam today).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: A.&lt;/strong&gt; It adopts the one adapter that is already right (the write side reads the ref in
that state) and makes every other reader use it.&lt;/p&gt;
&lt;h3 id=&quot;the-door&quot;&gt;The door&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_status_read(repo_root, mission, *, owned=None) -&gt; StatusReadSurface&lt;/code&gt; is the only way a
status read finds its source (FR-001, FR-005). The surface carries &lt;code dir=&quot;auto&quot;&gt;topology&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;source&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;mission_dir_name&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;repo_root&lt;/code&gt; (normalized), &lt;code dir=&quot;auto&quot;&gt;ref&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fallback_reason&lt;/code&gt; (data model §2).
Readers consume a surface through &lt;code dir=&quot;auto&quot;&gt;read_status_events&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;read_status_stream&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;materialize_status&lt;/code&gt;;
writers keep the write seam.&lt;/p&gt;
&lt;h3 id=&quot;sources&quot;&gt;Sources&lt;/h3&gt;


















































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Topology&lt;/th&gt;&lt;th&gt;Coordination state&lt;/th&gt;&lt;th&gt;Source&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;any&lt;/td&gt;&lt;td&gt;the Mission has landed on its target (the “landed” signal below)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; (owned checkout included), &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, provisional (&lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt;, not settled)&lt;/td&gt;&lt;td&gt;not applicable&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/td&gt;&lt;td&gt;materialized&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_WORKTREE&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/td&gt;&lt;td&gt;empty (worktree root present, Mission directory absent)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/td&gt;&lt;td&gt;unmaterialized (branch exists, no worktree)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/td&gt;&lt;td&gt;branch exists but holds no log yet (pre-seed)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fallback_reason&lt;/code&gt; set&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/td&gt;&lt;td&gt;deleted&lt;/td&gt;&lt;td&gt;raise &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; (unchanged)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;provisional or settled default Mission (&lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;no usable checkout holds the topic branch&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_BRANCH_REF&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT&lt;/code&gt;&lt;/strong&gt; is the working tree of the repository root checkout, or the validated owned
checkout when &lt;code dir=&quot;auto&quot;&gt;owned&lt;/code&gt; is given. It is never a ref: appends there are not committed yet, so a ref
read would drop rows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_WORKTREE&lt;/code&gt;&lt;/strong&gt; is the coordination worktree’s file. The transaction commits in the same unit
of work; &lt;code dir=&quot;auto&quot;&gt;status_surface_guard&lt;/code&gt; stays the divergence backstop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt;&lt;/strong&gt; is &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;:kitty-specs/&amp;#x3C;dir&gt;/status.events.jsonl&lt;/code&gt;, read with
&lt;code dir=&quot;auto&quot;&gt;git cat-file --batch&lt;/code&gt;. Owned checkouts of a coordination Mission follow the same rule instead of
raising (FR-003).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;MISSION_BRANCH_REF&lt;/code&gt;&lt;/strong&gt; is &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;mission_branch&gt;:kitty-specs/&amp;#x3C;dir&gt;/status.events.jsonl&lt;/code&gt;, for a
&lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt; Mission whose topic branch no usable checkout holds (for example the
repository root checkout was switched to another branch). When a checkout does hold the topic
branch, that checkout is the &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT&lt;/code&gt; instead. Read like &lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt;; a command that
needs a file refuses with the door’s remedy (&lt;code dir=&quot;auto&quot;&gt;status_surface_on_ref&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pre-seed fallback.&lt;/strong&gt; When the coordination branch exists but carries no log at that path, the door
returns &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;fallback_reason&lt;/code&gt; set. The rule is declared, scoped to coordination
topologies, and visible on the surface, so it is not silent. It covers the explicit-topology create
window. A default Mission settled to &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; does not reach it: its coordination branch
is the topic branch, which already holds the log written before settlement.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt;&lt;/strong&gt; is the target’s copy in the repository root checkout (FR-001). The landed
check runs before any coordination probe, so a coordination branch torn down by consolidation never
raises &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; keeps meaning “deleted without
landing”, which is data loss and fails closed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;The “landed” signal is not defined here.&lt;/strong&gt; The door asks the placement seam whether the Mission has
landed; it uses the same signal that switches a default Mission’s PRIMARY partition from the topic
branch to &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; (see “PRIMARY placement” below). That signal is defined by
&lt;a href=&quot;/adr/4.x/2026-11-06-3-topology-is-settled-once-at-first-finalize/&quot;&gt;ADR 2026-11-06-3&lt;/a&gt; and owned by the
placement seam (Mission WP14), which fixes the record consolidate writes for it. The nearest existing
signal is the lifecycle phase that &lt;code dir=&quot;auto&quot;&gt;mission_runtime.lifecycle_phase.resolve_lifecycle_phase&lt;/code&gt; derives
from &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt;, which already routes a published Mission’s status reads to the PRIMARY
Mission directory. This ADR adds no second signal.&lt;/p&gt;
&lt;h3 id=&quot;root-normalization&quot;&gt;Root normalization&lt;/h3&gt;
&lt;p&gt;Every input root is normalized first (FR-002). A lane root re-anchors to the main repository root
through the #6884 worktree registry classifier; a repository root input is returned unchanged.
&lt;strong&gt;A worktree registry that cannot be read fails closed with a typed error&lt;/strong&gt;, for every caller,
repository root callers included: without the registry the door cannot tell a lane root from the
repository root, and Rule 1 forbids reading a lane copy by mistake. This deliberately tightens #6884,
which keeps the caller’s root when the registry is unreadable (its
&lt;code dir=&quot;auto&quot;&gt;test_an_unreadable_worktree_registry_keeps_the_callers_root&lt;/code&gt; is flipped on purpose in Mission WP04).
WP04 names the error, reusing an existing typed resolver error when one fits.&lt;/p&gt;
&lt;h3 id=&quot;ref-reader&quot;&gt;Ref reader&lt;/h3&gt;
&lt;p&gt;The ref reader returns &lt;code dir=&quot;auto&quot;&gt;RefRead.ABSENT&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;RefRead.PRESENT(bytes)&lt;/code&gt; (FR-004, research R-2):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;an absent file on a readable ref is &lt;code dir=&quot;auto&quot;&gt;ABSENT&lt;/code&gt;, which callers read as an empty history (the door
first applies the pre-seed rule above);&lt;/li&gt;
&lt;li&gt;a missing or unreadable ref, a missing object or any git failure raises
&lt;code dir=&quot;auto&quot;&gt;StatusSurfaceRefUnreadable&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;STATUS_SURFACE_REF_UNREADABLE&lt;/code&gt;), and the command exits non-zero;&lt;/li&gt;
&lt;li&gt;where the coordination probe already classifies the branch as deleted, &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;
is raised as today.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A read served from a ref spawns at most one batched object-read subprocess per Mission per command
(NFR-001).&lt;/p&gt;
&lt;h3 id=&quot;invariants&quot;&gt;Invariants&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;The door never returns a path inside a registered lane checkout (ruling 8, FR-043).&lt;/li&gt;
&lt;li&gt;The door never returns a path that does not exist; exactly one of &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ref&lt;/code&gt; drives a read.&lt;/li&gt;
&lt;li&gt;Every fallback is declared and stamped; there is no silent fallback.&lt;/li&gt;
&lt;li&gt;No status read runs outside the door (FR-005); an architectural gate with an empty allowlist
enforces it (FR-006).&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;reverses&quot;&gt;Reverses&lt;/h3&gt;
&lt;p&gt;This ADR reverses two requirements of Mission &lt;code dir=&quot;auto&quot;&gt;coord-artifact-single-home-01M3V4BE&lt;/code&gt;, cited by
reference:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;coord-artifact-single-home-01M3V4BE#C-002&lt;/code&gt; (“Keep the read-side fallback”: an empty coordination
surface reads the repository root checkout, with a warning);&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;coord-artifact-single-home-01M3V4BE#FR-017&lt;/code&gt;, in the part that documents “the retained read-side
fallback” in ADR 2026-06-19-1.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;New behaviour: an empty or unmaterialized coordination worktree reads the committed coordination
branch, never the repository root checkout’s copy. The 2026-06-21 loud fallback of ADR 2026-06-19-1 is
superseded for status reads; that ADR carries an amendment pointing here. For the status kind
(&lt;code dir=&quot;auto&quot;&gt;STATUS_STATE&lt;/code&gt;) the door also replaces the raise of ADR 2026-09-24-2 on an unmaterialized
coordination worktree; other COORD-partition kinds keep that ADR’s rule until the S9 records (C-3)
decide them. The write side of ADR 2026-06-19-1 (single home, &lt;code dir=&quot;auto&quot;&gt;write_dir&lt;/code&gt;) is unchanged.&lt;/p&gt;
&lt;h3 id=&quot;primary-placement-for-default-missions&quot;&gt;PRIMARY placement for default Missions&lt;/h3&gt;
&lt;p&gt;This is a placement contract change (FR-061, DM &lt;code dir=&quot;auto&quot;&gt;01M6R0QJVPVZG2QT8MWQD4NXJR&lt;/code&gt;), carried by the read
door (Mission WP05) and the placement seam (Mission WP14) as one change.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PRIMARY partition kinds&lt;/strong&gt; are the members of &lt;code dir=&quot;auto&quot;&gt;_PRIMARY_ARTIFACT_KINDS&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py&lt;/code&gt;): spec, plan, research, data model, contracts, tasks, WP files,
&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, and the other members that frozenset lists. The frozenset is the
authority, not this list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt;.&lt;/strong&gt; Reads and writes of PRIMARY kinds resolve to &lt;code dir=&quot;auto&quot;&gt;meta.mission_branch&lt;/code&gt;,
the Mission topic branch (after a multi-lane settlement also the coordination branch), before and
after settlement, until &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; lands it on &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;. Once the “landed” signal is
recorded, the placement seam resolves the PRIMARY partition to &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;
stays the landing branch throughout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Explicit &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;) Missions&lt;/strong&gt; keep PRIMARY on &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, as today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consequence.&lt;/strong&gt; After settlement the repository root checkout no longer shows the planning files
(it returns to its create-time branch). Readers find them through the read door or the placement
seam, never through a path in the repository root checkout. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent context resolve --json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;check-prerequisites --paths-only&lt;/code&gt; report the PRIMARY-partition
location; WP05 and WP14 confirm both with tests.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;consequences&quot;&gt;Consequences&lt;/h3&gt;
&lt;h4 id=&quot;positive&quot;&gt;Positive&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Every status-reading command reports the same WP states, from any working directory and in every
coordination state (SC-001).&lt;/li&gt;
&lt;li&gt;Short-lived checkouts and a worktree-free coordination write stop breaking readers.&lt;/li&gt;
&lt;li&gt;A broken ref is a typed error, never an empty history.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;An unreadable worktree registry now stops every status read, where #6884 kept going.&lt;/li&gt;
&lt;li&gt;A ref read costs one git subprocess per Mission per command.&lt;/li&gt;
&lt;li&gt;After settlement, tools or people that open &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;dir&gt;/&lt;/code&gt; in the repository root checkout
of a default Mission find nothing there until consolidation lands it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; and the write seam are unchanged.&lt;/li&gt;
&lt;li&gt;The pre-seed fallback stays, but is declared and visible.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_read_surface_door.py&lt;/code&gt; (Mission WP05): the topology by coordination state matrix,
one source per cell, the pre-seed fallback stamp, the ref reader’s ABSENT versus unreadable split,
the subprocess count (NFR-001), and the FR-061 placement with its explicit-topology control.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_status_readers_cross_cwd_parity.py&lt;/code&gt; (Mission WP06): every reader agrees from the
repository root checkout, a lane checkout and the coordination path, with the coordination worktree
present, empty and absent.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_read_single_door.py&lt;/code&gt; (Mission WP07): the empty-allowlist call-site
gate with planted violations (FR-006).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/lanes/test_lane_checkout_helper.py&lt;/code&gt; (Mission WP09): every lane-checkout route excludes the
status files (the checkout half of ruling 3).&lt;/li&gt;
&lt;li&gt;WP04’s flipped &lt;code dir=&quot;auto&quot;&gt;test_registry_unreadable_fails_closed&lt;/code&gt; and its repository-root-caller control.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;pros-and-cons-of-the-options&quot;&gt;Pros and Cons of the Options&lt;/h2&gt;
&lt;h3 id=&quot;b-keep-the-loud-repository-root-fallback&quot;&gt;B. Keep the loud repository-root fallback&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; no change for readers today; liveness without a worktree.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; it reads a stale copy as truth, which is the root cause of #6466 and #7198. A warning does
not make the answer right.&lt;/p&gt;
&lt;h3 id=&quot;c-materialize-the-coordination-worktree-on-read&quot;&gt;C. Materialize the coordination worktree on read&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; every read sees a file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; a read writes; it fights ruling 5 and the S9 write service, which remove the worktree.&lt;/p&gt;
&lt;h3 id=&quot;d-raise-on-an-unmaterialized-coordination-worktree&quot;&gt;D. Raise on an unmaterialized coordination worktree&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; never stale.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; with short-lived checkouts every reader breaks in the normal state.&lt;/p&gt;
&lt;h2 id=&quot;open-points&quot;&gt;Open points&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Target not checked out.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt; reads the target’s copy in the repository root
checkout, as FR-001 says. When the repository root checkout is on another branch that lacks the
Mission, the door must not return a missing path (invariant 2). Recommendation: read the target ref
through the same ref reader. WP05 decides with a test.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-06-19-1-coord-empty-surface-fallback/&quot;&gt;ADR 2026-06-19-1&lt;/a&gt;: superseded for status
reads (amendment of 2026-11-06).&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-07-29-1-lane-base-recorded-planning-commit/&quot;&gt;ADR 2026-07-29-1&lt;/a&gt;: amendment of
2026-11-06, lane checkouts carry no live status; Assert A’ kept.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/3.x/2026-09-24-2-coord-read-fail-closed/&quot;&gt;ADR 2026-09-24-2&lt;/a&gt;: its unmaterialized raise no
longer applies to status reads.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/4.x/2026-10-01-2-mission-status-read-api-and-dashboard-extraction/&quot;&gt;ADR 2026-10-01-2&lt;/a&gt;: the Mission
Status Read API reads through this contract.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/4.x/2026-11-06-3-topology-is-settled-once-at-first-finalize/&quot;&gt;ADR 2026-11-06-3&lt;/a&gt; (forward reference):
topology settlement and the “landed” signal.&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/4.x/2026-11-06-4-coordination-branch-written-by-commit/&quot;&gt;ADR 2026-11-06-4&lt;/a&gt; (C-1, forward reference)
and &lt;a href=&quot;/adr/4.x/2026-11-06-6-committed-ledger-is-the-coordination-blob/&quot;&gt;ADR 2026-11-06-6&lt;/a&gt; (C-3, forward
reference): the worktree-free coordination write; C-3 ties the oracle fallback to this contract (a
missing ref is a typed error, not a read of the repository root checkout).&lt;/li&gt;
&lt;li&gt;PR #6884 and its contract &lt;code dir=&quot;auto&quot;&gt;status-read-root.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-11-08-proposed-the-call-site-gate-lands-with-a-priced-allowlist-and-landed-has-one-signal&quot;&gt;Amendment 2026-11-08 (Proposed): the call-site gate lands with a priced allowlist, and “landed” has one signal&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator). Accepted by merging the pull request that carries it.
&lt;strong&gt;Technical Story:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7408&quot;&gt;#7408&lt;/a&gt; (S5 of epic
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/3893&quot;&gt;#3893&lt;/a&gt;),
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7310&quot;&gt;#7310&lt;/a&gt; (the deferred FR-005/FR-006 of Mission
&lt;code dir=&quot;auto&quot;&gt;lane-worktree-model-hardening-01M6QY1M&lt;/code&gt;), &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7335&quot;&gt;#7335&lt;/a&gt;.
The body above is kept as written.&lt;/p&gt;
&lt;h3 id=&quot;the-gate-invariant-4-fr-006&quot;&gt;The gate (invariant 4, FR-006)&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_read_single_door.py&lt;/code&gt; scans &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; (AST) for the legacy ways of
finding a status source: &lt;code dir=&quot;auto&quot;&gt;resolve_status_surface&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;resolve_status_surface_with_anchor&lt;/code&gt; (a
&lt;code dir=&quot;auto&quot;&gt;for_write=True&lt;/code&gt; call is the write seam and is not scanned), &lt;code dir=&quot;auto&quot;&gt;read_event_log&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;read_event_stream_log&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_surface_dir_or_typed_error&lt;/code&gt;, and every &lt;code dir=&quot;auto&quot;&gt;STATUS_STATE&lt;/code&gt; read off the
placement seam (&lt;code dir=&quot;auto&quot;&gt;read_dir&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_partition_read_dir&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_artifact_surface&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;ctx.artifact(STATUS_STATE)&lt;/code&gt; unless only its &lt;code dir=&quot;auto&quot;&gt;write_dir&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;commit_target&lt;/code&gt; is used). A call
through an import alias is matched by the name it imports. Planted violations keep it non-vacuous.&lt;/p&gt;
&lt;p&gt;Invariant 4 asks for an empty allowlist. The gate lands with a &lt;strong&gt;transient, shrink-only allowlist&lt;/strong&gt;
instead, because about 45 readers remain and draining them all exceeds one reviewable change. Per
charter Standing Order #5 and ADR &lt;a href=&quot;/adr/4.x/2026-09-30-1-allowlist-ratchets-are-priced-debt/&quot;&gt;2026-09-30-1&lt;/a&gt;
the allowlist is priced debt: issue #7310 owns it, the follow-up Mission of #7310 drains it, and the
drain date is the gate’s &lt;code dir=&quot;auto&quot;&gt;ALLOWLIST_DRAIN_BY&lt;/code&gt; (2026-12-31, operator-confirmed; moving it is recorded on #7310).
A new bypass fails, and an entry that no longer matches a reader fails too, so a migrated reader
leaves the allowlist in the same change. The allowlist size is registered in
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/_baselines.yaml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;test_status_read_single_door.legacy_read_allowlist&lt;/code&gt;), so
adding an entry also fails &lt;code dir=&quot;auto&quot;&gt;test_ratchet_baselines.py&lt;/code&gt; unless the baseline grows with a
justification. An entry is keyed by enclosing function and form, not by call: a second legacy read
of the same form inside an already-listed function is not caught. Invariant 4 is reached when the
allowlist is empty.&lt;/p&gt;
&lt;p&gt;A second check pins the modules already moved onto the door (&lt;code dir=&quot;auto&quot;&gt;DOOR_ONLY_MODULES&lt;/code&gt;, grow-only): they may
not call a legacy source finder or a path-typed log reader (&lt;code dir=&quot;auto&quot;&gt;read_events&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;read_event_stream&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;wp_snapshot_state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reconstruct_wp_view&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;has_event_log&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;get_wp_lane&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;get_all_wp_lanes&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;event_sourced_review_result&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;get_arbiter_overrides_for_wp&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Not scanned (named limits).&lt;/strong&gt; A path-typed log read handed a directory that did not come from a
legacy finder (the census counted &lt;code dir=&quot;auto&quot;&gt;get_wp_lane&lt;/code&gt; 52, &lt;code dir=&quot;auto&quot;&gt;has_event_log&lt;/code&gt; 26, &lt;code dir=&quot;auto&quot;&gt;WorkPackage.status_dir&lt;/code&gt; 20
and &lt;code dir=&quot;auto&quot;&gt;reconstruct_wp_view&lt;/code&gt; 15 call sites), and &lt;code dir=&quot;auto&quot;&gt;resolve_handle_to_read_path&lt;/code&gt;, which also serves
non-status reads. Modules leave that blind spot by joining &lt;code dir=&quot;auto&quot;&gt;DOOR_ONLY_MODULES&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Known blind spots of the call-site scan.&lt;/strong&gt; Each is a way a legacy read passes the gate unseen:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the allowlist is keyed &lt;code dir=&quot;auto&quot;&gt;path::function::form&lt;/code&gt;, so a second legacy call of the same form inside a
function already listed passes;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind.STATUS_STATE&lt;/code&gt; bound to a variable first and read through that alias;&lt;/li&gt;
&lt;li&gt;a rebound &lt;code dir=&quot;auto&quot;&gt;read_event_log&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;r = read_event_log; r(d)&lt;/code&gt;);&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;getattr(x, &quot;read_event_log&quot;)&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;a direct read of a &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; path;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;for_write=True&lt;/code&gt; is a syntactic exemption: a call passing it is skipped whatever it reads.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;census-at-landing-45-entries&quot;&gt;Census at landing (45 entries)&lt;/h3&gt;























































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Reason&lt;/th&gt;&lt;th&gt;Entries&lt;/th&gt;&lt;th&gt;What has to happen&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Path-typed consumer (&lt;code dir=&quot;auto&quot;&gt;get_wp_lane&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;read_events&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;has_event_log&lt;/code&gt; on a dir)&lt;/td&gt;&lt;td&gt;13&lt;/td&gt;&lt;td&gt;read a surface instead&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Runtime decision path (&lt;code dir=&quot;auto&quot;&gt;ctx.artifact(STATUS_STATE)&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;runtime/next&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;move with the runtime bridge readers&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Existence or fail-closed probe relying on &lt;code dir=&quot;auto&quot;&gt;CoordinationWorktreeUnmaterialized&lt;/code&gt;&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;a door-level probe&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Write-side transaction reading its own target (&lt;code dir=&quot;auto&quot;&gt;status_transition&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;the writer cut-over (#6195, #6608)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Handed-dir partition authority (#5180)&lt;/td&gt;&lt;td&gt;3&lt;/td&gt;&lt;td&gt;surface-typed verdict and feedback reads&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Legacy Path projection (&lt;code dir=&quot;auto&quot;&gt;resolve_status_surface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_surface_dir_or_typed_error&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;deleted with their callers&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Finalize planning pin (#5702 decides its fail-open polarity first)&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;#5702&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;WorkPackage.status_dir&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;locate_work_package&lt;/code&gt;&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;a surface-typed WorkPackage read&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Placement seam &lt;code dir=&quot;auto&quot;&gt;STATUS_STATE&lt;/code&gt; arm, aggregate create-window gate, &lt;code dir=&quot;auto&quot;&gt;tasks_are_finalized&lt;/code&gt; drift check, lane-destroyed guard, committed-ref strand authority, owned identity check, review override written through a read path&lt;/td&gt;&lt;td&gt;1 each (7)&lt;/td&gt;&lt;td&gt;per entry&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;one-landed-signal&quot;&gt;One landed signal&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;runtime.next.committed_authority&lt;/code&gt; decided “merged” from &lt;code dir=&quot;auto&quot;&gt;meta.mission_number&lt;/code&gt;, which a reopen keeps,
while this door decides &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;mission_runtime.mission_has_landed&lt;/code&gt; (the
reopen-aware &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; marker). Both now ask &lt;code dir=&quot;auto&quot;&gt;mission_has_landed&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; is display-only
and is no landed signal. &lt;code dir=&quot;auto&quot;&gt;committed_status_dir&lt;/code&gt;, the status board’s own committed-source probe, is
removed: the board reads the door, which already answers &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt; for a landed Mission.
A Mission merged before &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; was written again (#4090) has no &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; (264 of the 819
Missions in this repository’s &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; carry &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; without it, which counts some
that never landed, see below). The door already treated such a Mission as not landed, and now &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; does too; a coordination-topology one,
whose coordination branch consolidation removed, refuses with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt; in both.
Reintroducing &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; as a second landed signal was rejected (operator ruling 2026-11-08):
&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; assigns it to Missions that never landed (#5471), so it is no evidence
of a landing either.&lt;/p&gt;
&lt;p&gt;Instead the upgrade migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_backfill_merged_at&lt;/code&gt; (#7433) stamps &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; once, from
the committed status log only (operator rulings 2026-11-08). The rule lives in one place,
&lt;code dir=&quot;auto&quot;&gt;specify_cli.status.landing_evidence&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Evidence.&lt;/strong&gt; Every work package in the Mission’s status log is terminal (&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;),
at least one is &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, and the log records no &lt;code dir=&quot;auto&quot;&gt;MissionReopened&lt;/code&gt; event. The log is read through
this door: &lt;code dir=&quot;auto&quot;&gt;resolve_landing_evidence_read&lt;/code&gt; takes the door’s own decision (the coordination
branch or worktree while it exists, the write checkout for a coordination-less Mission), with
one declared exception: when the door refuses with &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;, the evidence is
the target’s copy (&lt;code dir=&quot;auto&quot;&gt;resolve_consolidated_target_read&lt;/code&gt;), the only committed log left once
consolidation removed the coordination branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Date.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; of the latest transition to &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; in that log, normalized to aware UTC
(a naive stamp is read as UTC). No git history is read: neither &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; (the
target tip before the landing, a lower bound) nor the commit that set &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; (often a
bulk &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; rewrite) dates a landing.
A &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; written by a migration actor (&lt;code dir=&quot;auto&quot;&gt;migration:*&lt;/code&gt;, e.g. the #5579 &lt;code dir=&quot;auto&quot;&gt;backfill_wp_status&lt;/code&gt; seed,
which restates history near the Mission’s creation) supplies the date only when the log has no
other &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; event (operator ruling 2026-11-08); otherwise the latest non-migration &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; wins.
When the coordination branch is gone, the target’s copy (the file &lt;code dir=&quot;auto&quot;&gt;CONSOLIDATED_TARGET&lt;/code&gt; reads) is
the evidence; the operator signed off this exception on 2026-11-08.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Skipped and reported.&lt;/strong&gt; A Mission without that evidence (unfinished work packages, all
canceled, reopened, no log, an unreadable log) is never stamped; the migration names it in a
warning, one per reason. So is a Mission with a consolidation in progress (its
&lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/merge/&amp;#x3C;mission_id&gt;/state.json&lt;/code&gt; exists), whatever its log shows: consolidation
bakes &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; before it stamps &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt;, so an interrupted run meets the evidence, and stamping
it would point &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; at the target’s copy, which has no log yet.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It writes &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; only, through the canonical meta writer, records in the tracked ledger
partition (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; travels with the commit), declares &lt;code dir=&quot;auto&quot;&gt;requires_git_repository&lt;/code&gt; (the door reads
the worktree registry and coordination refs), and is idempotent. A dry run on this repository’s
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; (533 Missions without &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt;) would stamp 341 and skip 192: 172 with unfinished
work packages, 15 whose log records no work package and 5 with no log.&lt;/p&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt; remedy asks the same predicate of the target’s copy: when it
holds, the remedy is &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (and names the latest done date), not flattening the
Mission; otherwise the flatten remedy stands. &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; plays no part in that choice, and
the check only picks the remedy text; the landed verdict stays &lt;code dir=&quot;auto&quot;&gt;mission_has_landed&lt;/code&gt; alone.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Residual.&lt;/strong&gt; A Mission whose work packages are all &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; but which was never consolidated (a
manual &lt;code dir=&quot;auto&quot;&gt;move-task --to done&lt;/code&gt;) also satisfies the evidence and is stamped. &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; is ordinarily
written by consolidation itself, and the operator accepted this residual with the ruling.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Residual.&lt;/strong&gt; The backfill settles even when a Mission’s status log is unreadable; once that log is
repaired, &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer re-selects it and the &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt; remedy
is inert until a re-run path exists (#7449).&lt;/p&gt;
&lt;h3 id=&quot;moved-onto-the-door-in-this-change&quot;&gt;Moved onto the door in this change&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; (one surface read; every row field from it; a log that cannot be read fails the
command closed instead of rendering an empty board), the canceled-set read of
&lt;code dir=&quot;auto&quot;&gt;git/origin_freshness&lt;/code&gt;, the lane-tip terminal hook of &lt;code dir=&quot;auto&quot;&gt;lanes/claim_base&lt;/code&gt; and the review dependents
warning of &lt;code dir=&quot;auto&quot;&gt;workflow_executor&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;tests/status/test_status_readers_cross_cwd_parity.py&lt;/code&gt; carries
&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; in its matrix.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-11-11-owned-coordination-checkouts-read-vs-dispatch&quot;&gt;Amendment 2026-11-11: owned coordination checkouts, read vs dispatch&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator). Accepted by merging the pull request that carries it.
&lt;strong&gt;Technical Story:&lt;/strong&gt; Mission &lt;code dir=&quot;auto&quot;&gt;runtime-status-read-door-01M73HHB&lt;/code&gt; (FR-007, FR-012), Decision Moment
&lt;code dir=&quot;auto&quot;&gt;01M73HKG7WSR4VDRFXG9JWTGM8&lt;/code&gt; (DM-1). The body and the 2026-11-08 amendment above are kept as written.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Finding the Mission.&lt;/strong&gt; For an owned checkout of a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; Mission, the door
locates the Mission through the owned checkout, not the repository root checkout. The owned
checkout’s Mission directory gives &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, the landed check and the pre-seed fallback. The
coordination state (materialized, empty, unmaterialized, deleted) is still probed under the
repository root, because the coordination worktree and branch are registered there. A Mission that
exists only in the owned checkout therefore resolves. Owned &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Missions are
unchanged: they read the owned checkout’s Mission directory.
For every owned topology the owned fact decides the Mission and the door does not re-check the
handle against it: the fact was resolved from that handle (slug, mid8 or ULID) when it was minted (#7539).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reading.&lt;/strong&gt; Query and progress of an owned coordination Mission read the committed coordination
branch when its worktree is empty or unmaterialized, as §2 already says for every coordination
Mission.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Dispatching.&lt;/strong&gt; An advancing dispatch of that Mission (one that would send an agent to work in the
coordination workspace) refuses with &lt;code dir=&quot;auto&quot;&gt;OWNED_COORDINATION_WORKSPACE_UNAVAILABLE&lt;/code&gt; when that workspace
is empty. An unmaterialized workspace is not refused: the bootstrap’s decision-log write
materializes the coordination worktree before the dispatch is decided, the dispatch proceeds, and
the decision reports the materialization in &lt;code dir=&quot;auto&quot;&gt;Decision.remediation&lt;/code&gt;. This keeps the operator’s
ruling in DM-1: an agent must not be sent into a missing workspace, and a workspace the bootstrap
has just materialized is not missing. It is a dispatch rule, not a read rule; the door itself never
refuses for it. The code is raised by &lt;code dir=&quot;auto&quot;&gt;mission_runtime.resolution._resolve_status_surface_dir_owned&lt;/code&gt;
(an empty owned coordination worktree) and mapped to the typed &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; decision by
&lt;code dir=&quot;auto&quot;&gt;runtime.next.runtime_bridge._owned_coordination_unavailable_decision&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;amendment-2026-11-20-a-remote-only-branch-is-a-typed-refusal-5287&quot;&gt;Amendment 2026-11-20: a remote-only branch is a typed refusal (#5287)&lt;/h2&gt;
&lt;p&gt;The ref reader rule above gains one case. When a ref-sourced read (&lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt; or
&lt;code dir=&quot;auto&quot;&gt;MISSION_BRANCH_REF&lt;/code&gt;) fails and the branch has no local head (&lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;branch&gt;&lt;/code&gt; does not
resolve), the door looks at this clone’s remote-tracking refs (a local read):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When one proves a remote holds the branch, the door raises &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceRefRemoteOnly&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;STATUS_SURFACE_REF_REMOTE_ONLY&lt;/code&gt;). It is a subtype of &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceRefUnreadable&lt;/code&gt;, so every
caller that handles an unreadable ref handles it and relays its own code. Its message carries the
canonical remote-only remedy from &lt;code dir=&quot;auto&quot;&gt;mission_runtime.coord_remedy&lt;/code&gt;: create the local branch from
&lt;code dir=&quot;auto&quot;&gt;refs/remotes/&amp;#x3C;remote&gt;/&amp;#x3C;branch&gt;&lt;/code&gt;, then run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --mission &amp;#x3C;slug&gt; --fix&lt;/code&gt;
(or re-run the command, for a Mission topic branch).&lt;/li&gt;
&lt;li&gt;When none does, nothing local proves the branch exists: the coordination probe may have answered
“present” on an inconclusive remote, a topic branch is not probed, and the branch may be gone
everywhere. The door keeps &lt;code dir=&quot;auto&quot;&gt;STATUS_SURFACE_REF_UNREADABLE&lt;/code&gt;, whose message adds the same steps
(led by a fetch into the remote-tracking ref) as a hedged “if the branch still exists on a
remote” hint.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Further:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The classification runs only after a failed read, so a readable ref costs no extra subprocess
(NFR-001 unchanged).&lt;/li&gt;
&lt;li&gt;A local ref that names a missing object still resolves and keeps &lt;code dir=&quot;auto&quot;&gt;STATUS_SURFACE_REF_UNREADABLE&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A coordination branch the probe classifies as deleted keeps raising &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The door still never reads a remote-tracking ref as a status source: one declared source per
cell, no fallback. A remote-tracking read source, if wanted, belongs to #7408 under its own
amendment.&lt;/li&gt;
&lt;li&gt;Composing the remedy contacts no remote: it reads git configuration and local refs only (ADR
&lt;code dir=&quot;auto&quot;&gt;2026-10-06-3&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
