Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.

Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.

CYCLE Calibration position Position — MoW Cal Lab Workbench Cycle — Active Development Status — Calibration instrument in itself This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.

MediaWiki as Calibration Infrastructure

Canonical Question: What is this MediaWiki deployment for in The Sovereign Games / Metrology of the Abstract stack — and what success criteria apply if it is an instrument, not a product wiki?

MediaWiki on this site is a calibration workbench: versioned pages, structured metadata, templates, categories, and queryable status used to run metrological discipline on conceptual instruments. It is part of the metrology system’s tooling. It is not the discipline, and it is not a traditional encyclopedia product whose quality is measured by polish or zero red links.

Sovereign-Games-OG-Image.jpg

Intended Purpose

Traceability — Edits, histories, and calibration logs remain inspectable.
Declared position — Pages can state development stage and calibration cycle honestly (Seed to Fruit Development, Development Notice, Admin Page Status).
Structured status — Semantic properties / Cargo (where enabled) support browse, query, and maintenance without relying on memory.
Public trail — Sketches, reports, debt, and revisions stay visible; path is part of the product (Transparent Development principles as adopted).
Multi-operator challenge — Others can re-run, dispute, and document without a private “master file” as the only source of truth.
Future Lab On-Ramp — Make it easy for another lab to stand up without reinventing the rinse cycle — while keeping one clear traceability path until they mature enough to fork under their own certificates.

A calibration cycle that finds no edit required is a valid success. The platform exists to support checking on a schedule, not to force perpetual rewrite.

What This Instrument Is Not

Not a finished reference wiki (KPI ≠ zero red links, complete coverage, or marketing polish)
Not the Metrology of the Abstract itself (a platform change would not erase the discipline)
Not a CMS product site optimized for conversion funnels
Not legislative, judicial, or domain authority over subjects measured on the wiki
Not proof of truth by virtue of being published here

Red links on this system are treated like breadcrumbs / Calibration Debt: known need, not yet built, not hidden. Judging the site by “perfect wiki” standards is a category error — the same class of error as calling a Seed-stage page “incomplete” instead of “correctly staged.”

Operating Rules (How We Use the Wiki)

Instrument over article — Prefer explicit purpose, mechanism, boundaries, failure modes, standing, and trail over essay completeness.
Stage honesty — Declare Seed / sketch / provisional / higher standing only when earned; do not perform maturity in prose.
Path preserved — Superseded sketches are marked, not silently deleted, when they are calibration history.
Status fields matter — Admin Page Status, review dates, drift_report_status, and dependencies are part of the measurement system; leave them empty only deliberately.
Infrastructure bugs are data — Platform and template failures get logged (see site issues / calibration failure logs when present), not denied to protect appearance.
Tool ≠ discipline — Templates and extensions serve the loop (measure → document → challenge → correct). Template theater without real runs is a failure mode.

Stack Inventory (Implementation-Local)

Inventory is descriptive of this deployment and will drift; update this table when the stack changes. Exact enablement should be verified against Special:Version after any upgrade.

Layer	Component	Role in the metrology loop
Platform	MediaWiki (see Special:Version)	Versioned pages, history, categories, permissions, special pages
Structured data	Semantic MediaWiki and/or Cargo (as deployed)	Queryable properties, browse, maintenance tables (e.g. status, resources)
Logic	Scribunto (e.g. Module:CalibrationCycle)	Cycle status / date-derived maintenance signals
Review aids	ApprovedRevs (if enabled)	Optional tracking of approved revisions — not a substitute for standing rules
Discussion	DiscussionTools (+ dependencies such as Linter, if enabled)	Talk / calibration conversation surfaces
Notifications	Echo (if enabled; may be deferred)	Optional alerts — not required for calibration validity
Custom templates	Development Notice; GameModule; Admin Page Status; Resource; Page Transparency / Calibration Log headers; related maintenance templates	Declared position, module metadata, hidden structured status, transparency footers
Process pages	Calibration logs, Known Site Issues, failure logs (as they exist)	Trail for infrastructure and content calibration events

Pre-cal note: This inventory is Self-Assessed from operational knowledge of the TSG deployment. A Confirmed stack audit means a human pass against Special:Version + template list with date, not AI recollection.

Relationship to MoA and Other Implementations

Metrology of the Abstract — Discipline. This wiki is one workbench implementation.
The Sovereign Games — Primary human-systems sandbox using this infrastructure.
MoA Dictionary / other cells — May copy the instrument posture (purpose, debt, standing) with different skin or stack; they are not required to mirror every extension choice.

Portable lesson for a one-to-two person MoA cell: you need versioning + honest status + public trail + queryable maintenance. MediaWiki is a convenient pack of those properties, not a sacred dependency.

Failure Modes

Wiki-completeness capture — Optimizing for appearance of coverage instead of calibrated instruments and real Observation→Report loops.
Template theater — Rich metadata with no adversarial runs or empty standing discipline.
Standing inflation via UI — Confusing polish, categories, or extension count with Confirmed / Field Validated content.
Hidden debt — Removing red links or sketches to look finished, destroying traceability.
Single-operator fragility — Critical procedures only in one person’s shell history; not documented on-instrument.
Platform identity fusion — Treating MediaWiki outages or extension bugs as failures of MoA’s conceptual claims (or vice versa).

Typical Success Criteria

A new visitor can tell what the wiki is for within one screen of this page.
Status and stage on core instruments are declarable and queryable.
Infrastructure problems are loggable without shame theater.
Independent operators can challenge content using history, talk, and records — not private access.
Grade of this page tracks evidence of use, not ambition of the stack.

Revision Triggers

Reconsider this page when:

Major MW or extension upgrades change capability or break templates.
Semantic/Cargo property names or Admin fields are redesigned.
A second deployment (e.g. dictionary site) needs a shared vs local inventory split.
Failure modes above are observed in practice and need sharper controls.

See the Game. Refuse the Game. Build Better.

The tool is not the discipline. Judge the metrology by whether claims are calibrated and traceable — not by whether the workbench looks like a finished consumer wiki.

Structural Connections

Main Page

Page Transparency & Calibration

Calibration Log & Decision Records (via Talk Page) — This page uses Talk-only calibration tracking. Full history of reviews, version changes, calibration decisions, and any governance reasoning behind structural decisions all live on the same Talk page, per Calibration Log: When to Create One and Decision Records: Governance Memory. Not every Calibration Log entry is a Decision Record — scan the Talk page's headings for entries specifically marked as decisions; the link itself being active only confirms this page has calibration history, not that a formal decision was ever recorded.
View Current Page History — Complete edit history.

This page is under continuous calibration in line with the Permanent Beta principle.

Public Discussion Welcome

Questions, suggestions, feedback, disagreement, and proposed improvements are welcome on the Talk page.

Light rules:

Prefer evidence and concrete examples over slogans.
Apply Diagnostic Inversion Test when criticizing — the same standard to this page that you would apply elsewhere.
Distinguish observation from conclusion.
Calibration entries and Decision Records are maintenance records; public discussion belongs in ordinary Talk threads.
This framework remains in Permanent Beta. Better calibration is always in scope.

Page Reference

Title	MediaWiki as Calibration Infrastructure
URL	https://www.thesovereigngames.com/wiki/MediaWiki_as_Calibration_Infrastructure
Description	Working draft instrument page: MediaWiki and the local TSG stack treated as calibration infrastructure — purpose, non-goals, operating rules, inventory, failure modes, and standing.
Category	Meta & Framework

Type	Meta & Framework
Functional Layer	Framework Infrastructure
Application Layer	Framework Infrastructure
Category	Meta & Framework
Version	0.1
Maturity	Experimental
Last Calibration	2026-07-27
Status	Permanent Beta
Description	Declares MediaWiki (and the local extension/template stack) as calibration infrastructure for The Sovereign Games: purpose, non-goals, operating rules, inventory, failure modes, and standing — so the platform can be graded as an instrument rather than judged as an unfinished consumer wiki.