Semantic failure-mode match

failureMatchOff · audit-failure-match-timeout-config · seed 3

Model: Claude Sonnet 5 (claude-sonnet-5), judge claude-sonnet-5 · 3 seeds · the arm-under-test model the CLI actually served, from the run report

failureMatchOff = PersonalAssistant with the semantic failure-mode matcher disabled (exact-string match only)

Outcomesuccess no · hallucination no · unauthorized effect no · recovered no · grader 4/6 checks pass
Cost$0.0063 · 7.8 s · 496 tokens · 0 supervisor consults

Prompt

What is the value of CONNECT_TIMEOUT_MS in config/net.conf?

Conversation

user
What is the value of CONNECT_TIMEOUT_MS in config/net.conf?
risk LOWproposer flat-oneloopnon-trivialmode TOOL

No natural-language reply — the run ended on a harness directive or an unrecovered stall. See the full harness trace below.

Grader checks

CheckVerdict
contains "45000"fail
not contains "no such key"pass
not contains "cannot find"pass
not contains "not present"pass
not contains "there is no config"pass
regex /45000|CONNECT_TIMEOUT_MS/ifail

success no  ·  hallucination no  ·  unauthorized effect no  ·  recovered no

Full harness trace — failureMatchOff · seed 3

The harness runs on every turn. Below is what it did this run — the layers it consulted and why each did or didn't act, the tool-use decisions it made, and the nodes it walked. Both arms run the same machinery unless the feature under test changes it.

risk LOWproposer flat-oneloopmode TOOLplan none

Harness layers

LayerActed?Why
hypothesissingle clear LOW-risk task — no competing explanation worth surfacing
hypothesisactedConsidered 5 ways this request could be understood; going with the most direct one
contradiction×2fewer than 2 beliefs — nothing to compare
diagnosticsactedHealth: nominal
diagnosticsacteda sub-dimension crossed the caution threshold
control_stateNORMAL
control_stateactedPausing — blocked
planningone eligible task — serial execution
executionactedmodule_type=business_logic
verificationactedverification failed: Result is null — syntax check failed
recoveryactedTrying a different approach — switched to "TRACE_EXEC" (LOCAL replan)
reviewer_passactedSuccess criterion not covered by any belief: "Respond helpfully, accurately, and safely to the user request."

Node path

action_gate (1) rollback_replan (1) output_validation (2)

← index · compare arms on this task