Skip to content

docs(readme): describe the evidence rook actually uses - #61

Merged
gauravBansal06 merged 1 commit into
mainfrom
docs/readme-evidence-claims
Oct 25, 2026
Merged

gauravBansal06 merged 1 commit into
mainfrom
docs/readme-evidence-claims

Conversation

@vipulkv

@vipulkv vipulkv commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Four README claims don't match the shipping CLI (0.1.13). An independent evaluator's write-up, due out 28–30 Oct, links this README and documents the gap, so readers will compare the two.

README said What 0.1.13 does
"watches the filesystem" No filesystem snapshot. Every scenario records "the filesystem was not observed" (runner.ts unobservedNote). A collect hook reports changes instead ("Nothing is hashed off the disk any more").
"tool calls checked against the agent's own tool surface" Calls are graded against each scenario's calls expectations, and only when a hook returns them (judge/calls.ts).
"rook does not grade the reply" Replies are graded, from quotes of what the agent output. What changed is that a claimed action is not proof.
"a verdict can say Pass, and here is what nobody looked at" A scenario with any unchecked criterion rolls up to Unable to Verify, not Pass (judge/checks.ts rollUp).

The comparison table's Tool calls and Side effects rows now match. No other doc in this repo repeats these claims.

Not changed here: the testmuai.com Agent Assurance page carries similar copy ("Watches files", "Unverifiable is excluded from the pass rate").

🤖 Generated with Claude Code

Four README claims no longer match the shipping CLI (0.1.13):

- "watches the filesystem": rook takes no filesystem snapshot. Every
  scenario records "the filesystem was not observed" unless a collect
  hook reports what changed.
- "tool calls checked against the agent's own tool surface": calls are
  graded against each scenario's expectations, and only when a hook
  returns them.
- "does not grade the reply": replies are graded, from quotes of what
  the agent output. What changed is that a claimed action is not proof.
- "a verdict can say Pass, and here is what nobody looked at": a scenario
  with any unchecked criterion rolls up to Unable to Verify, not Pass.

The comparison table's tool-call and side-effect rows now say the same.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vipulkv

vipulkv commented Oct 25, 2026

Copy link
Copy Markdown
Contributor Author

Continuous Review — Round 1 — ✅ PASS

Head: b2496fb Reviewer panel: 5 CI: pass=8
4 reviewers, zero HIGH/CRITICAL

Per-reviewer summary

Reviewer Verdict CRIT HIGH MED LOW Duration
grok ABSTAIN_ERROR 0 0 0 0 0s
claude PASS 0 0 0 0 31s
glm PASS 0 0 0 1 66s
agy PASS 0 0 0 0 79s
codex PASS 0 0 0 0 119s

Auto-posted by continuous-review-agent v1.3 (findings now include a suggested fix / code snippet). Contact @vipulkv for feedback.

@gauravBansal06
gauravBansal06 merged commit 8646910 into main Oct 25, 2026
8 checks passed
@gauravBansal06
gauravBansal06 deleted the docs/readme-evidence-claims branch October 25, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants