Turn benchmark results into claims that hold up.

Your team knows what went into the result. Everyone else has to take your word for it. Colophon closes that gap with a public claim people can inspect for themselves.

A real published claimSelf-run

Judging the LoCoMo judges

A controlled benchmark of the grading prompts behind published LoCoMo scores. Six grading configurations judged the same 240 answers on the same model snapshot.

What it found

Changing only the grader moved agreement with the same labels from 60.8% to 87.9%.

4,320 of 4,320planned calls accounted for

For results that need to leave the room.

A benchmark becomes valuable when people beyond its authors can rely on it.

You are publishing a benchmark

Give the result a permanent place people can cite, inspect, and return to.

You are making a performance claim

Give customers, reviewers, and competitors something stronger than your word.

You are relying on a result

Put a clear public record behind a product, research, or procurement decision.

Run it where you already run it.

You run the benchmark on the harness you already use, and bring the run back to be sealed. The published claim names who ran it.

Lock the method first

Fix the tasks, setups, repetitions and grading before the run, so the method cannot be changed once results are in.

Bring the run back

Every planned result is accounted for, failures included, and the claim is sealed with its evidence attached.

Anyone can check the claim.

Checking is free. It stays free.

Get the files from the LoCoMo report
npx @colophon-claims/verify@0.2.1 ./bundle

The checker is available on npm.

Publishing your own claim

Checking a published claim is free, and needs nothing from Colophon. Publishing your own claim from this site is not available yet. Until it is, write to ritsu.kai2000@gmail.com to publish.