Revision as of 14:15, 15 July 2026

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.

Sovereign-Games-OG-Image.jpg

Page Structure Calibration Checklist

Purpose: Before calibrating a page's content (accuracy, symmetry, reasoning — see Template:Admin Page Status/doc's Conceptual Review), verify the page's structure is complete, current, and correctly wired. A page with perfect content but a missing Resource block, stale template, or broken transparency link is not calibration-ready. This checklist is Step 0 — run it first, every time.

Both automated and curated, deliberately: most items below can be verified by an `#ask` query (does the field/template exist). A minority require actual human/AI judgment (is it filled in *correctly*, not just present). Both passes are required — presence is not correctness.

Checklist

Item	Required?	Check Method	Notes
Development Notice	Only if page is genuinely in active development	Curated (presence appropriate, not content judgment)	Should be removed once a page reaches Confirmed or higher `instrument_grade`.
`== Page Title ==` heading	Every page	Curated	Confirm it's a real, manually-set title matching the actual page name — not left as placeholder text, not using `Page Structure Calibration Checklist`.
GameModule infobox	Every page, with narrow structural exceptions	Automated (presence) + Curated (field names current)	Confirm fields use current names (`Functional Layer` not `Calibration Type`), `Maturity` uses the 5-value scale.
Page Transparency footer	Every page	Automated (detect) + Curated (verify)	Detect which of the five states applies: `{{Page Transparency}}`, `{{Page Transparency-Subpage}}` , `{{Standalone Transparency}}` , or none present. Report the finding in the Calibration Report — do not judge correctness or auto-select; the tech decides which variant is actually appropriate for this page.
`{{Calibration Maintenance}}` block	Only on pages that retain it intentionally	Automated (presence)	Confirm present only where intended.
Standing footer (See the Game / Permanent Beta)	Every page	Automated (exact-text match)	Missing or altered footer, checked by string match.
Element ordering	Every page	Curated	Confirm required placement order per the seed template's own comments (footer above categories, categories above Resource block, etc.).
Categories	Every page	Automated (presence)	Confirm category tag(s) are present and non-empty — content-accuracy of which categories is a later calibration step, not this pass.
Hidden Resource block	Every page	Automated (presence)	Confirm block exists and all four fields (Title, URL, Description, Category) are non-empty — matching content to current page state is a later calibration step.
Admin Page Status block	Every page	Automated (field-by-field diff against canonical reference block)	Diff against Template:Admin Page Status/doc's canonical reference block. Confirm all fields present — filled-in accuracy is a later calibration step, not this pass.
Outbound links valid	Every page	Automated (Special:WantedPages)	Wiki-wide check, no manual link-clicking needed.
Backlinks exist	Every page (flag if none)	Automated (Special:LonelyPages)	Flag only — new pages are briefly orphaned by design, not automatically an error.

Reference Blocks (Current, Verified)

Use these to diff against any page's actual GameModule and Admin Page Status blocks. Do not rely on memory of field names — this is the exact mechanism that caught real missing/renamed fields multiple times tonight.

Current GameModule Reference

{{GameModule
| type = 
| category = 
| Functional Layer = 
| Application Layer = 
| Version = 
| Maturity = 
| Last Updated = 
| description = 
| contents = 
}}

Confirm: `Functional Layer` (not the old `Calibration Type`), `Maturity` uses the five-value scale (Experimental / Development / Confirmed / Field Validated / Reference Standard Candidate — not the old six-value draft), `contents` is not expected to be a stored/queryable field (see Template:GameModule/doc).

Current Admin Page Status Reference

{{Admin Page Status
| categorization = 
| calibration_review = 
| instrument_grade = 
| validation = 
| calibration_rationale = 
| review_confidence = 
| review_date = 
| reviewed_by = 
| priority = 
| review_threshold = 
| has_backlinks = 
| outbound_links_valid = 
| in_outline = 
| in_category_outline = 
| templates_complete = 
| formatting_standard = 
| symmetry_check = 
| self_report_flagged = 
| terminology_consistent = 
| standing_check = 
| drift_report_status = 
| depends_on = 
}}

Confirm: no `cited_by` field present (deprecated — generated by query, not stored). All 21 fields present, in this order, even if some values are still blank pending later content calibration.

If either reference block above ever appears to disagree with Template:GameModule/doc or Template:Admin Page Status/doc, those doc pages are correct — this checklist should be updated to match, not the reverse. This checklist is a convenience copy, not the canonical source.

Note on Automating the Related/Dependencies Section

You flagged this correctly — it should be automated before going further, and here's the concrete reasoning: a human-curated dependency list can silently drift out of sync with reality (a page's actual `depends_on` field vs. what a person remembers listing). The visible Calibration Dependencies section should stay human-curated (it requires judgment about what's genuinely load-bearing) — but the hidden field verification (does `depends_on` exist, is it non-empty for Core pages, does it match at least a subset of the visible list) can and should run automatically as an `#ask` check, flagging mismatches rather than requiring a human to notice them by inspection every time.

What This Checklist Does Not Cover

This is structural prep only. It does not evaluate:

Whether the page's content is accurate.
Whether `symmetry_check` should be Applied vs. Needs Work.
Whether `validation` and `instrument_grade` are honestly rated.

Those belong to the Content Calibration Procedure (see Open Items — not yet built), which should assume this checklist has already passed before it begins.

How to Use This Checklist

Run all Automated items first — via `#ask` queries and Special: pages, batched, not one page at a time where avoidable.
For pages that pass automated checks, run the Curated items — requires actually reading the page.
Only once both passes are clean does a page proceed to Content Calibration.
Log the result as a standard Calibration Report — structural-only passes should be noted as such ("Step 0 / structural pass only — content review pending") so nobody mistakes a clean structural pass for a completed calibration.

Calibration Dependencies

Open Items

Content Calibration Procedure does not yet exist as its own page — this page is deliberately scoped to structure only; content-level procedure (the judgment-heavy half) needs its own separate build, per the project owner's stated intent to keep the two distinct.
Automated dependency-mismatch flagging (`depends_on` vs. visible Calibration Dependencies section) is described above but not yet built as an actual query/report.
Whether this checklist itself should eventually be semi-automated as a template-driven form rather than a manual reference table is an open question — not solved now.

See the Game. Refuse the Game. Build Better.

@@ Line 123: / Line 123: @@
 == Calibration Dependencies ==
+* [[Template:GameModule/doc]]
+* [[Template:Admin Page Status/doc]]
 * [[Template:Admin Page Status/doc]]
 * [[Calibration Log: When to Create One]]

Page Structure Calibration Checklist: Difference between revisions

Sovereign (talk | contribs)