Check our claims yourself

Every claim on this site points at evidence you can rerun. Start with the checker in a clone of the repository:

git clone https://github.com/event4u-app/agent-config && cd agent-config
npm ci
./scripts-run src/scripts/check_claims

How it works

• A ledger of claims. Each public claim has an entry in the claims ledger with its evidence — a test, a benchmark report or a file:line — and a status. Only a backed entry may be cited.
• The build checks the pages. A number on the README or on a hand-written page of this site must carry a marker pointing at a backed entry; one that does not fails the check.
• We publish what did not hold. Measured nulls stay published, and features are retired or narrowed when the evidence does not support them; every published null links the run that produced it.

Where to look

• Verify it yourself — the claims, the nulls and the known limits, with the commands to reproduce them.
• Discipline benchmark — every run, including the ones that showed nothing.
• Benchmark & cost, explained — the same results in plain words.
• What leaves your machine — every network call, and how to switch it off.