DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to detect any edited forecast in a ledger file with Brier

Run the verify command to find the exact line where a sealed probability was changed.

Short answer: Place the ledger file in the Brier project folder; then run brier ledger --verify; if it reports a break, note the line number it names. All steps.

  • Research
  • Beginner
  • 15 minutes
  • From the README
  • Any agent

Who it is forSomeone who received a forecast ledger from another person or team and needs to confirm no answer was edited after it was sealed.

The problemA forecast file can be quietly altered after the fact, which makes past accuracy claims impossible to trust.

The outcomeA verification result confirming the chain is intact, or naming the first line where the hashes stop matching.

What you need first

  • A terminal with Node.js and npx, since the README's commands run through npx
  • An API key in a .env file, only if you want your own models on the board
  • A wallet you control, only if you want to anchor the head hash on Robinhood Chain

Steps

  1. Place the ledger file in the Brier project folder.
  2. Run brier ledger --verify.
  3. If it reports a break, note the line number it names.
  4. Compare that line against the original source you trust before drawing any conclusion.

Prompt for your agent

In the Noisyxl/brier repo, run `brier ledger --verify` on the ledger file at <path-to-ledger>. Report whether the chain is intact, and if not, the exact line the command names. Verify the output text before stating a result.

Caveat. The hash chain proves the file was not edited, but it does not by itself prove when a forecast was sealed, which is what anchoring is for.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for Noisyxl/brier and "Detect any edited forecast in a ledger file"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer