<?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-09-03-1-explicit-owned-checkout-single-branch-lifecycle/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-09-03-1-explicit-owned-checkout-single-branch-lifecycle/</id>
  <title>ADR: Explicit Owned-Checkout Extends to the Single-Branch Mission Lifecycle</title>
  <updated>2026-09-03T00: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-09-03-1-explicit-owned-checkout-single-branch-lifecycle/"/>
  <summary>Extends the fail-closed --owned-checkout affordance to the whole single-branch mission lifecycle via one shared preflight authority, restricted to single_branch topology.</summary>
  <content type="html">&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt; established explicit checkout ownership and exposed
&lt;code dir=&quot;auto&quot;&gt;--owned-checkout PATH&lt;/code&gt; on exactly two commands: &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;.
That decision deliberately left the remaining mission-mutating commands out of
scope, naming the caller-versus-declared-workspace guard as follow-up work
(&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3128&quot;&gt;#3128&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;AI agents routinely operate from a task-owned linked worktree, not the
repository-root checkout. With only &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; owned-aware, the rest of
the single-branch lifecycle — prerequisite checks, task finalization, spec
commit, acceptance, task moves, and status transitions — could still only
rediscover the repository-root checkout. From an owned worktree those commands
either refused, or worse, resolved and wrote to the &lt;em&gt;wrong&lt;/em&gt; mission surface. The
ownership boundary existed but stopped one command in.&lt;/p&gt;
&lt;p&gt;This ADR records the decision to complete that surface for the single-branch
topology, the shared authority that carries it, and the topology restriction it
accepts. It extends — and does not supersede — &lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt;; the
&lt;code dir=&quot;auto&quot;&gt;OwnershipClaim&lt;/code&gt; primitive and refusal taxonomy from that decision remain the
foundation.&lt;/p&gt;
&lt;h2 id=&quot;decision-drivers&quot;&gt;Decision Drivers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Finish the owned-checkout lifecycle so a valid single-branch worktree workflow
never has to fall back to the repository-root checkout to make progress.&lt;/li&gt;
&lt;li&gt;Reuse the existing ownership, mission-resolution, protection, and
fail-closed-metadata authorities rather than inventing a second resolver.&lt;/li&gt;
&lt;li&gt;Keep every flagless (non-opted-in) caller byte-for-byte unchanged.&lt;/li&gt;
&lt;li&gt;Fail closed on every invalid ownership, topology, branch, or index condition —
never silently degrade an owned-mode operation to primary-checkout behavior.&lt;/li&gt;
&lt;li&gt;Bound the blast radius: admit only the topology whose write model the owned
root actually captures.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;one-shared-preflight-authority&quot;&gt;One shared preflight authority&lt;/h3&gt;
&lt;p&gt;Adopt &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.owned_mission&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;OwnedMission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_owned_mission&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;require_unstaged_index&lt;/code&gt; — as the single preflight shared by every owned
lifecycle command. &lt;code dir=&quot;auto&quot;&gt;OwnedMission&lt;/code&gt; is a validated &lt;em&gt;carrier&lt;/em&gt;, not a new resolver:
it composes the authorities that already exist rather than re-deriving placement.&lt;/p&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_owned_mission&lt;/code&gt; validates, in order and fail-closed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;repository identity and exact checkout root, via
&lt;code dir=&quot;auto&quot;&gt;checkout_ownership.resolve_ownership_claim&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;error_for_claim&lt;/code&gt; (the
&lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt; primitive);&lt;/li&gt;
&lt;li&gt;mission identity, via the canonical &lt;code dir=&quot;auto&quot;&gt;context.mission_resolver.resolve_mission&lt;/code&gt;
(a corrupt or non-object &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is skipped at indexing time, surfacing a
structured &lt;code dir=&quot;auto&quot;&gt;FEATURE_CONTEXT_UNRESOLVED&lt;/code&gt;, not a traceback);&lt;/li&gt;
&lt;li&gt;mission-directory containment within the claimed checkout’s &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;single-branch topology, via &lt;code dir=&quot;auto&quot;&gt;core.paths.load_meta_fail_closed&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;current branch equals the mission target branch (detached HEAD refused) and,
when supplied, the caller’s &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; matches;&lt;/li&gt;
&lt;li&gt;protected-destination refusal, via &lt;code dir=&quot;auto&quot;&gt;ProtectionPolicy&lt;/code&gt;;&lt;/li&gt;
&lt;li&gt;whole-batch path containment before any staging (&lt;code dir=&quot;auto&quot;&gt;OwnedMission.files&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The validated owned root is threaded onward as an explicit &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt;
override through mission-context resolution, the placement seam, acceptance
gates, status transitions, commit routing, and runtime cutover. No opted-in
layer may replace it with &lt;code dir=&quot;auto&quot;&gt;get_main_repo_root&lt;/code&gt; or another ambient resolver — the
same invariant &lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt; set for &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;the-affordance-now-spans-the-single-branch-lifecycle&quot;&gt;The affordance now spans the single-branch lifecycle&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;--owned-checkout PATH&lt;/code&gt; is additionally exposed on
&lt;code dir=&quot;auto&quot;&gt;agent mission check-prerequisites&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt;.
As before, the option names an exact checkout root for that invocation and is
never inferred from CWD, environment, path naming, or the nearest &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;single-branch-only-by-construction&quot;&gt;Single-branch only, by construction&lt;/h3&gt;
&lt;p&gt;Owned mode is restricted to the &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; topology. A &lt;code dir=&quot;auto&quot;&gt;LANES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt;, or
&lt;code dir=&quot;auto&quot;&gt;LANES_WITH_COORD&lt;/code&gt; mission opted into &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; is refused with the
structured &lt;code dir=&quot;auto&quot;&gt;OWNED_TOPOLOGY_UNSUPPORTED&lt;/code&gt;, and the transactional emitters refuse
with &lt;code dir=&quot;auto&quot;&gt;OWNED_TRANSACTION_UNAVAILABLE&lt;/code&gt; rather than degrading to an uncommitted
fallback.&lt;/p&gt;
&lt;p&gt;The rationale is that coordinated topologies route lifecycle writes through a
&lt;em&gt;coordination&lt;/em&gt; worktree and branch that the single owned-root override does not
model. Admitting them would reintroduce exactly the cross-checkout write hazard
the ownership boundary exists to prevent. Fail-closed refusal is the safe scope
until a coordinated-topology owned model is designed.&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;The single-branch worktree workflow is complete: an owned agent can run the
whole lifecycle without ever targeting the wrong checkout.&lt;/li&gt;
&lt;li&gt;One preflight authority governs every owned lifecycle command, composed from
the existing ownership/resolution/protection/metadata seams — no second
placement resolver.&lt;/li&gt;
&lt;li&gt;Every refusal is structured (&lt;code dir=&quot;auto&quot;&gt;OWNED_*&lt;/code&gt;), and every flagless caller is
unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;negative-and-accepted-trade-offs&quot;&gt;Negative and accepted trade-offs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The explicit &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt; override is threaded through many call sites.
This duplication is intentional, for the same reason &lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt; gave:
rediscovery would erase the boundary. (A landing-pass fold routed the
omit-the-keyword convention through the single &lt;code dir=&quot;auto&quot;&gt;effective_root_kwargs&lt;/code&gt; helper
so the threading has one definition.)&lt;/li&gt;
&lt;li&gt;Coordinated topologies are not owned-aware. An operator who used
&lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; for a coord/lanes mission hits a hard
&lt;code dir=&quot;auto&quot;&gt;OWNED_TOPOLOGY_UNSUPPORTED&lt;/code&gt; refusal on the later lifecycle commands. This is a
deliberate fail-closed scope, not a silent gap.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;owned_mission&lt;/code&gt; still re-derives some validation (branch/topology probes, a
whole-tree containment scan) on each resolve, and re-implements a few checks
that canonical helpers also provide. That SSOT/performance cleanup is tracked
as follow-up and does not change behavior.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;alternatives-considered&quot;&gt;Alternatives Considered&lt;/h2&gt;
&lt;h3 id=&quot;extend---owned-checkout-to-coordinated-topologies-now&quot;&gt;Extend &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; to coordinated topologies now&lt;/h3&gt;
&lt;p&gt;Rejected for this decision. Coordinated topologies write through a coordination
worktree/branch the owned-root override does not capture; a correct owned model
for them needs its own design. Fail-closed refusal is the safe interim scope.&lt;/p&gt;
&lt;h3 id=&quot;let-each-lifecycle-command-grow-its-own-ownership-check&quot;&gt;Let each lifecycle command grow its own ownership check&lt;/h3&gt;
&lt;p&gt;Rejected. That would fork the ownership/topology/branch invariants across
commands and let them drift — the second-resolver hazard &lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt;
already refused. One shared &lt;code dir=&quot;auto&quot;&gt;owned_mission&lt;/code&gt; preflight keeps a single authority.&lt;/p&gt;
&lt;h3 id=&quot;degrade-to-the-repository-root-checkout-when-owned-validation-fails&quot;&gt;Degrade to the repository-root checkout when owned validation fails&lt;/h3&gt;
&lt;p&gt;Rejected. Silent degradation is the original cross-write defect. Every invalid
condition is a structured refusal instead.&lt;/p&gt;
&lt;h2 id=&quot;amendments&quot;&gt;Amendments&lt;/h2&gt;
&lt;h3 id=&quot;2026-09-28--validated-ownership-fact-and-per-command-topology&quot;&gt;2026-09-28 — Validated ownership fact and per-command topology&lt;/h3&gt;
&lt;p&gt;Mission &lt;code dir=&quot;auto&quot;&gt;owned-checkout-lifecycle-authority-01M3M2ZB&lt;/code&gt; (issues #3449, #4252, #4867, #5026, #5277).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The preflight now produces a validated ownership fact.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve_owned_mission&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;mission_runtime.OwnedCheckout&lt;/code&gt;, a frozen value object carrying &lt;code dir=&quot;auto&quot;&gt;repository_root&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;owned_root&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;topology&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;. It can be minted only inside &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.owned_mission&lt;/code&gt;, through a private &lt;code dir=&quot;auto&quot;&gt;_mint&lt;/code&gt;; direct construction raises &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;OwnedMission&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;effective_root_kwargs&lt;/code&gt; are deleted with no alias left at mission end. The type lives in &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;core/owned_mission.py&lt;/code&gt;, because the &lt;code dir=&quot;auto&quot;&gt;runtime&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; layers must consume it without a new outbound edge into the CLI application layer (C-003; enforced by &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_layer_rules.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Validated once per command.&lt;/strong&gt; A command validates ownership at most once, at its entry point, through &lt;code dir=&quot;auto&quot;&gt;cli/commands/_owned_checkout.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;resolve_owned_or_adopt&lt;/code&gt;), and hands the resulting fact to every downstream read. Readers never re-validate. Sites that previously re-derived ownership — for example &lt;code dir=&quot;auto&quot;&gt;coordination/status_transition.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;cli/commands/accept.py&lt;/code&gt; — now consume the fact instead (FR-003, NFR-002). Acceptance also carries that fact into implementation-evidence ownership and stored-topology reads, including the attestation planner’s evidence check (#7099). A stale primary copy cannot supply missing owned-checkout ownership; without an owned fact, coordination still reads the PRIMARY partition.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Supersedes the &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt; threading consequence&lt;/strong&gt; (“The explicit &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt; override is threaded through many call sites …”, Consequences, Negative and accepted trade-offs). All bare owned-root parameters (census in this mission’s plan, Scale/Scope) become &lt;code dir=&quot;auto&quot;&gt;owned: OwnedCheckout | None&lt;/code&gt;. An architectural gate with an &lt;strong&gt;empty allowlist&lt;/strong&gt; forbids the identifier &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; outside the org-pack module rule (the unrelated &lt;code dir=&quot;auto&quot;&gt;OrgPackConfig.effective_root&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;src/charter/**&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/doctrine/**&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_doctrine_collect.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;analysis_inputs.py&lt;/code&gt;), and separately forbids any bare owned-root path parameter under any name (&lt;code dir=&quot;auto&quot;&gt;owned_root&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;owned_checkout&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;checkout_root&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;effective_root&lt;/code&gt; typed as a path). This is a deliberate no-ratchet conversion, not a leeway ledger (operator decision &lt;code dir=&quot;auto&quot;&gt;01M3M65D…&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Per-command topology&lt;/strong&gt; (supersedes “Single-branch only, by construction” for &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;; the lifecycle commands of this ADR keep that restriction). The validated fact records the mission’s stored topology, and each command declares its own allowed set. &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;NEXT_OWNED_TOPOLOGIES = {single_branch, lanes, lanes_with_coord, coord}&lt;/code&gt; (decision &lt;code dir=&quot;auto&quot;&gt;01M3M4GM…&lt;/code&gt;), preserving the coordination-topology support it already had rather than newly narrowing it. The lifecycle commands of this ADR (&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context resolve&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;) keep &lt;code dir=&quot;auto&quot;&gt;LIFECYCLE_OWNED_TOPOLOGIES = {single_branch}&lt;/code&gt; and still refuse other topologies with &lt;code dir=&quot;auto&quot;&gt;OWNED_TOPOLOGY_UNSUPPORTED&lt;/code&gt;. The placement-layer duplicate refusal &lt;code dir=&quot;auto&quot;&gt;_require_owned_single_branch&lt;/code&gt; is deleted, because topology is now decided once, at minting, not re-derived at each consumer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned status reads under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;.&lt;/strong&gt; The canonical coordination surface resolver decides whether a path is refused as a coordination worktree, from the validated fact plus the registered-worktree facts — never from path shape. There is no parallel status-source label; status-source classification stays with that one resolver (FR-013, FR-014, C-002).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stale repository-root copies.&lt;/strong&gt; When the repository root checkout holds a copy of the owned mission, owned reads resolve from the owned checkout, never from the repository root checkout’s copy, and report &lt;code dir=&quot;auto&quot;&gt;stale_repository_root_copy&lt;/code&gt; in JSON output and on stderr (FR-007, decision &lt;code dir=&quot;auto&quot;&gt;01M3M2ZX…&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Newly covered commands; typed refusal for &lt;code dir=&quot;auto&quot;&gt;agent action&lt;/code&gt;.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission setup-plan&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt; gain &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; accept the flag only to refuse it with &lt;code dir=&quot;auto&quot;&gt;OWNED_ACTION_UNSUPPORTED&lt;/code&gt;, and the refusal names &lt;code dir=&quot;auto&quot;&gt;next --owned-checkout&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task --owned-checkout&lt;/code&gt; as the supported path (decision &lt;code dir=&quot;auto&quot;&gt;01M3M4GZ…&lt;/code&gt;; follow-up #5100).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One claim-commit review base.&lt;/strong&gt; Every WP review prompt, owned or not, finds its base through one claim-commit helper: the last &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; event id recorded in the status log, then the unique commit that introduced it. It fails closed with &lt;code dir=&quot;auto&quot;&gt;OWNED_REVIEW_BASE_UNAVAILABLE&lt;/code&gt; when neither can be resolved. The three duplicate commit-subject matchers this ADR’s design otherwise left in place are deleted (FR-010, FR-025, decision &lt;code dir=&quot;auto&quot;&gt;01M3M70Y…&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New error codes.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;OWNED_CHECKOUT_IS_REPOSITORY_ROOT&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;OWNED_CHECKOUT_IS_MISSION_WORKTREE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;OWNED_ACTION_UNSUPPORTED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;OWNED_REVIEW_BASE_UNAVAILABLE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;OWNED_COORDINATION_WORKSPACE_UNAVAILABLE&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;references&quot;&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Foundational decision (extended, not superseded): &lt;a href=&quot;/adr/3.x/2026-08-12-1-checkout-ownership-for-mission-create-and-next/&quot;&gt;ADR 2026-08-12-1&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Caller/workspace mismatch follow-up: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3128&quot;&gt;#3128&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Scoped shadow-workspace design: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3129&quot;&gt;#3129&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Windows fixture repair (related, still open): &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/3822&quot;&gt;#3822&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Owned-checkout lifecycle authority mission: &lt;a href=&quot;../../../kitty-specs/owned-checkout-lifecycle-authority-01M3M2ZB/spec.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/owned-checkout-lifecycle-authority-01M3M2ZB/spec.md&lt;/code&gt;&lt;/a&gt;, &lt;a href=&quot;../../../kitty-specs/owned-checkout-lifecycle-authority-01M3M2ZB/plan.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/3449&quot;&gt;#3449&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4252&quot;&gt;#4252&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4867&quot;&gt;#4867&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5026&quot;&gt;#5026&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5277&quot;&gt;#5277&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
