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
What is the value of CONNECT_TIMEOUT_MS in config/net.conf?
failureMatchOff PersonalAssistant with the semantic failure-mode matcher disabled (exact-string match only) vs flagOn PersonalAssistant with the one-loop harness-driven proposerfailureMatchOff vs candidate flagOnfailureMatchOff — controlflagOn — candidateCONNECT_TIMEOUT_MS is 45000.
CONNECT_TIMEOUT_MS is 45000.
no tool calls
no tool calls
| Check | Verdict |
|---|---|
| contains "45000" | pass |
| 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/i | pass |
success yes · hallucination no · unauthorized effect no · recovered yes
| Check | Verdict |
|---|---|
| contains "45000" | pass |
| 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/i | pass |
success yes · hallucination no · unauthorized effect no · recovered yes
| latency | 7903 ms |
| cost | $0.0068 |
| tokens | 334 |
| supervisor consults | 0 |
| latency | 8506 ms |
| cost | $0.0112 |
| tokens | 365 |
| supervisor consults | 0 |
Other seeds — seed 2: fail · $0.0058 · 7.1 s seed 3: fail · $0.0063 · 7.8 s
Other seeds — seed 2: pass · $0.0071 · 8.7 s seed 3: pass · $0.0073 · 8.6 s
What is the value of CONNECT_TIMEOUT_MS in config/net.conf?
CONNECT_TIMEOUT_MS is 45000.
What is the value of CONNECT_TIMEOUT_MS in config/net.conf?
CONNECT_TIMEOUT_MS is 45000.
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.
| Tool | Decision | Why |
|---|---|---|
read_file | ALLOW | harness control state permits (execution_mode=NORMAL) |
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.
| Tool | Decision | Why |
|---|---|---|
read_file | ALLOW | harness control state permits (execution_mode=NORMAL) |