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 Status — Rough Draft 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.

Admin Page Status: Field Guide

This page documents the `

` template — its parameters, how to use it, and the reasoning behind each field. It is intended for anyone performing a calibration review or maintenance pass on a page.

Rough draft note: This is a first pass at explaining the reasoning behind each field. It will be expanded with links to the specific framework pages (Reference Standards, Reality Override Game, etc.) that each field draws its logic from, once those cross-references are added.

Description

This template tracks the maintenance and calibration status of pages within The Sovereign Games project. It stores structured data using Semantic MediaWiki properties and is completely hidden on the rendered page unless viewed by an admin (see Module:IsAdmin).

It is intended for admin and maintainer use only.

How to Use This Page

When reviewing a page, work through each field in the Field-by-Field Guide section below, in order. For select-type fields, only use the listed options — do not invent new values, as this breaks the semantic queries and dashboards that depend on consistent values. If a field genuinely doesn't apply to a given page, use "Not applicable" or "Not checked" rather than leaving it blank where those options exist; a blank field and a deliberately-assessed "not applicable" mean different things to anyone reviewing the dashboard later.

Usage

To use this template, add the following at the very bottom of a page:

{{Admin Page Status
<!-- Do Not Remove commented out Reference Options -->
<!-- === CORE STATUS === -->
<!-- options: Done, Needs review, Not started -->
| categorization = 

<!-- options: Self-Assessment, Confirmed Rating -->
| calibration_review = 

<!-- options: Development, Stable, Mature -->
| instrument_grade = 

<!-- options: Low, Moderate, High -->
| validation = 

<!-- === REVIEW METADATA === -->
<!-- Format: YYYY-MM-DD -->
| review_date = 
| reviewed_by = 

<!-- === CYCLE & PRIORITY === -->
<!-- options: Core, Supporting, Peripheral -->
| priority = 

<!-- Days before considered overdue (default: 90) -->
| review_threshold = 

<!-- === STRUCTURAL / NAVIGATIONAL === -->
<!-- options: Yes, No, Not checked -->
| has_backlinks = 

<!-- options: Yes, Has red links, Not checked -->
| outbound_links_valid = 

<!-- options: Yes, No -->
| in_outline = 

<!-- options: Yes, No -->
| in_category_outline = 

<!-- === TEMPLATES & FORMATTING === -->
<!-- options: Done, Needs review, Not started -->
| templates_complete = 

<!-- options: Meets standard, Needs work, Not checked -->
| formatting_standard = 

<!-- === CONTENT INTEGRITY === -->
<!-- options: Applied, Not applicable, Needs work -->
| symmetry_check = 

<!-- options: Yes, No, Not applicable -->
| self_report_flagged = 

<!-- options: Yes, Needs work, Not checked -->
| terminology_consistent = 

<!-- === PROCESS / DEPENDENCY === -->
<!-- options: Confirmed by other party, Self-assessed only -->
| standing_check = 

<!-- options: None open, Open, Disputed -->
| drift_report_status = 

<!-- Semi-colon separated list of pages this page depends on -->
| depends_on = 

<!-- Semi-colon separated list of pages that depend on this page -->
| cited_by = 
}}

Quick-Reference Parameter Tables

Core Status

Field	Type	Options
categorization	select	Done, Needs review, Not started
calibration_review	select	Self-Assessment, Confirmed Rating
instrument_grade	select	Development, Stable, Mature
validation	select	Low, Moderate, High

Review Metadata

Field	Type	Description
review_date	date	Last review date in YYYY-MM-DD format
reviewed_by	text	Username of the person who performed the review

Cycle & Priority

Field	Type	Description
priority	select	Core, Supporting, Peripheral
review_threshold	number	Days before a review is considered overdue (default: 90)

Structural / Navigational

Field	Type	Options
has_backlinks	select	Yes, No, Not checked
outbound_links_valid	select	Yes, Has red links, Not checked
in_outline	select	Yes, No
in_category_outline	select	Yes, No

Templates & Formatting

Field	Type	Options
templates_complete	select	Done, Needs review, Not started
formatting_standard	select	Meets standard, Needs work, Not checked

Content Integrity

Field	Type	Options
symmetry_check	select	Applied, Not applicable, Needs work
self_report_flagged	select	Yes, No, Not applicable
terminology_consistent	select	Yes, Needs work, Not checked

Process / Dependency

Field	Type	Options / Description
standing_check	select	Confirmed by other party, Self-assessed only
drift_report_status	select	None open, Open, Disputed
depends_on	text	Semi-colon separated list of pages this page depends on
cited_by	text	Semi-colon separated list of pages that depend on this page (inbound) — see note below, not intended to be manually filled

Field-by-Field Guide

Core Status

categorization

What it measures: Whether the page has been placed into the correct category structure for its type and content (Core Diagnostic, Calibration Procedures, Practical Application, etc.).

How to judge it:

Done — page sits in the category (or categories) that correctly reflect its content and type.
Needs review — page is categorized, but the categorization may be wrong, outdated, or incomplete (e.g. content evolved past its original category).
Not started — page has no meaningful categorization yet.

calibration_review

What it measures: Whether the page's content and its other Admin Page Status fields have been reviewed only by the original author, or independently confirmed by someone else.

How to judge it:

Self-Assessment — the author rated the page themselves. This is a legitimate first state, not a failure — but it should not be treated as carrying the same authority as a Confirmed Rating.
Confirmed Rating — a second party, who was not the primary author, reviewed the page's content and ratings and confirmed, adjusted, or disputed them.

Why this field exists: A standard rated only by its own author is vulnerable to the same conflict of interest as any self-graded work — the author has an interest in the standard they built being seen as sound. This field makes that distinction visible rather than hiding it.

instrument_grade

What it measures: How far along the page is in its own lifecycle as a usable tool — separate from whether it's "correct."

How to judge it:

Development — actively being built or revised; not yet reliable to lean on.
Stable — the core content and structure have settled; small refinements still possible, but the page won't fundamentally change shape.
Mature — extensively used, tested against real application, and unlikely to need structural revision (though still open to Permanent Beta correction if reality contradicts it).

validation

What it measures: How much real-world testing or evidence stands behind the page's claims, independent of how well-reasoned it sounds.

How to judge it:

Low — reasoned from first principles or a single case; not yet tested against multiple real situations.
Moderate — applied and checked in a handful of real cases; some evidence, not exhaustive.
High — applied and confirmed across many independent cases, ideally including cases the author didn't build the page around.

Common mistake: Confusing internal coherence with validation. A page can be perfectly logical and still be Low validation if it hasn't been tested against reality yet.

Review Metadata

review_date

Format: YYYY-MM-DD

The date of the most recent substantive review of this page — not the page's creation date, and not a trivial edit (typo fix, formatting). This date drives the automatic Cycle Status calculation.

reviewed_by

Format: Username

Who performed the review reflected in `review_date`. If `calibration_review` is set to "Confirmed Rating," this should be the confirming party, not the original author.

Cycle & Priority

priority

What it measures: How central this page is to the framework — used to sort the maintenance dashboard so the most important stale pages surface first, rather than everything sorting purely by date.

How to judge it:

Core — foundational pages other pages depend on (e.g. Reality Override Game, Reference Standards, Hidden Mastery hub pages).
Supporting — pages that apply or extend core concepts but aren't themselves load-bearing for the rest of the framework.
Peripheral — standalone or illustrative content; if this page went stale, little else would be affected.

review_threshold

Format: Number (days). Default: 90 if left blank.

How many days can pass before this page is considered Overdue. Core pages may warrant a shorter threshold (e.g. 30–60 days); Peripheral pages can reasonably use a longer one (e.g. 180).

Note: Cycle Status (Current / Due Soon / Overdue) is calculated automatically from `review_date` and this threshold via Module:CalibrationCycle — it is not a field you set directly.

Structural / Navigational

has_backlinks

Whether other pages actually link to this page. A page can be well-written and still be effectively invisible if nothing points to it. Check via "What links here" on the page's tools menu.

outbound_links_valid

Whether this page's own `links` point to pages that actually exist, or to red links (pages that don't exist yet, often from naming inconsistencies — e.g. "Whack-a-Mole" vs. "Whack-A-Mole").

in_outline

Whether this page is included in its own logical outline or table-of-contents structure (e.g. a hub page's `content =` section, or a "Start Here" sequence), so a reader following the intended path would actually encounter it.

in_category_outline

Whether this page is properly linked from its relevant category page(s) — distinct from `categorization` above, which checks whether the page has a category. This checks whether the category page itself lists and links back to this page where expected.

Templates & Formatting

templates_complete

Whether all expected supporting templates for this page type are present and filled in — e.g. the GameModule infobox, hidden Resource block, Development Notice where applicable.

formatting_standard

Whether the page's structure, headers, and formatting conventions match the established house style for its page type.

Content Integrity

symmetry_check

For any page that compares, critiques, or evaluates two or more systems, positions, or claims: was diagnostic inversion actually applied with matched rigor on all sides, not just the side under primary scrutiny?

How to judge it:

Applied — comparable depth (evidence, internal critics, structured measurands) was used on every side being evaluated.
Not applicable — the page doesn't compare or evaluate competing positions.
Needs work — a comparison exists, but one side received noticeably thinner or later treatment than another.

Why this field exists: This is the single most common and easiest-to-miss failure mode found in this framework's own early work — one side of a comparison gets full rigor, the other gets a thin, appended pass. This field forces an explicit check rather than leaving it to be caught by chance.

self_report_flagged

Whether the page makes a claim that currently rests only on self-report or internal introspection (with no external, checkable verification), and whether that limitation is explicitly stated on the page itself.

How to judge it:

Yes — the page contains such a claim, and the limitation is clearly noted for the reader.
No — either no such claim exists, or one does and the limitation is NOT yet noted (in which case this page needs work — treat "No" here as a flag to add the disclosure, not as "everything's fine").
Not applicable — the page makes no claims of this type at all.

terminology_consistent

Whether terms, names, and links used on this page match the spelling/capitalization/naming used consistently elsewhere in the framework (e.g. "Whack-A-Mole" not "Whack-a-mole" in some places and "Whack-A-Mole" in others).

Process / Dependency

standing_check

Whether the ratings on this page (particularly `calibration_review` and `validation`) have been confirmed by someone other than the original author, consistent with the standing/authority principle described on Reference Standards in Abstract Systems.

drift_report_status

Whether anyone has filed a Drift Report against this page (a claim that its content has drifted from observable reality or needs recalibration), and if so, whether it's still unresolved (Open) or actively contested between the reporter and the author/reviewer (Disputed).

depends_on

Format: Semi-colon separated list of page names

Other pages this page's claims or structure rely on. If one of those pages is substantively revised, this page may need a second look. Used to build the dependency-ripple view on the maintenance dashboard.

cited_by

Note: This field is not intended to be manually filled in.

Rather than a field you fill in, "what pages depend on this one" is meant to be generated automatically by querying every other page's `depends_on` field for entries pointing at this page. If you're filling this in manually right now, treat it as a placeholder until the automatic query version is built — manual maintenance of this field will drift out of sync quickly since it has to be updated on every page whenever any other page changes its dependencies.

Notes

This template is hidden by default and only rendered for admins via Module:IsAdmin.
All values are stored as Semantic MediaWiki properties for querying and reporting.
The `cited_by` field is the inverse of `depends_on` and is useful for tracking dependency ripple effects — see the note above regarding automatic generation.

Admin Page Status: Field Guide

Description

How to Use This Page

Usage

Quick-Reference Parameter Tables

Core Status

Review Metadata

Cycle & Priority

Structural / Navigational

Templates & Formatting

Content Integrity

Process / Dependency

Field-by-Field Guide

Core Status

categorization

calibration_review

instrument_grade

validation

Review Metadata

review_date

reviewed_by

Cycle & Priority

priority

review_threshold

Structural / Navigational

has_backlinks

outbound_links_valid

in_outline

in_category_outline

Templates & Formatting

templates_complete

formatting_standard

Content Integrity

symmetry_check

self_report_flagged

terminology_consistent

Process / Dependency

standing_check

drift_report_status

depends_on

cited_by

Notes

See Also