# Contradiction Model

## Principle

A Tile can carry several incompatible claims because the Oracle models discourse, not a single compulsory ontology. Contradiction is represented explicitly through claim layers, evidence states, sources, and typed graph edges. It is not resolved by averaging every account into “somewhere in between.”

## Examples

**Fifteen-Minute City** contains a documented urban-planning practice and a separate political mythology of enforced enclosure. Evidence for the planning model does not validate the control narrative. **MKULTRA** contains documented state abuse and later expansions; verified misconduct must not certify every subsequent allegation. **Med Bed** is a useful symbolic technology of complete repair, while current miracle-device claims are contradicted by available evidence and can cause health harm.

## Data Rule

Each claim records layer, Material Modes, Evidence State, summary, and source IDs. Relationships carry a rationale and provenance kind. “Contrasts-with,” “later-mythologized-as,” “fictionalizes,” and “contextualizes” allow disagreement without inventing a generic relationship. When sources disagree, retain both and narrow the claim to what each can actually establish.

## Reading Rule

State which layer is being read. Offer at least one rival explanation. Name what evidence would increase or decrease confidence. Preserve symbolic value without using it as literal proof. If no concept-specific source exists, mark the gap and treat the history as a research lead.
