<?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-3-topology-is-settled-once-at-first-finalize/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-11-06-3-topology-is-settled-once-at-first-finalize/</id>
  <title>ADR: a default Mission topology is settled once, by size, at the first finalize</title>
  <updated>2026-11-13T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/4.x/2026-11-06-3-topology-is-settled-once-at-first-finalize/"/>
  <summary>Create without --topology mints one topic branch; the first finalize-tasks settles single_branch or lanes_with_coord by size, once, and only then materializes it.</summary>
  <content type="html">&lt;h2 id=&quot;a-default-mission-topology-is-settled-once-by-size-at-the-first-finalize&quot;&gt;A default Mission topology is settled once, by size, at the first finalize&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.&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;).&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/7282&quot;&gt;#7282&lt;/a&gt; (S7): small Missions stay small; the topology is chosen once, at finalize. Epic &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7276&quot;&gt;#7276&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Supersedes&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5100&quot;&gt;#5100&lt;/a&gt; item 2, the “explicit-only topology” decision (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5100#issuecomment-5870360497&quot;&gt;issue comment 5870360497&lt;/a&gt;). No ADR file held that decision; this record replaces it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Amends&lt;/strong&gt; &lt;a href=&quot;/adr/3.x/2026-06-22-1-mission-topology-ssot/&quot;&gt;ADR 2026-06-22-1&lt;/a&gt; Decision 2 (“stored at create, read thereafter”), by an appended amendment on that file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Depends on&lt;/strong&gt; the S8 bound (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7283&quot;&gt;#7283&lt;/a&gt;), recorded as the 2026-11-06 amendment of &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;ADR 2026-10-04-5&lt;/a&gt;. Constraint C-010: S8 ships before or with this decision.&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) carries the reads that this record’s placement rule changes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer who needs to know why &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; mints only a branch, when and how &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; turns that into &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;, and where a default Mission’s planning artifacts live meanwhile.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Terms.&lt;/strong&gt; “PRIMARY partition” is the artifact partition (spec, plan, 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;; &lt;code dir=&quot;auto&quot;&gt;_PRIMARY_ARTIFACT_KINDS&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py&lt;/code&gt;), never the primary branch; “repository root checkout” is the main working tree; “target branch” is the branch the Mission lands on at &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;. “Lane consolidation” is the landing of lane branches into the Mission or coordination branch; the landing on the target is named as such. See &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;.&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;Today &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; chooses the topology before any work package exists. On a protected target it mints a coordination branch and its worktree, so a Mission that later turns out to be two work packages carries a coordination topology it never needed. The Mission tracer files record operators hand-removing those scaffolds after &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; chose a coordination topology on a protected branch.&lt;/p&gt;
&lt;p&gt;The transitions are not symmetric. Shrinking a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; or coordination topology into &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; needs a worktree removal and a branch hand-over; growing from one topic branch needs neither a projection nor a deletion. The operator’s rationale (ruling 1 and the S7 escalation answer, DM &lt;code dir=&quot;auto&quot;&gt;01M6QY2SJ9ND1SKMH2230FS7JA&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;01M6QY46RJGFZN6WBVQQXCZSY6&lt;/code&gt;): build nothing that may have to be torn down, and decide the shape when the work packages are known.&lt;/p&gt;
&lt;p&gt;#5100 item 2 made the topology explicit-only; ADR 2026-06-22-1 Decision 2 stores it at create and reads it thereafter. Both have to change for a size-based default to be decided at finalize, and the change has to stay a stored, read-once value, not a re-inference.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Build nothing that might be torn down: a Mission is created with the least structure that can carry its planning work.&lt;/li&gt;
&lt;li&gt;One stored topology value (ADR 2026-06-22-1): settlement writes it once; nothing re-infers it from disk.&lt;/li&gt;
&lt;li&gt;No WP is ever re-homed: the topology is fixed before any WP is claimed.&lt;/li&gt;
&lt;li&gt;A failed settlement costs nothing (NFR-003): &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, branch tips and the repository root checkout come back byte for byte.&lt;/li&gt;
&lt;li&gt;No planning artifact reaches the target before &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;No user-reachable size default without the S8 bound (C-010), because the default sends most small Missions to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;.&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;Deferred materialization: one topic branch at create, settled by size at the first finalize, one settlement path on every target&lt;/strong&gt; (chosen).&lt;/li&gt;
&lt;li&gt;Keep &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; as the provisional default and re-stamp it to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; at finalize.&lt;/li&gt;
&lt;li&gt;Store a new &lt;code dir=&quot;auto&quot;&gt;topology: provisional&lt;/code&gt; enum value.&lt;/li&gt;
&lt;li&gt;Write pre-settlement artifacts by commit, with no checkout.&lt;/li&gt;
&lt;li&gt;Keep the write checkout on the topic branch for a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission’s whole life.&lt;/li&gt;
&lt;li&gt;On an unprotected target, land the topic branch’s planning commits on the target at settlement (fast-forward, else a git merge commit) and settle to plain &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;.&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:&lt;/strong&gt; Option 1, because it builds only what the settled size needs, keeps one stored topology value, and has one settlement path that never lands anything on the target.&lt;/p&gt;
&lt;h3 id=&quot;decision-1-create-without---topology-mints-one-topic-branch-and-nothing-else&quot;&gt;Decision 1: create without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; mints one topic branch and nothing else&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; mints exactly one Mission topic branch, &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; (assumption A-1), whatever the target’s protection. It creates no lane, no lane or coordination worktree, and no coordination branch (FR-051).&lt;/li&gt;
&lt;li&gt;The topic branch name is the existing Mission and coordination branch grammar (&lt;code dir=&quot;auto&quot;&gt;mission_branch_name&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;coordination_branch_name&lt;/code&gt;). Settlement assigns it a role; it never renames or re-mints it.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--topology &amp;#x3C;X&gt;&lt;/code&gt; records &lt;code dir=&quot;auto&quot;&gt;topology_source: explicit&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; records &lt;code dir=&quot;auto&quot;&gt;topology_source: owned_checkout&lt;/code&gt;. Both are settled at create and materialize exactly as today (FR-052). An explicit topology always wins, at create and at finalize.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;decision-2-the-size-rule&quot;&gt;Decision 2: the size rule&lt;/h3&gt;
&lt;p&gt;At the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, a provisional Mission settles to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/strong&gt; when it has at most 2 non-canceled WPs, or at most 1 code lane. Planning-artifact WPs count toward the WP count; canceled WPs do not. &lt;code dir=&quot;auto&quot;&gt;lane-planning&lt;/code&gt; is not a code lane; 0 code lanes settles to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; (A-6).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/strong&gt; otherwise, on &lt;strong&gt;every&lt;/strong&gt; target, protected or not, with the topic branch as the coordination branch under the same name (A-3; DM &lt;code dir=&quot;auto&quot;&gt;01M6QZ02HDACM7A0VNYSAQ8MQB&lt;/code&gt; for protected targets, extended to every target by DM &lt;code dir=&quot;auto&quot;&gt;01M6R0B954ZPQN5NV4R1ZRE7NY&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A tie (exactly 2 WPs in 2 code lanes) settles to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;: the WP-count arm wins. Plain &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; (no coordination) and &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; (coordination, no lanes) are never default outcomes; both stay available through &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt;. The recorded rule names are &lt;code dir=&quot;auto&quot;&gt;wp_count_le_2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;code_lanes_le_1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Why &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; on every target: create no longer mints a coordination branch, and a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission whose status lives on a protected target is refused at &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; is a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; key (read through &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_KEY&lt;/code&gt; by about 32 readers) whose default name already uses the Mission branch grammar, and the reconstruct-from-slug paths (&lt;code dir=&quot;auto&quot;&gt;coordination/coord_seed.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination/workspace.py&lt;/code&gt;) yield the same name, so the topic branch can carry the coordination designation unchanged (corroborated 2026-11-06). One settlement path removes the protection-dependent arm and its landing step.&lt;/p&gt;
&lt;h3 id=&quot;decision-3-deferred-materialization&quot;&gt;Decision 3: deferred materialization&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Settlement writes the lane manifest (&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;). Lane branches and lane checkouts appear only through the existing implement-time allocation (A-7); nothing is pre-allocated at finalize.&lt;/li&gt;
&lt;li&gt;Lanes are cut from the topic branch. Lane consolidation lands into it. It lands on the target branch at &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, as for an explicit &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; Mission.&lt;/li&gt;
&lt;li&gt;Nothing lands on the target at settlement. There is no fast-forward or git merge step.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Settlement to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/strong&gt; has no git step: it writes &lt;code dir=&quot;auto&quot;&gt;topology_settled: true&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;topology_decision&lt;/code&gt;; the topic branch stays the Mission branch and stays checked out in the write checkout.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Settlement to &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;&lt;/strong&gt; is the one git-moving path:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Commit the Mission directory on the topic branch in the write checkout.&lt;/li&gt;
&lt;li&gt;Move the repository root checkout off the topic branch, back to &lt;code dir=&quot;auto&quot;&gt;create_return_branch&lt;/code&gt;. Git forbids one branch checked out in two worktrees, so this precedes step 4.&lt;/li&gt;
&lt;li&gt;Re-stamp &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; = the topic ref name, &lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt; kept (it now names the same ref), &lt;code dir=&quot;auto&quot;&gt;topology: lanes_with_coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;topology_settled: true&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;topology_decision&lt;/code&gt; written.&lt;/li&gt;
&lt;li&gt;Materialize and seed the coordination worktree on the topic branch through &lt;code dir=&quot;auto&quot;&gt;CoordinationWorkspace.resolve()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Write &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;decision-4-the-provisional-representation-and-topology_source&quot;&gt;Decision 4: the provisional representation and &lt;code dir=&quot;auto&quot;&gt;topology_source&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;A provisional Mission is stored as (DM &lt;code dir=&quot;auto&quot;&gt;01M6R0BDYC29D6XMDY72R22CP9&lt;/code&gt;):&lt;/p&gt;








































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; key&lt;/th&gt;&lt;th&gt;Provisional value&lt;/th&gt;&lt;th&gt;Notes&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;topology&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Reuses the minted &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; write path (&lt;code dir=&quot;auto&quot;&gt;single_branch_write_ref&lt;/code&gt;), so specify, plan and tasks land on the topic branch with no new placement code.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the topic branch&lt;/td&gt;&lt;td&gt;Kept at promotion to &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;topology_source&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt;&lt;/td&gt;&lt;td&gt;New, additive. &lt;code dir=&quot;auto&quot;&gt;explicit&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;owned_checkout&lt;/code&gt; for explicit creates. &lt;strong&gt;Absent means legacy, and legacy means settled&lt;/strong&gt; (FR-057).&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;topology_settled&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt;&lt;/td&gt;&lt;td&gt;New. Written only when &lt;code dir=&quot;auto&quot;&gt;topology_source == default&lt;/code&gt;; settlement sets &lt;code dir=&quot;auto&quot;&gt;true&lt;/code&gt;. Absent with &lt;code dir=&quot;auto&quot;&gt;topology_source == default&lt;/code&gt; is invalid and refuses.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;create_return_branch&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the branch the write checkout was on before create switched it&lt;/td&gt;&lt;td&gt;New. Read only by settlement to &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;; kept afterwards for audit, never read once settled.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;topology_decision&lt;/code&gt;&lt;/td&gt;&lt;td&gt;absent&lt;/td&gt;&lt;td&gt;Written once at settlement: &lt;code dir=&quot;auto&quot;&gt;{rule, wp_count, code_lane_count, from, to, target_protected, decided_at}&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;target_protected&lt;/code&gt; is informational. Write-once.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;create --json&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;topology: single_branch&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;topology_provisional: true&lt;/code&gt; until finalize; &lt;code dir=&quot;auto&quot;&gt;finalize-tasks --json&lt;/code&gt; reports the decision and &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; previews it without writing (FR-058). These fields reach &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; in one additive contract bump, 1.24.0 to 1.25.0 (main took 1.24.0 for #7210 meanwhile), together with the S5 cleanup report (DM &lt;code dir=&quot;auto&quot;&gt;01M6R0BJQ6Q1MV6492EH6HB66H&lt;/code&gt;); no release ships 1.25.0 without all of them.&lt;/p&gt;
&lt;h3 id=&quot;decision-5-the-primary-partition-of-a-default-mission-lives-on-the-topic-branch-until-consolidate&quot;&gt;Decision 5: the PRIMARY partition of a default Mission lives on the topic branch until &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;For &lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt;, the PRIMARY partition resolves to the Mission topic branch (&lt;code dir=&quot;auto&quot;&gt;meta.mission_branch&lt;/code&gt;, which after a multi-lane settlement is 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; (FR-061, DM &lt;code dir=&quot;auto&quot;&gt;01M6R0QJVPVZG2QT8MWQD4NXJR&lt;/code&gt;, which supersedes the mirror-an-explicit-create rule of DM &lt;code dir=&quot;auto&quot;&gt;01M6R0B3YX291STRVVQ0HQCJD5&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; stays the landing branch. Explicit &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; Missions keep today’s placement: the PRIMARY partition on &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One “landed” signal, owned by the placement seam.&lt;/strong&gt; Before the landing, the seam resolves a default Mission’s PRIMARY partition to &lt;code dir=&quot;auto&quot;&gt;meta.mission_branch&lt;/code&gt;; once &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; records that the topic branch has landed on the target, it resolves to &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; does not decide placement itself: after the landing it re-reads the seam (analysis H1).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Readers go through the seam or the read door.&lt;/strong&gt; Settlement moves the repository root checkout back to &lt;code dir=&quot;auto&quot;&gt;create_return_branch&lt;/code&gt;, so the root checkout does not show the planning files of a settled &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; default Mission. &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;check-prerequisites --paths-only&lt;/code&gt; return the PRIMARY-partition location from the resolver, never a fixed root path. The status read side is ADR 2026-11-06-2.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Landing.&lt;/strong&gt; The mission-to-target phase (&lt;code dir=&quot;auto&quot;&gt;_phase_mission_to_target&lt;/code&gt; through &lt;code dir=&quot;auto&quot;&gt;integrate_mission_into_target&lt;/code&gt;) already carries the topic branch’s tip. FR-062 covers the PRIMARY commits after the consolidation checkpoint that that landing does not carry; the default-Mission landing decision is its own predicate, and &lt;code dir=&quot;auto&quot;&gt;lands_mission_branch&lt;/code&gt; keeps its &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; meaning.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;decision-6-decided-once-before-any-wp-starts&quot;&gt;Decision 6: decided once, before any WP starts&lt;/h3&gt;
&lt;p&gt;The topology is settled only at the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, before finalize’s first status write and before any WP is claimed (FR-054, C-011). Re-finalize, the legacy &lt;code dir=&quot;auto&quot;&gt;tasks-finalize&lt;/code&gt; repair path and doctor rebuilds never re-decide. Growth after settlement keeps the settled topology. A finalize that finds any WP with a lifecycle event past &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;, or any recorded lane branch or worktree, does not settle; the topology stays.&lt;/p&gt;
&lt;h3 id=&quot;decision-7-settlement-is-compensated&quot;&gt;Decision 7: settlement is compensated&lt;/h3&gt;
&lt;p&gt;Settlement is a planned list of reversible steps executed in order, with an undo stack. Any failure restores &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; byte for byte, every branch tip, the absence of a coordination worktree, and the repository root checkout on the topic branch (FR-056, NFR-003; fault-injected at every git step). Preconditions, each a refusal with nothing changed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the write checkout is not occupied by another in-progress WP (&lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_OCCUPIED&lt;/code&gt;) and is clean (&lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY&lt;/code&gt;, #5676);&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create_return_branch&lt;/code&gt; exists and is not checked out in another worktree, the coordination worktree can be materialized, and no git step failed (&lt;code dir=&quot;auto&quot;&gt;TOPOLOGY_SETTLEMENT_REFUSED&lt;/code&gt;, new; its remedy names the branch).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;decision-8---pr-bound-and---commit-to-target&quot;&gt;Decision 8: &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--commit-to-target&lt;/code&gt;&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt; coordination-unreachable fallback to plain &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; is dropped for default Missions (A-5, DM &lt;code dir=&quot;auto&quot;&gt;01M6R0QQM5FCPY736008AD4W6V&lt;/code&gt;). Multi-lane settlement always yields &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;. The #2533 stranded-branch hazard the fallback guarded does not apply once the topic branch is the coordination branch.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--commit-to-target&lt;/code&gt; still requires an explicit &lt;code dir=&quot;auto&quot;&gt;--topology single_branch&lt;/code&gt; (FR-060). A provisional Mission never writes straight to its target.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;decision-9-s8-before-or-with-s7-c-010&quot;&gt;Decision 9: S8 before or with S7 (C-010)&lt;/h3&gt;
&lt;p&gt;No user-reachable settlement ships in a release without the per-WP approval windows of the ADR 2026-10-04-5 amendment of 2026-11-06. A default &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission always consolidates its minted topic branch (A-4), so every size-default &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission falls inside that bound; only an explicit &lt;code dir=&quot;auto&quot;&gt;--commit-to-target&lt;/code&gt; Mission stays in the unbounded residual.&lt;/p&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;A small Mission is created and finalized with one branch and no worktree; nothing is built only to be torn down.&lt;/li&gt;
&lt;li&gt;One settlement path for every target: no protection-dependent arm, no landing step at settlement, no conflict handling.&lt;/li&gt;
&lt;li&gt;The topology stays one stored value; settlement writes it once and records why (&lt;code dir=&quot;auto&quot;&gt;topology_decision&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Pre-settlement placement needs no new code: the provisional Mission uses the existing minted &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; write path.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;negative&quot;&gt;Negative&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Every size-default multi-lane Mission carries a coordination worktree, also on unprotected targets where it would have been &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; before. This is the accepted cost of one settlement path.&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; population grows, which is why C-010 ties this decision to the S8 bound.&lt;/li&gt;
&lt;li&gt;Every no-topology &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; moves the repository root checkout onto the topic branch until settlement. A second &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; run from there could record the first Mission’s topic branch as its target. Mitigation: target resolution never picks a branch recorded as another Mission’s &lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt;, and resolves the primary branch (the repository’s default branch) instead. A refusal instead would be a new code, to be raised in review.&lt;/li&gt;
&lt;li&gt;After a &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; settlement the repository root checkout no longer shows the planning files; any reader that reads a root-checkout path for a default Mission is wrong and must use the seam.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create_return_branch&lt;/code&gt; may be deleted or checked out elsewhere by settlement time; settlement then refuses until the operator restores it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;neutral&quot;&gt;Neutral&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Legacy Missions (no &lt;code dir=&quot;auto&quot;&gt;topology_source&lt;/code&gt;) are settled and never re-decided, so upgrading changes no in-flight Mission’s shape.&lt;/li&gt;
&lt;li&gt;Plain &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; remain available, explicitly.&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/specify_cli/cli/commands/agent/test_mission_create_provisional_topology.py&lt;/code&gt; (WP13): create without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; mints one branch and records the provisional keys; the explicit &lt;code dir=&quot;auto&quot;&gt;--topology coord&lt;/code&gt; control still creates its coordination branch.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/cli/commands/agent/test_finalize_topology_settlement.py&lt;/code&gt; (WP14): the size rule, the tie, canceled and planning-artifact WP counting, decide-once on re-finalize, legacy Missions untouched, &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/lanes/test_topology_settlement_compensation.py&lt;/code&gt; (WP14): fault injection at every git step leaves &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; byte-identical, branch tips unchanged and the root checkout on the topic branch.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/integration/test_default_mission_primary_placement.py&lt;/code&gt; (WP14): the PRIMARY partition of a default Mission resolves to the topic branch before and after settlement and to the target after &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;; the explicit control keeps &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/integration/test_default_mission_consolidate_lands_primary.py&lt;/code&gt; (WP20): &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; leaves no PRIMARY change of the topic branch off the target.&lt;/li&gt;
&lt;li&gt;The S8 confirmation tests are named in the ADR 2026-10-04-5 amendment of 2026-11-06.&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;option-1-deferred-materialization-one-settlement-path&quot;&gt;Option 1: deferred materialization, one settlement path&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; builds only what the size needs; growth only, never a shrink; one path on every target; reuses the minted &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; write path before settlement.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; a coordination worktree on every multi-lane default Mission; the root checkout move needs a recorded return branch and compensation.&lt;/p&gt;
&lt;h3 id=&quot;option-2-provisional-lanescoord-re-stamped-to-single_branch&quot;&gt;Option 2: provisional &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;, re-stamped to &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; no change at create.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; the most expensive transition (a worktree removal and a branch hand-over) becomes the common one. Rejected by the escalation ruling (DM &lt;code dir=&quot;auto&quot;&gt;01M6QY46RJGFZN6WBVQQXCZSY6&lt;/code&gt;).&lt;/p&gt;
&lt;h3 id=&quot;option-3-a-topology-provisional-enum-value&quot;&gt;Option 3: a &lt;code dir=&quot;auto&quot;&gt;topology: provisional&lt;/code&gt; enum value&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; the provisional state is explicit in the type.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; about 55 stored-topology readers would need a new arm; the &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; representation needs none. Rejected.&lt;/p&gt;
&lt;h3 id=&quot;option-4-pre-settlement-writes-by-commit-no-checkout&quot;&gt;Option 4: pre-settlement writes by commit, no checkout&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; the repository root checkout never moves.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; agents author spec, plan and tasks in a working tree. Rejected.&lt;/p&gt;
&lt;h3 id=&quot;option-5-the-write-checkout-holds-the-topic-branch-for-a-lanes-missions-life&quot;&gt;Option 5: the write checkout holds the topic branch for a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission’s life&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; no coordination worktree.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; it occupies the repository root checkout for the whole Mission (#5550, #5676). Rejected (A-3).&lt;/p&gt;
&lt;h3 id=&quot;option-6-land-planning-commits-on-an-unprotected-target-at-settlement-and-settle-to-lanes&quot;&gt;Option 6: land planning commits on an unprotected target at settlement and settle to &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt; today’s &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; shape on unprotected targets.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt; planning artifacts reach the target before &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;; a conflict path and a protection-dependent arm. This was the plan’s original recommendation for OQ-2; rejected by the operator (DM &lt;code dir=&quot;auto&quot;&gt;01M6R0B954ZPQN5NV4R1ZRE7NY&lt;/code&gt;).&lt;/p&gt;
&lt;h2 id=&quot;more-information&quot;&gt;More Information&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Mission artifacts: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/lane-worktree-model-hardening-01M6QY1M/spec.md&lt;/code&gt; (User Story 3, FR-050 to FR-062, A-1 to A-7), &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt; R-6, &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt; §1, &lt;code dir=&quot;auto&quot;&gt;contracts/finalize-tasks-json.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts/mission-create-json.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts/error-codes.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Decision Moments: &lt;code dir=&quot;auto&quot;&gt;01M6QY2SJ9ND1SKMH2230FS7JA&lt;/code&gt; (ruling 1), &lt;code dir=&quot;auto&quot;&gt;01M6QY46RJGFZN6WBVQQXCZSY6&lt;/code&gt; (deferred materialization), &lt;code dir=&quot;auto&quot;&gt;01M6QZ02HDACM7A0VNYSAQ8MQB&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;01M6R0B954ZPQN5NV4R1ZRE7NY&lt;/code&gt; (the “lanes otherwise” mapping), &lt;code dir=&quot;auto&quot;&gt;01M6R0BDYC29D6XMDY72R22CP9&lt;/code&gt; (provisional representation), &lt;code dir=&quot;auto&quot;&gt;01M6R0BJQ6Q1MV6492EH6HB66H&lt;/code&gt; (contract bump), &lt;code dir=&quot;auto&quot;&gt;01M6R0QJVPVZG2QT8MWQD4NXJR&lt;/code&gt; (PRIMARY placement), &lt;code dir=&quot;auto&quot;&gt;01M6R0QQM5FCPY736008AD4W6V&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Related: &lt;a href=&quot;/adr/3.x/2026-06-22-1-mission-topology-ssot/&quot;&gt;ADR 2026-06-22-1&lt;/a&gt; (stored topology, amended), &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;ADR 2026-10-04-5&lt;/a&gt; (approval bound, amended for S8), &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; (status read contract), &lt;a href=&quot;/context/topology/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/topology.md&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-11-13-an-explicit-lanes-create-on-a-protected-target-is-refused&quot;&gt;Amendment 2026-11-13: an explicit &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; create on a protected target is refused&lt;/h2&gt;
&lt;p&gt;Operator ruling Q2 (2026-11-13), &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/7632&quot;&gt;#7632&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The gap.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; is explicit-only (Decision 1) and mints neither a Mission branch nor a coordination branch. On a protected target, &lt;code dir=&quot;auto&quot;&gt;agent mission create --topology lanes&lt;/code&gt; was admitted, its scaffold commit was skipped, and every later status write was refused with &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decision.&lt;/strong&gt; Create refuses that shape before any write, with &lt;code dir=&quot;auto&quot;&gt;LANES_PROTECTED_TARGET_REFUSED&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;LanesProtectedTargetError&lt;/code&gt;, exit 1, the code in the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload). The message names two remedies: an unprotected target branch (&lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt;), or &lt;code dir=&quot;auto&quot;&gt;--topology lanes_with_coord&lt;/code&gt;. Create does not mint a branch for a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission; that would be Option 5, which stays rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Predicate.&lt;/strong&gt; The refusal asks the predicate the later status write asks, &lt;code dir=&quot;auto&quot;&gt;ProtectionPolicy.is_protected&lt;/code&gt; with the operator hatch, over the repository root’s configuration and, for an owned create, the owned checkout’s as well. It does not ask the #5100 mint rule (&lt;code dir=&quot;auto&quot;&gt;is_protected_target&lt;/code&gt;, primary branch plus configured branches). A primary branch the project un-protects (&lt;code dir=&quot;auto&quot;&gt;protection.protected_branches: []&lt;/code&gt;) still admits &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, because its status writes succeed there.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Scope.&lt;/strong&gt; Only create changes. A stored &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission, the migrations that stamp or restamp &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, and finalize (which never settles to &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;) are unchanged. The scaffold commit’s &lt;code dir=&quot;auto&quot;&gt;ProtectedBranchRefused&lt;/code&gt; bootstrap skip is no longer reached by a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; create; it stays for the other skip causes.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Nothing else in this record changes.&lt;/p&gt;</content>
</entry>
