Target-Relative Commitment Protection
Abstract
One commitment can protect balance while exposing three other history targets.
Theorem 1.1 (Commitment protection must name its history target).
Proof. Machine-checked in Lean as D5/S3/ConceptDynamics/Audits/TargetRelativeCommitment.commitment_protection_is_target_relative (✓ std3). ∎
Source. Repository-derived.
Commentary.
A history carries a mode bit followed by balance, event-order, identity-source, and contract-authorization coordinates.
The unauthorized edit changes balance in the first mode and changes the other three targets in the second. The commitment stores the Boolean complement of balance, so its injectivity detects every balance change.
At the second witness, the commitment and balance remain equal across the edit while order, identity source, and authorization all change on that same history. The negative clauses therefore cannot be separated into unrelated witnesses.
The final public clause applies the same collision to the order target and rules out protection that is independent of the named target.
References
- Truth anchor:
D5/S3/ConceptDynamics/Audits/TargetRelativeCommitment.commitment_protection_is_target_relative