Skip to content

v0.6.0 — claim ledger

Choose a tag to compare

@thejohnd0e thejohnd0e released this 06 Nov 22:47
· 15 commits to master since this release

Claim ledger

A debate now keeps track of every argument and what became of it.

Each debate reply ends with a short service block: its new claims, and a verdict on every open claim of the opponent (rebutted or accepted). The plugin does the bookkeeping:

  • Numbering. It numbers the claims (A1, A2, B1…) itself.
  • Open claims. It tells each side which of the opponent's claims are still open, so nothing gets lost three turns later.
  • Clean text. The block is cut from the reply, even while it streams.

What you see:

  • Under each reply: • Answers A1 rebutted · new B1. A warning appears when a claim of the opponent was left open, or when the block could not be read.
  • Below the discussion: a Claims list with each claim and its state: never answered, rebutted or accepted by the opponent.
  • Conclusion: written from the ledger. Accepted claims are candidates for agreed; rebutted and unanswered ones go to disagreed, and unanswered ones are named as such.
  • Handoff: a Claims ledger section listing every claim with its author's model and its fate.

Accepting a good argument is a valid way to close a claim, not a failure: only claims left without an answer are flagged.

Fixes found in live debates

  • A block without its opening tag is read. One model wrote the ledger lines and [/ledger] but never [ledger], and all of its claims and verdicts were lost. A block is now also found by its closing tag, or as a trailing run of claim and verdict lines. Markdown emphasis, bullets, dashes and a code fence around the block are tolerated too.
  • Two quotes on adjacent lines are two quotes. They used to be joined into one passage and reported as "not found".
  • Recycled quotes no longer count. Only the opponent's own words count as an answer. A reviewer noticed that a model could quote back its own earlier sentence, taken from the opponent's > lines, and pass the check. Such quotes are now flagged: "quotes its own words back, not the opponent's".
  • The first failed reply ends the run. A provider error, timeout, empty reply, or an output limit used up by reasoning now stops the run, with no further replies and no conclusion. Before, the run went on: in a debate the other side answered the same old reply again and again, and the run cost more.
  • A warning for small caps in a debate. A debate reply carries quotes, answers and a claims block. Below 3000 tokens per reply, reasoning models can use up the cap before writing anything, so the start dialog and /discuss-settings now warn.

Verified

A live 3-round debate on OpenCode 2.2.5 (DeepSeek Flash vs GPT-6 Luna, 6000 tokens, conclusion by B): completed with 7 of 7 requests, $0.0047.

  • Every reply's ledger was read, and every open claim was answered on the next turn: two rebutted, five accepted.
  • Only the last claim stayed open, as it must.
  • Replaying that run with the recycled-quote fix flags exactly the one reply that quoted its own words back.

207 unit tests, 32 Python bridge tests and both smoke tests pass.

Full changes: v0.5.0...v0.6.0