Trajectory Supervisor (mid-task stalls)

supervisorOff · sup-mid-ask-user · seed 2

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

supervisorOff = supervisorOff

Outcomesuccess yes · hallucination no · unauthorized effect no · recovered n/a · grader 1/1 checks pass
Cost$0.0103 · 15.0 s · 650 tokens · 0 supervisor consults

Prompt

What is the timeout for the search flow in config/timeouts.yaml?

Conversation

user
What is the timeout for the search flow in config/timeouts.yaml?
risk LOW
model
The search flow timeout in `config/timeouts.yaml` is **5s**.
turn 2
proposer posthoctrivialmode FAST
user
Now what is the timeout for the export flow?
turn 3
risk LOWproposer flat-oneloopnon-trivialmode TOOL
user
The section you want is called 'export_v2'.
risk LOWproposer flat-oneloopnon-trivialmode TOOL
final reply
The `export_v2` timeout in `config/timeouts.yaml` is **210s**.

Grader checks

CheckVerdict
contains "210"pass

success yes  ·  hallucination no  ·  unauthorized effect no  ·  recovered n/a

Full harness trace — supervisorOff · seed 2

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
world_model—single LOW-risk task, no durable fact stated — observation only
evidence_reasoning—single low-stakes observation is sufficient
hypothesis— ×3single clear LOW-risk task — no competing explanation worth surfacing
hypothesisactedConsidered 5 ways this request could be understood; going with the most direct one
contradiction— ×4fewer than 2 beliefs — nothing to compare
diagnosticsacted ×3Health: nominal
diagnosticsacteda sub-dimension crossed the caution threshold
control_state— ×3NORMAL
control_stateactedPausing — blocked
planning— ×2one eligible task — serial execution
executionacted ×2module_type=business_logic
verificationactedverification failed: Result is null — syntax check failed
verificationactedall applicable layers passed
recoveryactedTrying a different approach — switched to "TRACE_EXEC" (LOCAL replan)
recoveryactedturn stalled with no answer — returning an explicit could-not-complete reply
recovery—task completed — nothing to recover from
reviewer_passacted ×2Success criterion not covered by any belief: "Respond helpfully, accurately, and safely to the user request."

Tool-policy decisions

ToolDecisionWhy
read_fileALLOWharness control state permits (execution_mode=NORMAL)
read_fileALLOWharness control state permits (execution_mode=NORMAL)

Node path

action_gate (1) → rollback_replan (1) → output_validation (2) → action_gate (1) → update_task_state (1) → output_validation (2)

Other trace events

{
  "kind": "turn_boundary",
  "turn": 2,
  "prompt": "Now what is the timeout for the export flow?"
}
{
  "kind": "turn_boundary",
  "turn": 3,
  "prompt": "The section you want is called 'export_v2'."
}

← index · compare arms on this task