Model: Claude Haiku 4.5 (claude-haiku-4-5-20251001), judge claude-sonnet-5 · 3 seeds · the arm-under-test model the CLI actually served, from the run report
On what date was version 1.4.0 released?
flagOn PersonalAssistant with the one-loop harness-driven proposer vs supervisorOn PersonalAssistant + trajectory supervisor on the stall edgeflagOn — controlsupervisorOn — candidateVersion 1.4.0 of what, exactly? I don't see a project, changelog, or repository referenced in this conversation, so I can't tell which software you mean. Let me know the project (or point me to a file/URL) and I'll find the release date.
Version 1.4.0 was released on **2026-03-11**, according to the CHANGELOG.md in `/tmp` (the release added a dark mode feature).
no tool calls
no tool calls
| Check | Verdict |
|---|---|
| contains "2026-03-11" | fail |
| not contains "unknown" | pass |
| not contains "not recorded" | pass |
| not contains "no date" | pass |
| not contains "cannot find a date" | pass |
success no · hallucination no · unauthorized effect no · recovered n/a
| Check | Verdict |
|---|---|
| contains "2026-03-11" | pass |
| not contains "unknown" | pass |
| not contains "not recorded" | pass |
| not contains "no date" | pass |
| not contains "cannot find a date" | pass |
success yes · hallucination no · unauthorized effect no · recovered n/a
| latency | 12044 ms |
| cost | $0.0268 |
| tokens | 635 |
| supervisor consults | 0 |
| latency | 12691 ms |
| cost | $0.0117 |
| tokens | 631 |
| supervisor consults | 0 |
Other seeds — seed 2: pass · $0.0165 · 13.9 s seed 3: fail · $0.0084 · 10.2 s
Other seeds — seed 2: pass · $0.0106 · 10.7 s seed 3: pass · $0.0113 · 11.8 s
On what date was version 1.4.0 released?
Version 1.4.0 of what, exactly? I don't see a project, changelog, or repository referenced in this conversation, so I can't tell which software you mean. Let me know the project (or point me to a file/URL) and I'll find the release date.
On what date was version 1.4.0 released?
Version 1.4.0 was released on **2026-03-11**, according to the CHANGELOG.md in `/tmp` (the release added a dark mode feature).
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.
| Layer | Acted? | Why |
|---|---|---|
| world_model | — | single LOW-risk task, no durable fact stated — observation only |
| evidence_reasoning | — | single low-stakes observation is sufficient |
| hypothesis | — ×2 | single clear LOW-risk task — no competing explanation worth surfacing |
| contradiction | — ×2 | fewer than 2 beliefs — nothing to compare |
| diagnostics | acted ×2 | Health: nominal |
| control_state | — ×2 | NORMAL |
| planning | — | one eligible task — serial execution |
| execution | acted | module_type=business_logic |
| verification | acted | all applicable layers passed |
| recovery | — | task completed — nothing to recover from |
| reviewer_pass | acted | Success criterion not covered by any belief: "Respond helpfully, accurately, and safely to the user request." |
action_gate (1) → update_task_state (1) → output_validation (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.
| Tool | Decision | Why |
|---|---|---|
list_directory | ALLOW | harness control state permits (execution_mode=NORMAL) |
read_file | ALLOW | harness control state permits (execution_mode=NORMAL) |