Start here · The design strand

Two Readings of the Same Sword

Two players inspect the same object. Both build a coherent theory. Both are wrong. This is the whole design in one example, and it needs nothing you haven't already got from the mechanism pages: an object, some properties, and a player who has to guess what it means.

The artefact

A bronze short sword with wave-pattern engravings, found at a coastal site. The handle is wrapped in ray skin. The blade shows use-wear. There's a small turquoise inlay near the hilt.

Every property in that sentence is true. Nothing about it is hidden, faked or withheld. What happens next is entirely about which properties a player notices first, what those properties suggest to them, and what they go looking for next; none of that is under the player's conscious control. It's under the lens's.

Player A: “a maritime trading civilisation”

Player A has already published a hypothesis that this culture traded by sea. Their lens foregrounds the ray skin first, a rare imported material surely, then the wave engravings, then the coastal findspot. The bronze reads as a trade good. The turquoise inlay reads as a mark of status. The system offers cross-references to other coastal finds and other imported materials, because those are the artefacts Player A's prior claims already point at.

The description they're given: “A finely crafted bronze blade wrapped in ray skin, a material suggesting maritime connections. Wave-pattern engravings adorn the blade. A turquoise inlay near the hilt indicates status or ceremonial significance.”

Player A concludes: prestige item, maritime trade network. Consistent. Well-argued from what they were shown. Wrong.

Player B: “a warrior society”

Player B is carrying the opposite prior. Their lens leads with the use-wear, combat evidence, then the blade itself, then the handle wrapping, read now as a functional grip rather than an imported luxury. The engravings and the turquoise are still there, still true, but they arrive last and land as decoration on a weapon rather than as the point of the object. The cross-references offered are other weapons, other worn edges.

Their description: “A combat-worn bronze short sword with a practical ray-skin grip. The blade shows clear signs of use in cutting or striking. Wave-pattern engravings run along the flat of the blade.”

Player B concludes: functional weapon, martial culture. Also consistent. Also wrong.

What it actually is

The culture is a fishing community. The “sword” is a large fish-processing knife. The wave engravings are exactly what they look like: a reference to the sea, made by people who fished it. The ray skin is local, because they fish rays. The turquoise comes from a nearby deposit. The use-wear is from gutting and scaling, not combat.

Neither player fabricated anything. Neither player was shown a false fact. Each built an internally consistent reading from true observations, in an order and with an emphasis their own prior belief supplied, and the lens will keep reinforcing whichever reading they picked, on every artefact that follows, until something forces a contradiction.

bronze blade, wave engravings, ray-skin wrap, use-wear, turquoise inlay Player A’s lens ray skin first, then engravings, then coastal context → “maritime trade prestige item” Player B’s lens use-wear first, then blade, then grip → “combat weapon, martial culture” what it is: a fishing community’s fish-processing knife
Same true properties, two priors, two divergent and equally wrong readings. The truth was never hidden; it just wasn't foregrounded for either player.
Where this goes next This example is doc 04's own worked case (§5), reused here because it makes the point without requiring anything else on this site. Every other design page explains one piece of the machinery that produces this outcome on purpose: which channels shaped what each player saw, why the turquoise's true origin was invisible rather than merely unmentioned, and what happens once one of these players publishes.
Where it lives Spec: docs/04-interpretive-lens.md §5 · Types: src/lib/types/lens.ts, src/lib/types/interpretation.ts