Latest revision as of 06:14, 27 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.

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. Historical residual: A display-label-only rename for Functional Layer / Last Calibration was incorrectly applied to stored parameter/property names and later reverted. Canonical parameter names remain Calibration Type and Last Updated (display labels may differ). Instance pages may still carry residual wording from the bad rename — treat mismatches as nonconformance, correct to this reference, and do not re-open a rename project during routine pre-cal. 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	When the page should declare an in-cycle calibration position (most conceptual instruments still under Permanent Beta / Seed to Fruit). Not required on pure infrastructure stubs or pages that have explicitly retired the banner by human decision.	Curated + Automated (template presence; optional property match on `position` / `cycle`)	Prefer the two-parameter form: `{{Development Notice \|position = … \|cycle = … }}` position — loose shorthand (2–4 words); not a closed list; may change next cal. Examples: `Seed`, `Foundational Draft`, `Working Draft`, `Early Draft`. No full sentences. cycle — short controlled set only: `Active Development` · `Calibration in Progress` · `Stable under check` · `Deferred`. Default if omitted: `Active Development`. Legacy single `status=` is allowed until the page is next calibrated; on that cal, migrate to `position` + `cycle`. Banner means calibration position, not “incomplete product.” Do not treat presence of the notice as nonconformance. Remove only when a calibrator decides the page no longer needs a public cycle declaration (often when grade is high and the banner is no longer useful — not automatic on Confirmed alone). Exact old rule “must be the string Active Development or nonconformance” is retired.
`== Page Title ==` heading	Every page	Curated	Real, manually set H1 that matches the actual page title. Not `{{PAGENAME}}`.
GameModule infobox, positioned after the first heading AND its introductory content	Every page, narrow exceptions	Automated + Curated	Parameter name `Calibration Type` displays as "Functional Layer"; `Last Updated` displays as "Last Calibration" — confirm display mapping is not reversed. 5-value Maturity scale only: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate. Application Layer ∈ {Multi-Layer, Framework Infrastructure, Individual, Institutional, Civilizational}. New Application Layer values only via deliberate vocabulary update (this checklist + Template:GameModule/doc), not silent invention on one page. GameModule must not sit immediately under the bare heading — it belongs after opening framing prose. See Feature Request Log for a confirmed correct placement example.
GameModule description is page-specific, not boilerplate	Every page	Curated (critical)	Non-empty is insufficient. Description must accurately and distinctly describe this page’s content/purpose — not a copy-pasted hub-level or generic blurb reused across subpages. Generic/boilerplate description = nonconformance.
`Last Calibration` and `review_date` match, are static, only change together on a real content calibration	Every page	Curated (critical)	Must NOT use `{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}`. GameModule `Last Updated` must equal Admin `review_date`. Mismatch = nonconformance. See Calibration Failure Log.
Magic-word date violation handled correctly, not just detected	Every page	Curated (critical)	If a live magic-word date is found during pre-cal (Step 2): log nonconformance first. Replace with the prior, already-documented static date if one is known/recoverable. If no prior static date is known, do not stamp today’s date — leave for content cal (Step 3) and add an Open Calibration Item. Pre-cal never sets `Last Updated` / `review_date` to a new value. Only content cal may update both, together, same edit.
Markdown syntax leakage	Every page	Automated (string search)	Literal `bold`, `__underline__`, or `# heading` in wikitext instead of `bold`, `italic`, `== heading ==`. Common when AI drafts in Markdown habits.
Field display name matches underlying stored property	Every page using GameModule	Curated	Confirm displayed label and actual `#set` / `#cargo_store` property have not silently diverged. Residual rename scar: see historical residual note above and Calibration Failure Log.
Page Transparency footer	Every page	Automated + Curated	Exactly one transparency template, in the mandatory footer order (after `RelatedPages`). Default on new pages: `{{Standalone Transparency}}`. Other variants (`Page Transparency`, `Page Transparency-Subpage`, `Subpage Hub-Linked Transparency`) only when human-confirmed for that page type. None present = flag missing. Multiple present = nonconformance. Do not invent runtime workarounds. `Standalone Transparency` and `Subpage Hub-Linked Transparency` are confirmed broken on the `Template:` namespace. If missing-transparency flags become too noisy, use a human-confirmed lookup table — not AI inference alone.
Mandatory templates (locked order)	Every page	Automated	Exact order: `{{RelatedPages}}`, `{{Standalone Transparency}}` (default on new pages; exactly one transparency template total; other variants only if human-confirmed), `{{Calibration Dependent}}`, `{{Calibration Dependencies Display}}`, `{{Calibration Maintenance}}`, `{{Framework Reference}}`, `{{Calibration Procedure Reference}}`, `{{Tracking Logs Reference}}`.
`{{AllTemplates}}`	`Template:` namespace only	Automated	Not for content pages. Elsewhere = remove.
`drift_report_status` matches actual page content	Every page	Curated	Allowed values (multi, semicolon-separated): `Breadcrumb-Open`, `Nonconformance-Open`, `Nonconformance-Open-With-Dependencies`, `Resolved-Unverified`, `Disputed`, `None open`. `None open` is valid only alone — never combined with any other value.
Resource block (visible, not hidden)	Every page	Automated	Must not be wrapped in `display:none`. Hidden Resource is deprecated = nonconformance.
Closing footer appears exactly once	Every page	Automated (count check)	Exact string `See the Game. Refuse the Game. Build Better.` must appear exactly once (count = 1, not merely ≥ 1). Duplicate footer = nonconformance (observed: Slave Owner Game/Revenge Game).
Element ordering	Every page	Curated	Closing footer → Open Calibration Items (if any) → mandatory templates in locked order → categories → Resource → Admin Page Status (typical end-of-page pattern; follow current seed if it differs).
Categories	Every page	Automated	Present and non-empty. `type` / category must match an existing Category page — do not invent new categories.
Admin Page Status block	Every page	Automated	Diff field-by-field against canonical reference (21 fields + `depends_on`). No `cited_by` field (deprecated).
Every field has an accurate, current inline options comment	Every page — GameModule and Admin Page Status	Curated (critical)	Missing, stale, or incorrect inline options = nonconformance, not cosmetic. This comment is the only validation mechanism until dropdown UI exists. Covers both templates. Development Notice parameter comments (position / cycle) should match Template:Development Notice when the notice is present.
`depends_on` is load-bearing and current	Every page	Curated	Real page names only. Forbidden: universal infrastructure (Admin Page Status, GameModule), casual mentions. Must be genuinely load-bearing for claims or structure. Confirm names match current canonical titles, not stale renames.
Template/doc pairs — status on template only	Template/doc pairs	Curated	If `Template:X` + `Template:X/doc` exist, Admin Page Status lives on `Template:X` only. Doc page = pointer link only, no separate status block. See Template/Doc Calibration Pattern.
Outbound links valid / Backlinks exist	Every page	Automated	Special:WantedPages / Special:LonelyPages.
Open Calibration Items section, if present, correctly placed and formatted	Every page (section optional)	Curated	Sits after the closing footer, before the mandatory template block. Freeform bullets: specific and actionable only. Section entirely absent if nothing is open — do not write “None open” as a placeholder. Calibrators/AI-in-calibration-role may add an item at any point during work. Remove a closed item as soon as resolution is confirmed; if uncertain, leave it and note uncertainty in the bullet.
Open Calibration Items does not hardcode a log link	Every page with the section present	Curated (critical)	Reference the page’s existing Transparency & Calibration section (wired by the transparency template) rather than hardcoding a Talk or `/Calibration Log` path.
Open Calibration Items content matches `drift_report_status`	Every page with the section present	Curated (critical)	If the section has any content, `drift_report_status` must include at least one open value: `Breadcrumb-Open`, `Nonconformance-Open`, `Nonconformance-Open-With-Dependencies`, `Resolved-Unverified`, or `Disputed`. `None open` may never coexist with a populated Open Calibration Items section or with any other status value. Mismatch = nonconformance.
Open Calibration Items edit access respected	Every page with the section present	Curated	Only calibrators or AI operating in a calibration role add/remove entries directly. Public suggestions go through Talk/discussion; a calibrator reviews and promotes valid, specific items into this section.
Readiness Gap (rating exceeds supported state)	Every page	Curated (critical)	If `instrument_grade` / Maturity claims more than the page’s documented state supports — even with zero structural defects — treat as a Readiness Gap, distinct from structural nonconformance. Downgrade the rating. Log explicitly as “Readiness Gap” in the Calibration Report. Correct language: “Not judging idea soundness — page does not yet satisfy documented criteria to support this rating.” AI round-robin does not create Confirmed standing.

Process sequence (Calibration Tech reference)

0 — Check whether the page already exists (skip create if subject-precision > duplication-risk).
0.5 — Title has no &, and no / outside real subpage structure.
1 — Create via {{New Page Seed}} if needed. Not a calibration event — leave review_date / Last Updated untouched.
2 — Structural pre-cal (this checklist). Structure only. Do not set new review_date / Last Updated values (magic-word recovery rule above is the only date touch allowed, and never a new “today” stamp).
3 — Content calibration. Only this step updates review_date and Last Updated, together, same edit.

On finding a nonconformance: log via Nonconformance Reporting Procedure before fixing.

Alignment note

This table is the human-readable source of truth for intent and expanded guidance. The AI Execution Format is the operational restatement for automated/assisted passes. If the two ever disagree, this page wins until deliberately revised.

Readiness Gap (Distinct from Structural Nonconformance)

A Readiness Gap occurs when a page's claimed instrument_grade, Maturity, or similar rating exceeds what its actual documented state currently supports — even when the page has zero structural nonconformances otherwise. This is not a judgment about whether the underlying idea or content is good; it is a judgment about whether the page has currently earned the right to claim a specific rating, per its own documented governance requirements. Example: a page rated "Foundational" (or an equivalent high-maturity claim) while missing required governance elements should be downgraded — not because the concept is wrong, but because the rating cannot currently be supported by what the page actually demonstrates. Correct reviewer language when downgrading for this reason: "I have not judged whether the underlying idea is sound. I have judged that the page does not yet satisfy the documented criteria required to support this rating." This distinction matters — it separates a procedural readiness judgment from a substantive evaluation of the content, and gives a reviewer a defensible, criteria-based answer rather than an appeal to personal opinion. A Readiness Gap is logged the same way as any other pre-cal finding — it does not require its own separate tracker, but should be named explicitly as a Readiness Gap in the Calibration Report, not folded silently into a generic "structural issue" note, so future readers understand the downgrade was about documentation state, not content quality.

Open Calibration Items (Page-Level Action List)

Distinct from Development Breadcrumb: a Development Breadcrumb explains why something is unfinished. Open Calibration Items is a short, freeform action list of what to do next — not limited to formal calibration passes; it may be added to at any point calibrators or AI are working on the page. Who can edit this section directly: calibrators and AI operating in a calibration role, only. The public is not restricted from raising concerns — but they do so via this page's Talk/discussion channel, the same as any other feedback. A calibrator reviewing Talk decides whether a public suggestion is valid and specific enough to promote into an actual Open Calibration Items entry. This keeps the list itself trustworthy and vetted, while keeping the discussion channel genuinely open to anyone, per Feature Request Log's same public-uptake pattern. If this section does not yet exist and a valid, specific item needs recording, create it. Do not wait for a separate step or a formal pass — the section coming into existence is itself the correct response to the first real item needing a home. Placement: after the closing footer, before the mandatory template block. Format:

== Open Calibration Items ==
* [specific, actionable item]
* [specific, actionable item]
''See the Page Transparency & Calibration section above for this page's Calibration Log / Decision Records / Talk links.''

Do not hardcode a specific log link here. The correct destination varies by page (Talk-only, dedicated /Calibration Log, hub-level shared log) and is already determined correctly by whichever transparency template is in use on this page — pointing back to that section, rather than duplicating its logic, avoids ever having a wrong or stale link. Rules:

Add only items that still require concrete work. An Open Item should name a specific, actionable gap, not a general unease. If you can't state what the next calibrator should actually do differently, it's not ready to be an Open Item yet.
Items may be added at any point during work on the page — not only at the end of a formal pass. Noticing something mid-read or mid-edit is a valid moment to record it immediately, so it isn't lost to memory in the meantime.
Amend wording if scope changes during a later pass.
Remove a bullet as soon as it is confirmed resolved — do not wait for a separate formal calibration pass to clean up the list. If uncertain whether an item is genuinely resolved, leave it in place and note the uncertainty in the item's own text rather than removing it prematurely.
Do not strike-through or archive closed items on the page. History lives in the Calibration Log, not here.
Omit the section entirely when empty — do not leave "None open" sitting on the page. A missing section IS the "nothing open" signal.
If this section has any content, drift_report_status MUST include at least one open value: Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, or Disputed. None open may never coexist with a populated Open Calibration Items section, and may never be combined with any other status value. Mismatch = nonconformance.

Reference Blocks (Current, Verified)

Critical Rule: Every Field Must State Its Exact Options Inline

Every field in Admin Page Status, GameModule, and Development Notice (when present) 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, Template:GameModule/doc, and Template:Development Notice as the canonical sources for their respective fields.

Current Development Notice Reference

Development Notice is a calibration-position tool, not a warning banner and not a claim that the page is an incomplete product. It declares a real in-cycle stance under Permanent Beta / Seed to Fruit Development. Presence is normal for conceptual instruments still in cycle. Removal is a calibrator decision when a public cycle declaration is no longer useful — not automatic when instrument_grade reaches Confirmed.

{{Development Notice
<!-- position: loose shorthand (2–4 words). Not a closed list. Update next cal when useful.
     Examples only: Seed | Foundational Draft | Working Draft | Early Draft | Post-calibration revise
     Avoid full sentences; detail belongs in Calibration Log / Admin calibration_rationale. -->
|position = Foundational Draft
<!-- cycle: short controlled set only.
     options: Active Development | Calibration in Progress | Stable under check | Deferred
     Default if omitted: Active Development -->
|cycle = Active Development
}}

Legacy (allowed until next content cal on that page; then migrate to position + cycle):

{{Development Notice
<!-- status: legacy single string when position/cycle not used.
     Prefer position + cycle on new edits and on next content cal. -->
|status = Active Development
}}

Confirm: banner language is calibration position / in cycle — not “incomplete product.” Do not flag presence as nonconformance. Do not require exact legacy string Active Development as the only valid form. If this block disagrees with Template:Development Notice, the template page is correct.

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, Civilizational. New values only via deliberate vocabulary update on Page Structure Calibration Checklist and Template:GameModule/doc (rationale + Decision Record or Calibration Failure Log entry) — not by inventing a value on a single content page. -->
| 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. For Development Notice, Template:Development Notice is correct.

AI Execution Format

Why this section exists: the prose/wikitable version above is built for a human to read — visual scanning, formatting cues, explanatory connective tissue. A model executing this checklist mechanically doesn't benefit from that structure the same way; it reads every table pipe and formatting token as sequential text, at real cost, with no added information density. This section compresses the same checks into a flat, unambiguous rule list — one line per check, condition → required state → citation — the same design instinct already applied to depends_on and Calibration Recommendation elsewhere in this project: machine-consumed data wants minimal syntax overhead and maximum unambiguous structure. Status: Confirmed working as operational format. Tested successfully across multiple real pages and by independent reviewers executing pre-cal passes against this format. Admin standing on this page remains Self-assessed / Development — “Confirmed working” here means the execution format is usable in practice, not that this page has Confirmed instrument_grade. It remains lighter on redundancy than the human-readable version above — a transcription error here has less built-in cross-checking to catch it — so it should still be periodically spot-checked for sync against the human page. See the "last confirmed synced" marker below. Last confirmed synced against human-readable checklist: 2026-07-27. If this section and the human-readable checklist above ever disagree, the human-readable version is correct — check this date against the checklist's own Last Calibration date; if the checklist has been updated since, this section needs re-verification before being trusted. As always: AI can make mistakes. Check this section for errors before trusting it blindly, the same as any other page on this wiki.

PAGE STRUCTURE PRE-CAL CHECKLIST — AI EXECUTION FORMAT
Source of truth: Page Structure Calibration Checklist (human-readable version). If this AI version and that page ever disagree, the human page is correct.

RULE: Development Notice = calibration-position tool, NOT an "incomplete product" warning banner. Presence is normal for instruments under Permanent Beta / Seed to Fruit.
RULE: Prefer {{Development Notice|position=…|cycle=…}}. position = loose shorthand (2–4 words); not a closed list; examples only (Seed, Foundational Draft, Working Draft, Early Draft); no full sentences. cycle ∈ {Active Development, Calibration in Progress, Stable under check, Deferred}; default if omitted = Active Development.
RULE: Legacy |status= alone is allowed until next content cal on that page; on that cal, migrate to position + cycle. Do NOT flag legacy status as nonconformance solely for missing position/cycle.
RULE: RETIRED — old rule requiring exact status string "Active Development" only, and treating variants as nonconformance. RETIRED — auto-remove notice when instrument_grade reaches Confirmed. Removal = human calibrator decision when public cycle declaration is no longer useful.
RULE: CRITICAL — Every field in GameModule AND AdminPageStatus MUST carry an inline HTML comment stating exact current valid options (or free-text guide) directly above that field. Missing, stale, or wrong comment = nonconformance. Until dropdown UI exists, the comment IS the validation mechanism. Canonical option lists: Template:GameModule/doc, Template:Admin Page Status/doc, and this checklist's Reference Blocks. If those disagree, the template doc pages win.
RULE: CRITICAL (when present) — When {{Development Notice}} is used, |position and |cycle (or legacy |status) SHOULD carry the same style of inline option/guide comments as in this checklist's Development Notice Reference Block / Template:Development Notice. Prefer position+cycle form. Missing DN comments on a content page: flag and fix when touching the banner; lower blast-radius than missing GameModule/Admin comments, but still a structural defect once the call is under edit — do not invent a third standard.
RULE: Reference Blocks in the human-readable checklist (Development Notice, GameModule, Admin Page Status) and Template:New Page Seed must stay in sync with those docs. Stale seed/reference options = nonconformance on the seed/checklist page itself when found in pre-cal of those pages.
RULE: H1 heading present, literal text (not {{PAGENAME}}), matches actual page title.
RULE: GameModule block placement = AFTER first heading AND after any intro prose (Canonical Question, framing statements). NOT immediately under bare heading.
RULE: GameModule param `Calibration Type` = canonical name, DISPLAYS as "Functional Layer". Do not treat these as different fields. Do not rename the stored parameter during pre-cal.
RULE: GameModule param `Last Updated` = canonical name, DISPLAYS as "Last Calibration". Must be static date. FORBIDDEN VALUE: {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}} (live-eval, defeats cycle tracking — see Calibration Failure Log).
RULE: IF magic-word date found during pre-cal THEN log as nonconformance. Replace with the prior, already-documented static date if one is known/recoverable. If no prior static date is known, do NOT stamp today's date as a new value — leave the field for content cal to set, and add an explicit Open Calibration Item flagging it needs a real date. Pre-cal (Step 2) never sets `Last Updated`/`review_date` to a new value, even when fixing this violation — only content cal (Step 3) may do that, and only both fields together, same edit.
RULE: GameModule.Last Updated == AdminPageStatus.review_date. MISMATCH = nonconformance.
RULE: Maturity ∈ {Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate}. No other values.
RULE: Application Layer ∈ {Multi-Layer, Framework Infrastructure, Individual, Institutional, Civilizational}. New values only via deliberate vocabulary update on this checklist + Template:GameModule/doc — not silent invention on one content page.
RULE: type/category must match existing Category page. Do not invent new category.
RULE: No Markdown syntax (**bold**, __underline__, # heading) present in wikitext. Wikitext only: '''bold''', ''italic'', == heading ==.
RULE: MANDATORY TEMPLATES, exact order: {{RelatedPages}}, {{Standalone Transparency}} (default on new pages; exactly one transparency template; other variants only if human-confirmed for page type), {{Calibration Dependent}}, {{Calibration Dependencies Display}}, {{Calibration Maintenance}}, {{Framework Reference}}, {{Calibration Procedure Reference}}, {{Tracking Logs Reference}}.
RULE: Transparency = exactly one of the allowed transparency templates, in the position above. NONE present = flag missing. Multiple present = nonconformance. Do not invent a runtime workaround.
RULE: KNOWN BROKEN — Standalone Transparency, Subpage Hub-Linked Transparency both fail on Template: namespace. No substitute exists yet. Do not invent a workaround at runtime.
RULE: If noise from missing-transparency flags becomes operationally costly, the fix is a human-confirmed lookup table mapping specific pages (or hub patterns) to the correct transparency variant — not AI runtime inference alone.
RULE: {{AllTemplates}} valid ONLY in Template: namespace. Elsewhere = remove.
RULE: drift_report_status ∈ {Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open}. Multi-value, semicolon-separated. "None open" valid ONLY alone, never combined with any other value.
RULE: Resource block MUST be visible (no display:none wrapper). Hidden = deprecated, flag as nonconformance.
RULE: Closing footer string '''See the Game. Refuse the Game. Build Better.''' must appear EXACTLY ONCE per page. Presence check alone is insufficient — verify count = 1, not merely count ≥ 1. Duplicate footer = nonconformance (observed real case: Revenge Game).
RULE: Categories present, non-empty.
RULE: AdminPageStatus block present, diff field-by-field against canonical 21-field + depends_on reference. No cited_by field (deprecated).
RULE: depends_on = real page names only. FORBIDDEN: universal infrastructure (Admin Page Status, GameModule), casual mentions. Must be genuinely load-bearing.
RULE: IF Template:X + Template:X/doc pair THEN AdminPageStatus lives on Template:X ONLY. doc page = pointer link only, no separate status block.
RULE: outbound links checked via Special:WantedPages. backlinks checked via Special:LonelyPages.
RULE: If instrument_grade/Maturity claim exceeds what page's documented state actually supports (missing governance elements, incomplete provenance, etc.) even with zero structural nonconformances = READINESS GAP, distinct from structural nonconformance. Downgrade rating. Log explicitly as "Readiness Gap" in Calibration Report, not folded into generic structural note. Correct language: "Not judging idea soundness — page does not yet satisfy documented criteria to support this rating." AI round-robin does not create Confirmed standing.
RULE: Open Calibration Items section (if present) sits after closing footer, before mandatory template block. Freeform bullets, specific/actionable only. Omit section if empty (absence IS the signal, do NOT write "None open"). Do NOT hardcode a log link — reference the page's existing Transparency & Calibration section instead. EDIT ACCESS: calibrators and AI-in-calibration-role only. Public suggestions go through page Talk/discussion; calibrator reviews and promotes valid, specific suggestions into this section — public does NOT edit this section directly.
RULE: IF Open Calibration Items has content THEN drift_report_status MUST include at least one open value (Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, or Disputed). `None open` may NEVER coexist with a populated Open Calibration Items section, and may never coexist with any other status value. Mismatch = nonconformance.
RULE: If Open Calibration Items section does not yet exist and a valid, specific item needs recording, CREATE the section (do not wait for a separate step). Placement: after closing footer, before mandatory template block.
RULE: Calibrators/AI-in-calibration-role may add an item at ANY point during work on the page — not only at the end of a formal pass. Noticing something mid-read/mid-edit is a valid moment to record it immediately, so it is not lost to memory.
RULE: Remove a closed item AS SOON AS it is confirmed resolved — do not wait for a separate formal calibration pass to clean up the list. If uncertain whether an item is actually resolved, leave it and flag uncertainty in the item text rather than removing prematurely.
RULE: GameModule `description` field must be page-specific — describe THIS page's actual content/purpose, not a copy-pasted hub-level or generic blurb reused across multiple pages. Non-empty is insufficient; verify the description text is actually accurate to and distinct for this specific page. Generic/boilerplate description = nonconformance.
SEQUENCE:
0. Check if page already exists (skip if subject-precision > duplication-risk).
0.5. Title has no &, no / outside real subpage structure.
1. Create via Template:New Page Seed. NOT a calibration event — review_date/Last Updated untouched.
2. Run this checklist (pre-cal). Structure only. review_date/Last Updated untouched (except recoverable prior static replacement for magic words per rule above — never a new "today" stamp).
3. Content calibration. ONLY this step updates review_date/Last Updated, together, same edit.
ON FINDING NONCONFORMANCE: log via Nonconformance Reporting Procedure BEFORE fixing.

What This Checklist Does Not Cover

Content accuracy, symmetry_check correctness, honest validation/instrument_grade ratings — Content Calibration Procedure (not yet built). Operator procedure for human verification after an AI pre-cal pass — documented sequence not yet built (see Open Calibration Items).

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 when Step 3 runs.
Log any nonconformance found per Nonconformance Reporting Procedure before fixing it.

See the Game. Refuse the Game. Build Better.

Open Calibration Items

Build Content Calibration Procedure (referenced as not yet built).
Automated dependency-mismatch flagging as a real query (not yet built).
Document operator procedure: human verification pass after AI pre-cal (sequence, what is checked, what may change standing, edit summary convention).
Clarify residual GameModule display-label vs stored-property rename history for calibrators on instance pages still carrying old values (canonical names remain Calibration Type / Last Updated; see Calibration Failure Log).
Keep Application Layer vocabulary (including Civilizational) synced to Template:GameModule/doc; extend only via deliberate vocabulary update.

See the Page Transparency & Calibration section above for this page's Calibration Log / Decision Records / Talk links.

Structural Connections

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.

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

Page Structure Calibration Checklist: Difference between revisions

Sovereign (talk | contribs)