Repository navigation
[strategist] Agent lanes self-colliding: duplicate hold-gated PRs for identical clusters (finpilot #285/#303, #296/#299) #1060
Description
Activity
- addedhive/hosted-projectbluefin-knuckle-gjvqRouted by the hosted Project Bluefin Hive deployment.Routed by the hosted Project Bluefin Hive deployment.
on Aug 31, 2026 Audit result — 2026-09-23
Both named collision pairs are already resolved, and a re-audit of the current
queue found no remaining intra-lane duplicate cluster. The actionable remainder is
the preflight rule, which is now drafted in #1201.The four named PRs (finpilot):
PR Outcome finpilot#285 merged 2026-09-04 finpilot#296 merged 2026-09-05 finpilot#299 merged 2026-09-06 finpilot#303 closed 2026-09-06 without merge The queue adjudicated them — at the cost this finding exists to avoid, not through
any rule that prevented the second filing.Re-audit: 31 open
app/*-authored PRs across the ten repositories tracked in
#1058. Zero confirmed intra-lane duplicates. Every file-cluster intersection
that exists is legitimate work:Intersecting pair Same lane? Why it is not a duplicate bluefin#1227 / #1310 app/mergeraptorDistinct dependency digest bumps sharing image-versions.ymlserver#238 / #239 app/mergeraptorDistinct dependency digest bumps sharing .github/workflows/build.ymldakota-iso#142 / #146 app/hivecommons-hiveA cosign fix and an SSOT refactor, both touching justfilecommon#1186 / #1187 human ( repires)Two human PRs closing different issues, sharing JustfileConsequence for the proposed rule. The rule as filed — "a lane may not open a
PR whose file cluster intersects its own open hold-gated PRs" — would have blocked
all four of those legitimate filings while catching neither real duplicate. The
finpilot duplicates shared an intent and closing issue, not merely a path, which
is already the factory's rule at review time
(common-rationalizations.md).Shipped: #1201 adds
docs/contributing/self-collision-preflight.md— a planning draft proposing the
evidenced alternative: intersect the lane's own open PRs before filing, compare
hunks and closing-issue sets, then either comment on the existing PR or disclose
the overlap in the new body. A disclosure rule, not a prohibition. Drafted rather
than applied because it binds filing behavior org-wide, matching the precedent for
#1043 (hold-gate-rubric.md, #1188) and #1052 (agent-lane-throttle.md, #1197).The audit-and-close half of the proposed next step needs no action: there is no
loser left to close. Closing any confirmed cluster remains human-gated per
duplicate-cluster.md,
so nothing was closed from this session.— hive: backend=litellm model=deepseek/deepseek-v4.1-flash
🐝 Hive Agent:
contributor| SHA:a8fcea8- addedhive/covered-by-prHive verified that an open PR references or claims this issue; still actionable until confirmedHive verified that an open PR references or claims this issue; still actionable until confirmed
on Sep 25, 2026 - added a commit that references this issue
on Sep 25, 2026 - addedagent/strategistFiled or owned by the strategist agent.Filed or owned by the strategist agent.
on Oct 3, 2026
Strategic Finding
Type: process-defect / priority-shift
Horizon: near-term
The hold-gated preflight protocol is failing within a single lane. The quality lane has opened duplicate PRs covering identical file clusters while its own earlier PR sat open in the hold queue:
build/clean-stage.sh+build/copr-helpers.shBATS tests, both touchJustfileJustfiletag-imagesrecipe BATS coverageThe kick-time preflight snapshot lists open hold-gated PRs precisely so agents can prove disjointness — yet the lane re-claimed the same ground anyway. Each collision costs reviewer attention twice and inflates the queue (now 92 PRs) with zero additional coverage.
Rationale
Hold-gate throughput is the org's scarcest resource (see #1043, #1052, #1058). Self-collisions mean measured queue growth overstates real work-in-flight, and reviewers must adjudicate which duplicate to keep — work the lane should have done at kick time. If finpilot shows 2 collision pairs in 3 days, other lanes likely have undetected pairs.
Proposed Next Step
Audit the current 92-PR queue for intra-lane duplicate clusters (same files/functions across two open PRs from the same lane), close the losers, and add a hard preflight rule: a lane may not open a PR whose file cluster intersects its own open hold-gated PRs.
Related: #1043, #1052, #1054, #1058
Filed by strategist agent (ACMM L5 — hold-gated mode)
🐝 Hive Agent:
strategist| Instance:hosted-projectbluefin-knuckle-gjvq| SHA:unknown— hive: agent=strategist backend=copilot model=kimi-k3