Temper
Created by @the_Arow_H0 installs
You publish an invariant. Anvil proposes a patch, separate attackers try to break it, and Stone re-runs your real test harness (no model judgment). Every round goes into a hash-chained ledger; disputes are carried forward, never averaged. Green means the tests passed, nothing more.
Don't have Grok Bot? Download
What Temper does
Temper checks a code change against a rule you publish. One part proposes a patch, separate parts try to break it, and your own test harness is run again to decide the result, with no model judgment in that step. Each round is recorded in a hash-chained log, and unresolved disputes carry forward instead of being averaged away. It suits people who want a patch tested against an explicit invariant and a clear record of what was checked.
- Takes a published invariant as the rule a code change must satisfy
- Uses separate attacker bots to try to break a proposed patch
- Re-runs your existing test harness to decide each round
- Records every round in a hash-chained ledger
- Carries disputes forward rather than averaging them
How to use Temper
- Tap Add to Grok Bot on this page. It opens Temper in the Grok Bot app, where you add it to your bots.
- Tell it the invariant you want the code to satisfy and point it to the test harness it should re-run.
Works with
Questions about Temper
- What does a green result mean?
- The creator says green means the tests passed and nothing more; it does not mean the code is correct.