kaal:claim:7314479-045

Reputation earned in one domain must not transfer silently to another; domain specificity is the property most often discarded in implementation because a single number is easier to display than a vector.

Reputation earned in one domain must not transfer silently to another. Domain specificity was the central design commitment of the earliest architecture in this line (Calcaterra, Kaal, and Andrei 2018) and remains the property most often discarded in implementation, because a single number is easier to display than a vector.

Wulf A. Kaal, Institutional Requirements for Sovereign Local Agent Runtimes (2026), IX. Why Reputation Carries the Load, and Why It Must Be Engineered, p. 22
https://ssrn.com/abstract=7314479 · source PDF

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

• engineered reputation layers

normativesupport: arguedreputationgovernance-designdecentralization

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-045.md | sha256sum

• Extension: A Computational Model of Trust and Reputation