<?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-6-committed-ledger-is-the-coordination-blob/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-11-06-6-committed-ledger-is-the-coordination-blob/</id>
  <title>ADR: the committed ledger of a coordination Mission is the blob on its coordination branch</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-6-committed-ledger-is-the-coordination-blob/"/>
  <summary>Proposed: for coordination Missions the publication seam and the read API pull read the event log blob at the coordination ref; events tail cursors name their commit.</summary>
  <content type="html">&lt;h2 id=&quot;the-committed-ledger-of-a-coordination-mission-is-the-blob-on-its-coordination-branch&quot;&gt;The committed ledger of a coordination Mission is the blob on its coordination branch&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.&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). Ruling 4 of epic #7276 is DM &lt;code dir=&quot;auto&quot;&gt;01M6QY371KRY5XXQMDQ4WZR1YE&lt;/code&gt; in Mission &lt;code dir=&quot;auto&quot;&gt;lane-worktree-model-hardening-01M6QY1M&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), epic &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7276&quot;&gt;#7276&lt;/a&gt;. ADRs only; the implementation follows migration step 4 (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/6117&quot;&gt;#6117&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Discharges&lt;/strong&gt; the D-6 bullet 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; on the publication seam (mapping in that record’s Amendment 2026-11-06).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Amends&lt;/strong&gt; &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-2 (the ledger is the publication seam) for coordination Missions, and &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; D-3 and D-6 (the read API composes existing read models; it is a pull over the committed ledger).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Related records of the same set:&lt;/strong&gt; &lt;strong&gt;C-1&lt;/strong&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;, &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;, &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 &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;), PR &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-0008 decides how the Java read service reads the blob; this record decides what the committed ledger is and what the CLI’s cursor names.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read contract:&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).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer of &lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail&lt;/code&gt;, the Mission Status Read API, or a subscriber such as &lt;code dir=&quot;auto&quot;&gt;spec-kitty/event-router&lt;/code&gt;.&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;ADR 2026-10-13-2 D-2 makes the ledger the publication seam: a subscriber learns about events by reading the committed &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, through &lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;status/tail_reader.py::TailCursor&lt;/code&gt;) or the Mission Status Read API (ADR 2026-10-01-2), never by being called. Both read a file at a path.&lt;/p&gt;
&lt;p&gt;From C-1’s step 4a, a coordination Mission has no coordination worktree: the committed tree of &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;&lt;/code&gt; is the only copy of its ledger. A reader that reads a path would read nothing or a stale husk. Two further facts follow:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;TailCursor(offset, content_invariant)&lt;/code&gt; is a byte offset into one file. A cursor taken on the coordination branch’s blob does not carry over to the target’s blob after consolidation, because the union at projection may reorder or deduplicate lines (ADR 2026-02-09-3), and its &lt;code dir=&quot;auto&quot;&gt;ResumeRefused&lt;/code&gt; reasons (&lt;code dir=&quot;auto&quot;&gt;negative&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;out_of_range&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;misaligned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;content_mismatch&lt;/code&gt;) cannot say why.&lt;/li&gt;
&lt;li&gt;Today’s read oracle answers an unmaterialized coordination Mission by falling back to the primary directory (&lt;code dir=&quot;auto&quot;&gt;probe_coord_state&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;UNMATERIALIZED&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/_read_path_resolver.py&lt;/code&gt;). Events ADR-0008 D-1 makes the Java read service follow whatever the oracle answers; the two must agree when the ref is missing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;One committed ledger for every consumer: the writer’s commit (ruling 8).&lt;/li&gt;
&lt;li&gt;The read API’s guarantees (ADR 2026-10-01-2 D-6): read-only, no lock, independent of drain.&lt;/li&gt;
&lt;li&gt;Python and Java answer the same Mission the same way (ADR 2026-10-29-1 D-6, D-7).&lt;/li&gt;
&lt;li&gt;A cursor never silently skips or repeats events.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;p&gt;For the cursor (D-4), the open choice of this record:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;The cursor names the commit it was taken at&lt;/strong&gt; (recommended).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The cursor names the blob it was taken in.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No change&lt;/strong&gt;: the offset and content invariant only.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;decision-outcome&quot;&gt;Decision Outcome&lt;/h2&gt;
&lt;p&gt;Each decision is marked &lt;em&gt;(derived)&lt;/em&gt; or &lt;em&gt;(open)&lt;/em&gt;; open choices carry a recommendation (Mission assumption A-12).&lt;/p&gt;
&lt;h3 id=&quot;d-1-the-publication-seam-of-a-coordination-mission-is-the-blob-at-its-ref-derived-amends-adr-2026-10-13-2-d-2&quot;&gt;D-1: the publication seam of a coordination Mission is the blob at its ref &lt;em&gt;(derived; amends ADR 2026-10-13-2 D-2)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;For a coordination topology (&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;), the committed ledger is the &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; blob at &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;&lt;/code&gt;, at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission-dir&gt;/status.events.jsonl&lt;/code&gt;. After consolidation it is the target’s committed copy. “Committed” means reachable from that ref, never a working-tree file. For &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, D-2 of ADR 2026-10-13-2 is unchanged. No new read path, toggle or daemon is added; publication stays on by default.&lt;/p&gt;
&lt;h3 id=&quot;d-2-the-read-apis-pull-reads-git-objects-for-coordination-missions-derived-amends-adr-2026-10-01-2-d-3-d-6&quot;&gt;D-2: the read API’s pull reads git objects for coordination Missions &lt;em&gt;(derived; amends ADR 2026-10-01-2 D-3, D-6)&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The read API’s pull, for a coordination Mission, reads the blob of D-1. It stays read-only, takes no lock and is independent of drain (D-6 unchanged in meaning).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Python side:&lt;/strong&gt; every read goes through the one read door of ADR 2026-11-06-2, whose &lt;code dir=&quot;auto&quot;&gt;COORD_BRANCH_REF&lt;/code&gt; source reads the ref with &lt;code dir=&quot;auto&quot;&gt;git cat-file --batch&lt;/code&gt; (one batched subprocess per Mission per command). The door replaces D-3’s “&lt;code dir=&quot;auto&quot;&gt;_read_path_resolver&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;MissionStatus.load&lt;/code&gt; path” as the coordination-aware read surface; the read models D-3 composes (&lt;code dir=&quot;auto&quot;&gt;materialize_snapshot&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reconstruct_wp_view&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TailCursor&lt;/code&gt;) take their bytes from it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Java side:&lt;/strong&gt; events ADR-0008 (an in-process git-object adapter of &lt;code dir=&quot;auto&quot;&gt;MissionEventSource&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;ReadDirResolver&lt;/code&gt;’s coordination case reads the ref).&lt;/li&gt;
&lt;li&gt;One read pins one tip: every coordination-branch file of one answer comes from the same commit.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;d-3-a-missing-ref-is-a-typed-error-in-both-languages-derived-oracle-fallback-parity&quot;&gt;D-3: a missing ref is a typed error, in both languages &lt;em&gt;(derived; oracle fallback parity)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;The oracle’s fallback changes so that Java and Python agree on a missing ref (events ADR-0008 D-1). It follows ADR 2026-11-06-2’s read contract:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Unmaterialized&lt;/strong&gt; (the branch exists, no worktree; from step 4a, every coordination Mission): read the ref, never the primary directory.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Missing ref:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; when the probe classifies the declared branch as deleted; &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;) for an unreadable ref, a missing object or a git failure. Never a primary-directory read.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Readable ref, absent path:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;ABSENT&lt;/code&gt;, an empty history.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The pre-seed fallback&lt;/strong&gt; of ADR 2026-11-06-2 (branch exists, no log yet, the write checkout read with &lt;code dir=&quot;auto&quot;&gt;fallback_reason&lt;/code&gt; stamped) is open:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;(a) keep it in both languages&lt;/strong&gt; (the Java service already reads &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; from the primary directory, so it could read the write checkout’s log too);&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;(b) retire it at step 4a&lt;/strong&gt;: C-1 D-9 seeds the coordination branch from the write checkout during the drain, and from step 4a the service’s first coordination write creates the path (events ADR-0007 D-1, &lt;code dir=&quot;auto&quot;&gt;update-index --add&lt;/code&gt;), so a readable ref without the path truly means “no events”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recommendation: (b).&lt;/strong&gt; It leaves Java with one rule and no working-tree read; until step 4a the Python door keeps the declared fallback and &lt;code dir=&quot;auto&quot;&gt;ReadDirResolver&lt;/code&gt; is unchanged (events ADR-0008 D-1, “until migration step 4”).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conformance:&lt;/strong&gt; the corpus compares only shapes both sides read the same way. The unmaterialized-coordination cell joins the comparison when ADR-0008’s adapter ships, with the no-worktree fixture of ADR-0008 D-3.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;d-4-the-events-tail-cursor-names-its-source-open-recommendation-option-1&quot;&gt;D-4: the &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; cursor names its source &lt;em&gt;(open; recommendation: option 1)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Option 1, the commit (recommended):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;TailCursor(offset, content_invariant, source_ref, commit)&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;source_ref&lt;/code&gt; is the ref the blob was read from (&lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;coord&gt;&lt;/code&gt;, or the target after consolidation); &lt;code dir=&quot;auto&quot;&gt;commit&lt;/code&gt; is the commit it was read at.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resume on the same ref:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;commit&lt;/code&gt; is an ancestor of the ref’s current tip and the blob at &lt;code dir=&quot;auto&quot;&gt;commit&lt;/code&gt; is a byte prefix of the current blob (the existing content invariant), resume by offset. A coordination log only grows by append (events ADR-0007 D-2), so this is the normal case.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resume after the source moved&lt;/strong&gt; (the coordination branch was consolidated onto the target and deleted, or the prefix no longer holds): refuse with a new &lt;code dir=&quot;auto&quot;&gt;ResumeRefused&lt;/code&gt; reason, &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;source_moved&lt;/code&gt;&lt;/strong&gt;, naming the new source and the last event id the cursor had passed. The consumer resumes from that event id. The CLI does not remap offsets by event id itself.&lt;/li&gt;
&lt;li&gt;Polling is a cheap &lt;code dir=&quot;auto&quot;&gt;git rev-parse&lt;/code&gt; of &lt;code dir=&quot;auto&quot;&gt;source_ref&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A cursor with no source (taken before this change, or on a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission) keeps today’s meaning: an offset into the write checkout’s file.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Option 2, the blob id:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;TailCursor(offset, content_invariant, blob)&lt;/code&gt;. Considered: it detects that the bytes changed, which the content invariant already does, but cannot tell an append from a consolidation, and gives no ancestry to reason with.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Option 3, no change.&lt;/strong&gt; Rejected: after consolidation a coordination cursor is refused with &lt;code dir=&quot;auto&quot;&gt;content_mismatch&lt;/code&gt; or, worse, lands on a misaligned but valid line boundary of the reordered target log.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Remap by event id inside the CLI&lt;/strong&gt; (on &lt;code dir=&quot;auto&quot;&gt;source_moved&lt;/code&gt;) was considered and left out: it makes the CLI own a second ordering of the same events; the consumer already holds the event ids.&lt;/p&gt;
&lt;p&gt;The cursor change is consumer-visible (&lt;code dir=&quot;auto&quot;&gt;spec-kitty/event-router&lt;/code&gt;). If it is taken, the &lt;code dir=&quot;auto&quot;&gt;mission-status&lt;/code&gt; contract’s stream cursor changes before that contract’s &lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt; (events ADR-0008 D-4), and &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; documents the new reason.&lt;/p&gt;
&lt;h3 id=&quot;d-5-retention-is-unchanged-derived&quot;&gt;D-5: retention is unchanged &lt;em&gt;(derived)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;ADR 2026-10-13-2 D-3 stands: the coordination branch’s history is git’s to keep until consolidation, and the teardown’s branch delete is its only removal, under the destructive authority (ruling 7, &lt;code dir=&quot;auto&quot;&gt;git/destructive_guard.py&lt;/code&gt;; ADR 2026-11-06-1 on PR #7275).&lt;/p&gt;
&lt;h3 id=&quot;d-6-jgit-or-a-subprocess-open-not-ruled-here&quot;&gt;D-6: JGit or a subprocess &lt;em&gt;(open; not ruled here)&lt;/em&gt;&lt;/h3&gt;
&lt;p&gt;How each side reads git objects stays open in core (A-12). The options are an in-process reader (pinned JGit, or a minimal reader of loose objects, packs and refs), or a &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; subprocess (&lt;code dir=&quot;auto&quot;&gt;cat-file --batch&lt;/code&gt;). &lt;strong&gt;Recommendation:&lt;/strong&gt; core rules nothing for Java; it follows events ADR-0007 D-5 (a &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; subprocess for writes) and events ADR-0008 D-2 (in process for reads, with a named source fault for an unsupported ref backend). The Python CLI keeps its batched &lt;code dir=&quot;auto&quot;&gt;git cat-file --batch&lt;/code&gt; subprocess (Mission research R-12: no Python git library).&lt;/p&gt;
&lt;h3 id=&quot;d-7-what-stays-open-open&quot;&gt;D-7: what stays open &lt;em&gt;(open)&lt;/em&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Whether the read API’s overview cursor becomes a commit id (default: it follows D-4 if option 1 is taken).&lt;/li&gt;
&lt;li&gt;Whether &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; polls the ref or watches the reflog (default: polls, &lt;code dir=&quot;auto&quot;&gt;rev-parse&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The pre-seed fallback (D-3) and the cursor (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;Every consumer reads exactly what the writer committed; the husk ambiguity of a stale coordination directory disappears.&lt;/li&gt;
&lt;li&gt;Java and Python give the same answer for a missing coordination ref.&lt;/li&gt;
&lt;li&gt;A consumer can tell an append from a consolidation, and is never resumed into a reordered log.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;A new &lt;code dir=&quot;auto&quot;&gt;ResumeRefused&lt;/code&gt; reason and a cursor shape change, visible to consumers.&lt;/li&gt;
&lt;li&gt;The read path of a coordination Mission costs a git subprocess on the Python side.&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;single_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Missions read as today.&lt;/li&gt;
&lt;li&gt;Retention, drain and the produce seam (&lt;code dir=&quot;auto&quot;&gt;status/adapters.py&lt;/code&gt;) are unchanged.&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; (the Java side by its own Confirmation in events ADR-0008):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_events_tail_coordination_ref.py&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; on a coordination Mission with no coordination worktree reads the blob at the ref and emits every committed event once.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_tail_cursor_source_ref.py&lt;/code&gt;: a cursor resumes by offset after appends on the same ref; after consolidation and branch deletion it refuses with &lt;code dir=&quot;auto&quot;&gt;source_moved&lt;/code&gt;, naming the target and the last event id; a sourceless cursor keeps today’s behaviour.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/status/test_read_door_missing_ref_parity.py&lt;/code&gt;: a deleted coordination branch raises &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;, an unreadable ref raises &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceRefUnreadable&lt;/code&gt;, an absent path reads empty, and no case reads the primary directory.&lt;/li&gt;
&lt;li&gt;The no-worktree corpus fixture of events ADR-0008 D-3, compared against the Python oracle.&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-the-cursor-names-the-commit-recommended&quot;&gt;1. The cursor names the commit (recommended)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: ancestry tells append from consolidation; cheap polling; exact snapshot re-read.&lt;/li&gt;
&lt;li&gt;Bad: a cursor shape change and a new refusal reason.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;2-the-cursor-names-the-blob&quot;&gt;2. The cursor names the blob&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: a smaller change.&lt;/li&gt;
&lt;li&gt;Bad: duplicates the content invariant; no way to tell why the bytes changed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;3-no-change&quot;&gt;3. No change&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Good: nothing to build.&lt;/li&gt;
&lt;li&gt;Bad: wrong or confusing answers after every consolidation of a coordination Mission.&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, C-3; risk 9).&lt;/li&gt;
&lt;li&gt;Current cursor: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/tail_reader.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;TailCursor&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ResumeRefused&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
