CYCLE Calibration position — Active Development 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.

Page Structure Calibration Checklist

Terminology: this Step 0 pass is referred to as a Pre-Calibration Check ("pre-cal") throughout this project. A pre-cal is explicitly not a calibration — it verifies structure only, never touches `review_date` or `Last Calibration`, and produces no rating changes. See the date-field rule below for why this distinction matters mechanically, not just semantically.

This is not optional preamble — it is a hard dependency. Content calibration produces judgments that get recorded in specific fields, on a specific page structure, and cross-referenced by other pages and queries. If that structure is missing, wrong, or stale, a content calibration's result has nowhere reliable to live. Skipping Step 0 does not make content calibration faster; it makes its output unreliable.

`Last Calibration` (GameModule) and `review_date` (Admin Page Status) represent the same real event — the last actual calibration — from two angles:

`review_date` is the machinery input — Module:CalibrationCycle computes `Has_cycle_status` from it. This field certifies a page as currently trustworthy.
`Last Calibration` is the public-facing mirror of the same fact.
Both update together, to the same date, in the same edit — never one without the other, and never during pre-calibration checks or minor edits. If these two fields ever diverge, that is itself a nonconformance — see Calibration Failure Log.

A display-label rename can silently drag the underlying stored property along with it. Confirmed real, not hypothetical — see Calibration Failure Log's entry on `Has calibration type`/`Has functional layer`. Changing what a field shows and changing what it's stored as are two separate actions and must be verified independently, every time either is touched.

Purpose: Before calibrating a page's content, verify the page's structure is complete, current, and correctly wired. This checklist is Step 0 — run it first, every time.

Both automated and curated, deliberately: most items below can be verified by a query. A minority require actual human/AI judgment. Both passes are required — presence is not correctness.

Sovereign-Games-OG-Image.jpg

Standard Page Creation Sequence

Step 0 (before Step 1): Check whether the page already exists. Search and check categories first — creating a duplicate page is real, avoidable waste. Exception: if getting the subject itself precisely right matters more than the risk of a duplicate, proceed to Step 1 anyway. A wrong or muddled subject is expensive to untangle later; a duplicate page is comparatively cheap to catch and merge.

Step 0.5: Confirm the page title itself is safe. Avoid `&`, `/` outside intentional subpage structure, and other URL-special characters — spell them out in plain words. Easy to forget in the moment of naming a brand-new page.

Step 1: Create the new page with the discussed subject. Use Template:New Page Seed. Creating the page, even a good draft, is not itself a calibration event — it does not set `review_date` or `Last Calibration`. Only Step 3 does.

Step 2: Pre-Calibration Check (pre-cal). Run this checklist. Structure only — do not touch `review_date`/`Last Calibration`.

Step 3: Calibration. Content review — accuracy, symmetry, evidentiary grading, round-robin if warranted. Only this step updates `review_date`/`Last Calibration`, per the minor-vs-calibration test in Template:New Page Seed/doc.

Checklist

Item	Required?	Check Method	Notes
Development Notice	Only if genuinely active development	Curated	Remove once Confirmed or higher.
`== Page Title ==` heading	Every page	Curated	Real, manually-set title, not `{{PAGENAME}}`.
GameModule infobox, positioned after the first heading AND its introductory content	Every page, narrow exceptions	Automated + Curated	Current field/display mapping (parameter `Calibration Type` displays as "Functional Layer" — confirm this matches, not reversed), 5-value Maturity scale. GameModule should NOT sit immediately under the bare heading — it belongs after any opening framing prose (Canonical Question, "why this page exists" statements, etc.) that orients the reader first. See Feature Request Log for a confirmed correct example of this placement.
`Last Calibration` and `review_date` match, are static, only change together on a real calibration	Every page	Curated (critical)	Must NOT use `{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}`. See Calibration Failure Log.
Markdown syntax leakage	Every page	Automated (string search)	Check for literal `bold`, `__underline__`, or `# heading` Markdown syntax left in wikitext instead of proper `bold`, `italic`, `== heading ==`. Common when content is drafted by an AI defaulting to Markdown habits.
Field display name matches underlying stored property	Every page using GameModule	Curated	Confirm displayed label and actual `#set`/`#cargo_store` property haven't silently diverged. See Calibration Failure Log.
Page Transparency footer	Every page	Automated + Curated	Detect: `{{Page Transparency}}`, `{{Page Transparency-Subpage}}`, `{{Standalone Transparency}}`, `{{Subpage Hub-Linked Transparency}}`, or none. Latter two confirmed broken on `Template:` namespace.
`{{RelatedPages}}`	Every page	Automated	Mandatory.
`{{Calibration Dependent}}`, `{{Calibration Dependencies Display}}`, `{{Calibration Maintenance}}`	Every page	Automated	All three mandatory.
`{{Framework Reference}}`, `{{Calibration Procedure Reference}}`, `{{Tracking Logs Reference}}`	Every page	Automated	All three mandatory.
`{{AllTemplates}}`	`Template:` namespace only	Automated	Not for content pages.
`drift_report_status` matches actual page content	Every page	Curated	Multi-value: `Breadcrumb-Open`, `Nonconformance-Open`, `Nonconformance-Open-With-Dependencies`, `Resolved-Unverified`, `Disputed`, `None open` (alone only).
Resource block (visible, not hidden)	Every page	Automated	`display:none` is deprecated.
Standing footer	Every page	Automated	Exact-text match.
Element ordering	Every page	Curated	Per seed template; seven mandatory templates in locked order.
Categories	Every page	Automated	Present and non-empty.
Admin Page Status block	Every page	Automated	Diff against canonical reference.
`depends_on` uses correct, current property/field names	Every page	Curated	Confirm references match documented canonical names, not stale or renamed ones.
Template/doc pairs — status on template only	Template/doc pairs	Curated	See Template/Doc Calibration Pattern.
Outbound links valid / Backlinks exist	Every page	Automated	Special:WantedPages / Special:LonelyPages.
Every field has an accurate, current inline options comment	Every page	Curated (critical)	Missing, stale, or incorrect inline options are a nonconformance, not a cosmetic gap — this comment is the only validation mechanism available until dropdown controls exist.
Every field has an accurate, current inline options comment	Every page — applies to both GameModule and Admin Page Status fields	Curated (critical)	Missing, stale, or incorrect inline options are a nonconformance, not a cosmetic gap — this comment is the only validation mechanism available until dropdown controls exist. Explicitly covers both templates, not Admin Page Status alone.

Reference Blocks (Current, Verified)

Critical Rule: Every Field Must State Its Exact Options Inline

Every field in Admin Page Status and GameModule must carry a hidden comment listing its exact, current, valid options — directly above the field, every time. This is not optional formatting. Until this project has real dropdown/enforced-value controls, the inline comment is the validation mechanism. A tech editing a page should never have to leave that page, dig through a doc page, or guess, to know whether a field takes `Yes/No`, a longer controlled list, or free text.

If a field's inline comment is missing, stale, or doesn't match the current canonical options, that is a nonconformance — log it per Nonconformance Reporting Procedure and correct it, the same as any other structural defect this checklist exists to catch.

This applies to every seed and reference copy of these templates — Template:New Page Seed, Template:New Page Seed/doc, Template:Calibration Maintenance Log, and this checklist's own Reference Blocks below — must all show the current, correct inline options, kept in sync with each other and with Template:Admin Page Status/doc and Template:GameModule/doc as the canonical source.

Current GameModule Reference

{{GameModule
| type = 
<!-- HIDDEN GUIDE: pick from existing controlled vocabulary (Core Diagnostic Game, Meta & Framework, etc.) — check Category pages before inventing a new type. -->
| category = 
<!-- HIDDEN GUIDE: must match an existing Category page. Do not create a new category casually. -->
| Calibration Type = 
<!-- HIDDEN GUIDE: options — Governance, Diagnostic, Maintenance, Framework, Calibration. This IS the correct parameter name — displays publicly as "Functional Layer." Do not rename this parameter; only its display label was changed, per Calibration Failure Log. -->
| Application Layer = 
<!-- HIDDEN GUIDE: options — Multi-Layer, Framework Infrastructure, Individual, Institutional. -->
| Version = 0.1
| Maturity = Experimental
<!-- HIDDEN GUIDE: 5-value scale only — Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate. See Versioning for the canonical definition. Do NOT invent new values. -->
| Last Updated = 
<!-- CRITICAL WARNING: DO NOT use {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}} here. That is a live template call — it silently shows TODAY'S date on every page view forever, which is FALSE and defeats calibration tracking. This field must be a real, static, manually-typed date, set only when an actual calibration event occurs — must match the corresponding review_date in Admin Page Status. See Calibration Failure Log for the incident this warning exists because of. This IS the correct parameter name — displays publicly as "Last Calibration." Do not rename this parameter; only its display label was changed. -->
| description = 
<!-- HIDDEN GUIDE: 1-2 sentences, public-facing, plain language. Not the same as calibration_rationale below (that one is internal/technical). -->
| contents = 
}}

Confirm: parameter is `Calibration Type` (displays as "Functional Layer"), `Last Updated` parameter (displays as "Last Calibration"), both static and matching `review_date`. If either display label ever appears to conflict with the parameter name shown here, this reference block and Template:GameModule/doc are correct — the display label is separate from the stored parameter name, per Calibration Failure Log.

Current Admin Page Status Reference

<!-- '''Note:''' There is no `cited_by` field. Inbound dependencies are generated automatically by query, not entered manually. -->
{{Admin Page Status
<!-- === CORE STATUS === -->
| categorization = 
<!-- options: Done, Needs review, Not started -->
| calibration_review = 
<!-- options: Self-Assessment, Confirmed Rating -->
| instrument_grade = 
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| validation = 
<!-- options: Low, Moderate, High -->
| calibration_rationale = 
<!-- 1-2 sentences explaining validation and instrument_grade -->
| review_confidence = 
<!-- options: High, Moderate, Low -->
| review_date = 
<!-- CRITICAL WARNING: SAME RULE AS Last Calibration above. This is NOT a live template. It is set ONLY when a real Calibration Report is filed — never during pre-cal discussion, exploration, or a check that finds nothing wrong. See Calibration Failure Log. -->
| reviewed_by = 
<!-- HIDDEN GUIDE: is this a minor edit or an actual calibration? Test: does the change affect a field rating (instrument_grade, validation, drift_report_status) or a claim's actual content/structure? If yes — real calibration, review_date updates, full report required. If pure formatting/typo/link fix with zero rating effect — minor, edit summary only, review_date stays untouched. -->
| priority = 
<!-- options: Core, Supporting, Peripheral. Main/master pages default toward Core if they are a hub for other pages. -->
| review_threshold = 
<!-- Days before overdue, default 90. Core pages typically use 30-60. -->
| has_backlinks = 
<!-- options: Yes, No, Not checked (default) -->
| outbound_links_valid = 
<!-- options: Yes, Has red links, No, Not checked -->
| in_outline = 
<!-- options: Yes, No -->
| in_category_outline = 
<!-- options: Yes, No -->
| templates_complete = 
<!-- options: Done, Needs review, Not started -->
| formatting_standard = 
<!-- options: Meets standard, Needs work, Not checked -->
| symmetry_check = 
<!-- options: Applied, Not applicable, Needs work -->
| self_report_flagged = 
<!-- options: Yes, No, Not applicable -->
| terminology_consistent = 
<!-- options: Yes, Needs work, Not checked -->
| standing_check = 
<!-- options: Confirmed by other party, Self-assessed only -->
| drift_report_status = 
<!-- options (multiple allowed, semicolon-separated): Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open. "None open" valid ONLY alone. -->
| depends_on = 
<!-- Semi-colon separated list of pages this page genuinely relies on — NOT universal infrastructure (Admin Page Status, GameModule), NOT casual mentions. See Calibration Dependencies: Standards and Process. -->
}}

Confirm: no `cited_by`, 21 fields present, `review_date` static and matches GameModule. If either reference block ever disagrees with Template:GameModule/doc or Template:Admin Page Status/doc, those doc pages are correct.

What This Checklist Does Not Cover

Content accuracy, `symmetry_check` correctness, honest `validation`/`instrument_grade` ratings — Content Calibration Procedure (not yet built).

How to Use This Checklist

Run Automated items first, batched.
Run Curated items on pages that pass.
Only then proceed to Content Calibration.
Log as a standard Calibration Report.
Log any nonconformance found per Nonconformance Reporting Procedure before fixing it.

Open Items

Content Calibration Procedure not yet built.
Automated dependency-mismatch flagging not yet built as a real query.

See the Game. Refuse the Game. Build Better.

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.

Structural Connections

Calibration Dependent

Pages that list this page as a load-bearing dependency:

Page	Priority	Instrument Grade	Last Updated	Cycle Status	Drift Status
Insights and Future Layers	Core	Experimental	2026-07-14	Current	Breadcrumb-Open
Milestone: Pre-Calibration Check Confirmed Under Adversarial Stress Test	Core	Confirmed	2026-07-14	Current	None open
Nonconformance Reporting Procedure	Core	Experimental	2026-07-20	Current	Breadcrumb-Open
Breadcrumb Tracking	Core	Experimental	2026-07-20	Current	Breadcrumb-Open
Known Site Issues & Fixes	Core	Development	2026-07-20	Current	Breadcrumb-Open
Calibration Report Standard Format	Core	Experimental	2026-07-20	Current	Breadcrumb-Open
Calibration Log: When to Create One	Core	Development	2026-07-13	Current	Breadcrumb-Open
Decision Records: Governance Memory	Core	Development	2026-07-14	Current	Breadcrumb-Open
Admin:Maintenance Dashboard	Core	Experimental	2026-07-19	Current	Breadcrumb-Open
Template:New Page Seed/doc	Supporting	Experimental	2026-07-14	Current	None open
Framework Features Reference	Supporting	Development	2026-07-20	Current	Breadcrumb-Open
Calibration Failure Log	Supporting	Experimental	2026-07-24	Current	Breadcrumb-Open
Template:Calibration Template	Supporting	Development	2026-07-20	Current	Breadcrumb-Open
Template:New Page Seed	Supporting	Experimental	2026-07-14	Current	None open

If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.

Calibration Dependencies

Pages this page relies on as load-bearing dependencies: Template:GameModule/doc • Template:Admin Page Status/doc • Calibration Log: When to Create One • Decision Records: Governance Memory • Nonconformance Reporting Procedure • Breadcrumb Tracking • Calibration Failure Log • Template/Doc Calibration Pattern If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.

Calibration References

This page is calibrated against the following core standards and reference materials:

The Sovereign Games Framework — Overall framework philosophy and operating principles
Permanent Beta — Core maintenance and continuous improvement standard
Reference Standards — Principles for traceable, confirmed standards
Calibrating Conceptual Instruments — Methodology for evaluating and refining pages
Civilizational Traceability Hierarchy — How standards should connect to reality across levels
Diagnostic Inversion Test — Mandatory self-application standard
Reality Game — Foundational reality-alignment tool
Reality Override Game — Standing discipline against protecting an existing model rather than updating it
Observable Behavior Rule — Standing principle that diagnostics evaluate observable actions, mechanisms, and consequences, not internal motive, belief, or intent
One-Way Nature of the Sovereign Games — Anti-capture design principles
The Royal Cubit Civilization (Strategy) — Long-term civilizational vision and metrology metaphor
Conceptual Instruments — Overall direction and metrology metaphor
Breadcrumb Philosophy — Standing discipline for making unresolved questions and provisional decisions explicit
Calibration Dependencies: Standards and Process — Rule that visible and hidden dependency lists must match, and that dependencies describe genuine reliance

Page Construction & Maintenance References

How we construct, maintain, and utilize each page as a self-admin control panel.

Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
Template:New Page Seed — the seed template this page's basic structure was built from.
Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.

Calibration Procedure

In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.

Tracking & Log Pages

Admin:Maintenance Dashboard - This dashboard shows pages that require calibration or review.
Nonconformance Reporting Procedure — What counts as a nonconformance and where it routes.
Known Site Issues & Fixes — Technical/mechanism bugs.
Calibration Failure Log — Calibration-design failures.
Breadcrumb Tracking — Live index of open Development Breadcrumbs.
Decision Records: Governance Memory — Why governance/structural decisions exist, plus its Index.
Insights and Future Layers — Unexpected benefits and project-wide future ideas.
Feature Request Log — Genuinely desired features that were attempted and confirmed not currently possible with available tools. Index-only; full write-ups and discussion live on Talk.
Calibration Report Standard Format - Standardrized reporting formatting.

Page Reference

Title	Page Structure Calibration Checklist
URL	https://www.thesovereigngames.com/wiki/Page_Structure_Calibration_Checklist
Description	Step 0 structural prep checklist verifying a page's templates, fields, and tooling are complete and current before content calibration begins.
Category	Meta & Framework