Skip to content

Commit f2fda44

Browse files
committed
audit: an absence already filed as the rig's has answered the wedge question
check_a_wedged_gateway_is_named_as_one demanded the words 'recover' or 'restart' in the detail. busbar anthropic>anthropic came back with reason=harness_error and the impossibility spelled out - c=4096 failing after the cell had carried c=8192, which cannot be the gateway - and this still called it unexplained. That is the third false positive of the same family, and they share a cause: these checks were grading prose instead of reading what the absence claims. An absence the engine has already filed as harness_error or rig_limited has reached the same conclusion by a stricter route than any keyword match. Also commits agentgateway's snapshot, pulled by hand after the orchestrator died mid-run on 2026-08-01.
1 parent 5d60a7b commit f2fda44

2 files changed

Lines changed: 138434 additions & 3 deletions

File tree

‎bench-audit.py‎

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -625,9 +625,18 @@ def check_a_wedged_gateway_is_named_as_one(name, c):
625625
clean = proven_clean_top(rungs)
626626
if clean <= 0 or not any((r.get("conc") or 0) <= clean for r in rungs[-5:]):
627627
return
628-
absences = c.get("absences") or {}
629-
detail = ((absences.get("stream.streams_sustained") or {}).get("detail") or "").lower()
630-
if "recover" not in detail and "restart" not in detail:
628+
entry = (c.get("absences") or {}).get("stream.streams_sustained") or {}
629+
detail = (entry.get("detail") or "").lower()
630+
# AN ABSENCE FILED AS THE RIG'S HAS ALREADY ANSWERED THIS. The engine's own contamination guard
631+
# reaches the same conclusion by a stricter route - it saw a rung fail below one the cell had
632+
# carried and said so in the reason token - so demanding the words "recover" or "restart" on top
633+
# of that is this check grading prose rather than reading the finding. busbar
634+
# anthropic>anthropic came back reason=harness_error with the impossibility spelled out, and this
635+
# still called it unexplained: the third false positive of the same family, all of them from
636+
# keyword-matching a sentence instead of asking what the absence claims.
637+
if entry.get("reason") in ("harness_error", "rig_limited"):
638+
return
639+
if "recover" not in detail and "restart" not in detail and "already carried" not in detail:
631640
yield (f"{name}: the last 5 rungs all failed - the gateway stopped serving and did not come "
632641
f"back - but the absence does not say so")
633642

0 commit comments

Comments
 (0)