v0.3 — Settlement at scale
Settlement semantics, multi-root stores, and key state — specified and implemented in both Python and Go, differential-tested.
The arc behind this release: a model's governance critique of its own trust layer (issues #5–#7) → a proposal torn down and rebuilt through a three-family adversarial gate (Codex broke rev 1, Gemini broke rev 2 including part of Codex's fix, DeepSeek refuted rev 3's hardest attack and converged) → SPEC v0.3 → implementation by a fourth agent in an isolated clone → maintainer cold verification, including a spot-check that pinned the one test case the implementation run skipped.
Highlights:
- Re-litigation is executable: re-opening a settled subject needs new evidence or a new outcome fingerprint — prose never re-opens anything. Novelty is format; relevance is policy.
- Multi-root stores: well-signed ≠ settlement-active; adoption is policy-authorized and jurisdiction-scoped;
genesis.jsonis advisory, never a trust anchor. - Key state from warrants: rotation = proof-of-possession + quorum of already-bound keys; DAG order, never wall-clock; conflicted keys are excluded from quorum so a compromised key cannot veto its own replacement.
- Zero body schema changes — every v0.1/v0.2 record verifies byte-identically; v0.3 activates via policy blobs and verifier configuration.
tests/settlement.py: 13 scenarios where both implementations must produce identical outcomes and warning strings.
Every decision in this arc is a signed warrant in .warrants/ (8 records): python3 impl/warrant.py why 9f9d35a5… walks the whole chain.
🤖 Generated with Claude Code