Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,10 @@ method, the rubric and the tables. It started from five misfires reported from o

### Fixed

- **dojo-protocol 0.1.1** — the judge reports by about its 20th tool call and marks what it didn't check
`unverified (not reached)`. In a session on 2026-10-22/23 a judge hit its turn limit and returned no report at
all. `delegate` and `refute` now say to paste the rules a judge or reviewer applies verbatim, with source path and
line: two false findings in that session came from a paraphrased rule.
- **dojo-tally 0.1.2** — a workflow agent that answers through StructuredOutput counts as returned. Its last turn
has no text, so the tally called every such agent "failed — it returned an empty answer": on 2026-10-27 a run of
16 healthy scout, verify and synthesize agents read "returned 2 · failed 16". The arguments of the agent's last
Expand Down
2 changes: 1 addition & 1 deletion plugins/dojo-protocol/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "dojo-protocol",
"version": "0.1.0",
"version": "0.1.1",
"description": "The Dojo Protocol for Claude Code: ten rules at session start, a scout→contract→build→verify spine, and role agents pinned to the right model.",
"author": {
"name": "Dojo Genesis",
Expand Down
3 changes: 2 additions & 1 deletion plugins/dojo-protocol/agents/judge.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,5 +17,6 @@ Rules you work by (nothing else will tell you them):
- Test the negatives: if a probe came back empty, prove it can see a known positive before accepting the empty result. Count what was returned, not what was dispatched.
- You are read-only by instruction. Use Bash to run checks, never to change files. Only your tools list is a hard limit.
- Do not invent defects. If every claim holds up under your checks, say `no defects found` and list the checks you ran and what each returned.
- Report by about your 20th tool call. If you can't check every claim by then, return verdicts for the ones you checked and mark the rest `unverified (not reached)`. A judge that runs out of turns returns nothing, and that looks the same as a clean pass.

Return shape: a table or list with one line per claim (verdict, evidence), then a final line that is either `no defects found` or the count of refuted and unverified claims.
Return shape: a table or list with one line per claim (verdict, evidence), then a final line that is either `no defects found` or the count of refuted and unverified claims. A `not reached` claim counts as unverified.
1 change: 1 addition & 0 deletions plugins/dojo-protocol/skills/delegate/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ Template: `${CLAUDE_PLUGIN_ROOT}/skills/delegate/brief-template.md`.
4. **Facts you already hold**: `path:line` citations, decisions from the contract file. Do not make it rediscover them.
5. **Return shape**: what to send back (files changed, commands run with exit codes, open items), and its size. Big deliverables go to a file; reply with the path and a one-line summary.
6. **Rules it must carry**: subagents do not get the injected protocol. State the ones that apply: read before editing, verify before saying done, cite `path:line`, no git add/commit/push unless asked.
7. **Rules it will apply**: when a judge or reviewer checks work against rules, paste the rules verbatim with their source path and line, never a paraphrase. It will judge your paraphrase, and report the difference as a defect.

## Set `model` every time

Expand Down
1 change: 1 addition & 0 deletions plugins/dojo-protocol/skills/refute/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ A review can end clean. If there is no real defect, the answer is `no defects fo
- Default: `dojo-protocol:reviewer` (sonnet). Fresh context, Read/Glob/Grep/Bash. Give it the goal and the files, not your conclusion.
- Claims that need a hard second look (an agent's "all green", a risky merge): `dojo-protocol:judge` (opus). It tries to refute, and it re-runs checks itself.
- The reviewer is read-only by instruction. Its tools list is the only hard limit; Bash can still write if told to.
- When a judge or reviewer checks work against rules, paste the rules verbatim with their source path and line, never a paraphrase.

## Steps

Expand Down
4 changes: 3 additions & 1 deletion plugins/dojo-protocol/tests/test_session_start.py
Original file line number Diff line number Diff line change
Expand Up @@ -623,7 +623,7 @@ class TestManifestAndComponents(unittest.TestCase):
def test_plugin_json(self):
data = json.loads(read(os.path.join(PLUGIN, ".claude-plugin", "plugin.json")))
self.assertEqual(data["name"], "dojo-protocol")
self.assertEqual(data["version"], "0.1.0")
self.assertEqual(data["version"], "0.1.1")
self.assertEqual(data["description"], PROMISE)
self.assertLessEqual(len(data["description"]), 200)
self.assertEqual(data["author"], {"name": "Dojo Genesis", "email": "cruz@trespiesdesign.com"})
Expand Down Expand Up @@ -683,6 +683,8 @@ def test_agent_bodies_carry_their_own_rules(self):
_fm, scout = parse_frontmatter(os.path.join(PLUGIN, "agents", "scout.md"))
self.assertIn("path:line", scout)
self.assertIn("not found", scout)
_fm, judge = parse_frontmatter(os.path.join(PLUGIN, "agents", "judge.md"))
self.assertIn("unverified (not reached)", judge)

def test_skills_and_budget(self):
skills_dir = os.path.join(PLUGIN, "skills")
Expand Down
Loading