<?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-10-06-3-evidence-gates-check-origin-freshness/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-10-06-3-evidence-gates-check-origin-freshness/</id>
  <title>ADR: evidence gates check origin freshness before they trust local evidence</title>
  <updated>2026-10-07T00: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-10-06-3-evidence-gates-check-origin-freshness/"/>
  <summary>Remote contact has one owner; review, accept and consolidate refresh and classify the branches they trust against origin before any mutation, with an explicit opt-out.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-10-06&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (owner). The operator rulings on the two escalated forks (origin ahead, origin unreachable) are recorded under Decision.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5780&quot;&gt;#5780&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5758&quot;&gt;#5758&lt;/a&gt; and &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5759&quot;&gt;#5759&lt;/a&gt;, Mission &lt;code dir=&quot;auto&quot;&gt;second-clone-origin-reconciliation-01M48V8W&lt;/code&gt;. Builds on the probe-only fixes &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4969&quot;&gt;#4969&lt;/a&gt; and &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4979&quot;&gt;#4979&lt;/a&gt;. Amends Decisions 1 and 2 of ADR &lt;a href=&quot;/adr/3.x/2026-06-05-1-merge-publish-layer-boundary/&quot;&gt;2026-06-05-1&lt;/a&gt;.&lt;/p&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;spec-kitty consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; and the two &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; gates contact origin, which codes they refuse with, and which module may run &lt;code dir=&quot;auto&quot;&gt;git fetch&lt;/code&gt;. An operator looking at &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_DIVERGED&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt; should start from the remedy in the refusal text.&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;Two people work on one Mission from two clones of one remote. The reviewer in clone B rejects a work package and pushes the status change. The integrator in clone A has not pulled and runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;. Clone A’s local view says the work package is approved, so the rejected work lands as done with exit 0 and the “Reconciliation verified” banner, and &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; publishes it (#5780).&lt;/p&gt;
&lt;p&gt;The same shape breaks the review loop. A reviewer rejects, the author pushes a fix, the reviewer runs &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; (which updates only the remote-tracking ref of the lane) and reviews again: the workspace still holds the rejected version, the reviewer approves it, and consolidate lands it (#5758). And a teammate’s fresh clone never receives the per-clone merge-driver settings, so its first pull text-merges &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and leaves conflict markers that wedge every command (#5759).&lt;/p&gt;
&lt;p&gt;Every gate decided on local state alone. Nothing in the code base asked origin before trusting a branch. The only remote contacts that existed were narrow: a target-branch refresh in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt;, and an existence probe in &lt;code dir=&quot;auto&quot;&gt;remote_probes&lt;/code&gt; (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4979&quot;&gt;#4979&lt;/a&gt;). The earlier fixes (&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4969&quot;&gt;#4969&lt;/a&gt;, &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/4979&quot;&gt;#4979&lt;/a&gt;) fixed one probe each and left the class open.&lt;/p&gt;
&lt;p&gt;ADR 2026-06-05-1 had set the rule that blocked a general fix: remote-state inspection lives only in &lt;code dir=&quot;auto&quot;&gt;push_preflight.py&lt;/code&gt; and the domain preflight stays network-free. That rule was written to stop &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; from refusing when the local target is legitimately ahead of origin (#1706). It is the right rule for &lt;strong&gt;push safety&lt;/strong&gt; and the wrong rule for &lt;strong&gt;evidence&lt;/strong&gt;: a gate that reads status events as the truth about a Mission cannot be network-free when the truth lives on a branch another person writes.&lt;/p&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;p&gt;Recorded in the Mission’s &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt; (R-1, R-2, R-4, R-7); the first four were rejected, the last is the chosen shape.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Read the existing &lt;code dir=&quot;auto&quot;&gt;refs/remotes/*&lt;/code&gt; only.&lt;/strong&gt; Keeps ADR 2026-06-05-1 network-free, and is the shape of the probe-only fixes #4969 and #4979. Rejected: #5780’s clone never fetched, so the tracking refs were as stale as the local branches and the P0 stayed open. The operator rejected it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A full &lt;code dir=&quot;auto&quot;&gt;git fetch &amp;#x3C;remote&gt;&lt;/code&gt;.&lt;/strong&gt; Rejected: it transfers an unbounded set of refs (every lane of every Mission), is slower, and with pruning can remove unrelated refs. The chosen check lists the wanted branches with one &lt;code dir=&quot;auto&quot;&gt;ls-remote&lt;/code&gt; and fetches only those, which also makes &lt;code dir=&quot;auto&quot;&gt;remote_missing&lt;/code&gt; a positive answer from the remote instead of an inference from an absent local ref (and a &lt;code dir=&quot;auto&quot;&gt;git fetch&lt;/code&gt; of an absent ref fails the whole call).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A hard-coded &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;.&lt;/strong&gt; The state of #4969. Rejected: wrong for a clone whose only remote is &lt;code dir=&quot;auto&quot;&gt;upstream&lt;/code&gt; or a fork, and it cannot honor &lt;code dir=&quot;auto&quot;&gt;branch.&amp;#x3C;b&gt;.remote&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ask every remote.&lt;/strong&gt; Rejected: one dead secondary remote (a fork named &lt;code dir=&quot;auto&quot;&gt;upstream&lt;/code&gt;) would then refuse every gate. The rule is the branch’s configured remote, else the sole remote, else &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;; the all-remotes existence probe of #4979 keeps its own semantics inside the same owner (see #5859).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A boolean skip flag (&lt;code dir=&quot;auto&quot;&gt;--skip-origin-check&lt;/code&gt;).&lt;/strong&gt; Rejected for the opt-out: it has no environment-default symmetry and no way to say “warn but continue”. A valued &lt;code dir=&quot;auto&quot;&gt;--origin-check&lt;/code&gt; with a &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK&lt;/code&gt; default mirrors &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_MODE&lt;/code&gt; and is the shape chosen.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Chosen:&lt;/strong&gt; a named freshness preflight that contacts the one resolved remote with &lt;code dir=&quot;auto&quot;&gt;ls-remote&lt;/code&gt;, fetches only the listed branches into their tracking refs, and applies a per-gate policy.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Remote contact has one owner. Evidence freshness is a named preflight in the evidence gates. Push safety stays where it was.&lt;/strong&gt;&lt;/p&gt;
&lt;h3 id=&quot;amendment-to-adr-2026-06-05-1&quot;&gt;Amendment to ADR 2026-06-05-1&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Decision 1 (remote inspection only in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;) is amended.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kernel.git.remote&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/kernel/git/remote.py&lt;/code&gt;) is the only module that builds a remote-contacting argv: &lt;code dir=&quot;auto&quot;&gt;fetch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ls-remote&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote show&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;-n&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pull&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;clone&lt;/code&gt;. It owns the no-prompt environment, the timeouts (&lt;code dir=&quot;auto&quot;&gt;LS_REMOTE_TIMEOUT&lt;/code&gt; 5 s, &lt;code dir=&quot;auto&quot;&gt;FETCH_TIMEOUT&lt;/code&gt; 15 s) and the meaning of “unreachable”. &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt; keeps the push-safety predicate (&lt;code dir=&quot;auto&quot;&gt;is_safe_to_push&lt;/code&gt;) and asks the owner by intent. &lt;code dir=&quot;auto&quot;&gt;push&lt;/code&gt; itself is outside the rule.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decision 2 (domain preflight is network-free) is amended&lt;/strong&gt; from “the domain layer never touches a remote” to “the domain layer never contacts a remote &lt;strong&gt;except through a named evidence-freshness preflight&lt;/strong&gt;”. The local merge path still performs no remote contact that decides push safety, and a local consolidate still never refuses because the target is behind for commits that do not touch this Mission’s status log (#1706, FR-015). Decisions 3 to 5 are unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;the-remote-rule&quot;&gt;The remote rule&lt;/h3&gt;
&lt;p&gt;One rule says which remote a branch is checked against: the branch’s configured remote, else the sole configured remote, else the remote named &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;, else no remote. Reachability is judged against that remote only. The all-remotes existence probe of #4979 keeps its own documented semantics inside the same owner. With no remote resolving, no remote is contacted and every gate behaves as before.&lt;/p&gt;
&lt;h3 id=&quot;the-check&quot;&gt;The check&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.git.origin_freshness&lt;/code&gt; is the intent layer. In one invocation it refreshes the remote’s view of the branches a gate is about to trust (one contact per remote), then classifies each against the remote tip: &lt;code dir=&quot;auto&quot;&gt;up_to_date&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;behind&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ahead&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;diverged&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;local_missing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote_missing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unreachable&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;no_remote&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;up_to_date&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;remote_missing&lt;/code&gt; are concluded only from a remote that answered in this invocation; a failed refresh is &lt;code dir=&quot;auto&quot;&gt;unreachable&lt;/code&gt; whether or not a stale remote-tracking ref exists. &lt;code dir=&quot;auto&quot;&gt;specify_cli.git.origin_gate.run_origin_gate&lt;/code&gt; is the one shared adapter the gates call: it contacts the remote once, sets a coordination-only &lt;code dir=&quot;auto&quot;&gt;local_missing&lt;/code&gt; verdict aside for the existing &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt; refusal (ADR &lt;a href=&quot;/adr/3.x/2026-09-24-2-coord-read-fail-closed/&quot;&gt;2026-09-24-2&lt;/a&gt;, reused, not duplicated), applies the policy and returns the warnings to print. The common case costs one round trip: when every tip &lt;code dir=&quot;auto&quot;&gt;ls-remote&lt;/code&gt; lists already equals the local remote-tracking ref, the fetch is skipped; any doubt fetches.&lt;/p&gt;
&lt;p&gt;Status evidence is judged on the commits that change this Mission’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, under every directory alias of the Mission (ADR &lt;a href=&quot;/adr/4.x/2026-10-05-1-bare-slug-coordination-directory-alias/&quot;&gt;2026-10-05-1&lt;/a&gt;). A lanes Mission whose target branch is behind only because a teammate landed an unrelated Mission is not stale, which keeps FR-001 and FR-015 consistent.&lt;/p&gt;
&lt;h3 id=&quot;the-policy&quot;&gt;The policy&lt;/h3&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Gate&lt;/th&gt;&lt;th&gt;Branch class&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;behind&lt;/code&gt;&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;diverged&lt;/code&gt;&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;local_missing&lt;/code&gt; (remote has it)&lt;/th&gt;&lt;th&gt;&lt;code dir=&quot;auto&quot;&gt;unreachable&lt;/code&gt;&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;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;orchestrator-api accept-mission&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;consolidate-mission&lt;/code&gt;&lt;/td&gt;&lt;td&gt;status evidence branch&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt; on a coordination branch, else &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt;&lt;/td&gt;&lt;td&gt;approved code lanes&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt;&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt;&lt;/td&gt;&lt;td&gt;the work package’s lane&lt;/td&gt;&lt;td&gt;fast-forward, else refuse&lt;/td&gt;&lt;td&gt;refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_DIVERGED&lt;/code&gt;&lt;/td&gt;&lt;td&gt;create the workspace from the remote’s lane&lt;/td&gt;&lt;td&gt;warn and continue&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;up_to_date&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ahead&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote_missing&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;no_remote&lt;/code&gt; pass everywhere.&lt;/p&gt;
&lt;h3 id=&quot;operator-rulings&quot;&gt;Operator rulings&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Origin ahead splits by branch class.&lt;/strong&gt; The gates never mutate the status evidence branch (a refusal names the commits and the pull command; with a merge record present the remedy is &lt;code dir=&quot;auto&quot;&gt;consolidate --abort&lt;/code&gt;, then the pull, then &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;). A reviewer’s local lane is the one branch a gate may move, forward only: it is cut from origin when absent, and fast-forwarded when it is a strict ancestor of the remote tip, every checkout of it is clean (review-lock residue excepted) and no foreign review lock is live. The fast-forward goes through &lt;code dir=&quot;auto&quot;&gt;advance_branch_ref&lt;/code&gt;, which is compare-and-swap, updates every checkout and records the lane work tip. The consolidate lane check runs before the approval-stamp check of ADR &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;2026-10-04-5&lt;/a&gt; and only refuses: it never adds content to the approved claim, and its remedy is to update the lane, after which the stamp check decides.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Unreachable fails closed, with an opt-out.&lt;/strong&gt; No remote, or a branch that was never pushed, passes silently. A remote that resolves but cannot be reached refuses at the merge-path gates (&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and their orchestrator-api forms) and only warns at review. &lt;code dir=&quot;auto&quot;&gt;--origin-check warn&lt;/code&gt; per invocation (on &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and the two &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; forms), with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=warn&lt;/code&gt; as its environment default (default &lt;code dir=&quot;auto&quot;&gt;enforce&lt;/code&gt;), turns every freshness refusal into a printed warning that names the verdict and where the opt-out came from (&lt;code dir=&quot;auto&quot;&gt;flag&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;environment&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; has no flag and honors only the environment variable: in &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; mode a diverged lane is kept as it is and the warning is printed. An unrecognized value enforces and warns. The variable name avoids the retired “sync” vocabulary on purpose: that transport was deleted and nothing here re-enables it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; is a no-contact mode (2026-10-07).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--origin-check off&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=off&lt;/code&gt;) contacts no remote, refuses nothing and prints one warning that origin was not checked and stale evidence is accepted. It exists for an offline machine or a remote that cannot be reached, where &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; would still pay the contact and its timeout. The accepted risk is the one this ADR removes: a teammate’s pushed rejection or lane fix is not seen and can land as done. Before this ruling &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; was an unrecognized value and enforced. Review honors it through the environment variable only and keeps the last-known lane with the warning.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id=&quot;surfaces&quot;&gt;Surfaces&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; runs one combined check (status evidence and approved lanes, one contact per remote) right after the placement seam is resolved and before &lt;code dir=&quot;auto&quot;&gt;_resolve_run_status_dir&lt;/code&gt; can seed or commit a coordination surface, so before any branch moves and before the lock; lanes are selected read-only. &lt;code dir=&quot;auto&quot;&gt;consolidation/origin_gate.py&lt;/code&gt; keeps only lane selection (skipping planning lanes, fully canceled lanes and, on &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;, lanes whose work packages are all completed), the merge-record flag, rendering and &lt;code dir=&quot;auto&quot;&gt;typer.Exit&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; runs it once, between the merge-commit verification and the summary. &lt;code dir=&quot;auto&quot;&gt;accept --no-commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--diagnose&lt;/code&gt; are read-only and only warn.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api accept-mission&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_READY&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate-mission&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt;, each with &lt;code dir=&quot;auto&quot;&gt;data.preflight_error_code(s)&lt;/code&gt; set to the freshness code and the verdicts in &lt;code dir=&quot;auto&quot;&gt;data.origin_freshness&lt;/code&gt;. The contract version is 1.11.0.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; is &lt;strong&gt;not&lt;/strong&gt; a gate: it returns the conflict forecast before the executor is entered, moves nothing and acts on no evidence. It is recorded as a reasoned non-gate in the registry gate below, not as an allowlist entry.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; on an already-initialized clone, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; even when every migration is recorded as applied, install the per-clone merge-driver settings idempotently. Upgrade reports the install in its one outcome (ADR &lt;a href=&quot;/adr/4.x/2026-10-04-3-upgrade-reports-one-outcome/&quot;&gt;2026-10-04-3&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;two-architectural-gates-both-with-empty-allowlists&quot;&gt;Two architectural gates, both with empty allowlists&lt;/h3&gt;
&lt;p&gt;Standing order: an allowlist is priced debt (ADR &lt;a href=&quot;/adr/4.x/2026-09-30-1-allowlist-ratchets-are-priced-debt/&quot;&gt;2026-09-30-1&lt;/a&gt;). Both gates close with none.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_remote_contact_owner.py&lt;/code&gt;: zero remote-contacting argv outside &lt;code dir=&quot;auto&quot;&gt;src/kernel/git/&lt;/code&gt;, a scanned-file floor, a planted violation per argv form and an owner-bypass positive control.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_evidence_gates_check_origin.py&lt;/code&gt;: the entry set is &lt;strong&gt;derived&lt;/strong&gt; (the &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; command, and every function in &lt;code dir=&quot;auto&quot;&gt;cli/commands/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator_api/&lt;/code&gt; that transitively calls &lt;code dir=&quot;auto&quot;&gt;_run_lane_based_consolidation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_execute_lane_merge&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;collect_feature_summary&lt;/code&gt; and is not called by another such function), asserted to contain a floor of five known entry points, and each must reach an &lt;code dir=&quot;auto&quot;&gt;ast.Call&lt;/code&gt; to a freshness-check function (&lt;code dir=&quot;auto&quot;&gt;run_origin_gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check_origin_before_status_dir&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check_mission_branches&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check_branches&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;enforce_merge_gate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan_review_lane&lt;/code&gt;). A name reference or an import proves nothing, and neither does calling a lane selector such as &lt;code dir=&quot;auto&quot;&gt;approved_lane_branches&lt;/code&gt;. A planted entry that omits the call fails the gate; removing the call from each real entry point was shown to fail it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;pre-existing-drift-this-records&quot;&gt;Pre-existing drift this records&lt;/h2&gt;
&lt;p&gt;ADR 2026-06-05-1 said remote inspection lives in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;. It did not. &lt;code dir=&quot;auto&quot;&gt;remote_probes&lt;/code&gt; (the existence probe) and &lt;code dir=&quot;auto&quot;&gt;protection_policy&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;git remote show&lt;/code&gt;) already contacted remotes outside &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;git_source&lt;/code&gt; in the doctrine layer cloned and fetched on its own. Each decided its own timeout and prompt behaviour. Those sites now call &lt;code dir=&quot;auto&quot;&gt;kernel.git.remote&lt;/code&gt;, which is what makes the first gate enforceable at zero.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A second clone that has not heard from origin can no longer land a teammate’s rejection, review a superseded lane, or accept on a stale log; the integrator gets a refusal with the exact remedy before anything moves.&lt;/li&gt;
&lt;li&gt;Every merge-path gate can now contact the network. A user with a remote and no connectivity is refused until they opt out; a solo user with no remote, or whose Mission branches were never pushed, is unaffected.&lt;/li&gt;
&lt;li&gt;A committed project-tier environment file that sets &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=warn&lt;/code&gt; turns the check off for every clone. The warning names its source so the choice is visible; refusing a repository-tier value is a policy change left for later.&lt;/li&gt;
&lt;li&gt;NFR-003 (under 200 ms overhead when no remote resolves) is &lt;strong&gt;review-checked, not timed in CI&lt;/strong&gt;. A wall-clock assertion would be the flaky kind the flakiness policy forbids; the no-remote arm is covered functionally (no remote contact, behaviour unchanged) and the reviewer reads the code path.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;residuals&quot;&gt;Residuals&lt;/h2&gt;
&lt;p&gt;Each is recorded, not fixed here.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The check and the mutation are not atomic.&lt;/strong&gt; A teammate can push after the fetch and before the gate moves a branch. The window is the gate’s own run time. It is bounded by what runs after: consolidate’s lane check and the approval-stamp check (&lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt;, ADR 2026-10-04-5) and the reconciliation gate catch a moved lane at the end, and nothing is pushed unless &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; is given.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The consolidate check runs before the consolidation lock.&lt;/strong&gt; A push that lands between the check and the lock is unseen by the check. The reconciliation gate and the rollback authority are the backstop: a late commit that the gate cannot attribute fails it and the run restores the branches it moved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Review only warns when the remote is unreachable.&lt;/strong&gt; That is safe because review is not the terminus: what review approves is judged again at consolidate, where an unreachable remote refuses, and a lane that moved after approval is refused there. Refusing at review would block a reviewer on a train for no safety gain.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; has no &lt;code dir=&quot;auto&quot;&gt;--origin-check&lt;/code&gt; flag.&lt;/strong&gt; It reads &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK&lt;/code&gt; only, so &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; (which lifts &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_DIVERGED&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; are environment-only there. Unlike the merge-path gates, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; lands nothing, which is also why it warns, not refuses, on &lt;code dir=&quot;auto&quot;&gt;unreachable&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;remote_ambiguous&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;compare_failed&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A comparison git cannot make refuses (&lt;code dir=&quot;auto&quot;&gt;ORIGIN_COMPARE_FAILED&lt;/code&gt;).&lt;/strong&gt; When the remote answered but &lt;code dir=&quot;auto&quot;&gt;rev-list&lt;/code&gt; fails locally (a shallow boundary, a damaged ref) the verdict is &lt;code dir=&quot;auto&quot;&gt;compare_failed&lt;/code&gt;, never “up to date”, and the merge-path gates refuse; &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; warns.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A clone whose remote was removed warns, never refuses.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;no_remote&lt;/code&gt; still passes, but when the clone keeps remote-tracking refs the gate adds one note that nothing was checked; a repository that never had a remote stays silent.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An ambiguous remote refuses (operator ruling 2026-10-07).&lt;/strong&gt; When remotes exist but none owns the branch (no &lt;code dir=&quot;auto&quot;&gt;branch.&amp;#x3C;b&gt;.remote&lt;/code&gt;, not exactly one remote, no &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;) the verdict is &lt;code dir=&quot;auto&quot;&gt;remote_ambiguous&lt;/code&gt; and the merge-path gates refuse &lt;code dir=&quot;auto&quot;&gt;ORIGIN_REMOTE_AMBIGUOUS&lt;/code&gt; (review warns). Before the ruling this read &lt;code dir=&quot;auto&quot;&gt;no_remote&lt;/code&gt; and passed silently. A repository with no remote at all still passes with nothing contacted (NFR-003).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; is a no-contact mode (operator ruling 2026-10-07)&lt;/strong&gt; and accepts the risk the ADR exists to remove. It prints one warning and nothing is asked of origin. See operator ruling 3.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A customized merge driver is preserved (operator ruling 2026-10-07).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; write a &lt;code dir=&quot;auto&quot;&gt;merge.&amp;#x3C;key&gt;.name&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;.driver&lt;/code&gt; value only when it is unset or one a release shipped (the current one, plus the 3.2.6rc1 issue-matrix name); a value the operator set is kept and named in a warning. The merge path’s own self-heal (&lt;code dir=&quot;auto&quot;&gt;_ensure_merge_driver_git_config&lt;/code&gt;) still restores the shipped values when a consolidation or auto-rebase runs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The freshness fetch never moves a local branch.&lt;/strong&gt; It passes &lt;code dir=&quot;auto&quot;&gt;--refmap=&lt;/code&gt; so a mirror-style &lt;code dir=&quot;auto&quot;&gt;remote.&amp;#x3C;name&gt;.fetch&lt;/code&gt; cannot reset a lane, and it compares fully qualified &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;b&gt;&lt;/code&gt; so a tag of the same name cannot shadow the branch.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Follow-ups filed:&lt;/strong&gt; #5857 (review’s lane fast-forward re-probes ancestry in the CLI; the diverged-lane policy lives in two places), #5858 (&lt;code dir=&quot;auto&quot;&gt;consolidate --push&lt;/code&gt; runs &lt;code dir=&quot;auto&quot;&gt;git push&lt;/code&gt; with no timeout, no prompt guard, to the literal &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;), #5859 (two rules for which remote: the existence probe and the freshness check disagree), #5860 (a credential dialog through &lt;code dir=&quot;auto&quot;&gt;GIT_ASKPASS&lt;/code&gt; or a GUI helper can still appear, and a hang can outlive the timeout on Windows), #5861 (&lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; does not predict &lt;code dir=&quot;auto&quot;&gt;ORIGIN_*&lt;/code&gt; refusals).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The literal &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; survives in push safety and push.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;’s default remote, the &lt;code dir=&quot;auto&quot;&gt;phase_finalize&lt;/code&gt; push, &lt;code dir=&quot;auto&quot;&gt;consolidation/preflight.py:307&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;orchestrator_api/consolidation.py:170&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_branch_context.py:228&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination/policy.py:112&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;core/git_ops.py:331&lt;/code&gt; still name &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;. FR-015 keeps push safety unchanged, so they stay; a non-&lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; freshness test pins the new rule where it applies.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; refreshes the target branch twice in the &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; topology&lt;/strong&gt;: once for the evidence check (the evidence branch is the target there) and once in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;. Correct, one extra bounded contact.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;write_target&lt;/code&gt;’s #4979 probe&lt;/strong&gt; still answers its own existence question with the all-remotes semantics; the owner hosts it but it does not use the FR-017 rule.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;run_git&lt;/code&gt;’s timeout does not reap a grandchild on Windows.&lt;/strong&gt; On POSIX the timeout kills the child and returns. On Windows &lt;code dir=&quot;auto&quot;&gt;subprocess.run&lt;/code&gt; keeps reading pipes a grandchild (an &lt;code dir=&quot;auto&quot;&gt;ssh&lt;/code&gt; hung on a prompt) still holds, so a hang can outlive the timeout. Pre-existing, shared with &lt;code dir=&quot;auto&quot;&gt;remote_probes&lt;/code&gt;; a follow-up, not changed here.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;protection_policy&lt;/code&gt;’s default-branch probe still uses &lt;code dir=&quot;auto&quot;&gt;remote show&lt;/code&gt;.&lt;/strong&gt; Swapping it for &lt;code dir=&quot;auto&quot;&gt;ls-remote --symref&lt;/code&gt; would drop that argv form from the census, but changes its argv and needs a characterization test; deferred.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Not covered, linked follow-ups:&lt;/strong&gt; an origin check at the approval transition itself (&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt;), which the consolidate lane check covers at the terminus; &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; on an existing lane (reuse, crash recovery, dependency tips); &lt;code dir=&quot;auto&quot;&gt;doctor coordination&lt;/code&gt; staleness against the remote; a &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; finding for missing merge-driver settings; renaming the &lt;code dir=&quot;auto&quot;&gt;*Sync*&lt;/code&gt; identifiers in &lt;code dir=&quot;auto&quot;&gt;push_preflight&lt;/code&gt;. Linked only (same family, separate seams): #5460, #5465, #4955, #5644, #5778, #2273.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
