A phenomenon should never become its own rule, and a rule should never float without an interpretive anchor. Canonical cross-references exist to keep those layers distinct and connected.
Operational definition
A canonical cross-reference system is an internal architecture that links observed phenomena to the map that governs them, and the map to the doctrinal layer that justifies it. Its purpose is to reduce internal competition and preserve the hierarchy of explanatory layers.
Why cross-references are indispensable
Without governed cross-references, a corpus starts competing with itself. Phenomena pages begin acting like doctrine, doctrine pages absorb examples, and maps lose their operational role. Cross-references restore stable routes: symptom → constraint → principle.
Types of canonical cross-reference
- Rule reference: from a phenomenon to the map that governs it.
- Illustration reference: from a map to a phenomenon that exemplifies it.
- Dependency reference: from a map or phenomenon to the doctrine that grounds it.
- Definition reference: to stabilize the vocabulary of the involved objects.
- Navigation reference: to prevent internal orphaning and semantic competition.
Design principles
- Do not let a phenomenon page prescribe the full rule set that belongs to a map.
- Do not let a doctrine page absorb every example and lose its stability.
- Make the direction of the reference explicit when the relation is asymmetrical.
- Use cross-references to reinforce authority hierarchy, not to multiply equivalent pages.
- Audit cross-links when adding new maps or doctrinal layers.
What this system prevents
- Internal pages competing to define the same thing in different ways.
- Symptoms being mistaken for canonical rules.
- Doctrine losing stability by absorbing local examples and local fixes.
- Readers navigating the corpus without a stable interpretive route.
