<?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-4-coordination-branch-written-by-commit/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-11-06-4-coordination-branch-written-by-commit/</id>
  <title>ADR: a coordination branch is written by commit, not through a coordination worktree</title>
  <updated>2026-11-06T00: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-4-coordination-branch-written-by-commit/"/>
  <summary>Proposed: the coordination branch stays the lifecycle home and the write service commits to it with no coordination worktree; every coordination kind, status.json and migration.</summary>
  <content type="html">&lt;h2 id=&quot;a-coordination-branch-is-written-by-commit-not-through-a-coordination-worktree&quot;&gt;A coordination branch is written by commit, not through a coordination worktree&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, together with the other records of the set (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). The rulings are recorded as resolved Decision Moments in Mission &lt;code dir=&quot;auto&quot;&gt;lane-worktree-model-hardening-01M6QY1M&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision list --mission lane-worktree-model-hardening-01M6QY1M&lt;/code&gt;); ruling 4 is DM &lt;code dir=&quot;auto&quot;&gt;01M6QY371KRY5XXQMDQ4WZR1YE&lt;/code&gt;.&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/7284&quot;&gt;#7284&lt;/a&gt; (S9): the worktree-free coordination write is decided before it is built. Epic &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7276&quot;&gt;#7276&lt;/a&gt;. Implementation follows write-service migration step 4 (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/6117&quot;&gt;#6117&lt;/a&gt;); this record builds nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Discharges&lt;/strong&gt; part of the obligation of &lt;a href=&quot;/adr/4.x/2026-10-22-1-the-java-write-service-is-the-canonical-event-writer/&quot;&gt;ADR 2026-10-22-1&lt;/a&gt; D-6 (“each of those needs its own ADR before such an adapter is built”); the mapping is in that record’s Amendment 2026-11-06. This record supplies the step that amendment names &lt;strong&gt;4a&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Amends&lt;/strong&gt; &lt;a href=&quot;/adr/4.x/2026-10-27-1-the-write-service-protocol-is-loopback-http-with-a-bearer-token/&quot;&gt;ADR 2026-10-27-1&lt;/a&gt; D-3: &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; is required for the coordination surface (D-7 below).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Amends&lt;/strong&gt; ADR 2026-10-22-1 open question 2: write-location resolution for coordination Missions moves into the service at step 4 (its default), and the location it resolves is a ref, not a worktree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Related records of the same set&lt;/strong&gt; (all Proposed, accepted together):
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;C-2&lt;/strong&gt; &lt;a href=&quot;/adr/4.x/2026-11-06-5-gates-over-worktree-less-coordination/&quot;&gt;ADR 2026-11-06-5&lt;/a&gt;: consolidation gates over a worktree-less coordination branch, and the write fence;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C-3&lt;/strong&gt; &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;: the committed ledger of a coordination Mission is the blob on its coordination branch (publication seam, read API, &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; cursor);&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;events ADR-0007&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;docs/adr/0007-write-service-commits-coordination-status-by-ref.md&lt;/code&gt; and &lt;strong&gt;events ADR-0008&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;docs/adr/0008-read-service-reads-coordination-ledger-from-git-objects.md&lt;/code&gt;, in repository &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-events&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty-events&lt;/code&gt;&lt;/a&gt;, branch &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; (merged from &lt;code dir=&quot;auto&quot;&gt;issue-7284-coordination-ref-write-adrs&lt;/code&gt;), pull request &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-events/pull/215&quot;&gt;spec-kitty/spec-kitty-events#215&lt;/a&gt;. ADR-0007 decides how the service commits; this record decides what is committed where, and what the CLI retires. ADR-0008 decides how the Java read service reads it.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read side:&lt;/strong&gt; &lt;a href=&quot;/adr/4.x/2026-11-06-2-one-status-read-contract/&quot;&gt;ADR 2026-11-06-2&lt;/a&gt; (one status read contract, S1) is the ref read contract this record relies on.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Destructive authority:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/pull/7275&quot;&gt;ADR 2026-11-06-1&lt;/a&gt; (a destructive git operation discharges named proof obligations; on PR #7275, branch &lt;code dir=&quot;auto&quot;&gt;issue-7211-safe-landed-prune&lt;/code&gt;) governs the removal of existing coordination worktrees (D-9).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Settlement:&lt;/strong&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; (topology settled once at first finalize) materializes a coordination worktree today; Consequences say what changes for it at step 4a.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer building the step-4 write path for coordination Missions, changing the coordination transaction, or retiring the coordination worktree.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Terms.&lt;/strong&gt; “Coordination topology” is &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;. “Coordination branch” is the branch named by &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt;. “Coordination worktree” is a checkout of it under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&amp;#x3C;mission&gt;-coord/&lt;/code&gt;. “Repository root checkout” is the main working tree; “PRIMARY partition” is the artifact partition, never the primary branch (&lt;a href=&quot;/context/orchestration/#primary-partition&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/orchestration.md&lt;/code&gt;&lt;/a&gt;). “Step 4” and “step 4a” are steps of the migration order of ADR 2026-10-22-1.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;A coordination Mission records its lifecycle on a coordination branch. Today the CLI writes that branch through a coordination worktree. &lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/coordination/transaction.py&lt;/code&gt;) resolves the worktree (&lt;code dir=&quot;auto&quot;&gt;_resolve_coord_worktree_root_for_transaction&lt;/code&gt;), appends the event log there (&lt;code dir=&quot;auto&quot;&gt;append_events&lt;/code&gt;), writes non-event artefacts there (&lt;code dir=&quot;auto&quot;&gt;write_artifact&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;enroll_subprocess_byproducts&lt;/code&gt;), commits with &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;commit&lt;/code&gt;) and cuts the append when the commit fails (&lt;code dir=&quot;auto&quot;&gt;_cut_event_log&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_rollback&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;The worktree is a second copy of the branch, and each way that copy can be wrong became a refusal code:&lt;/p&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Code&lt;/th&gt;&lt;th&gt;Raised by&lt;/th&gt;&lt;th&gt;Failure&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coordination/status_surface_guard.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination/transaction_errors.py&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the worktree’s log lost events its &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; committed&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_UNREADABLE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the same&lt;/td&gt;&lt;td&gt;the committed log is malformed, repeats an id or cannot be read&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_WORKTREE_MISSING&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coordination/transaction_errors.py&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the coordination worktree the transaction needs is missing&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;FALLBACK_COORD_WORKTREE_UNRESOLVED&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coordination/status_transition.py&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the fallback coordination worktree cannot be resolved&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;coordination/surface_resolver.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination/commit_router.py&lt;/code&gt;, the origin gates&lt;/td&gt;&lt;td&gt;the coordination worktree is declared but not created&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;mission-write&lt;/code&gt; contract encoded the same worktree: &lt;code dir=&quot;auto&quot;&gt;WriteSurface&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;coordination_transaction_append&lt;/code&gt; was “an append inside the coordination transaction, in the coordination worktree”, and the five codes above were protocol codes too.&lt;/p&gt;
&lt;p&gt;The operator ruled on 2026-11-06 (ruling 4, and rulings 2, 3 and 8 of epic #7276): the coordination branch stays the lifecycle home; the resolved status surface is the only source of truth; lane branches carry no status copies; and the Java write service writes coordination status &lt;strong&gt;without a coordination worktree&lt;/strong&gt;. ADRs only; the implementation follows migration step 4.&lt;/p&gt;
&lt;p&gt;The coordination transaction writes more than status events. A rule that covers only &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; would leave notes, trace, issue matrix and decision artefacts still needing a worktree, so the worktree could never be retired. This record covers every coordination-partition kind.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;One source of truth: the committed tree of the coordination branch. A working tree is a second copy that can diverge (ruling 8).&lt;/li&gt;
&lt;li&gt;One writer per ref: the write service (ADR 2026-10-22-1 D-1, D-5: no Python fallback writer).&lt;/li&gt;
&lt;li&gt;Nothing may keep needing a coordination worktree once step 4a ships; a kind without a rule blocks the retirement.&lt;/li&gt;
&lt;li&gt;Existing coordination Missions must keep working through the cut: no release in which their status writes are refused.&lt;/li&gt;
&lt;li&gt;Every destructive step goes through the one destructive authority (ruling 7, &lt;code dir=&quot;auto&quot;&gt;git/destructive_guard.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;mission-write&lt;/code&gt; contract must change before its &lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt; (ADR 2026-10-27-1: a closed-response change after &lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt; is a major).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The coordination branch is written by commit, through the write service, for every coordination-partition kind&lt;/strong&gt; (chosen).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep a coordination worktree, owned by the service.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retire the coordination branch&lt;/strong&gt; and record coordination status on the target or the repository root checkout.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Chosen option: 1.&lt;/strong&gt; Each decision is marked &lt;em&gt;(ruled)&lt;/em&gt; where it restates an operator ruling and &lt;em&gt;(derived)&lt;/em&gt; where this record derives it. Choices the rulings leave open are given as options with a &lt;strong&gt;recommendation&lt;/strong&gt;; they stay open until the operator accepts this record (Mission assumption A-12).&lt;/p&gt;
&lt;h3 id=&quot;d-1-the-coordination-branch-stays-the-lifecycle-home-and-is-written-by-commit-ruled&quot;&gt;D-1: the coordination branch stays the lifecycle home and is written by commit &lt;em&gt;(ruled)&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The coordination branch remains where a coordination Mission’s lifecycle lives (ruling 2). Nothing moves to the target or to the repository root checkout.&lt;/li&gt;
&lt;li&gt;From step 4a, no coordination worktree is created, for new or existing Missions. Every write to the coordination branch is a commit built from git objects and moved onto &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;&lt;/code&gt; by compare-and-swap, by the write service (events ADR-0007 D-1, D-3). No index, working tree or checkout of the repository is touched.&lt;/li&gt;
&lt;li&gt;Lane branches carry no status copies (ruling 3, as restated in &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 2026-11-06).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;d-2-this-is-a-new-storage-adapter-in-adr-2026-10-22-1-d-6s-sense-derived&quot;&gt;D-2: this is a new storage adapter in ADR 2026-10-22-1 D-6’s sense &lt;em&gt;(derived)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;Committing into the object store is not “the local file ledger”: the file is no longer appended in place, and readers read a blob, not a path. D-6 therefore applies: the coordination ledger may move to git objects only after the records it lists exist. This set (C-1, C-2, C-3, events ADR-0007, events ADR-0008) is those records; ADR 2026-10-22-1 Amendment 2026-11-06 maps each D-6 bullet to one of them.&lt;/p&gt;
&lt;h3 id=&quot;d-3-every-coordination-partition-kind-has-a-rule-derived-the-artefact-rule-is-open-with-a-recommendation&quot;&gt;D-3: every coordination-partition kind has a rule &lt;em&gt;(derived; the artefact rule is open with a recommendation)&lt;/em&gt;&lt;/h3&gt;








































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Kind&lt;/th&gt;&lt;th&gt;Writer today (through &lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction&lt;/code&gt;)&lt;/th&gt;&lt;th&gt;From step 4a&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Status events (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;append_events&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the write service, &lt;code dir=&quot;auto&quot;&gt;writeSurface: coordination_ref_commit&lt;/code&gt; (events ADR-0007)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the transaction’s materialize step&lt;/td&gt;&lt;td&gt;D-4&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Notes, trace (&lt;code dir=&quot;auto&quot;&gt;traces/*.md&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;write_artifact&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the artefact rule below&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Issue matrix (&lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;write_artifact&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tasks/issue_matrix.py&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;the artefact rule below&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Decision artefacts (&lt;code dir=&quot;auto&quot;&gt;decisions/&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;decisions/service.py&lt;/code&gt; (4 call sites)&lt;/td&gt;&lt;td&gt;the artefact rule below&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Subprocess byproducts&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;enroll_subprocess_byproducts&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tasks_move_task_gates.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workflow.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement_planning_commit.py&lt;/code&gt;)&lt;/td&gt;&lt;td&gt;the artefact rule below&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;strong&gt;The artefact rule&lt;/strong&gt; (open; it ties to &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7266&quot;&gt;#7266&lt;/a&gt;, artefact placement):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(a) The service gains an artefact operation on the same surface.&lt;/strong&gt; A &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt; unit may carry artefact blobs (path, bytes) beside its rows, committed in the same compare-and-swap commit. One writer per ref; one commit per unit; the transaction’s “rows and artefacts land together” property is kept.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(b) The non-status kinds move to the PRIMARY partition&lt;/strong&gt; (#7266). The coordination branch then carries only the event log, and the kinds are written where PRIMARY artefacts are written today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(c) The CLI commits the non-status kinds itself&lt;/strong&gt;, by plumbing, onto the same ref. Rejected: two writers on one ref race; the compare-and-swap detects it, but every race becomes a refusal on one side, and it breaks “one writer” (ADR 2026-10-22-1 D-1).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Recommendation:&lt;/strong&gt; (a) as the default for every kind, so step 4a does not wait on #7266; #7266 may later move a kind to PRIMARY under (b), and that kind then leaves this surface. Whatever is chosen, it is chosen per kind, before step 4a, and no kind is left without a rule.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The decision ledger.&lt;/strong&gt; &lt;a href=&quot;/adr/4.x/2026-10-01-3-decision-ledger-primary-partition/&quot;&gt;ADR 2026-10-01-3&lt;/a&gt; places the decision ledger on the PRIMARY partition, yet &lt;code dir=&quot;auto&quot;&gt;decisions/service.py&lt;/code&gt; writes through the coordination transaction. &lt;strong&gt;Recommendation:&lt;/strong&gt; follow ADR 2026-10-01-3 (option (b) for decision artefacts), and treat the transaction route as the drift to remove; confirm with #7266 before step 4a.&lt;/p&gt;
&lt;h3 id=&quot;d-4-statusjson-on-the-coordination-branch-open-with-a-recommendation&quot;&gt;D-4: &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; on the coordination branch &lt;em&gt;(open with a recommendation)&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(a) Not committed on the coordination branch.&lt;/strong&gt; It is derived; readers reduce the committed log (&lt;code dir=&quot;auto&quot;&gt;materialize_snapshot&lt;/code&gt;, read-only). The drain commit of D-9 removes the coordination branch’s copy. The target’s &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; is still written by consolidation’s own bookkeeping, as today.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(b) The service recomputes it in the same commit.&lt;/strong&gt; The Java reducer must then produce &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; byte for byte as the Python &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt; does: a new fixture family and a second derived-file writer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(c) The CLI keeps writing it.&lt;/strong&gt; Rejected: a second writer on the ref (D-3 (c)).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Recommendation: (a).&lt;/strong&gt; It keeps events ADR-0007’s commit at “only the event log path changed”, adds no byte-parity surface, and fits the S10 late window as written: a change to &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; between the window base and the tip is judged &lt;strong&gt;derived&lt;/strong&gt; while the target’s committed snapshot is the reduction of its committed log (&lt;a href=&quot;/adr/3.x/2026-09-19-1-terminus-safety-invariant/&quot;&gt;ADR 2026-09-19-1&lt;/a&gt; Amendment 2026-11-06, on PR #7274), so the drain commit’s removal is not refused.&lt;/p&gt;
&lt;h3 id=&quot;d-5-the-read-contract-is-read-the-ref-derived&quot;&gt;D-5: the read contract is “read the ref” &lt;em&gt;(derived)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;Readers of a coordination Mission read &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;&lt;/code&gt;, never a coordination working tree. The contract is &lt;a href=&quot;/adr/4.x/2026-11-06-2-one-status-read-contract/&quot;&gt;ADR 2026-11-06-2&lt;/a&gt; (the &lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt; source, the ref reader’s &lt;code dir=&quot;auto&quot;&gt;ABSENT&lt;/code&gt; versus &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceRefUnreadable&lt;/code&gt; split, &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; unchanged). At step 4a its &lt;code dir=&quot;auto&quot;&gt;COORD_WORKTREE&lt;/code&gt; row retires: a coordination Mission is always in the “unmaterialized” state, which reads the ref. How a missing ref is answered, and the parity of that answer with the Java read service, is C-3’s D-3.&lt;/p&gt;
&lt;h3 id=&quot;d-6-the-events-side-contract-this-record-relies-on-cites-events-adr-0007-d-7&quot;&gt;D-6: the events-side contract this record relies on &lt;em&gt;(cites events ADR-0007 D-7)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;mission-write&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;1.0.1-SNAPSHOT&lt;/code&gt; (the operator ruled on 2026-11-06 that &lt;code dir=&quot;auto&quot;&gt;1.0.0-SNAPSHOT&lt;/code&gt;, shipped in &lt;code dir=&quot;auto&quot;&gt;service-v0.1.0-rc.1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;rc.2&lt;/code&gt;, is not rewritten):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;WriteSurface&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;coordination_transaction_append&lt;/code&gt; is &lt;strong&gt;replaced&lt;/strong&gt; by &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;checkout_append&lt;/code&gt; &lt;strong&gt;narrows&lt;/strong&gt; to the repository root checkout only (a lane checkout is never a status surface).&lt;/li&gt;
&lt;li&gt;New refusal codes, provisional while ADR-0007 is Proposed: &lt;code dir=&quot;auto&quot;&gt;COORDINATION_REF_MOVED&lt;/code&gt; (409), &lt;code dir=&quot;auto&quot;&gt;COORDINATION_REF_CHECKED_OUT&lt;/code&gt; (409), &lt;code dir=&quot;auto&quot;&gt;COORDINATION_LEDGER_UNREADABLE&lt;/code&gt; (500).&lt;/li&gt;
&lt;li&gt;Removed protocol codes: the five of the Context table.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;RequestContext&lt;/code&gt;: for &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;missionDirectory&lt;/code&gt; is the path in the tree of &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; is required (D-7).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Core’s client (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/write_service_protocol.py&lt;/code&gt;, a core file per &lt;a href=&quot;/adr/4.x/2026-10-29-1-the-events-domain-and-its-java-services-live-in-spec-kitty-events/&quot;&gt;ADR 2026-10-29-1&lt;/a&gt; D-7) follows: its &lt;code dir=&quot;auto&quot;&gt;WriteSurface&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;WriteRefusalCode&lt;/code&gt; enums and &lt;code dir=&quot;auto&quot;&gt;_SURFACE_BY_TARGET&lt;/code&gt; take the new values when core vendors a service pin that serves &lt;code dir=&quot;auto&quot;&gt;1.0.1&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;d-7-destinationref-becomes-required-for-the-coordination-surface-derived-amends-adr-2026-10-27-1-d-3&quot;&gt;D-7: &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; becomes required for the coordination surface &lt;em&gt;(derived; amends ADR 2026-10-27-1 D-3)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;ADR 2026-10-27-1 D-3 keeps &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; null “until placement moves into the service”. For &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt; it is &lt;strong&gt;required and non-empty&lt;/strong&gt;, from the first release that serves the surface:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;transition_unit_from&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;status/write_service_protocol.py&lt;/code&gt;) sets &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; to the Mission’s coordination branch, read from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt;, and sets &lt;code dir=&quot;auto&quot;&gt;missionDirectory&lt;/code&gt; to the &lt;strong&gt;tree-relative&lt;/strong&gt; path (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission-dir&gt;&lt;/code&gt;), not a path relative to a checkout.&lt;/li&gt;
&lt;li&gt;The service resolves the coordination branch itself and refuses a request whose &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; differs with &lt;code dir=&quot;auto&quot;&gt;WRITE_LOCATION_UNVERIFIED&lt;/code&gt; (events ADR-0007 D-4).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;checkout_append&lt;/code&gt; keeps D-3’s null &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; until its own placement moves into the service.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;d-8-the-cli-side-codes-retire-with-the-worktree-at-step-4a-not-now-derived&quot;&gt;D-8: the CLI-side codes retire with the worktree, at step 4a, not now &lt;em&gt;(derived)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_UNREADABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_WORKTREE_MISSING&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;FALLBACK_COORD_WORKTREE_UNRESOLVED&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt; retire &lt;strong&gt;in the release that ships step 4a&lt;/strong&gt;, with the worktree they describe. Until then they stay live: they guard the worktree that still exists. With no working tree, divergence cannot occur and there is nothing to materialize. A use of &lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_WORKTREE_MISSING&lt;/code&gt; outside a coordination topology, if any remains at step 4a, is audited then and keeps its own meaning only if it does not name a coordination worktree. The &lt;code dir=&quot;auto&quot;&gt;status_surface_guard&lt;/code&gt; module and its tests retire with them.&lt;/p&gt;
&lt;h3 id=&quot;d-9-existing-coordination-worktrees-are-drained-then-removed-under-the-destructive-guard-derived&quot;&gt;D-9: existing coordination worktrees are drained, then removed under the destructive guard &lt;em&gt;(derived)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;A one-way, clone-local upgrade migration (&lt;code dir=&quot;auto&quot;&gt;clone_local_effect = True&lt;/code&gt;: worktrees live outside version control; its &lt;code dir=&quot;auto&quot;&gt;apply()&lt;/code&gt; is idempotent), shipped in the step-4a release, visits every coordination worktree of the clone:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Mid-operation refuses.&lt;/strong&gt; A worktree with &lt;code dir=&quot;auto&quot;&gt;MERGE_HEAD&lt;/code&gt;, a rebase, a cherry-pick or a bisect in progress is kept and reported; nothing is changed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Drain.&lt;/strong&gt; The worktree’s log must hold every event its &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; committed (the guard’s own check, run one last time). Uncommitted rows the worktree holds beyond &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; are committed onto the coordination branch by the migration itself: a plain git commit, in that worktree, of the bytes already in its log file. The migration appends, reorders and rewrites no row; it is not an event writer and not a Python fallback writer under ADR 2026-10-22-1 D-5, which is why it can ship in the release that deletes the Python appenders (D-10). Any other uncommitted or untracked path that is not residue refuses, and the worktree is kept and reported with the path list. “Drained” means clean and committed, or refused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Seed.&lt;/strong&gt; A Mission in WP01’s pre-seed state (the coordination branch exists, its log path is absent, the write checkout holds rows) gets those rows committed onto the coordination branch, so that from step 4a a readable ref without the path means “no events” (C-3 D-3).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remove.&lt;/strong&gt; The worktree is removed through &lt;code dir=&quot;auto&quot;&gt;git/destructive_guard.py&lt;/code&gt; under the obligations of ADR 2026-11-06-1 that apply to a worktree removal: O1, O2, O4 (with O6), O5, O7 and O8. Only O3 does not arise, because the coordination &lt;strong&gt;branch is never deleted&lt;/strong&gt; by this migration. O4 applies although the branch survives: removing the worktree drops its &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; reflog, so a commit that only that reflog reaches (an amended, reset or abandoned-rebase commit) is recorded under &lt;code dir=&quot;auto&quot;&gt;refs/spec-kitty/discarded/reflog/&lt;/code&gt; before the removal, or the worktree is kept and reported. “Probe unavailable means keep and report” applies (O2), as it does for lane cleanup.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Report.&lt;/strong&gt; A kept worktree is reported with its code, remedy and command. Until it is resolved, that Mission’s status writes refuse with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_REF_CHECKED_OUT&lt;/code&gt;, which is the honest answer: the branch is still checked out.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;d-10-rollout-ordering-steps-4-and-4a-ship-together-derived-from-events-adr-0007s-precondition-this-record-owns-the-ordering&quot;&gt;D-10: rollout ordering: steps 4 and 4a ship together &lt;em&gt;(derived from events ADR-0007’s precondition; this record owns the ordering)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt; goes live &lt;strong&gt;only in the same release&lt;/strong&gt; as both:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;this record’s artefact rule (D-3: notes, trace, issue matrix, decisions, byproducts; #7266), and&lt;/li&gt;
&lt;li&gt;the drain and removal of existing coordination worktrees (D-9).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;That is, migration steps 4 and 4a of ADR 2026-10-22-1 land in one release. Otherwise, from step 4 on, the CLI has no coordination status writer (ADR 2026-10-22-1 D-5: no Python fallback writer; step 4 deletes the Python appenders), and every existing coordination Mission is refused with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_REF_CHECKED_OUT&lt;/code&gt; on every transition, because its worktree still checks the branch out (events ADR-0007 D-3).&lt;/p&gt;
&lt;h3 id=&quot;d-11-what-stays-open-open&quot;&gt;D-11: what stays open &lt;em&gt;(open)&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Whether &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; needs a rule of its own beyond &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; (default: none; both read and write the coordination ref alike).&lt;/li&gt;
&lt;li&gt;The owned-checkout (&lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;) interplay: an owned checkout of a coordination Mission is a checkout, not a status surface (default: it follows D-5 for reads and never holds the coordination branch).&lt;/li&gt;
&lt;li&gt;The artefact rule (D-3) and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; (D-4), as above.&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;The five worktree failure codes disappear by construction, with their guard.&lt;/li&gt;
&lt;li&gt;A unit of work is atomic on the ref: the branch moves to a commit holding all its rows (and, under D-3 (a), its artefacts), or it does not move.&lt;/li&gt;
&lt;li&gt;Every reader and writer of a coordination Mission sees one copy: the committed tree.&lt;/li&gt;
&lt;li&gt;No coordination worktree to create, materialize, resync, reset or tear down (C-2 lists what consolidation loses).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;No repository hook runs on a status commit (events ADR-0007 runs with an emptied &lt;code dir=&quot;auto&quot;&gt;core.hooksPath&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The step-4 release is larger: steps 4 and 4a, the artefact rule and a migration ship together (D-10).&lt;/li&gt;
&lt;li&gt;A coordination worktree the migration has to keep blocks that Mission’s status writes until the operator resolves it (D-9 step 5).&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;: from step 4a, settlement no longer materializes a coordination worktree; it records the designation only. Its move of the repository root checkout off the topic branch stays needed, now because the service refuses to write a checked-out coordination branch.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The coordination branch, its name, its role at consolidation and its retention are unchanged (&lt;a href=&quot;/adr/4.x/2026-10-13-2-the-event-ledger-is-the-publication-seam-default-on-with-local-retention/&quot;&gt;ADR 2026-10-13-2&lt;/a&gt; D-3; C-3 D-5).&lt;/li&gt;
&lt;li&gt;&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 keep &lt;code dir=&quot;auto&quot;&gt;checkout_append&lt;/code&gt; in the repository root checkout.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;confirmation&quot;&gt;Confirmation&lt;/h3&gt;
&lt;p&gt;Named here, &lt;strong&gt;to be written by the step-4 Mission&lt;/strong&gt;; none exists yet:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/coordination/test_coordination_ref_commit_kinds.py&lt;/code&gt;: every coordination-partition kind of D-3 is written with no coordination worktree on disk, and the commit’s parent is the prior tip.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_write_service_protocol_coordination_ref_commit.py&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;transition_unit_from&lt;/code&gt; sets a non-empty &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; and a tree-relative &lt;code dir=&quot;auto&quot;&gt;missionDirectory&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt;, and keeps &lt;code dir=&quot;auto&quot;&gt;destinationRef&lt;/code&gt; null for &lt;code dir=&quot;auto&quot;&gt;checkout_append&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/upgrade/test_coordination_worktree_drain_migration.py&lt;/code&gt;: a clean worktree is drained and removed; uncommitted rows are committed first; a dirty non-residue path, a mid-operation worktree and an unavailable process probe each keep and report; a reflog-only commit in the worktree is recorded under &lt;code dir=&quot;auto&quot;&gt;refs/spec-kitty/discarded/reflog/&lt;/code&gt; before removal (O4, O6); the branch survives; a second run is a no-op; a pre-seed Mission’s rows are seeded onto the ref.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_coordination_worktree_retired.py&lt;/code&gt;: no code path creates a coordination worktree, and the five retired codes of D-8 appear nowhere in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; (planted-violation self-test).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_coordination_ref_commit_rollout.py&lt;/code&gt;: the release that serves &lt;code dir=&quot;auto&quot;&gt;coordination_ref_commit&lt;/code&gt; registers the D-9 migration in the order manifest (D-10).&lt;/li&gt;
&lt;li&gt;The events-side tests of events ADR-0007’s Confirmation (&lt;code dir=&quot;auto&quot;&gt;command-cli&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;).&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;1-written-by-commit-through-the-service-chosen&quot;&gt;1. Written by commit through the service (chosen)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: one copy, one writer, atomic units, lost updates detected; the worktree’s failure modes disappear.&lt;/li&gt;
&lt;li&gt;Bad: no hooks on status commits; a larger step-4 release; a migration with a destructive step.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;2-a-coordination-worktree-owned-by-the-service&quot;&gt;2. A coordination worktree owned by the service&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: closest to today’s code.&lt;/li&gt;
&lt;li&gt;Bad: keeps the second copy and every failure mode the rulings retire; the service would own a checkout’s lifecycle.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;3-retire-the-coordination-branch&quot;&gt;3. Retire the coordination branch&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: no coordination ref to fence.&lt;/li&gt;
&lt;li&gt;Bad: contradicts ruling 2; puts in-flight lifecycle on the target, where a protected target refuses it (&lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt;).&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;Mission discovery map: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/lane-worktree-model-hardening-01M6QY1M/upstream/doctrine-and-write-service-adr-map.md&lt;/code&gt; (Part 2).&lt;/li&gt;
&lt;li&gt;Mission research R-10 (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/lane-worktree-model-hardening-01M6QY1M/research.md&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The events records: &lt;code dir=&quot;auto&quot;&gt;docs/adr/0007-write-service-commits-coordination-status-by-ref.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;docs/adr/0008-read-service-reads-coordination-ledger-from-git-objects.md&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty-events&lt;/code&gt;, branch &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; (merged from &lt;code dir=&quot;auto&quot;&gt;issue-7284-coordination-ref-write-adrs&lt;/code&gt;), PR &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty-events/pull/215&quot;&gt;#215&lt;/a&gt;; the contract change is &lt;code dir=&quot;auto&quot;&gt;contracts/mission-write/CHANGELOG.md&lt;/code&gt; there.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
