<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-06-24-1-kind-and-topology-aware-artifact-placement/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-06-24-1-kind-and-topology-aware-artifact-placement/</id>
  <title>ADR: Kind- and Topology-Aware Artifact Placement — One Partition, Read/Write Symmetry</title>
  <updated>2026-06-24T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-06-24-1-kind-and-topology-aware-artifact-placement/"/>
  <summary>Artifact placement becomes a frozenset partition over `MissionArtifactKind`: planning and identity kinds sit in the PRIMARY partition, status kinds on the coordination branch.</summary>
  <content type="html">&lt;h2 id=&quot;context&quot;&gt;Context&lt;/h2&gt;
&lt;p&gt;A coordination-topology mission keeps two on-disk copies of its feature directory:
the &lt;strong&gt;primary checkout&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;) and the &lt;strong&gt;coordination worktree&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;.worktrees/&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;-coord/kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;). Where each mission artifact
&lt;em&gt;lives&lt;/em&gt; — which surface authors and reads it, and which branch its commit lands on —
is the central correctness question of the planning lifecycle.&lt;/p&gt;
&lt;p&gt;The merged read-side mission &lt;code dir=&quot;auto&quot;&gt;single-authority-topology-cleanup&lt;/code&gt; (PR #2099) introduced
the canonical answer for &lt;strong&gt;reads&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; in
&lt;a href=&quot;../../../src/mission_runtime/artifacts.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py&lt;/code&gt;&lt;/a&gt;. Every
mission artifact has a kind; &lt;code dir=&quot;auto&quot;&gt;artifact_home_for(kind, placement_ref)&lt;/code&gt; resolves its
read/write/commit home; &lt;code dir=&quot;auto&quot;&gt;is_coordination_artifact_residue_path&lt;/code&gt; classifies a stale
primary copy as residue-or-dirt by kind. That model already routed reads by &lt;strong&gt;kind&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The &lt;strong&gt;write/authoring&lt;/strong&gt; path, however, was &lt;strong&gt;kind-blind&lt;/strong&gt;. &lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;mission_runtime/resolution.py&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;specify_cli/coordination/commit_router.py&lt;/code&gt;) routed &lt;em&gt;purely by topology&lt;/em&gt;: under
coordination topology, &lt;strong&gt;every&lt;/strong&gt; planning artifact was written to the coordination
branch. So the read model said &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; belong on primary,
while the write path committed them to coordination. That asymmetry &lt;strong&gt;is&lt;/strong&gt; the
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2101&quot;&gt;#2101&lt;/a&gt; deadlock: for a
protected-main / &lt;code dir=&quot;auto&quot;&gt;pr_bound&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;topology: coord&lt;/code&gt; mission, &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; wrote WP
files to the coordination worktree while &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; globbed &lt;code dir=&quot;auto&quot;&gt;tasks/*.md&lt;/code&gt; on the
main checkout and found nothing — &lt;code dir=&quot;auto&quot;&gt;requirement_refs_parsed: {}&lt;/code&gt;, every functional
requirement reported unmapped. No single location satisfied both commands, and the
&lt;code dir=&quot;auto&quot;&gt;/tasks&lt;/code&gt; phase could not complete without a manual file-copy workaround.&lt;/p&gt;
&lt;p&gt;The predecessor ADR named and stored the mission &lt;em&gt;shape&lt;/em&gt; (&lt;code dir=&quot;auto&quot;&gt;MissionTopology&lt;/code&gt;) so the
shape is resolved once. This mission addresses the orthogonal question the shape alone
cannot answer: &lt;strong&gt;two artifacts of the same mission can legitimately want different
surfaces.&lt;/strong&gt; Topology says &lt;em&gt;whether a coordination branch exists&lt;/em&gt;; it must not be the
sole decider of &lt;em&gt;which&lt;/em&gt; artifacts go there.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;Make the write side &lt;strong&gt;kind-aware&lt;/strong&gt; by consulting the same &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; model
the read side already uses, and decide placement by a &lt;strong&gt;single frozenset partition&lt;/strong&gt;.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Placement is a partition, not a topology switch.&lt;/strong&gt; The PRIMARY-vs-coordination
decision is the membership test &lt;code dir=&quot;auto&quot;&gt;kind in _PRIMARY_ARTIFACT_KINDS&lt;/code&gt;
(&lt;a href=&quot;../../../src/mission_runtime/artifacts.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;artifacts.py&lt;/code&gt;&lt;/a&gt;). Planning + identity
kinds — &lt;code dir=&quot;auto&quot;&gt;SPEC&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DATA_MODEL&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;RESEARCH&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CHECKLIST&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;FINALIZED_EXECUTION_PLAN&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;TASKS_INDEX&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WORK_PACKAGE_TASK&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LANE_STATE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PRIMARY_METADATA&lt;/code&gt; — author, read,
and commit on the primary &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; &lt;strong&gt;for every topology shape&lt;/strong&gt;. The
status/bookkeeping/verification kinds — &lt;code dir=&quot;auto&quot;&gt;STATUS_STATE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ISSUE_MATRIX&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;ACCEPTANCE_MATRIX&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ANALYSIS_REPORT&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_PLACEMENT_ARTIFACT_KINDS&lt;/code&gt;), plus
&lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; — stay on the &lt;strong&gt;coordination branch&lt;/strong&gt; under coordination
topology (&lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;LANES&lt;/code&gt; collapse to primary). The two frozensets are the
&lt;strong&gt;single swappable locus&lt;/strong&gt;: flipping where a kind lands is moving it between the
sets — one line, no caller change, no signature or returned-shape change (NFR-004).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The write projection consults the partition.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt;
(&lt;a href=&quot;../../../src/mission_runtime/resolution.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;resolution.py:1017&lt;/code&gt;&lt;/a&gt;) now takes a
&lt;strong&gt;required&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kind: MissionArtifactKind&lt;/code&gt; keyword (no default — an un-threaded call
site fails at the type level rather than silently flipping coord→primary). A
&lt;code dir=&quot;auto&quot;&gt;_PRIMARY_ARTIFACT_KINDS&lt;/code&gt; member returns &lt;code dir=&quot;auto&quot;&gt;CommitTarget(ref=target_branch)&lt;/code&gt;; every
other kind keeps the topology-routed &lt;code dir=&quot;auto&quot;&gt;destination_ref&lt;/code&gt; the full resolver already
computes via &lt;code dir=&quot;auto&quot;&gt;_assemble_core_fragments&lt;/code&gt; — &lt;strong&gt;one authority, two projections&lt;/strong&gt;, not a
parallel resolver (C-006). &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt; derives &lt;code dir=&quot;auto&quot;&gt;use_coord&lt;/code&gt; from that single
kind-aware placement (&lt;code dir=&quot;auto&quot;&gt;routes_through_coordination(topology) and placement.ref != primary_target&lt;/code&gt;), so a primary kind never materializes the coordination worktree
even under coordination topology.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Read/write symmetry (INV-5).&lt;/strong&gt; The read side (&lt;code dir=&quot;auto&quot;&gt;artifact_home_for&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;is_coordination_artifact_residue_path&lt;/code&gt;, #2099) and the write side
(&lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt;, plus the bypass writers and the
second routing authority — see §4) now both consult the same partition. For a given
kind they resolve the &lt;strong&gt;same&lt;/strong&gt; surface. &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;PRIMARY_METADATA&lt;/code&gt;) is the
capstone: it already &lt;em&gt;read&lt;/em&gt; from primary, and now &lt;em&gt;writes&lt;/em&gt; to primary too, closing
the last read/write split. The #2101 class is structurally impossible once both
legs agree: the command that writes WP files and the command that validates them
resolve the identical &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Converge every write site — no “fixed N of M”.&lt;/strong&gt; Kind-awareness is threaded
through &lt;em&gt;all&lt;/em&gt; planning-placement writers, not just &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt;’s callers
(&lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt;, finalize tail, &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;,
analyze/tasks/accept): also the &lt;strong&gt;bypass writers&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;append-history&lt;/code&gt;, which hold a &lt;em&gt;path&lt;/em&gt; and classify it via the new public
&lt;code dir=&quot;auto&quot;&gt;kind_for_mission_file&lt;/code&gt; classifier) &lt;strong&gt;and&lt;/strong&gt; the &lt;strong&gt;second routing authority&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;_planning_commit_worktree&lt;/code&gt;
(&lt;a href=&quot;../../../src/specify_cli/cli/commands/agent/mission.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;mission.py:792&lt;/code&gt;&lt;/a&gt;), which
maps each &lt;code dir=&quot;auto&quot;&gt;artifact_type&lt;/code&gt; to a &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_ARTIFACT_TYPE_TO_KIND&lt;/code&gt;) and
delegates to &lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt;. The planning-artifact→coordination &lt;em&gt;write&lt;/em&gt;
route is &lt;strong&gt;removed&lt;/strong&gt;, not preserved as a fallback (C-005 — unification, not parity).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Topology governs only the status destination.&lt;/strong&gt; After this mission,
&lt;code dir=&quot;auto&quot;&gt;MissionTopology&lt;/code&gt; decides &lt;em&gt;where the status commit lands&lt;/em&gt;, &lt;strong&gt;not&lt;/strong&gt; where the planning
commit lands. Planning is partition-decided (always primary); status is
topology-routed (coordination under &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 two questions
are finally separated.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;binding-invariant--protected-primary-fr-008--c-002&quot;&gt;Binding invariant — protected primary (FR-008 / C-002)&lt;/h3&gt;
&lt;p&gt;Because planning artifacts now always land on the primary &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, a
coordination-topology mission whose &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; is a &lt;strong&gt;protected&lt;/strong&gt; branch
(&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;master&lt;/code&gt;) is &lt;strong&gt;refused&lt;/strong&gt; at the planning-commit boundary
(&lt;a href=&quot;../../../src/specify_cli/coordination/commit_router.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;commit_router.py:160&lt;/code&gt;&lt;/a&gt;,
&lt;code dir=&quot;auto&quot;&gt;no_op_wrong_surface&lt;/code&gt;) with guidance to start a non-protected feature branch. The
protected-primary deadlock is avoided by this &lt;strong&gt;feature-branch invariant&lt;/strong&gt; — not by
transiting the coordination worktree. Status commits are unaffected: they continue to
route to the (non-protected) coordination branch. This deliberately revises mission
&lt;code dir=&quot;auto&quot;&gt;01KSPTVW&lt;/code&gt; FR-005 (which originally placed planning-artifact commits on the coordination
branch); the revision is operator-confirmed unification, called out so it is not read
as a regression.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;h3 id=&quot;positive&quot;&gt;Positive&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The #2101 / #2062-#2064 desync class is closed at the root.&lt;/strong&gt; Read and write
resolve the same surface per kind, so the command that authors a planning artifact
and the command that validates it can never disagree about its &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt;. A fresh
coordination-topology mission completes specify → plan → tasks →
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks --validate-only&lt;/code&gt; with 100% of requirements mapped and &lt;strong&gt;zero&lt;/strong&gt; manual
coordination-worktree steps (SC-001).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Placement is one named, swappable partition.&lt;/strong&gt; Re-homing a kind is a one-line set
move; callers and the returned &lt;code dir=&quot;auto&quot;&gt;CommitTarget&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissionArtifactHome&lt;/code&gt; shape are blind to
the membership (NFR-004 / G-5). The decision lives in exactly one module.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status semantics are preserved.&lt;/strong&gt; The append-only &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;, and WP transition commits still land on the
coordination branch under coordination topology (C-001), keeping the atomic-event-log
model from mission &lt;code dir=&quot;auto&quot;&gt;01KSPTVW&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Behavior-neutral for flattened / single-branch missions&lt;/strong&gt; (NFR-001): with no
coordination branch, both partitions collapse to &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; — identical to
pre-mission behavior.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;negative--risks&quot;&gt;Negative / risks&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Forward-only (C-003).&lt;/strong&gt; A mission already &lt;em&gt;split&lt;/em&gt; (planning on coordination, reads
on primary) is not reconciled; the flatten / manual-recovery flow remains the
documented remedy for legacy split missions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A required &lt;code dir=&quot;auto&quot;&gt;kind&lt;/code&gt; keyword is a breaking internal-seam change.&lt;/strong&gt; Every
&lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt; call site must thread a
&lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt;. This is intentional (fail at the type level, not silently),
but any out-of-tree caller must be updated.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The coordination-worktree mechanism stays&lt;/strong&gt; (C-004). This mission stops routing
planning artifacts through it; it does not remove the materialization used for
status/sync. The &lt;code dir=&quot;auto&quot;&gt;_planning_commit_worktree&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_materialise_coord_worktree&lt;/code&gt; staging,
the &lt;code dir=&quot;auto&quot;&gt;_try_advance_ref&lt;/code&gt; ff-advance (#1878), and the &lt;code dir=&quot;auto&quot;&gt;is_coordination_artifact_residue_path&lt;/code&gt;
dirty-filter remain, now governing only status-class coord writes (FR-005). A stale
&lt;em&gt;primary&lt;/em&gt; copy of a planning artifact is now &lt;strong&gt;real dirt&lt;/strong&gt;, not residue.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;alternatives-considered&quot;&gt;Alternatives considered&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Keep routing purely by topology (status quo).&lt;/strong&gt; Rejected: that &lt;em&gt;is&lt;/em&gt; the #2101 bug —
it forces planning artifacts onto coordination while reads expect primary.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Build a second, write-only resolver that mirrors the read partition.&lt;/strong&gt; Rejected
(C-006): &lt;code dir=&quot;auto&quot;&gt;artifact_home_for&lt;/code&gt; / the partition is already the single classification
authority. &lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt; &lt;em&gt;projects&lt;/em&gt; the same &lt;code dir=&quot;auto&quot;&gt;_assemble_core_fragments&lt;/code&gt;
builder; a parallel resolver re-reading &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;/git would re-create the split-brain
under repair — the same anti-pattern the predecessor topology-SSOT ADR rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Move status to primary too (uniform primary placement).&lt;/strong&gt; Rejected (C-001): it
would break the atomic coordination event-log model; status legitimately wants the
coordination branch under coordination topology. The bifurcation is the point.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Solve protected-primary by transiting the coordination worktree for planning
commits.&lt;/strong&gt; Rejected (FR-008 / D-3): the feature-branch invariant is a cleaner
guarantee with no special-case transit; it removes the deadlock by construction rather
than re-introducing the coord landing the read side just escaped.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Driver: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2090&quot;&gt;#2090&lt;/a&gt; (kind- and topology-aware write-side placement)&lt;/li&gt;
&lt;li&gt;User-reported deadlock closed: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2101&quot;&gt;#2101&lt;/a&gt; (coordination-worktree missions: planning/tasks resolve different &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Read-side predecessor: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/2099&quot;&gt;#2099&lt;/a&gt; / mission &lt;code dir=&quot;auto&quot;&gt;single-authority-topology-cleanup&lt;/code&gt; (&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/147&quot;&gt;#147&lt;/a&gt;) — the &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; read model&lt;/li&gt;
&lt;li&gt;Desync class closed structurally by the read+write pair: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2062&quot;&gt;#2062&lt;/a&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2063&quot;&gt;#2063&lt;/a&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2064&quot;&gt;#2064&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Epics: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1716&quot;&gt;#1716&lt;/a&gt; (single surface authority), &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2007&quot;&gt;#2007&lt;/a&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1619&quot;&gt;#1619&lt;/a&gt; (execution-context)&lt;/li&gt;
&lt;li&gt;Mission spec: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/write-surface-coherence-01KVTVZS/spec.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Placement contract: &lt;code dir=&quot;auto&quot;&gt;kitty-specs/write-surface-coherence-01KVTVZS/contracts/placement-bifurcation.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Data model (INV-5 read/write symmetry, the swappable locus): &lt;code dir=&quot;auto&quot;&gt;kitty-specs/write-surface-coherence-01KVTVZS/data-model.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Phase-0 decisions (D-1..D-8): &lt;code dir=&quot;auto&quot;&gt;kitty-specs/write-surface-coherence-01KVTVZS/research.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Canonical seams: &lt;a href=&quot;../../../src/mission_runtime/artifacts.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py&lt;/code&gt;&lt;/a&gt; (partition + &lt;code dir=&quot;auto&quot;&gt;artifact_home_for&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;kind_for_mission_file&lt;/code&gt;), &lt;a href=&quot;../../../src/mission_runtime/resolution.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/resolution.py&lt;/code&gt;&lt;/a&gt; (&lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt;, kind-aware), &lt;a href=&quot;../../../src/specify_cli/coordination/commit_router.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/coordination/commit_router.py&lt;/code&gt;&lt;/a&gt; (&lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt;, FR-008 protected-primary refusal), &lt;a href=&quot;../../../src/specify_cli/cli/commands/agent/mission.py&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/agent/mission.py&lt;/code&gt;&lt;/a&gt; (&lt;code dir=&quot;auto&quot;&gt;_planning_commit_worktree&lt;/code&gt;, second routing authority)&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
