# kaal:claim:7314479-045

**Claim.** 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.

**Type.** normative  **Support.** argued

**Holds when.**

- engineered reputation layers

**Source quote.**

> 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.

**From.** Wulf A. Kaal, *Institutional Requirements for Sovereign Local Agent Runtimes* (2026), IX. Why Reputation Carries the Load, and Why It Must Be Engineered, page 22

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

**Verify.** sha256 of source PDF `debace24a155ae924a155b1fafe98856d98cf83689feff2f87a32f1c06171ce6` at https://raw.githubusercontent.com/wulfkaal/Academic-Papers/main/papers/pdf/Kaal%20-%202026%20-%20Institutional%20Requirements%20for%20Sovereign%20Local%20Agent%20Runtimes.pdf

**Topics.** reputation, governance-design, decentralization

**Canonical form.** This markdown file is the canonical hashed representation of the claim. Its sha256 is the content hash used for attestation.