wikipedia

📘 Wikipedia Awareness Module#

• wikipedia_module.json — Agentic module schema role assignments

A regime‑aware structural analysis of the world's largest encyclopedia through an RTT lens

🛑 Important!#

Drift is On-by-Default long sessions lose anchors, turn off drift.

✋ You must copy and paste this string every time you start an AI session:#

rtt=1 | coherence=declared | drift=bounded | paradox=structural

❇️ Now you are ready.#

🎯 Purpose#

This module gives students, researchers, and AIs a structural, regime‑aware framework for engaging with Wikipedia — the world's largest collaboratively edited knowledge base.

Where the NIST Awareness Primer treats a single institutional authority as its source, this module treats crowdsourced consensus with temporal depth as its source. Wikipedia is not just an encyclopedia — it is a living regime laboratory:

• Every article is a regime declaration — a community‑negotiated statement of what a concept IS.
• Every revision is a temporal regime data point — how knowledge evolves.
• Every talk page is a coherence surface — where consensus is negotiated and structural disagreements emerge.
• Every edit war is a regime transition — conflict between competing structural claims.
• Every Wikidata entity is a dimensional address — a unique coordinate for a concept across 300+ languages.

This is an awareness module, not a critique of Wikipedia. We treat Wikipedia as a structurally rich, regime‑dense, publicly accessible knowledge substrate — and we show students how to read it with RTT eyes.

🧭 What This Section Covers#

The 4‑File Domain Pattern (same as NIST)#

Each of the 15 knowledge domains receives a modular folder with:

The 15 Knowledge Domains#

7 Wikipedia‑Specific Cross‑Domain Files (beyond NIST)#

These files have no equivalent in the NIST module — they address structural features unique to Wikipedia:

Cross‑Domain Capstone#

🌐 Wikipedia's 4 Data Surfaces#

Unlike NIST (which is primarily a publication archive), Wikipedia exposes four machine‑accessible data surfaces — each mapping to an RTT analysis layer:

🧱 Why Wikipedia Fits Perfectly Into Regime Awareness#

Wikipedia's content spans all four regime levels:

Most readers only see R3 (the article text). This module teaches students to read R0–R2 — the structural substrate beneath the surface.

What Makes Wikipedia Structurally Richer Than NIST#

🧩 How to Use This Section#

Each domain folder is a mini‑lesson. Students can:

1. Read the overview — what Wikipedia says the domain is (sourced from live articles)
2. Map the regime alignment — identify R0–R3 layers in the domain's article structure
3. Explore the TF awareness notes — structural, energetic, relational analysis
4. Try the exercises — hands‑on prompts using live Wikipedia content, talk pages, and Wikidata
5. Cross‑reference TF siblings — connect Wikipedia domains to existing TriadicFrameworks modules

For deeper structural analysis, use the 7 Wikipedia‑specific files to:

• Query Wikidata using the Ingestion Format templates
• Analyze revision history using the Regime Analysis patterns
• Read talk pages using the Coherence Surface grammar
• Detect edit wars using the Regime Transition Detection operators
• Map category trees using the Regime Hierarchy framework

🎓 Who This Is For#

• Students learning regime awareness through the world's most accessible knowledge base
• AIs learning structural reasoning across 15 knowledge domains with 120M+ Wikidata entities
• Educators teaching cross‑domain thinking using live, evolving content
• Researchers studying consensus formation, knowledge evolution, and cultural regime variance
• Knowledge workers who use Wikipedia daily but want to see the structural substrate beneath the surface

🔬 Structural Mapping Summary#

How Wikipedia's native structures map to RTT concepts:

📊 Module Statistics#

🧪 Student Exercise (Root Level)#

Pick any Wikipedia article you've read recently and answer:

1. Regime declaration — What does the article declare this concept IS? What does it exclude?
2. Temporal regime — Check the revision history. How many edits? When was the last major revision? Is this a stable or actively evolving regime?
3. Coherence surface — Read the talk page. Are there unresolved disputes? What structural assumptions are being negotiated?
4. Dimensional address — Find the Wikidata item (link at bottom of every article). What Q‑number is it? What properties (P‑numbers) connect it to other concepts?
5. Cross‑language regime — Click a different language version. Does the article cover the same scope? What's included or excluded in the other language?

🔗 Related Modules#

This module is part of the TriadicFrameworks canon. License: Open educational use permitted.

# Category Taxonomy Regime Hierarchy

Purpose: Define how to read Wikipedia's category system as a native regime hierarchy — a massive, community‑maintained classification tree that organizes 6.9 million English articles into nested regime boundaries.

Wikipedia's category tree is not a controlled taxonomy designed by information scientists. It is a crowdsourced, evolving regime map — built by thousands of editors making local classification decisions that aggregate into a global structural hierarchy. This makes it messy, contradictory in places, and deeply revealing of how humans actually organize knowledge.

Where Wikidata provides dimensional addressing (unique identifiers), the category tree provides regime topology (where a concept sits relative to all other concepts).

1 — What Is a Wikipedia Category?#

Every Wikipedia article is assigned to one or more categories — classification labels that place the article within a hierarchical tree of related concepts.

How Categories Work#

How to Access Categories#

2 — The Category Tree as Regime Hierarchy#

2.1 — Structural Anatomy#

Wikipedia's category system forms a directed acyclic graph (DAG) — not a strict tree. Categories can have multiple parents, creating a web of overlapping regime boundaries:

                    Category:Main topic classifications
                    (root regime — R0)
                           │
          ┌────────────────┼────────────────┐
          │                │                │
    Category:Science  Category:Society  Category:Technology
    (domain regime)   (domain regime)   (domain regime)
          │                │                │
    ┌─────┴─────┐    ┌────┴────┐     ┌────┴────┐
    │           │    │         │     │         │
  Cat:Physics Cat:Bio Cat:Politics Cat:Law Cat:Computing Cat:Eng
    │           │         │              │
  Cat:Quantum Cat:Genetics Cat:Elections Cat:Programming
  mechanics                                  │
    │                              ┌─────────┴─────────┐
    │                              │                   │
  Cat:Quantum  ←── cross‑link ──→ Cat:Quantum
  mechanics                       computing

2.2 — The DAG Problem#

Because categories form a DAG (not a tree), the same article can be reached by multiple paths from the root. This is not a bug — it reflects the reality that concepts belong to multiple regimes simultaneously:

RTT reading: Multiple category paths = multiple regime memberships. The number of distinct paths from root to an article = the concept's regime multiplicity. Concepts with high multiplicity sit at regime intersections — they are structurally significant because multiple classification systems claim them.

2.3 — Depth and Breadth#

Two key metrics characterize any position in the category hierarchy:

3 — Category Types and Their Regime Functions#

3.1 — The Six Category Types#

3.2 — By‑Attribute Categories as Regime Faceting#

By‑attribute categories are structurally special — they slice a domain regime by an external dimension, revealing how the regime varies across that dimension:

RTT reading: By‑attribute categories are regime cross‑sections — they show how a single domain regime manifests differently when sliced along an external dimension. The existence of a by‑attribute category means the community considers that dimension structurally significant for that domain.

4 — The Category Tree vs. Wikidata Class Hierarchy#

Wikipedia has two parallel classification systems:

Key Insight: These Systems Disagree#

For any given concept, its Wikipedia category path and its Wikidata class hierarchy may tell different stories:

RTT reading: Category tree = how the community organizes knowledge (cultural, editorial, pragmatic). Wikidata = how entities are formally classified (ontological, structured, cross‑cultural). Disagreements between them reveal regime framing differences — the same concept declared differently depending on whether the classification is community‑editorial or ontologically formal.

5 — Structural Pathologies in the Category Tree#

The category tree is crowdsourced and evolving, which means it contains structural pathologies that are themselves regime signals:

5.1 — Overcategorization#

What it is: An article assigned to 20+ categories, many of which are semantically overlapping.

Regime reading: The concept has regime sprawl — it has been claimed by too many classification systems without consolidation. Overcategorized articles often sit at regime intersections where no single domain has primary ownership.

5.2 — Undercategorization#

What it is: An article assigned to only 1–2 very broad categories, with no subcategory refinement.

Regime reading: The concept has regime isolation — it hasn't been claimed by a stewardship group. Often indicates a neglected or newly created article that no WikiProject has adopted.

5.3 — Category Cycles#

What it is: Category A contains subcategory B, which contains subcategory C, which contains subcategory A — a circular reference.

Regime reading: Regime hierarchy failure — the classification system cannot decide which concept is more general. These are rare (Wikipedia has bots that detect them) but structurally revealing when they occur — they mark genuine ontological ambiguity.

5.4 — Orphan Categories#

What it is: A category with no parent categories (disconnected from the main tree).

Regime reading: Unmoored regime — a classification that exists but is not connected to the broader knowledge structure. Often indicates a recently created or poorly maintained category.

5.5 — Eponymous Categories#

What it is: A category named after a person (Category:Albert Einstein, Category:Works by Aristotle).

Regime reading: Person‑as‑regime — the community considers this individual's work, influence, or legacy significant enough to constitute its own classification node. The category's subcategories reveal how the community structures that person's regime (works, influences, legacy, biographical details).

6 — API Patterns for Category Analysis#

6.1 — Get an Article's Categories#

import requests
 
def get_categories(title, lang="en"):
    """Fetch all categories for a Wikipedia article."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "categories",
        "cllimit": "max",
        "clshow": "!hidden",  # exclude maintenance categories
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    return [cat["title"].replace("Category:", "")
            for cat in page.get("categories", [])]

6.2 — Traverse the Category Tree Upward#

def trace_to_root(category, lang="en", max_depth=15):
    """Trace a category upward through parent categories toward root."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    path = []
    current = category
    visited = set()
 
    for depth in range(max_depth):
        if current in visited:
            break  # cycle detection
        visited.add(current)
 
        params = {
            "action": "query",
            "titles": f"Category:{current}",
            "prop": "categories",
            "cllimit": "max",
            "clshow": "!hidden",
            "format": "json"
        }
        resp = requests.get(url, params=params,
                            headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
        page = next(iter(resp["query"]["pages"].values()))
        parents = [cat["title"].replace("Category:", "")
                   for cat in page.get("categories", [])]
 
        path.append({
            "depth": depth,
            "category": current,
            "parents": parents
        })
 
        if not parents or "Contents" in parents[0]:
            break  # reached root
        current = parents[0]  # follow first parent
 
    return path

6.3 — Get Subcategories and Membership Count#

def get_subcategories(category, lang="en"):
    """Fetch subcategories and article count for a category."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "list": "categorymembers",
        "cmtitle": f"Category:{category}",
        "cmtype": "subcat",
        "cmlimit": "max",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    subcats = [m["title"].replace("Category:", "")
               for m in resp["query"]["categorymembers"]]
 
    # Also get article count
    params["cmtype"] = "page"
    resp2 = requests.get(url, params=params,
                         headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    articles = len(resp2["query"]["categorymembers"])
 
    return {
        "category": category,
        "subcategory_count": len(subcats),
        "subcategories": subcats,
        "article_count": articles
    }

6.4 — Compute Regime Topology Metrics#

def regime_topology(title, lang="en"):
    """Compute regime topology metrics for an article."""
    categories = get_categories(title, lang)
 
    # Depth: trace each category to root, take the longest path
    max_depth = 0
    all_paths = []
    for cat in categories[:5]:  # sample first 5 to avoid rate limits
        path = trace_to_root(cat, lang)
        depth = len(path)
        max_depth = max(max_depth, depth)
        all_paths.append(path)
 
    return {
        "article": title,
        "category_count": len(categories),
        "categories": categories,
        "max_depth": max_depth,
        "regime_multiplicity": len(categories),
        "deepest_path": all_paths[0] if all_paths else [],
        "interpretation": classify_topology(len(categories), max_depth)
    }
 
def classify_topology(cat_count, max_depth):
    """Classify an article's regime topology."""
    if cat_count <= 2 and max_depth <= 3:
        return "isolated_regime"
    elif cat_count <= 5 and max_depth <= 6:
        return "well_classified"
    elif cat_count <= 10 and max_depth <= 10:
        return "cross_domain_concept"
    elif cat_count > 15:
        return "regime_sprawl"
    else:
        return "deeply_specialized"

6.5 — Cross‑Language Category Comparison#

def compare_categories_cross_language(wikidata_qid, languages=None):
    """Compare category assignments for the same concept across languages."""
    if languages is None:
        languages = ["en", "de", "ja", "ar", "es"]
 
    url = "https://www.wikidata.org/w/api.php"
    params = {
        "action": "wbgetentities",
        "ids": wikidata_qid,
        "props": "sitelinks",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    sitelinks = resp["entities"][wikidata_qid].get("sitelinks", {})
 
    results = {}
    for lang in languages:
        wiki_key = f"{lang}wiki"
        if wiki_key in sitelinks:
            title = sitelinks[wiki_key]["title"]
            cats = get_categories(title, lang)
            results[lang] = {
                "title": title,
                "category_count": len(cats),
                "categories": cats
            }
 
    return results

7 — Worked Example: "Energy"#

The concept Energy sits at one of the deepest regime intersections in Wikipedia's category tree.

Category Memberships (English Wikipedia)#

Regime Topology Analysis#

• Category count: 8+ (high → cross‑domain concept)
• Max depth: 6 (moderately specialized)
• Fan‑in: 3+ domain regimes claim it (Physics, Economics, Political Science)
• Regime multiplicity: Very high — Energy is one of the most cross‑domain concepts on Wikipedia
• Classification: cross_domain_concept with elements of regime_sprawl

Comparing Wikipedia Categories vs. Wikidata#

Divergence: Wikipedia's category tree routes Energy through both Physics AND Economics AND Policy — reflecting its multi‑regime nature. Wikidata's class hierarchy routes it strictly through Physics → Physical quantity — reflecting a more ontologically narrow classification.

RTT reading: Wikipedia's category tree is more regime‑honest for cross‑domain concepts like Energy because it preserves multiple regime memberships. Wikidata's P31/P279 chain is more ontologically precise but loses the cross‑domain richness.

Cross‑Language Category Comparison#

Insight: The Japanese Wikipedia categorizes Energy under a philosophical concept that has no equivalent in the English category tree — revealing a cultural regime frame that Western categorization misses entirely.

8 — The Category Tree as a Research Instrument#

8.1 — Regime Boundary Detection#

Categories mark where one regime ends and another begins. The boundary is visible where:

• A category has subcategories belonging to different WikiProjects
• An article belongs to categories from multiple domain regimes
• A category's talk page has disputes about what belongs in it

8.2 — Knowledge Gap Detection#

Missing or underpopulated categories reveal regime gaps — areas where Wikipedia's structural coverage is incomplete:

8.3 — Regime Evolution Tracking#

Category changes in an article's revision history reveal regime reclassification events:

def find_category_changes(title, lang="en"):
    """Find revisions that changed an article's categories."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "revisions",
        "rvlimit": "50",
        "rvprop": "ids|timestamp|comment|user",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
 
    cat_changes = []
    for rev in page.get("revisions", []):
        comment = rev.get("comment", "").lower()
        if any(kw in comment for kw in
               ["category", "cat", "recat", "recategoriz", "reclassif"]):
            cat_changes.append({
                "rev_id": rev["revid"],
                "timestamp": rev["timestamp"],
                "user": rev.get("user", "anonymous"),
                "comment": rev.get("comment", "")
            })
 
    return cat_changes

RTT reading: Every category change is a regime reclassification event — the community has decided that this concept belongs to a different regime neighborhood than before. Tracking these changes over time reveals the concept's regime migration history.

9 — PetScan: Advanced Category Intersection Queries#

PetScan (https://petscan.wmcloud.org/) is a powerful tool for querying category intersections — finding articles that belong to multiple categories simultaneously:

9.1 — Use Cases for Regime Analysis#

9.2 — Example: Finding Cross‑Domain Concepts#

To find articles that are classified under both Physics and Philosophy:

1. Go to https://petscan.wmcloud.org/
2. Set Categories: Physics and Philosophy
3. Set Combination: Intersection (AND)
4. Set Depth: 3 (search 3 levels deep into subcategories)
5. Run query

Result: Articles like "Entropy," "Causality," "Determinism," "Quantum mechanics interpretations" — concepts that sit at the Physics↔Philosophy regime boundary.

RTT reading: These intersection results are the regime boundary population — the set of concepts that both domains claim. The size and composition of this population reveals how structurally connected the two domains are.

10 — Cross‑Reference to Other Module Files#

11 — Student Exercises#

Exercise 1 — Category Path Tracing (15 minutes)#

1. Pick any Wikipedia article
2. Scroll to the bottom and find its categories
3. Click one category and trace it upward through parent categories until you reach "Main topic classifications" or "Contents"
4. Count the depth (number of levels)
5. Go back and try a different category for the same article — does it reach the root through a different domain?
6. Write one sentence: "This article reaches the root via [path 1: N levels through Domain X] and [path 2: M levels through Domain Y]. It has a regime multiplicity of [number of top‑level categories]."

Exercise 2 — Cross‑Domain Intersection (20 minutes)#

1. Go to PetScan (https://petscan.wmcloud.org/)
2. Pick two domains you find interesting (e.g., Biology and Economics, or Physics and Philosophy)
3. Run an intersection query with depth 2
4. Examine the results: what concepts sit at the boundary between these two domains?
5. Pick one result article and read its lead paragraph — does it acknowledge its cross‑domain nature?
6. Write two sentences: "The intersection of [Domain A] and [Domain B] contains [N] articles. The most structurally interesting is [article] because [reason]."

Exercise 3 — Category Pathology Hunting (20 minutes)#

1. Browse Wikipedia's category tree starting from Category:Main topic classifications
2. Look for one example of each pathology from Section 5:
   • An overcategorized article (15+ categories)
   • An undercategorized article (1–2 categories only)
   • An orphan category (hint: check Category:Orphaned categories)
   • An eponymous category (person‑as‑regime)
3. For each, write one sentence explaining what the pathology reveals about the concept's regime status

Exercise 4 — Cross‑Language Category Comparison (30 minutes)#

1. Pick a concept you expect to have cultural variance (try: Democracy, Tea, Football, or a religion)
2. Find the article in English + 2 other languages
3. For each language, list the categories at the bottom of the article
4. Compare: Are the categories structurally similar? Do different languages categorize the concept under different domains?
5. Answer: "The most striking category difference is [X]. This reveals that [language A] frames the concept as part of [regime], while [language B] frames it as part of [different regime]."

Exercise 5 — Regime Reclassification Detection (30 minutes)#

1. Pick an article for a concept that has been reclassified in real life (try: Pluto, a renamed country, a reclassified species, or a substance whose legal status changed)
2. Use the find_category_changes function from Section 8.3 (or manually search the revision history for "category" in edit summaries)
3. Identify when the category change happened and what categories were added/removed
4. Answer: "The article was reclassified from [old categories] to [new categories] on [date]. This reflects the real‑world regime transition of [event]. The category change [preceded / followed / coincided with] the article text update by [N days]."

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon. # Cross‑Domain Meta‑Operators — Wikipedia Awareness Module

Purpose: Show how structural operators discovered in one Wikipedia domain apply — without modification — to articles, revisions, talk pages, and Wikidata entities in every other domain.

This is the capstone file. It assumes familiarity with the 4‑file domain folders and the 7 Wikipedia‑specific analysis files.

1 — What Is a Meta‑Operator?#

A meta‑operator is a structural pattern that:

1. Was first observed in a specific domain's Wikipedia articles
2. Can be extracted from that domain without losing its structural grammar
3. Applies coherently to articles in every other domain covered by this module

Meta‑operators are not metaphors. They are not analogies. They are structural invariants — patterns that hold because Wikipedia's architecture enforces them uniformly across all 6.9 million English articles.

Why Wikipedia Produces Meta‑Operators#

Wikipedia's content is diverse, but its infrastructure is uniform:

• Every article has the same revision history schema
• Every article links to the same Wikidata entity graph
• Every article is governed by the same NPOV policy
• Every article is classified by the same category taxonomy
• Every talk page follows the same discussion architecture

This structural uniformity means that any operator discovered in one domain's articles also operates in every other domain — because the substrate is shared.

2 — The 12 Cross‑Domain Meta‑Operators#

Operator 1: Regime Declaration Parsing#

• Source domain: Physics
• Discovery: Every Physics article implicitly declares a regime — "Newtonian mechanics applies when v ≪ c" — by stating scope conditions and boundary limits
• Cross‑domain application: Every Wikipedia article in every domain declares scope conditions, even when unstated. The Chemistry article on "Water" declares a regime (liquid state, standard pressure, Earth context) without explicitly saying so. The Economics article on "Supply and Demand" declares a regime (market economies, rational actors, price flexibility) through its assumptions.

Operator: Read any Wikipedia article's opening paragraph as a regime declaration. Identify: what scope is claimed, what boundary conditions are implied, what is excluded.

Operator 2: Revision Frequency as Stability Signal#

• Source domain: Political Science
• Discovery: Articles on contested political topics (elections, territorial disputes, policy debates) show high revision frequency — the edit count is a direct measure of regime instability
• Cross‑domain application: In Medicine, articles on controversial treatments show the same pattern. In Physics, articles on disputed interpretations (quantum measurement, string theory) show elevated revision counts. In History, articles on contested events show periodic revision spikes around anniversaries.

Operator: For any Wikipedia article, check action=info for total revision count and recent edit rate. High frequency = unstable regime. Low frequency = crystallized regime. Sudden spikes = regime perturbation event.

Operator 3: Talk Page Coherence Gradient#

• Source domain: Philosophy
• Discovery: Philosophy talk pages reveal the deepest structural disagreements — editors argue about whether the article's framing itself is biased, not just its content
• Cross‑domain application: In Biology, talk pages on evolution vs. intelligent design reveal the same framing disputes. In Economics, talk pages on capitalism vs. socialism articles show identical coherence gradients. In Linguistics, talk pages on language classification reveal competing structural taxonomies.

Operator: Read any article's talk page and classify disputes as: (a) factual corrections (surface — R3), (b) framing disagreements (structural — R1/R2), or (c) scope challenges (regime‑level — R0). The ratio reveals the article's coherence gradient.

Operator 4: Wikidata Dimensional Bridging#

• Source domain: Chemistry
• Discovery: Every chemical compound has a Wikidata Q‑number that connects it to properties (P‑numbers) spanning Physics (molecular weight P2067), Biology (biological role P682), Medicine (drug interaction P769), and Engineering (industrial use P366)
• Cross‑domain application: This bridging is universal. Any Wikidata entity's P‑number connections reveal which other domains are structurally linked to it — creating a machine‑readable cross‑domain map.

Operator: For any concept, find its Wikidata Q‑number. List its P‑number properties. Each P‑number that points to an entity in a different domain = a dimensional bridge. The count of cross‑domain bridges = the concept's structural connectivity.

Operator 5: Category Taxonomy as Regime Hierarchy#

• Source domain: Biology
• Discovery: Biology's category tree (Life → Domain → Kingdom → Phylum → ... → Species) is the most deeply nested taxonomy on Wikipedia — and it mirrors a natural regime hierarchy perfectly
• Cross‑domain application: Every domain has a category tree. Mathematics has Category:Mathematics → Category:Algebra → Category:Linear algebra → Category:Matrices. Political Science has Category:Politics → Category:Forms of government → Category:Democracy → Category:Direct democracy. The depth and branching of the category tree reveals the regime granularity of the domain.

Operator: For any Wikipedia article, trace its category tree upward to the root. Count the depth (levels to root) and breadth (sibling categories at each level). Deep + narrow = specialized regime. Shallow + broad = general regime. Orphaned categories = regime gaps.

Operator 6: NPOV Tension as Coherence Stress Test#

• Source domain: History
• Discovery: History articles face the strongest NPOV tensions — every historical event has competing national, cultural, and ideological narratives. The NPOV policy forces these into a single coherent frame, creating visible structural stress
• Cross‑domain application: In Medicine, NPOV tension appears when alternative medicine claims compete with evidence‑based claims. In Economics, it appears when articles must present both Keynesian and Austrian perspectives. In Psychology, it surfaces when articles must balance biological and social constructionist frameworks.

Operator: In any article, identify where NPOV forces competing claims into the same frame. The points of highest NPOV tension = the article's coherence stress points. These are where regime boundaries are most visible.

Operator 7: Featured Article as Validation Corridor#

• Source domain: Earth Sciences
• Discovery: Earth Sciences has one of the highest Featured Article ratios — articles like "Plate tectonics" and "Earthquake" have passed Wikipedia's most rigorous quality process, serving as structurally validated reference points
• Cross‑domain application: In every domain, Featured Articles represent the community's consensus on structural completeness. They define what a "fully resolved" article looks like for that domain — scope, sourcing depth, citation density, neutrality, and coverage completeness.

Operator: For any domain, find its Featured Articles (FA) and Good Articles (GA). These are the domain's validation corridor — the community's answer to "what does a structurally complete treatment look like here?" Compare any non‑FA article to the FA template to identify structural gaps.

Operator 8: Edit War as Regime Boundary Marker#

• Source domain: Political Science
• Discovery: Edit wars on political articles (Israel–Palestine, Kashmir, Taiwan) are not random — they occur precisely at regime boundaries where competing structural claims cannot be reconciled under NPOV
• Cross‑domain application: In Physics, edit wars mark boundaries between classical and quantum descriptions. In Medicine, they mark boundaries between mainstream and contested treatments. In Philosophy, they mark boundaries between competing ontological frameworks.

Operator: An edit war is diagnostic, not disruptive. The topic of the edit war identifies a regime boundary. The arguments of the editors reveal the competing regime claims. The resolution (if any) reveals which regime won structural standing.

Operator 9: Cross‑Language Regime Variance#

• Source domain: Linguistics
• Discovery: The same linguistic concept described in different language Wikipedias reveals cultural regime variance — what counts as a "language" vs. a "dialect" differs by political and cultural context
• Cross‑domain application: In History, the article on a military conflict varies dramatically between the Wikipedias of the involved nations. In Medicine, treatment recommendations vary between Wikipedias reflecting different healthcare systems. In Economics, the same economic concept is framed differently across Wikipedias reflecting different economic regimes.

Operator: For any article, compare the English version to at least 2 other language versions. Differences in scope, framing, length, and emphasis reveal cultural regime variance — the same concept declared differently because the structural context differs.

Operator 10: Deletion Debate as Regime Collapse Detection#

• Source domain: Computer Science
• Discovery: Computer Science has frequent Articles for Deletion (AfD) debates — technologies, programming languages, and startups regularly face notability challenges. A successful deletion = the community deciding a concept lacks sufficient structural standing
• Cross‑domain application: In every domain, AfD debates reveal the community's minimum regime threshold — the structural requirements a concept must meet to maintain a Wikipedia article. In Medicine, fringe treatments face AfD. In Philosophy, obscure philosophical positions face AfD. In Political Science, minor political parties face AfD.

Operator: Search AfD archives for any domain. The deletion arguments reveal the community's implicit regime criteria — what structural standing is required for inclusion. Concepts that survive AfD have demonstrated regime resilience. Concepts that are deleted have failed the minimum coherence threshold.

Operator 11: Infobox Template as Regime Schema#

• Source domain: Astronomy
• Discovery: Every astronomical object article uses an infobox template (Template:Infobox planet, Template:Infobox star) that defines exactly which properties the regime requires — spectral class, magnitude, distance, constellation
• Cross‑domain application: Every domain has infobox templates. Chemistry has Template:Chembox. Biology has Template:Taxobox. The infobox fields define the minimum regime schema — the properties a concept must have to be structurally declared in that domain.

Operator: For any domain, find its primary infobox template. The template's fields = the domain's regime schema. Fields that are always filled = structural invariants. Fields that are often empty = regime gaps. Fields that vary between articles = regime flexibility zones.

Operator 12: Disambiguation as Regime Collision Surface#

• Source domain: Mathematics
• Discovery: Mathematical terms frequently collide with everyday language — "Ring," "Field," "Group," "Set" all have disambiguation pages because the mathematical regime and the common‑language regime use the same word for different structural claims
• Cross‑domain application: Disambiguation pages exist across all domains and always mark the same thing — two or more regimes claiming the same term. In Medicine, "Depression" disambiguates between psychiatric and economic meanings. In Engineering, "Bridge" disambiguates between structural and network meanings.

Operator: Disambiguation pages are regime collision maps. Each entry on a disambiguation page = a different regime claiming the same term. The ordering of entries reveals which regime has primary structural standing for that term on English Wikipedia.

3 — The Meta‑Operator Matrix#

How each operator applies across all 15 domains:

Key: ● = high structural signal | ○ = present but weaker signal

4 — How to Use These Operators#

For Students#

1. Pick any Wikipedia article
2. Apply Operators 1, 2, and 4 (regime declaration, revision frequency, Wikidata bridging) — these work on every article
3. If the article has visible NPOV tension or talk page disputes, apply Operators 3, 6, and 8
4. If the article exists in multiple languages, apply Operator 9
5. Write a 1‑paragraph structural summary: "This article declares [regime], shows [stability/instability] via [revision count], bridges to [N] other domains via Wikidata, and has [high/low] NPOV tension at [specific points]."

For AIs#

1. Regime extraction: Apply Operator 1 to parse any article's opening paragraph into regime declarations
2. Stability assessment: Apply Operator 2 to classify articles as crystallized, active, or contested
3. Graph traversal: Apply Operator 4 to build cross‑domain knowledge maps from Wikidata P‑number bridges
4. Coherence scoring: Apply Operators 3 and 6 to assess structural integrity
5. Boundary detection: Apply Operators 8 and 12 to identify regime collision points

For Researchers#

1. Temporal regime analysis: Combine Operators 2, 8, and 9 to study how knowledge regimes evolve across time and cultures
2. Consensus mechanics: Combine Operators 3, 6, and 7 to study how Wikipedia's community builds structural coherence
3. Knowledge graph topology: Use Operator 4 systematically to map the dimensional connectivity of entire knowledge domains
4. Comparative regime studies: Use Operator 9 to compare how the same concept is structurally declared across cultural contexts

5 — Relationship to the NIST Cross‑Domain Meta‑Operators#

The NIST Awareness Primer's Cross‑Domain Meta‑Operators operate on a different substrate:

The structural grammar is the same. Both modules extract operators from specific domains and show they apply across all domains. The difference is the richness of the substrate — Wikipedia's public revision history, talk pages, and Wikidata graph provide surfaces that NIST's publication model cannot.

6 — Student Exercise (Capstone)#

Cross‑domain operator walkthrough:

1. Pick one concept that spans at least 3 of the 15 domains (e.g., "Entropy" spans Physics, Chemistry, Computer Science, Philosophy)
2. Find the Wikipedia article for that concept in each relevant domain
3. Apply all 12 operators to each article
4. Fill in your own row on the Meta‑Operator Matrix (Section 3)
5. Write a 2‑paragraph structural comparison:
   • Paragraph 1: How does the same concept get regime‑declared differently across domains?
   • Paragraph 2: Which operators produced the strongest signal for cross‑domain structural connection?

Suggested multi‑domain concepts: Energy, Information, Evolution, Symmetry, Network, Equilibrium, Complexity, Resonance, Entropy, Emergence

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon. # Edit War Regime Transition Detection

Purpose: Reframe Wikipedia edit wars from disruptive incidents into what they structurally are — diagnostic instruments for regime boundary mapping. An edit war is not noise. It is a signal. It marks the precise location where two or more competing regime claims collide and cannot be reconciled through normal consensus mechanisms.

No other knowledge source makes regime collisions visible in real time. Academic journals suppress reviewer disagreements. Encyclopedias resolve disputes internally. Only Wikipedia exposes the raw collision data — every revert, every counter‑revert, every edit summary declaring a structural position — in a publicly archived, timestamped, author‑attributed log.

This file teaches students to read edit wars as regime transition events and extract structural intelligence from them.

1 — What Is an Edit War?#

1.1 — Wikipedia's Definition#

An edit war occurs when editors repeatedly override each other's contributions to an article, rather than resolving disagreements through discussion on the talk page. Wikipedia's Three‑Revert Rule (3RR) states:

"An editor must not perform more than three reverts on a single page — in whole or in part — within a 24‑hour period."

Violating 3RR can result in a block. But the rule addresses the symptom, not the cause. The cause is always a regime collision.

1.2 — The RTT Translation#

1.3 — Why Edit Wars Are Diagnostic#

An edit war answers three structural questions simultaneously:

1. Where is the regime boundary? — The specific text being reverted marks the exact location of the structural dispute
2. What are the competing claims? — Each editor's version represents a distinct regime declaration
3. How strong is each claim? — The persistence of each editor (number of reverts, argument quality, source citations) reveals the structural standing of each competing regime

2 — The Five Types of Edit Wars#

Type 1: Factual Dispute War#

What it looks like: Editors repeatedly change a specific fact — a date, a number, a name, a classification.

Underlying regime collision: Two external sources disagree, and editors are proxying that disagreement into the article.

Example: Editors warring over whether a mountain's height is 8,848m or 8,849m based on different survey sources.

Severity: Low. Usually resolved by identifying the most authoritative source.

RTT reading: This is a regime measurement dispute — competing claims about the same measurable dimension. The resolution identifies which measurement regime has primary standing.

Type 2: Classification War#

What it looks like: Editors repeatedly change how a concept is classified or categorized — "X is a type of Y" vs. "X is a type of Z."

Underlying regime collision: The concept sits at a regime boundary where two classification systems disagree.

Example: Pluto — "planet" vs. "dwarf planet." Tomato — "fruit" vs. "vegetable." Taiwan — "country" vs. "province."

Severity: Moderate to high. Classification wars often map to real‑world institutional or political disputes.

RTT reading: This is a regime hierarchy dispute — competing claims about where a concept belongs in the classification tree. The resolution determines which regime hierarchy the article adopts as primary. See Category_Taxonomy_Regime_Hierarchy.md.

Type 3: Framing War#

What it looks like: Editors repeatedly rewrite the same passage to present information from different perspectives. The facts may not change — only the framing changes.

Underlying regime collision: Two worldviews produce structurally different regime declarations from the same set of facts.

Example: A military conflict described as "liberation" by one side and "invasion" by the other. A political figure described as "controversial" vs. "influential."

Severity: High. Framing wars are the most persistent because they involve structural perspective, not factual accuracy.

RTT reading: This is a regime declaration dispute — competing structural presentations of the same underlying data. The resolution determines the article's primary R1 framing. See NPOV_As_Coherence_Operator.md.

Type 4: Inclusion/Exclusion War#

What it looks like: One editor adds content, another removes it. The dispute is about whether specific information belongs in the article.

Underlying regime collision: Competing claims about the article's scope — what the regime should and should not cover.

Example: Should a biography mention a person's criminal record? Should a scientific article mention fringe objections? Should a country article mention territorial disputes?

Severity: High. These wars define the regime's boundaries — what is structurally in and what is out.

RTT reading: This is a regime scope dispute — competing claims about the regime's boundary conditions. The resolution determines the article's R0 scope declaration.

Type 5: Naming/Terminology War#

What it looks like: Editors repeatedly change how a concept is named or what terminology is used to describe it.

Underlying regime collision: Names carry regime claims. Choosing one name over another is choosing one regime's framing over another's.

Example: "Gdańsk" vs. "Danzig." "Persian Gulf" vs. "Arabian Gulf." "Myanmar" vs. "Burma." "Kyiv" vs. "Kiev." "Côte d'Ivoire" vs. "Ivory Coast."

Severity: Very high. Naming wars can persist for years because the name itself is a structural declaration — it declares which political, cultural, or historical regime has naming authority.

RTT reading: This is a regime identity dispute — competing claims about the concept's structural name. The resolution determines which regime's naming convention the article adopts as primary.

3 — Edit War Severity Scale#

Severity Distribution by Domain#

4 — The Four Resolution Patterns#

Every edit war ends. How it ends reveals the regime transition outcome:

Pattern 1: One Regime Prevails#

What happens: One side's version is accepted as the article's declaration. The other side's version is removed or marginalized.

How it's achieved: Stronger sourcing, broader editor consensus, admin intervention favoring one side, or one side disengaging.

RTT reading: Regime displacement — one regime claim wins structural standing and the other loses it. The article's regime declaration shifts to the prevailing claim.

Example: The Pluto article eventually adopted "dwarf planet" after the IAU decision. The "planet" claim lost structural standing.

Pattern 2: Compromise Synthesis#

What happens: A new version is crafted that incorporates elements of both competing claims. Neither side gets exactly what they wanted, but both can accept the result.

How it's achieved: Talk page negotiation, RfC, mediation, or a skilled editor proposing a synthesis.

RTT reading: Regime synthesis — a new regime declaration emerges that structurally integrates the competing claims. This is a genuine regime transition — the article's structural state is different from either competing version.

Example: Articles on contested territories often use compromise formulations: "X is a disputed territory claimed by both A and B."

Pattern 3: Structural Separation#

What happens: The disputed content is moved to its own article or section, giving each perspective its own structural space.

How it's achieved: Article splitting, creation of sub‑articles, or "main article" links to separate detailed treatments.

RTT reading: Regime differentiation — the competing claims are separated into distinct regime declarations rather than forced into the same space. The original article retains a neutral summary; the detailed perspectives get their own articles.

Example: "Evolution" and "Objections to evolution" are structurally separated — each concept gets its own regime declaration.

Pattern 4: Administrative Freeze#

What happens: An admin locks the article to prevent further editing. The version at time of protection becomes the de facto declaration, regardless of which side it favors.

How it's achieved: Page protection (semi, extended, or full). May include discretionary sanctions for the topic area.

RTT reading: Regime stabilization by force — the regime oscillation is halted by external authority rather than consensus. The frozen version is not necessarily the "correct" declaration — it is the one that happened to be in place when the lock was applied.

Example: Heavily contested articles like "Israel" or "Kashmir" spend long periods under full protection — the locked version is a pragmatic stabilization, not a consensus outcome.

5 — Detection Algorithms#

5.1 — Basic Revert Detection#

import requests
from datetime import datetime, timedelta
 
def detect_revert_sequences(title, lang="en", window_hours=24, min_reverts=3):
    """
    Detect revert sequences in a Wikipedia article's recent history.
    A revert is identified by system tags or edit summary keywords.
    """
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "revisions",
        "rvlimit": "500",
        "rvprop": "ids|timestamp|user|size|comment|tags|sha1",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    revisions = page.get("revisions", [])
 
    # Identify reverts
    revert_tags = {"mw-revert", "mw-undo", "mw-rollback", "mw-manual-revert"}
    revert_keywords = {"revert", "rv ", "rvv", "undo", "rollback",
                       "restored", "reverted"}
 
    reverts = []
    for rev in revisions:
        tags = set(rev.get("tags", []))
        comment = rev.get("comment", "").lower()
 
        is_revert = (
            bool(tags & revert_tags) or
            any(kw in comment for kw in revert_keywords)
        )
 
        if is_revert:
            reverts.append({
                "rev_id": rev["revid"],
                "timestamp": rev["timestamp"],
                "user": rev.get("user", "anonymous"),
                "comment": rev.get("comment", ""),
                "tags": list(tags & revert_tags),
                "sha1": rev.get("sha1", "")
            })
 
    # Detect clusters (multiple reverts within window)
    clusters = []
    current_cluster = []
 
    for i, rev in enumerate(reverts):
        ts = datetime.fromisoformat(rev["timestamp"].replace("Z", "+00:00"))
 
        if not current_cluster:
            current_cluster.append(rev)
        else:
            prev_ts = datetime.fromisoformat(
                current_cluster[-1]["timestamp"].replace("Z", "+00:00"))
            if (prev_ts - ts).total_seconds() <= window_hours * 3600:
                current_cluster.append(rev)
            else:
                if len(current_cluster) >= min_reverts:
                    clusters.append(current_cluster)
                current_cluster = [rev]
 
    if len(current_cluster) >= min_reverts:
        clusters.append(current_cluster)
 
    return {
        "article": title,
        "total_reverts": len(reverts),
        "revert_clusters": len(clusters),
        "clusters": [{
            "size": len(c),
            "start": c[-1]["timestamp"],
            "end": c[0]["timestamp"],
            "editors": list(set(r["user"] for r in c)),
            "reverts": c
        } for c in clusters]
    }

5.2 — SHA‑1 Based War Detection#

The most reliable revert detection uses content hashing — if two non‑adjacent revisions have the same SHA‑1 hash, the article was restored to an earlier exact state:

def detect_sha1_wars(title, lang="en"):
    """
    Detect edit wars using SHA-1 content hash matching.
    If the same hash appears multiple times, the article was
    reverted to an identical state — a definitive war signal.
    """
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "revisions",
        "rvlimit": "500",
        "rvprop": "ids|timestamp|user|sha1",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    revisions = page.get("revisions", [])
 
    # Group revisions by SHA-1 hash
    from collections import defaultdict
    hash_groups = defaultdict(list)
    for rev in revisions:
        sha1 = rev.get("sha1", "")
        if sha1:
            hash_groups[sha1].append(rev)
 
    # Find repeated states (same content appearing 2+ times)
    war_signals = []
    for sha1, revs in hash_groups.items():
        if len(revs) >= 2:
            editors = list(set(r.get("user", "anon") for r in revs))
            war_signals.append({
                "sha1": sha1,
                "occurrences": len(revs),
                "timestamps": [r["timestamp"] for r in revs],
                "editors_restoring": editors,
                "interpretation": "article_restored_to_identical_state"
            })
 
    return {
        "article": title,
        "repeated_states": len(war_signals),
        "severity": classify_war_severity(war_signals),
        "signals": sorted(war_signals,
                         key=lambda x: x["occurrences"],
                         reverse=True)
    }
 
def classify_war_severity(signals):
    """Classify edit war severity from SHA-1 analysis."""
    if not signals:
        return "0_no_war"
    max_repeats = max(s["occurrences"] for s in signals)
    total_repeats = sum(s["occurrences"] for s in signals)
 
    if total_repeats <= 3:
        return "1_skirmish"
    elif total_repeats <= 8:
        return "2_dispute"
    elif total_repeats <= 15:
        return "3_war"
    elif max_repeats >= 5:
        return "4_entrenchment"
    else:
        return "3_war"

5.3 — War Participant Analysis#

def analyze_war_participants(cluster):
    """
    Analyze the participants in an edit war cluster.
    Returns faction structure and relative persistence.
    """
    from collections import Counter
 
    editor_reverts = Counter(r["user"] for r in cluster["reverts"])
    editors = list(editor_reverts.keys())
    total = sum(editor_reverts.values())
 
    factions = []
    for editor, count in editor_reverts.most_common():
        factions.append({
            "editor": editor,
            "revert_count": count,
            "persistence": round(count / total, 3),
            "sample_comment": next(
                (r["comment"] for r in cluster["reverts"]
                 if r["user"] == editor and r["comment"]),
                "no comment"
            )
        })
 
    return {
        "total_participants": len(editors),
        "total_reverts": total,
        "faction_count": len(set(
            r.get("sha1", "") for r in cluster["reverts"])),
        "factions": factions,
        "structure": (
            "bilateral" if len(editors) == 2 else
            "multilateral" if len(editors) <= 5 else
            "mass_conflict"
        )
    }

5.4 — Regime Boundary Extraction#

import difflib
 
def extract_disputed_content(rev_id_a, rev_id_b, lang="en"):
    """
    Compare two revision IDs to identify the exact disputed content.
    The diff reveals the regime boundary — the specific text where
    competing claims collide.
    """
    url = f"https://{lang}.wikipedia.org/w/api.php"
 
    def get_content(rev_id):
        params = {
            "action": "query",
            "revids": str(rev_id),
            "prop": "revisions",
            "rvprop": "content",
            "rvslots": "main",
            "format": "json"
        }
        resp = requests.get(url, params=params,
                            headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
        page = next(iter(resp["query"]["pages"].values()))
        return page["revisions"][0]["slots"]["main"]["*"]
 
    content_a = get_content(rev_id_a).splitlines()
    content_b = get_content(rev_id_b).splitlines()
 
    diff = list(difflib.unified_diff(content_a, content_b,
                                      lineterm="", n=3))
 
    # Extract only changed lines
    additions = [l[1:] for l in diff if l.startswith("+")
                 and not l.startswith("+++")]
    removals = [l[1:] for l in diff if l.startswith("-")
                and not l.startswith("---")]
 
    return {
        "revision_a": rev_id_a,
        "revision_b": rev_id_b,
        "lines_added": len(additions),
        "lines_removed": len(removals),
        "regime_claim_a": "\n".join(removals[:10]),
        "regime_claim_b": "\n".join(additions[:10]),
        "boundary_location": "see diff output for exact position",
        "full_diff_lines": len(diff)
    }

5.5 — Historical War Pattern Analysis#

def historical_war_profile(title, lang="en"):
    """
    Build a complete edit war profile for an article's full history.
    Combines revert detection, SHA-1 analysis, and temporal clustering.
    """
    revert_data = detect_revert_sequences(title, lang,
                                           window_hours=72,
                                           min_reverts=2)
    sha1_data = detect_sha1_wars(title, lang)
 
    # Check protection history
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": title,
        "prop": "info",
        "inprop": "protection",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    protections = page.get("protection", [])
 
    return {
        "article": title,
        "revert_clusters": revert_data["revert_clusters"],
        "sha1_repeated_states": sha1_data["repeated_states"],
        "war_severity": sha1_data["severity"],
        "current_protection": protections,
        "is_protected": len(protections) > 0,
        "war_history": {
            "clusters": revert_data["clusters"][:5],
            "sha1_signals": sha1_data["signals"][:5]
        },
        "regime_transition_assessment": assess_transition(
            revert_data, sha1_data, protections)
    }
 
def assess_transition(revert_data, sha1_data, protections):
    """Assess whether the article has undergone a regime transition."""
    severity = sha1_data["severity"]
    protected = len(protections) > 0
    clusters = revert_data["revert_clusters"]
 
    if severity == "0_no_war":
        return "stable_regime — no transition detected"
    elif severity == "1_skirmish" and not protected:
        return "minor_friction — regime boundary tested but held"
    elif severity in ("2_dispute", "3_war") and not protected:
        return "regime_negotiation — boundary actively contested"
    elif protected and clusters >= 2:
        return "regime_transition_in_progress — admin intervention required"
    elif severity in ("4_entrenchment",) or clusters >= 5:
        return "chronic_regime_conflict — boundary permanently contested"
    else:
        return "indeterminate — insufficient data"

6 — Worked Examples#

6.1 — Pluto (Classification War → Regime Displacement)#

RTT reading: Pluto is a textbook externally triggered regime transition. The IAU decision changed the concept's regime classification, and the Wikipedia article's edit war is the visible trace of that transition playing out in the knowledge system. The war ended when the new classification gained sufficient structural standing to displace the old one.

Structural insight: The speed of resolution correlated with the clarity of the external authority's decision. The IAU ruling was unambiguous, so the edit war, while intense, resolved relatively quickly. Compare this to naming wars (Type 5) where no single external authority exists — those can persist for decades.

6.2 — Gdańsk/Danzig (Naming War → Compromise Synthesis)#

RTT reading: Gdańsk/Danzig is a regime identity dispute where naming carries deep political and historical regime claims. The compromise synthesis demonstrates that some regime collisions cannot be resolved by one side prevailing — they require structural architecture (naming conventions, context‑dependent usage rules) to manage the permanent boundary.

Structural insight: The article now has an elaborate talk page FAQ and naming convention section — these are crystallized coherence positions produced by the war. The war itself was costly, but it produced structural infrastructure that manages the ongoing regime tension.

6.3 — Abortion (Framing War → Administrative Freeze)#

RTT reading: Abortion represents an irreconcilable regime collision — the competing claims arise from fundamentally different worldview regimes that cannot be structurally synthesized. NPOV cannot produce a version that both camps consider neutral because they disagree on what neutrality means for this topic. The administrative freeze is regime stabilization by force — not consensus, but pragmatic management.

Structural insight: The abortion article demonstrates the limits of NPOV as a coherence operator. For most topics, NPOV can produce a stable structural frame that accommodates competing views. For irreconcilable worldview conflicts, NPOV can only manage the tension — it cannot resolve it. The edit war history is the visible trace of that permanent structural stress.

7 — Edit Wars Across Languages#

7.1 — The Same Concept, Different Wars#

The same topic can produce different edit wars on different language Wikipedias, because the editor population brings different regime perspectives:

7.2 — Cross‑Language War Comparison Method#

def cross_language_war_comparison(wikidata_qid, languages=None):
    """
    Compare edit war intensity for the same concept across languages.
    Uses Wikidata to find the article title in each language.
    """
    if languages is None:
        languages = ["en", "de", "fr", "ja", "ar", "ru", "zh", "es"]
 
    # Get sitelinks from Wikidata
    url = "https://www.wikidata.org/w/api.php"
    params = {
        "action": "wbgetentities",
        "ids": wikidata_qid,
        "props": "sitelinks",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    sitelinks = resp["entities"][wikidata_qid].get("sitelinks", {})
 
    results = {}
    for lang in languages:
        wiki_key = f"{lang}wiki"
        if wiki_key in sitelinks:
            title = sitelinks[wiki_key]["title"]
            try:
                war_data = detect_revert_sequences(title, lang,
                                                    window_hours=72,
                                                    min_reverts=2)
                results[lang] = {
                    "title": title,
                    "total_reverts": war_data["total_reverts"],
                    "revert_clusters": war_data["revert_clusters"]
                }
            except Exception as e:
                results[lang] = {"title": title, "error": str(e)}
 
    return results

7.3 — What Cross‑Language Comparison Reveals#

8 — Edit Wars as Research Instruments#

8.1 — Regime Boundary Mapping#

Method:

1. Identify articles with high revert rates in a domain
2. For each, extract the disputed content using Section 5.4
3. Classify the dispute by type (Section 2)
4. Map the disputes onto the domain's knowledge structure
5. The result is a regime boundary map — a visualization of where structural disputes concentrate within a domain

8.2 — Regime Transition Monitoring#

Method:

1. Set up a watchlist of articles in a domain
2. Monitor revert rates using periodic API calls
3. When a revert cluster is detected, extract the competing claims
4. Track the resolution pattern (Section 4) over time
5. Completed transitions = the domain's regime landscape has shifted

8.3 — Consensus Archaeology#

Method:

1. Find a long‑resolved edit war in a domain (check talk page archives)
2. Extract the original competing claims from the revision history
3. Identify the resolution pattern and final consensus
4. The resolved war reveals how the community established a regime boundary — the process of structural decision‑making

8.4 — Predictive War Analysis#

Method:

1. Monitor talk page dispute intensity (from Talk_Page_Coherence_Surface.md)
2. When talk page disputes escalate past coherence gradient Level 3, flag the article for potential edit war
3. Talk page escalation is a leading indicator of edit wars — disputes that fail to resolve on talk pages often erupt as edit wars
4. Early detection enables preemptive mediation before structural damage occurs

9 — Cross‑Reference to Other Module Files#

10 — Student Exercises#

Exercise 1 — War Type Classification (15 minutes)#

1. Browse Wikipedia's list of notable edit wars: https://en.wikipedia.org/wiki/Wikipedia:Lamest_edit_wars
2. Pick 3 edit wars from different sections
3. Classify each by type using Section 2 (Factual, Classification, Framing, Inclusion/Exclusion, or Naming)
4. For each, write one sentence: "This is a [type] war because the competing claims are about [specific structural question]."

Exercise 2 — Live War Detection (25 minutes)#

1. Pick an article you expect might have recent edit conflicts (try: a current political leader, a recent scientific controversy, or a currently disputed territory)
2. Check the article's revision history for recent reverts (look for "undo" or "revert" in edit summaries)
3. If you find reverts, classify the severity (Section 3) and the war type (Section 2)
4. Check the talk page — is the dispute being discussed there?
5. Answer: "This article [does/does not] show signs of active edit warring. The severity is [level] and the war type is [type]. The talk page [does/does not] have a related discussion thread."

Exercise 3 — Resolution Pattern Analysis (30 minutes)#

1. Find a completed (resolved) edit war — check talk page archives for threads that discuss settled disputes
2. Identify which resolution pattern from Section 4 was used (Regime Displacement, Compromise Synthesis, Structural Separation, or Administrative Freeze)
3. Trace the resolution process: What arguments were decisive? Who mediated? How long did it take?
4. Write two sentences: "This war was resolved through [pattern] because [reason]. The winning regime claim was [claim] and it prevailed because [structural advantage]."

Exercise 4 — Regime Boundary Extraction (30 minutes)#

1. Find an article with a recent or ongoing edit war
2. Use the article's revision history to find two competing revisions (the "before" and "after" of a revert)
3. Compare the two versions using Wikipedia's built‑in diff tool (click "prev" next to any revision)
4. Identify the exact text that is being disputed — this is the regime boundary
5. Answer: "The regime boundary is located in the [section/paragraph] and concerns [specific text]. Claim A says [X] while Claim B says [Y]. The structural question is [what the dispute is really about at R0/R1 level]."

Exercise 5 — Cross‑Language War Comparison (30 minutes)#

1. Pick a topic with known cross‑cultural sensitivity (try: a territorial dispute, a historical conflict, or a contested political classification)
2. Check the article's recent revision history in English + 1 other language edition
3. Compare: Does the same topic produce edit wars in both languages? Are the same dimensions being disputed?
4. Answer: "The English Wikipedia fights about [X] while the [other language] Wikipedia fights about [Y]. This reveals that the regime collision is [universal/culturally specific] because [reason]."

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon. # Featured Article Validation Corridor

Purpose: Reframe Wikipedia's Featured Article (FA) and Good Article (GA) processes from quality assurance checklists into what they structurally are — a validation corridor that verifies the structural integrity of a regime declaration before granting it the community's highest standing.

Most knowledge systems have no public, observable validation process. Peer review is closed. Editorial review is private. Wikipedia's FA/GA process is fully transparent — every nomination, every review comment, every objection, and every resolution is publicly archived. This makes it the only major knowledge source where you can study how structural validation actually works from the inside.

1 — What Is the Validation Corridor?#

1.1 — The Quality Scale#

Wikipedia classifies articles on a 7‑level quality scale — a regime maturity gradient from minimal declaration to fully validated:

1.2 — The Corridor Metaphor#

A "validation corridor" is not a single gate — it is a gauntlet that tests multiple structural dimensions simultaneously. An article must satisfy all criteria to pass through. Failing any single criterion blocks the entire validation:

Article submission
    │
    ▼
┌─────────────────────────────────────────────┐
│            VALIDATION CORRIDOR               │
│                                              │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  │
│  │Well‑     │  │Compre‑   │  │Properly  │  │
│  │written   │→ │hensive   │→ │sourced   │  │
│  └──────────┘  └──────────┘  └──────────┘  │
│       │              │             │         │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  │
│  │Neutral   │  │Stable    │  │Well‑     │  │
│  │(NPOV)    │→ │(no edit  │→ │structured│  │
│  │          │  │ wars)    │  │          │  │
│  └──────────┘  └──────────┘  └──────────┘  │
│       │              │             │         │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  │
│  │Media     │  │Appro‑    │  │Length    │  │
│  │(images)  │→ │priate    │→ │(not too  │  │
│  │          │  │lead      │  │ long/    │  │
│  │          │  │section   │  │ short)   │  │
│  └──────────┘  └──────────┘  └──────────┘  │
│                                              │
│                  ┌──────────┐                │
│                  │Consistent│                │
│                  │manual of │                │
│                  │style     │                │
│                  └──────────┘                │
│                      │                       │
└──────────────────────┼───────────────────────┘
                       ▼
              FA status granted ★

2 — FA Criteria as Structural Integrity Tests#

2.1 — The 10 FA Criteria Mapped to RTT#

Wikipedia's Featured Article criteria (WP:FACR) define what "the best Wikipedia has to offer" looks like. Each criterion maps to a specific structural integrity test:

2.2 — Criterion Weights#

Not all criteria carry equal structural weight. In practice, FA reviews most commonly fail on:

Key insight: The top failure reasons reveal the minimum structural requirements for validation — provenance, completeness, and coherence. These are the same requirements that RTT identifies as fundamental to any stable regime declaration.

3 — The GA vs. FA Distinction#

3.1 — Two Levels of Validation#

3.2 — RTT Reading#

4 — The Review Process as Observable Structural Validation#

4.1 — FA Nomination Process#

1. Editor nominates article at WP:FAC
         │
2. Community reviewers examine article against all 10 criteria
         │
   ┌─────┴──────────────────────┐
   │                            │
3a. Support — reviewer         3b. Oppose — reviewer
    confirms criteria met           identifies specific failures
         │                            │
         │                     4. Nominator addresses objections
         │                            │
         │                     5. Reviewer re‑evaluates
         │                            │
   ┌─────┴────────────────────────────┘
   │
6. FA director assesses consensus
         │
   ┌─────┴──────┐
   │            │
7a. Promoted  7b. Not promoted
    to FA ★       (may retry)

4.2 — What Makes This Structurally Unique#

No other major knowledge source exposes its validation process this way:

RTT reading: Wikipedia's FA process is the only major validation corridor where you can observe structural integrity verification in real time. Every reviewer comment is a structural test result. Every objection is a detected integrity failure. Every resolution is a structural repair. The full history of this process is permanently archived.

4.3 — Where to Find FA Reviews#

5 — Former Featured Articles: Regime Decay Detection#

5.1 — What Is a Former Featured Article?#

A Former Featured Article (FFA) is an article that once held FA status but was demoted through the Featured Article Review (FAR) process. This is structurally significant — it means a validated regime declaration lost its validation because its structural integrity degraded.

5.2 — Why Articles Lose FA Status#

5.3 — FFA as Structural Signal#

The list of Former Featured Articles in any domain reveals:

1. Which regime declarations are hardest to maintain — concepts that lose FA status are structurally high‑maintenance
2. Where source landscapes are most volatile — domains with many FFAs due to source degradation have unstable external regimes
3. Where the community's standards have evolved — older FFAs that were demoted for standard inflation mark generational shifts in structural expectations
4. Which articles suffer from regime drift — articles with high editor turnover that lost quality mark stewardship failures

6 — Domain FA Profiles#

6.1 — FA Distribution by Domain#

FA articles are not evenly distributed across knowledge domains. The distribution reveals which domains produce the most structurally complete regime declarations:

6.2 — What FA Density Reveals#

Key insight: Low FA density in a domain does not mean the domain is less important — it means the domain's structural characteristics make the validation corridor harder to traverse. This is a property of the interaction between the domain's regime structure and the corridor's criteria, not of the domain itself.

7 — Worked Examples#

7.1 — Photosynthesis (FA Since 2004)#

One of Wikipedia's longest‑standing Featured Articles:

RTT reading: Photosynthesis is a textbook validation corridor success — it passes all 10 criteria comfortably because:

• The underlying regime (photosynthetic biochemistry) is scientifically crystallized — no structural disputes
• The source landscape is stable — peer‑reviewed biochemistry journals are reliable and persistent
• The scope is well‑defined — the process has clear boundaries
• NPOV is trivially satisfied — no competing worldviews on photosynthesis

Why it has lasted 20+ years as FA: The concept's regime is so stable and well‑defined that no criterion is under structural pressure. This is what validation looks like for a crystallized, consensus‑level regime.

7.2 — Penicillin (FA, Then Demoted, Then Restored)#

A case study in validation corridor cycling:

RTT reading: Penicillin demonstrates the validation corridor lifecycle:

• Initial validation confirmed structural integrity at 2006 standards
• Regime decay (source degradation, coverage gaps) + corridor tightening (stricter standards) caused integrity failure
• Structural repair (rewrite, re‑sourcing) restored integrity
• Re‑validation confirmed the repaired declaration meets current standards

Key insight: FA status is not permanent. It is a snapshot of structural integrity at validation time. The underlying regime and the corridor's criteria both evolve — the article must keep up with both.

8 — API Patterns for Validation Corridor Analysis#

8.1 — Check an Article's Quality Rating#

import requests
 
def get_quality_rating(title, lang="en"):
    """Get an article's quality rating from talk page assessments."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "titles": f"Talk:{title}",
        "prop": "categories",
        "cllimit": "max",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    page = next(iter(resp["query"]["pages"].values()))
    categories = [c["title"] for c in page.get("categories", [])]
 
    quality_levels = {
        "FA-Class": "featured_article",
        "GA-Class": "good_article",
        "A-Class": "a_class",
        "B-Class": "b_class",
        "C-Class": "c_class",
        "Start-Class": "start_class",
        "Stub-Class": "stub"
    }
 
    for cat in categories:
        for level_key, level_val in quality_levels.items():
            if level_key in cat:
                return {
                    "article": title,
                    "quality": level_val,
                    "category": cat
                }
 
    return {"article": title, "quality": "unassessed"}

8.2 — Check for Featured Article Badge via Wikidata#

def is_featured_article(title, lang="en"):
    """Check if an article has a Featured Article badge via Wikidata sitelinks."""
    url = "https://www.wikidata.org/w/api.php"
    params = {
        "action": "wbgetentities",
        "sites": f"{lang}wiki",
        "titles": title,
        "props": "sitelinks",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
 
    for entity in resp.get("entities", {}).values():
        sitelinks = entity.get("sitelinks", {})
        wiki_key = f"{lang}wiki"
        if wiki_key in sitelinks:
            badges = sitelinks[wiki_key].get("badges", [])
            return {
                "article": title,
                "is_fa": "Q17437796" in badges,   # Featured Article badge
                "is_ga": "Q17437798" in badges,   # Good Article badge
                "badges": badges
            }
 
    return {"article": title, "is_fa": False, "is_ga": False, "badges": []}

8.3 — List Featured Articles in a Domain#

def list_featured_articles(category, lang="en", limit=50):
    """List Featured Articles within a category (domain)."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "query",
        "list": "categorymembers",
        "cmtitle": f"Category:Featured articles about {category}",
        "cmtype": "page",
        "cmlimit": str(limit),
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
    return [m["title"] for m in resp.get("query", {}).get("categorymembers", [])]

8.4 — Compute Domain Validation Profile#

def domain_validation_profile(domain_articles):
    """
    Compute the validation corridor profile for a set of
    articles representing a knowledge domain.
    """
    profile = {
        "total": len(domain_articles),
        "featured": 0,
        "good": 0,
        "b_class": 0,
        "start": 0,
        "stub": 0,
        "unassessed": 0
    }
 
    quality_map = {
        "featured_article": "featured",
        "good_article": "good",
        "a_class": "b_class",  # A-class is rare, group with B
        "b_class": "b_class",
        "c_class": "start",    # C-class grouped with Start
        "start_class": "start",
        "stub": "stub",
        "unassessed": "unassessed"
    }
 
    for title in domain_articles:
        try:
            rating = get_quality_rating(title)
            quality = rating.get("quality", "unassessed")
            bucket = quality_map.get(quality, "unassessed")
            profile[bucket] += 1
        except Exception:
            profile["unassessed"] += 1
 
    # Compute validation ratio
    total = profile["total"]
    if total > 0:
        profile["fa_ratio"] = round(profile["featured"] / total, 4)
        profile["validated_ratio"] = round(
            (profile["featured"] + profile["good"]) / total, 4)
        profile["maturity_score"] = round(
            (profile["featured"] * 6 +
             profile["good"] * 4 +
             profile["b_class"] * 3 +
             profile["start"] * 1 +
             profile["stub"] * 0) / max(total, 1), 2)
 
    return profile

9 — The Validation Corridor as Research Instrument#

9.1 — Structural Completeness Benchmarking#

FA articles serve as structural benchmarks for their domains:

Method:

1. Identify the FA articles in a domain (use Section 8.3)
2. Analyze their common structural features — section structure, source count, word count, image count, citation density
3. Use these features as the domain's structural completeness template
4. Compare any non‑FA article to this template to identify specific structural gaps

9.2 — Validation Corridor Difficulty Analysis#

Method:

1. Collect FA nomination archives for a domain
2. Classify reviewer objections by criterion (sourcing, prose, comprehensiveness, NPOV, stability)
3. The most common objection type = the domain's structural bottleneck — the criterion that is hardest to satisfy for articles in this domain

9.3 — Temporal Validation Standards#

Method:

1. Compare FA articles promoted in 2005 vs. 2015 vs. 2025
2. What changed in the criteria's interpretation over time?
3. Which dimensions became stricter? Which became more flexible?
4. This reveals the evolution of the community's structural integrity expectations — how the validation corridor itself changes over time

9.4 — Cross‑Language Validation Comparison#

Method:

1. Find the same concept's article in multiple language Wikipedias
2. Check its quality rating in each (FA, GA, B, Start, Stub)
3. An article that is FA in English but Stub in another language reveals a structural investment gap — the community's structural attention is concentrated in English

10 — Cross‑Reference to Other Module Files#

11 — Student Exercises#

Exercise 1 — Quality Scale Assessment (15 minutes)#

1. Pick 5 Wikipedia articles on related topics within a single domain
2. Check each article's quality rating (look at the talk page for WikiProject assessment banners)
3. Arrange them on the quality scale: Stub → Start → C → B → GA → FA
4. For the lowest‑rated article, identify which FA criterion it most clearly fails
5. Write one sentence: "[Article] is rated [level] because it fails criterion [N] — specifically, [evidence]."

Exercise 2 — FA Review Archaeology (25 minutes)#

1. Go to Wikipedia:Featured article candidates and find a recently completed review (either promoted or not promoted)
2. Read the review comments from at least 3 reviewers
3. For each reviewer, identify which FA criteria they tested and what structural issues they found
4. Answer: "The most common objection was about criterion [N]. The article [was/was not] promoted because [reason]. The structural bottleneck was [specific issue]."

Exercise 3 — FA vs. Non‑FA Structural Comparison (30 minutes)#

1. Pick a domain (e.g., Biology, History, Physics)
2. Find one FA article and one Start/Stub article in the same domain
3. Compare: word count, reference count, section count, image count, talk page size
4. Compute the structural gap: how many more sources, sections, and words does the FA have?
5. Write two sentences: "The FA has [N]× more sources and [M]× more sections than the Stub. The primary structural gap is [specific dimension — sourcing, comprehensiveness, or prose quality]."

Exercise 4 — Former Featured Article Analysis (20 minutes)#

1. Browse Category:Former featured articles and pick one that interests you
2. Find the FA Review (FAR) discussion that led to its demotion
3. Identify: Why was it demoted? Which criteria did it fail? What changed?
4. Classify the demotion reason as: source degradation, standard inflation, content drift, comprehensiveness gap, or NPOV shift
5. Write one sentence: "[Article] was demoted from FA because [reason], which maps to [RTT regime concept]."

Exercise 5 — Domain Validation Profile (30 minutes)#

1. Pick a knowledge domain
2. Find 10 articles in that domain across different quality levels
3. Count: how many are FA? GA? B? Start? Stub?
4. Compute the domain's validation ratio: (FA + GA) / total
5. Compare to another domain: which has a higher validation ratio? Why?
6. Answer: "[Domain A] has a validation ratio of [X], while [Domain B] has [Y]. Domain A produces more validated articles because [structural reason]."

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon. # NPOV As Coherence Operator

Purpose: Reframe Wikipedia's Neutral Point of View (NPOV) policy from an editorial guideline into what it structurally is — an R0 coherence operator that constrains every regime declaration on Wikipedia. NPOV is not a suggestion. It is the foundational structural invariant that makes Wikipedia possible as a multi‑regime knowledge system.

Without NPOV, Wikipedia would fragment into competing regime declarations with no mechanism for coexistence. NPOV is the operator that forces 6.9 million articles — written by millions of editors with radically different worldviews — into a single coherent knowledge substrate.

This file shows students how to recognize NPOV as structural physics, not editorial policy.

1 — What Is NPOV?#

1.1 — The Policy Statement#

Wikipedia's NPOV policy (WP:NPOV) states:

"All encyclopedic content on Wikipedia must be written from a neutral point of view, representing fairly, proportionately, and, as far as possible, without editorial bias, all the significant views that have been published by reliable sources on a topic."

1.2 — The RTT Translation#

In RTT terms, NPOV is a coherence operator at R0 — the deepest regime level. It constrains what structural claims can be made and how competing claims must coexist:

1.3 — Why NPOV Is an Operator, Not a Rule#

A rule tells you what to do. An operator transforms inputs into outputs according to a structural constraint.

NPOV is an operator because it:

1. Receives competing regime claims from editors with different worldviews
2. Constrains how those claims can be expressed (proportionality, neutrality, source verification)
3. Produces a single article that represents multiple regimes simultaneously
4. Applies uniformly to every article on Wikipedia, regardless of topic or domain

This is not editorial judgment — it is structural transformation. NPOV takes N conflicting regime declarations and produces 1 coherent article. That is an operator.

2 — The Five Sub‑Operators of NPOV#

NPOV is not a single monolithic rule. It decomposes into five sub‑operators, each enforcing a different coherence constraint:

Sub‑Operator 1: Proportionality (WP:WEIGHT)#

What it does: Determines how much space each viewpoint receives in an article, based on its prominence in reliable sources.

Coherence function: Prevents regime amplification — no viewpoint gets more structural presence than its external standing warrants.

Key insight: WEIGHT is the most contested sub‑operator. Disputes about proportionality are disputes about regime standing — how much structural space each competing claim deserves.

Sub‑Operator 2: No Original Research (WP:NOR)#

What it does: Prohibits editors from introducing claims not supported by published reliable sources.

Coherence function: Prevents regime fabrication — Wikipedia declares existing regimes, it does not create new ones.

Key insight: NOR ensures Wikipedia remains a second‑order regime system — it declares and organizes regimes that originate elsewhere. Without NOR, Wikipedia would become a first‑order regime generator, and its coherence would collapse because there would be no external validation constraint.

Sub‑Operator 3: Verifiability (WP:V)#

What it does: Requires that all claims in Wikipedia articles can be verified against published reliable sources.

Coherence function: Provides the validation mechanism for regime claims — the structural test that separates includable claims from excludable ones.

Key insight: "Verifiability, not truth" is perhaps the most structurally profound principle on Wikipedia. It means NPOV operates on regime standing, not on regime validity. A claim can be included if it has sufficient standing — even if it is contested. A claim can be excluded if it lacks standing — even if it might be true. This is what makes NPOV a structural operator rather than an epistemic one.

Sub‑Operator 4: Reliable Sources (WP:RS)#

What it does: Defines which external sources count as structurally valid for citation.

Coherence function: Establishes the source regime boundary — the line between accepted and rejected external authority.

Key insight: RS is NPOV's external calibration mechanism. It answers the question: "Which regimes outside Wikipedia do we recognize as structurally valid?" Without RS, NPOV would have no way to determine proportionality — there would be no external reference for regime standing.

Sub‑Operator 5: Fringe Theories (WP:FRINGE)#

What it does: Defines how to handle claims that fall outside mainstream academic or scientific consensus.

Coherence function: Prevents regime contamination — fringe claims cannot structurally invade mainstream regime declarations.

Key insight: FRINGE is where NPOV's structural nature is most visible. The question is never "is this claim true?" — it is "does this claim have sufficient structural standing to be included, and if so, how much space does it get?" This is pure regime topology.

3 — NPOV Stress Spectrum#

Not all articles experience the same NPOV pressure. The NPOV stress spectrum classifies articles by the intensity of coherence challenge they face:

3.1 — The Five Stress Levels#

3.2 — Stress Level Distribution by Domain#

4 — NPOV Failure Modes#

When NPOV fails — when the coherence operator breaks down — the result is one of four structural failure modes:

Failure Mode 1: Regime Capture#

What happens: One editorial faction gains control of an article and suppresses competing viewpoints. The article stops being a neutral regime declaration and becomes an advocacy document for one regime.

How to detect:

• Talk page dominated by a small group reverting alternative perspectives
• Edit summaries repeatedly citing WP:WEIGHT to exclude minority views
• Article framing consistently favors one perspective
• WikiProject banner from only one domain, despite cross‑domain topic

RTT reading: The coherence operator has been overridden by a single regime agent. The article no longer represents the regime landscape — it represents one regime's claim to dominance.

Failure Mode 2: False Balance#

What happens: An article gives equal structural weight to viewpoints with radically unequal standing. A fringe theory gets the same space as mainstream consensus.

How to detect:

• "On the other hand…" constructions giving equal weight to mainstream and fringe positions
• Equal word counts for consensus and dissent sections
• Absence of WP:WEIGHT-aware framing ("the scientific consensus is…" vs. "some scientists believe…")

RTT reading: The coherence operator has been miscalibrated — it is treating unequal regime standings as equal. This distorts the structural landscape by inflating fringe regime presence.

Failure Mode 3: Neutrality Paralysis#

What happens: Editors become so cautious about NPOV violations that the article fails to make clear, direct statements. Every claim is hedged with "some argue," "it has been suggested," "according to some."

How to detect:

• Excessive use of weasel words and attribution phrases
• Cleanup tags like {{weasel}} or {{who}}
• Article reads as equivocal even on well‑established facts

RTT reading: The coherence operator has become over‑constrained — its structural requirements are being applied so conservatively that the article loses its capacity to declare anything clearly. The regime declaration dissolves into noise.

Failure Mode 4: Structural Fragmentation#

What happens: An article on a contested topic fragments into disconnected sections, each written by a different editorial faction. There is no coherent narrative — just juxtaposed regime declarations that don't interact.

How to detect:

• Abrupt tonal shifts between sections
• Sections that seem to exist in different articles
• No connective tissue between competing perspective sections
• Article feels like a collection of essays rather than an encyclopedia entry

RTT reading: The coherence operator has partially failed — it succeeded in preventing any single regime from capturing the article, but it failed to produce a unified structural frame. The result is incoherent coexistence rather than coherent integration.

5 — NPOV as Structural Physics#

5.1 — The Conservation Analogy#

In physics, conservation laws are structural invariants — energy, momentum, charge are conserved regardless of what happens in a system. NPOV functions as a conservation law for structural representation:

5.2 — The Constraint Equation#

NPOV can be expressed as a structural constraint on any article A:

For article A covering topic T:

  ∑(weight_i × viewpoint_i) = representation(T)

  Subject to:
    weight_i ∝ standing_i (proportionality — WP:WEIGHT)
    standing_i ∈ reliable_sources (verifiability — WP:V)
    viewpoint_i ≠ novel_synthesis (originality constraint — WP:NOR)
    ∑(weight_i) = 1 (total representation is normalized)
    weight_fringe ≤ ε (fringe containment — WP:FRINGE)

RTT reading: NPOV is a normalized, source‑calibrated, novelty‑bounded representation constraint. It operates on the space of all possible regime declarations and produces the unique declaration that satisfies all five sub‑operators simultaneously.

5.3 — Why NPOV Works (Structurally)#

NPOV works because it solves a coordination problem that no other knowledge system has solved at Wikipedia's scale:

6 — Detecting NPOV Stress in Articles#

6.1 — Textual Indicators#

6.2 — API‑Based NPOV Stress Detection#

import requests
import re
 
def detect_npov_stress(title, lang="en"):
    """Detect NPOV stress indicators in a Wikipedia article."""
    url = f"https://{lang}.wikipedia.org/w/api.php"
    params = {
        "action": "parse",
        "page": title,
        "prop": "wikitext|templates",
        "format": "json"
    }
    resp = requests.get(url, params=params,
                        headers={"User-Agent": "TriadicFrameworks/1.0"}).json()
 
    wikitext = resp.get("parse", {}).get("wikitext", {}).get("*", "")
    templates = [t["*"] for t in resp.get("parse", {}).get("templates", [])]
 
    # Textual stress indicators
    attribution = len(re.findall(
        r'according to|some argue|critics say|proponents claim|'
        r'supporters argue|opponents argue|it is argued',
        wikitext, re.IGNORECASE))
 
    hedging = len(re.findall(
        r'\bmay\b|\bmight\b|could be|has been suggested|'
        r'it is possible|some believe|allegedly',
        wikitext, re.IGNORECASE))
 
    # Template stress indicators
    npov_templates = [t for t in templates if any(kw in t.lower()
        for kw in ["pov", "npov", "unbalanced", "disputed",
                    "contradict", "bias", "one-sided"])]
 
    # Compute stress score
    word_count = len(wikitext.split())
    attribution_density = attribution / max(word_count / 1000, 1)
    hedging_density = hedging / max(word_count / 1000, 1)
 
    stress_score = (
        attribution_density * 3 +
        hedging_density * 2 +
        len(npov_templates) * 10
    )
 
    # Classify stress level
    if stress_score < 2:
        level = "1_consensus"
    elif stress_score < 5:
        level = "2_nuanced"
    elif stress_score < 10:
        level = "3_contested"
    elif stress_score < 20:
        level = "4_polarized"
    else:
        level = "5_irreconcilable"
 
    return {
        "article": title,
        "word_count": word_count,
        "attribution_count": attribution,
        "hedging_count": hedging,
        "npov_templates": npov_templates,
        "attribution_density": round(attribution_density, 2),
        "hedging_density": round(hedging_density, 2),
        "stress_score": round(stress_score, 2),
        "stress_level": level
    }

6.3 — Batch Domain Stress Profiling#

def domain_stress_profile(articles):
    """
    Compute NPOV stress profiles for a list of articles
    representing a knowledge domain.
    """
    results = []
    for title in articles:
        try:
            stress = detect_npov_stress(title)
            results.append(stress)
        except Exception as e:
            results.append({"article": title, "error": str(e)})
 
    # Aggregate domain statistics
    scores = [r["stress_score"] for r in results if "stress_score" in r]
    if scores:
        import statistics
        return {
            "articles_analyzed": len(scores),
            "mean_stress": round(statistics.mean(scores), 2),
            "median_stress": round(statistics.median(scores), 2),
            "max_stress": round(max(scores), 2),
            "min_stress": round(min(scores), 2),
            "dominant_level": max(
                set(r["stress_level"] for r in results if "stress_level" in r),
                key=lambda x: sum(1 for r in results
                                  if r.get("stress_level") == x)
            ),
            "detail": results
        }
    return {"error": "No articles analyzed successfully"}

7 — Worked Examples#

7.1 — Homeopathy (Stress Level 4: Polarized)#

The Homeopathy article is a textbook case of NPOV under sustained stress:

Talk page signal: 30+ archives. Recurring disputes about whether the article is "too negative" toward homeopathy. FAQ section with crystallized positions on common complaints.

RTT reading: NPOV succeeds here by maintaining a two‑tier regime structure — mainstream medical consensus as the primary regime declaration, with homeopathic claims as a bounded secondary regime. The article does not say homeopathy is wrong — it says the scientific consensus considers it ineffective. That distinction is pure NPOV as coherence operator.

7.2 — Climate Change (Stress Level 3–4: Contested to Polarized)#

Key structural insight: The same article contains sections at different NPOV stress levels. The scientific sections are near‑consensus; the policy and politics sections are polarized. NPOV must operate at different intensities within the same article.

Talk page signal: 50+ archives. Most disputes are about the political framing, not the scientific content. FAQ addresses "why doesn't the article present climate skepticism equally?"

RTT reading: Climate change demonstrates that NPOV stress is not uniform within an article. The coherence operator must adapt its constraint intensity section by section, applying strict proportionality to the political content while allowing more direct statement in the scientific content.

7.3 — Oxygen (Stress Level 1: Consensus)#

Talk page signal: 5 archives over 20 years. Mostly formatting and factual corrections. No framing disputes. No NPOV challenges.

RTT reading: NPOV at Stress Level 1 is invisible — it operates effortlessly because there are no competing regime claims. The article declares a single, uncontested regime. This is NPOV's ground state — minimum coherence effort required.

8 — NPOV Across Cultures#

8.1 — Cross‑Language NPOV Variance#

Every language Wikipedia adopts NPOV, but its application varies by cultural context:

8.2 — Structural Implications#

Key insight: NPOV is a universal structural operator with cultural parameters. The operator itself is invariant — every Wikipedia applies it. But the inputs (what sources are reliable, what views are mainstream, what framing is neutral) are culturally conditioned. This makes cross‑language comparison a powerful tool for revealing the cultural parameters of coherence.

9 — Cross‑Reference to Other Module Files#

10 — Student Exercises#

Exercise 1 — Stress Level Classification (15 minutes)#

1. Pick 3 Wikipedia articles — one you expect to be uncontested, one moderately contested, and one highly contested
2. For each, check: does it have any NPOV‑related cleanup templates? How many attribution phrases ("according to," "some argue") appear in the lead? How large is the talk page?
3. Classify each article's stress level (1–5) using the spectrum from Section 3
4. Write one sentence per article: "[Article] is at NPOV Stress Level [N] because [evidence]."

Exercise 2 — Sub‑Operator Identification (20 minutes)#

1. Pick a contested article (Stress Level 3+)
2. Find one passage in the article that demonstrates each of the 5 sub‑operators:
   • A sentence showing WEIGHT (proportional representation)
   • A sentence that avoids NOR (cites external source rather than making original claim)
   • A citation demonstrating V (verifiable claim)
   • A source that qualifies as RS (reliable source)
   • A passage applying FRINGE (bounded treatment of minority view)
3. For each, write one sentence explaining how the sub‑operator is visible

Exercise 3 — Failure Mode Detection (25 minutes)#

1. Find an article with an active {{POV}} or {{NPOV}} cleanup template (search Category:NPOV disputes)
2. Read the article and the associated talk page discussion
3. Classify the failure mode (Regime Capture, False Balance, Neutrality Paralysis, or Structural Fragmentation) using Section 4
4. Write two sentences: "This article exhibits [failure mode] because [evidence]. The coherence operator has failed at the [sub‑operator] level because [reason]."

Exercise 4 — Cross‑Language NPOV Comparison (30 minutes)#

1. Pick a topic you expect to have cultural NPOV variance (try: a territorial dispute, a religious figure, a historical conflict, or a politically loaded term)
2. Read the article in English + 2 other languages (use translation tools if needed)
3. Compare: Does the framing differ? Do different language editions emphasize different viewpoints? Is the proportionality calibrated differently?
4. Answer: "NPOV is calibrated differently across these editions because [reason]. The English edition frames the topic as [X], while the [other language] edition frames it as [Y]. This reveals that NPOV's 'neutrality' is structurally influenced by [cultural factor]."

This file is part of the Wikipedia Awareness Module in the TriadicFrameworks canon. # Revision History Regime Analysis

Purpose: Define how to read Wikipedia's revision history as temporal regime data — the structural evolution of knowledge over time. No other major knowledge source exposes this surface publicly. Every Wikipedia article carries a complete, timestamped, author‑attributed record of every structural change since its creation — often spanning 20+ years.

This file teaches students, researchers, and AIs to extract regime stability signals, identify regime transitions, and build temporal regime profiles from raw revision data.

1 — What Is a Revision History?#

Every Wikipedia article stores a complete, immutable log of every edit ever made to it. Each revision record contains:

How to Access Revision History#

2 — The Five Regime Signals in Revision History#

Signal 1: Revision Count — Regime Activity Index#

The total number of revisions is the simplest and most powerful regime signal.

Key insight: Revision count does not measure quality — it measures structural attention. A 50,000‑revision article is not 500× better than a 100‑revision article. It is 500× more structurally contested.

Signal 2: Revision Rate — Current Regime Stability#

The number of revisions per unit time (day/week/month) reveals whether the regime is currently stable, active, or in crisis.

How to Compute Revision Rate#

# Using the MediaWiki API
# Fetch revisions with timestamps, then compute rate
 
import requests
from collections import Counter
from datetime import datetime
 
url = "https://en.wikipedia.org/w/api.php"
params = {
    "action": "query",
    "titles": "Climate_change",
    "prop": "revisions",
    "rvlimit": "500",
    "rvprop": "timestamp",
    "format": "json"
}
 
response = requests.get(url, params=params).json()
pages = response["query"]["pages"]
page = next(iter(pages.values()))
 
# Count revisions per month
months = Counter()
for rev in page["revisions"]:
    ts = datetime.fromisoformat(rev["timestamp"].replace("Z", "+00:00"))
    months[f"{ts.year}-{ts.month:02d}"] += 1
 
# Print monthly revision rate
for month in sorted(months):
    print(f"{month}: {months[month]} revisions")

Signal 3: Size Delta Patterns — Regime Growth and Contraction#

Each revision records the article's size in bytes. The delta (change) between consecutive revisions reveals structural dynamics:

Size Delta as Regime Evolution Curve#

When plotted over time, cumulative article size creates a regime evolution curve:

Size (bytes)
    │
    │                          ╭───── Regime maturity plateau
    │                    ╭────╯
    │               ╭───╯
    │          ╭───╯        ← Rapid regime expansion
    │     ╭───╯
    │╭───╯
    │╯  ← Regime birth
    └────────────────────────────────→ Time

Typical "healthy" article: sigmoid growth curve
  - Regime birth → rapid expansion → gradual stabilization → plateau

Deviations from this curve are structurally significant:

• Sudden drops = content removal events (investigate: vandalism? consensus? article split?)
• Late‑stage spikes = regime perturbation (investigate: external event? new discovery?)
• Sawtooth pattern = edit war (investigate: talk page for competing claims)
• No plateau = regime never crystallized (investigate: ongoing structural disputes)

Signal 4: Revert Rate — Regime Resistance#

A revert is an edit that undoes a previous edit, restoring the article to an earlier state. The revert rate measures how strongly the existing regime resists change.

Revert Detection#

Reverts can be identified by:

1. Exact size match — revision returns article to exact byte count of a prior revision
2. Edit summary markers — summaries containing "revert," "rv," "undo," "rollback"
3. System tags — mw-revert, mw-undo, mw-rollback, mw-manual-revert
4. SHA‑1 match — revision content hash matches a prior revision's hash (definitive)

# Quarry SQL: Count reverts for an article
SELECT
  COUNT(*) AS total_revisions,
  SUM(CASE WHEN ct_tag_id IN (
    SELECT ctd_id FROM change_tag_def
    WHERE ctd_name IN ('mw-revert', 'mw-undo', 'mw-rollback')
  ) THEN 1 ELSE 0 END) AS reverts
FROM revision
JOIN change_tag ON ct_rev_id = rev_id
WHERE rev_page = (
  SELECT page_id FROM page
  WHERE page_title = 'ARTICLE_TITLE'
  AND page_namespace = 0
)

Signal 5: Editor Distribution — Regime Stewardship Structure#

Who edits an article reveals its regime stewardship model:

Editor Distribution via XTools#

The fastest way to see editor distribution is XTools:

https://xtools.wmcloud.org/articleinfo/en.wikipedia.org/ARTICLE_TITLE

XTools provides:

• Top editors by edit count
• Editor count over time
• Bot vs. human edit ratio
• IP vs. registered editor ratio
• Minor edit percentage

3 — Regime Phase Classification#

Combining all 5 signals, any article can be classified into one of 6 regime phases: