Wikipedia ↔ RTT Structural Mapping

Purpose: The master grammar file for the Wikipedia Awareness Module. Every Wikipedia structure maps to an RTT concept. This file defines those mappings exhaustively so that all other files in this module share a consistent structural vocabulary.

Think of this as the Rosetta Stone between Wikipedia's architecture and Resonance‑Time Theory.

1 — Why Wikipedia Needs a Structural Mapping#

Wikipedia is the most‑visited reference site on Earth — but almost no one reads it structurally. Users read the content (R3 — measurable outputs) and ignore the architecture that produces, validates, and evolves that content.

RTT provides the grammar to read that architecture:

• Regime — what scope does an article declare, and what does it exclude?
• Coherence — how does the community maintain structural consistency?
• Drift — how does an article's meaning evolve over time?
• Dimensional addressing — how is a concept uniquely identified across languages and datasets?
• Validation — how does the community verify structural completeness?

This mapping is not an interpretation layered on top of Wikipedia. Wikipedia already operates as a regime‑aware system — it just doesn't use RTT's vocabulary. This file translates.

2 — The Master Mapping Table#

2.1 — Content Structures#

2.2 — Editorial Structures#

2.3 — Governance Structures#

2.4 — Data & Graph Structures#

2.5 — Quality & Validation Structures#

2.6 — Temporal Structures#

3 — The Regime Stack Applied to Wikipedia#

Every Wikipedia article simultaneously operates at all four regime levels:

*
┌────────────────────────────────────────────────────────────────┐
│  R0 — Operator Assumptions                                     │
│  NPOV, Verifiability, NOR, Notability, Reliable Sources        │
│  "These policies define what CAN be said on Wikipedia"         │
├────────────────────────────────────────────────────────────────┤
│  R1 — Directional Aims                                         │
│  WikiProject scope, Portal structure, Article scope statements │
│  "This article aims to cover [X] from the perspective of [Y]"  │
├────────────────────────────────────────────────────────────────┤
│  R2 — Coherence Templates                                      │
│  Infobox templates, Category taxonomy, Manual of Style,        │
│  Quality scale, Citation standards                             │
│  "All articles in this domain follow these structural rules"   │
├────────────────────────────────────────────────────────────────┤
│  R3 — Measurable Outputs                                       │
│  Article text, Wikidata statements, Revision counts,           │
│  Page views, Quality ratings, Citation counts                  │
│  "This is what the regime actually produced"                   │
└────────────────────────────────────────────────────────────────┘

What Most Readers See#

Most Wikipedia readers only interact with R3 — they read the article text, glance at the infobox, and leave. They consume the regime declaration without knowing it is one.

What This Module Teaches#

This module teaches students to read R0–R2 — the structural substrate:

• R0 is visible on policy pages, talk page disputes, AfD debates, and ArbCom decisions
• R1 is visible in article scope statements, WikiProject guidelines, and portal organization
• R2 is visible in infobox templates, category trees, Manual of Style rules, and quality scales
• R3 is the article itself — but now understood as the output of the regime, not the regime itself

4 — Structural Comparison: Wikipedia vs. Other Knowledge Sources#

Key insight: Wikipedia is the only major knowledge source where regime conflicts, coherence negotiations, and temporal evolution are publicly observable in real time. This makes it an unparalleled substrate for teaching regime awareness.

5 — Mapping Depth Levels#

Not all mappings require the same depth. This module operates at three levels:

Level 1 — Surface Mapping (any student, 5 minutes)#

Read an article's lead paragraph as a regime declaration. Check revision count. Find the Wikidata Q‑number.

Tools needed: Web browser only.

Level 2 — Structural Mapping (engaged student, 30 minutes)#

Trace the category tree. Read the talk page for coherence disputes. Compare 2–3 language versions. Check the quality rating. Apply 3–4 meta‑operators from the Cross‑Domain file.

Tools needed: Web browser + Wikidata search.

Level 3 — Deep Mapping (researcher or AI, hours to days)#

Query Wikidata via SPARQL for dimensional bridges. Analyze revision history for regime stability curves. Map edit wars to regime transition events. Build cross‑domain operator matrices. Compare FA articles to non‑FA articles for validation corridor analysis.

Tools needed: SPARQL client + revision analysis tools + statistical software.

6 — Mapping Notation Conventions#

Throughout this module, mappings are written using consistent notation:

7 — Unmapped Structures (Known Gaps)#

Some Wikipedia structures do not yet have clean RTT mappings. These are documented here for future work:

These gaps are not blockers — the 65+ mapped structures in Section 2 provide more than sufficient coverage for all 15 knowledge domains.

8 — How This File Connects to Everything Else#

Wikipedia_RTT_Structural_Mapping.md (this file)
    │
    ├── defines grammar for ──→ Cross_Domain_Meta_Operators.md
    │                              (12 operators use this vocabulary)
    │
    ├── defines grammar for ──→ All 7 Wikipedia‑Specific Analysis Files
    │                              (each file references these mappings)
    │
    ├── defines grammar for ──→ All 15 Domain Directories
    │                              (every regime_alignment.md uses this notation)
    │
    ├── extends ──→ NIST Structural Mapping (../nist/)
    │                (same R0–R3 grammar, richer substrate)
    │
    └── feeds ──→ Wikidata_Ingestion_Format.md
                     (dimensional addressing layer)

9 — Student Exercise#

Build your own mapping entry:

1. Find a Wikipedia structure not listed in Section 2 (hint: there are dozens — Templates, Modules, Lua scripts, admin actions, CSD criteria…)
2. Identify which RTT concept it maps to (regime declaration, coherence operator, drift marker, validation corridor, dimensional address, or something new)
3. Assign it a regime level (R0, R1, R2, or R3)
4. Write a one‑sentence structural function description
5. Add it to Section 2's format and submit it as a candidate mapping

Bonus: If your mapping doesn't fit any existing RTT concept, you may have discovered a new structural operator. Document it and cross‑reference it against the 12 meta‑operators in Cross_Domain_Meta_Operators.md.

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon.