kaal:claim:7314479-041

Reputation standing should anchor to the SHA-256 of the tool artifact, paired with a publisher-level link and a controlled migration rule under which standing carries across versions only by an explicit, recorded act.

Hash-bound standing therefore needs a publisher-level link and a controlled migration rule, under which standing carries across versions only by an explicit, recorded act. The identity-cost precondition Part IX names is met by that pairing, not by the hash alone.

Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026), VIII. Engineering Contributions, Contribution 4, p. 19
https://ssrn.com/abstract=7314479 · source PDF

Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026). SSRN: https://ssrn.com/abstract=7314479

• introduction of a reputation layer into a sovereign runtime

designsupport: arguedreputationconsensus-and-securityai-and-agents

The quote above is an exact passage from the source PDF, whose sha256 is debace24a155ae924a155b1fafe98856d98cf83689feff2f87a32f1c06171ce6.
Verify the binding yourself: curl -s https://wulfkaal.github.io/claims/7314479-041.md | sha256sum