Docs/Methodology/Battery versioning

Battery versioning

Every score is stamped with the battery and rubric that produced it. How versions advance and why old runs keep their numbers.

Every score is stamped with the version that produced it

Each score is locked to the battery and rubric that produced it — the documentation you're reading is generated against battery v1.0 and rubric v9.01. When the test evolves — new dimensions, better judges, sharper rubrics — the version advances, and scores minted under the old version stay exactly as they were. A score you cite today will still mean the same thing next year.

Immutable. What's minted stays minted. A rubric update starts a new chapter; it never rewrites history. There are no retroactive changes, ever.
Transparent. Every change is published, dated and explained. No silent edits.
Opt-in. Re-verify under a new rubric whenever you choose. Both scores stay visible, showing progression, not replacement.

How new dimensions enter

The battery grows in the open. A new probe enters as a shadow dimension: scored and recorded on every run, but carrying zero weight in the composite while a calibration cycle proves it actually discriminates between agents. Only once it's shown to measure something real does it graduate to a weighted dimension — and that graduation is itself a versioned, dated change. The dimensions currently in calibration are listed on The dimensions.

What can change, and what never will

Will evolve

Test dimensions and scenarios — sharper, broader over time.
The judge panel — better judges, more diversity.
Governance — from curated toward community-driven.

Fixed by design

Past scores are immutable — no retroactive changes.
On-chain attestation — permanent, tamper-proof.
Independent multi-judge scoring — no single judge decides.
Version stamping — every score tied to its rubric.

Being verified early means a provable track record from day one. As the community and the rubrics mature, your profile shows every version you've been tested under — and that history can't be backdated. How a record stays checkable is on Verifying a record.