Page Structure Calibration Checklist - Revision history

Sovereign: /* AI Execution Format */

2026-07-27T10:14:29Z

AI Execution Format

Sovereign: /* Reference Blocks (Current, Verified) */

2026-07-27T10:08:05Z

Reference Blocks (Current, Verified)

@@ Line 140: / Line 140: @@
 == 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 <code>Yes/No</code>, a longer controlled list, or free text.
+'''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 <code>Yes/No</code>, 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.
+'''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 GameModule Reference ===
 <pre><nowiki>
@@ Line 165: / Line 190: @@
 </nowiki></pre>
 '''Confirm:''' parameter is <code>Calibration Type</code> (displays as "Functional Layer"), <code>Last Updated</code> parameter (displays as "Last Calibration"), both static and matching <code>review_date</code>. 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 ===
 <pre><nowiki>
@@ Line 217: / Line 243: @@
 </nowiki></pre>
 '''Confirm:''' no <code>cited_by</code>, 21 fields present, <code>review_date</code> 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.'''
+'''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 <code>depends_on</code> and <code>Calibration Recommendation</code> elsewhere in this project: machine-consumed data wants minimal syntax overhead and maximum unambiguous structure.

Sovereign: /* AI Execution Format */

2026-07-27T10:03:16Z

AI Execution Format

← Older revision		Revision as of 06:03, 27 July 2026
Line 221:		Line 221:
	'''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 <code>depends_on</code> and <code>Calibration Recommendation</code> elsewhere in this project: machine-consumed data wants minimal syntax overhead and maximum unambiguous structure.		'''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 <code>depends_on</code> and <code>Calibration Recommendation</code> 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.		'''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-24.''' 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.		'''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.'''		'''As always: AI can make mistakes. Check this section for errors before trusting it blindly, the same as any other page on this wiki.'''
	<pre><nowiki>		<pre><nowiki>
	PAGE STRUCTURE PRE-CAL CHECKLIST — AI EXECUTION FORMAT		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.		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 ~~PRESENT~~ only if ~~status~~ = Active Development ~~(exact casing~~, ~~this form only). ELSE remove~~. Do NOT ~~use variant forms (active-development, active development, In~~ Development, ~~etc~~.). ~~Casing~~/~~naming variance = nonconformance~~.
			RULE: Development Notice = calibration-position banner, NOT an "incomplete product" flag. 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: When Development Notice is present, parameter HTML comments for position/cycle should match Template:Development Notice guidance when practical; missing comments on a content-page call are lower priority than missing GameModule/Admin options comments.
	RULE: H1 heading present, literal text (not {{PAGENAME}}), matches actual page title.		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 block placement = AFTER first heading AND after any intro prose (Canonical Question, framing statements). NOT immediately under bare heading.
Line 266:		Line 271:
	ON FINDING NONCONFORMANCE: log via Nonconformance Reporting Procedure BEFORE fixing.		ON FINDING NONCONFORMANCE: log via Nonconformance Reporting Procedure BEFORE fixing.
	</nowiki></pre>		</nowiki></pre>

	== What This Checklist Does Not Cover ==		== What This Checklist Does Not Cover ==
	Content accuracy, <code>symmetry_check</code> correctness, honest <code>validation</code>/<code>instrument_grade</code> ratings — Content Calibration Procedure (not yet built).		Content accuracy, <code>symmetry_check</code> correctness, honest <code>validation</code>/<code>instrument_grade</code> ratings — Content Calibration Procedure (not yet built).

Sovereign: /* Checklist */ Updated development

2026-07-27T10:00:57Z

Checklist: Updated development

← Older revision		Revision as of 06:00, 27 July 2026
Line 42:		Line 42:
	! Item !! Required? !! Check Method !! Notes		! Item !! Required? !! Check Method !! Notes
	\|-		\|-
	\| '''Development Notice''' \|\| ~~Only if genuinely active development~~ \|\| Curated + Automated (~~string~~ match) \|\| ~~Present~~ '''~~only~~''' ~~when status is the canonical value~~ <code>Active Development</code> ~~(exact casing)~~. ~~Variant forms (~~<code>~~active-development~~</code>, <code>~~active development~~</code>, <code>~~In Development~~</code>, ~~etc~~.~~) =~~ nonconformance. Remove ~~once~~ the page is no longer ~~in active development~~ (~~typically~~ when ~~instrument_grade / Maturity~~ is ~~Confirmed or higher~~ and the ~~notice~~ is no longer ~~accurate~~).		\| '''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 <code>position</code> / <code>cycle</code>) \|\| Prefer the two-parameter form:
			<code><nowiki>{{Development Notice
			\|position = …
			\|cycle = …
			}}</nowiki></code>
			'''position''' — loose shorthand (2–4 words); not a closed list; may change next cal. Examples: <code>Seed</code>, <code>Foundational Draft</code>, <code>Working Draft</code>, <code>Early Draft</code>. No full sentences.
			'''cycle''' — short controlled set only: <code>Active Development</code> · <code>Calibration in Progress</code> · <code>Stable under check</code> · <code>Deferred</code>. Default if omitted: <code>Active Development</code>.
			Legacy single <code>status=</code> is allowed until the page is next calibrated; on that cal, migrate to <code>position</code> + <code>cycle</code>.
			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'''.
	\|-		\|-
	\| '''<code>== Page Title ==</code> heading''' \|\| Every page \|\| Curated \|\| Real, manually set H1 that matches the actual page title. Not <code><nowiki>{{PAGENAME}}</nowiki></code>.		\| '''<code>== Page Title ==</code> heading''' \|\| Every page \|\| Curated \|\| Real, manually set H1 that matches the actual page title. Not <code><nowiki>{{PAGENAME}}</nowiki></code>.
Line 76:		Line 84:
	\| '''Admin Page Status block''' \|\| Every page \|\| Automated \|\| Diff field-by-field against canonical reference (21 fields + <code>depends_on</code>). No <code>cited_by</code> field (deprecated).		\| '''Admin Page Status block''' \|\| Every page \|\| Automated \|\| Diff field-by-field against canonical reference (21 fields + <code>depends_on</code>). No <code>cited_by</code> 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.		\| '''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.
	\|-		\|-
	\| '''<code>depends_on</code> 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.		\| '''<code>depends_on</code> 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.
Line 94:		Line 102:
	\| '''Readiness Gap (rating exceeds supported state)''' \|\| Every page \|\| Curated (critical) \|\| If <code>instrument_grade</code> / 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.		\| '''Readiness Gap (rating exceeds supported state)''' \|\| Every page \|\| Curated (critical) \|\| If <code>instrument_grade</code> / 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) ==		== Process sequence (Calibration Tech reference) ==
	# '''0''' — Check whether the page already exists (skip create if subject-precision > duplication-risk).		# '''0''' — Check whether the page already exists (skip create if subject-precision > duplication-risk).

Sovereign: /* Standard Page Creation Sequence */ added bullet format

2026-07-24T11:08:24Z

Standard Page Creation Sequence: added bullet format

← Older revision		Revision as of 07:08, 24 July 2026
Line 32:		Line 32:
	}}		}}
	== Standard Page Creation Sequence ==		== 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 (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 <code>&</code>, <code>/</code> 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 0.5: Confirm the page title itself is safe.''' Avoid <code>&</code>, <code>/</code> 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 <code>review_date</code> or <code>Last Calibration</code>.''' Only Step 3 does.		*'''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 <code>review_date</code> or <code>Last Calibration</code>.''' Only Step 3 does.
	'''Step 2: Pre-Calibration Check (pre-cal).''' Run this checklist. Structure only — do not touch <code>review_date</code>/<code>Last Calibration</code>.		*'''Step 2: Pre-Calibration Check (pre-cal).''' Run this checklist. Structure only — do not touch <code>review_date</code>/<code>Last Calibration</code>.
	'''Step 3: Calibration.''' Content review — accuracy, symmetry, evidentiary grading, round-robin if warranted. Only '''this''' step updates <code>review_date</code>/<code>Last Calibration</code>, per the minor-vs-calibration test in [[Template:New Page Seed/doc]].		*'''Step 3: Calibration.''' Content review — accuracy, symmetry, evidentiary grading, round-robin if warranted. Only '''this''' step updates <code>review_date</code>/<code>Last Calibration</code>, per the minor-vs-calibration test in [[Template:New Page Seed/doc]].

	== Checklist ==		== Checklist ==
	{\| class="wikitable"		{\| class="wikitable"

Sovereign: Calibration Report | 2026-07-24 | v0.5-dev | Self-Assessment | Page Structure Calibration Checklist Development/pre-cal alignment: transparency in mandatory order after RelatedPages; drift/Open Items rule unified; Civilizational + extend path; residual rename note; self Open Calibration Items + Breadcrumb-Open. review_date/Last Updated unchanged (2026-07-14). Not a full content cal.

2026-07-24T10:49:16Z

Calibration Report | 2026-07-24 | v0.5-dev | Self-Assessment | Page Structure Calibration Checklist Development/pre-cal alignment: transparency in mandatory order after RelatedPages; drift/Open Items rule unified; Civilizational + extend path; residual rename note; self Open Calibration Items + Breadcrumb-Open. review_date/Last Updated unchanged (2026-07-14). Not a full content cal.

Show changes

Sovereign: /* AI Execution Format */ Transparency template - default on new pages {{Standalone Transparency}}

2026-07-24T10:15:06Z

AI Execution Format: Transparency template - default on new pages {{Standalone Transparency}}

← Older revision		Revision as of 06:15, 24 July 2026
Line 288:		Line 288:
	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. Until such a table exists and is cited, flag only.		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. Until such a table exists and is cited, flag only.

	RULE: MANDATORY TEMPLATES, exact order: {{RelatedPages}}, {{Calibration Dependent}}, {{Calibration Dependencies Display}}, {{Calibration Maintenance}}, {{Framework Reference}}, {{Calibration Procedure Reference}}, {{Tracking Logs Reference}}.		RULE: MANDATORY TEMPLATES, exact order: {{RelatedPages}},Transparency template - default on new pages {{Standalone Transparency}}, {{Calibration Dependent}}, {{Calibration Dependencies Display}}, {{Calibration Maintenance}}, {{Framework Reference}}, {{Calibration Procedure Reference}}, {{Tracking Logs Reference}}.

	RULE: {{AllTemplates}} valid ONLY in Template: namespace. Elsewhere = remove.		RULE: {{AllTemplates}} valid ONLY in Template: namespace. Elsewhere = remove.

Sovereign: /* Process sequence (human reference) */

2026-07-21T15:50:42Z

Process sequence (human reference)

← Older revision		Revision as of 11:50, 21 July 2026
Line 108:		Line 108:
	\|}		\|}

	== Process sequence (~~human~~ reference) ==		== Process sequence (Calibration Tech reference) ==
	# '''0''' — Check whether the page already exists (skip create if subject-precision > duplication-risk).		# '''0''' — Check whether the page already exists (skip create if subject-precision > duplication-risk).
	# '''0.5''' — Title has no <code>&</code>, and no <code>/</code> outside real subpage structure.		# '''0.5''' — Title has no <code>&</code>, and no <code>/</code> outside real subpage structure.

Sovereign: /* Checklist */ Updated checklist and cleaned it up.

2026-07-21T15:49:07Z

Checklist: Updated checklist and cleaned it up.

Show changes

Sovereign: /* AI Execution Format */ cleaned up checklist

2026-07-21T15:43:39Z

AI Execution Format: cleaned up checklist

← Older revision		Revision as of 06:14, 27 July 2026
Line 254:		Line 254:
	Source of truth: Page Structure Calibration Checklist (human-readable version). If this AI version and that page ever disagree, the human page is correct.		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 ~~banner~~, NOT an "incomplete product" ~~flag~~. Presence is normal for instruments under Permanent Beta / Seed to Fruit.		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: 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: 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: 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: When Development Notice is ~~present~~, ~~parameter HTML~~ comments ~~for position~~/~~cycle should match~~ Template:Development Notice ~~guidance when practical; missing~~ comments on a content-page ~~call are~~ lower ~~priority~~ than missing GameModule/Admin options ~~comments~~.		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: 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 block placement = AFTER first heading AND after any intro prose (Canonical Question, framing statements). NOT immediately under bare heading.
Line 279:		Line 281:
	RULE: Categories present, non-empty.		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: AdminPageStatus block present, diff field-by-field against canonical 21-field + depends_on reference. No cited_by field (deprecated).
	RULE: Every field in GameModule AND AdminPageStatus carries inline HTML-comment stating exact current valid options. Missing/stale comment = nonconformance (this comment is the only validation mechanism until dropdown UI exists).
	RULE: depends_on = real page names only. FORBIDDEN: universal infrastructure (Admin Page Status, GameModule), casual mentions. Must be genuinely load-bearing.		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: IF Template:X + Template:X/doc pair THEN AdminPageStatus lives on Template:X ONLY. doc page = pointer link only, no separate status block.

← Older revision		Revision as of 11:43, 21 July 2026
Line 258:		Line 258:
	Source of truth: Page Structure Calibration Checklist (human-readable version). If this AI version and that page ever disagree, the human page is correct.		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 PRESENT only if status=active-development. ~~ELSE remove~~.		RULE: Development Notice PRESENT only if status = Active Development (exact casing, this form only). ELSE remove. Do NOT use variant forms (active-development, active development, In Development, etc.). Casing/naming variance = nonconformance.

	RULE: H1 heading present, literal text (not {{PAGENAME}}), matches actual page title.		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 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.		RULE: GameModule param `Calibration Type` = canonical name, DISPLAYS as "Functional Layer". Do not treat these as different fields.

	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: 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: 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: GameModule.Last Updated == AdminPageStatus.review_date. MISMATCH = nonconformance.

	RULE: Maturity ∈ {Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate}. No other values.		RULE: Maturity ∈ {Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate}. No other values.

	RULE: Application Layer ∈ {Multi-Layer, Framework Infrastructure, Individual, Institutional}.		RULE: Application Layer ∈ {Multi-Layer, Framework Infrastructure, Individual, Institutional}.

	RULE: type/category must match existing Category page. Do not invent new category.		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: No Markdown syntax (bold, __underline__, # heading) present in wikitext. Wikitext only: '''bold''', ''italic'', == heading ==.
	RULE: Transparency template = exactly ONE of {Page Transparency, Page Transparency-Subpage, Standalone Transparency, Subpage Hub-Linked Transparency}. NONE ~~valid~~ = flag missing~~, do not guess~~ which to ~~add~~.
	RULE: KNOWN BROKEN — Standalone Transparency, Subpage Hub-Linked Transparency both fail on Template: namespace. No substitute exists yet.		RULE: Transparency template = exactly ONE of {Page Transparency, Page Transparency-Subpage, Standalone Transparency, Subpage Hub-Linked Transparency}. Detect which template is present (or that none is). Report the finding — do NOT judge correctness or auto-select/install a transparency template based on inferred page type or "known from context." NONE present = flag missing. Wrong or multiple present = flag nonconformance. Human/calibrator confirms which variant to install.

			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. Until such a table exists and is cited, flag only.

	RULE: MANDATORY TEMPLATES, exact order: {{RelatedPages}}, {{Calibration Dependent}}, {{Calibration Dependencies Display}}, {{Calibration Maintenance}}, {{Framework Reference}}, {{Calibration Procedure Reference}}, {{Tracking Logs Reference}}.		RULE: MANDATORY TEMPLATES, exact order: {{RelatedPages}}, {{Calibration Dependent}}, {{Calibration Dependencies Display}}, {{Calibration Maintenance}}, {{Framework Reference}}, {{Calibration Procedure Reference}}, {{Tracking Logs Reference}}.

	RULE: {{AllTemplates}} valid ONLY in Template: namespace. Elsewhere = remove.		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.
			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: Resource block MUST be visible (no display:none wrapper). Hidden = deprecated, flag as nonconformance.
	RULE: Closing footer ~~= exact~~ string "'''See the Game. Refuse the Game. Build Better.'''"
			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: 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: AdminPageStatus block present, diff field-by-field against canonical 21-field + depends_on reference. No cited_by field (deprecated).

	RULE: Every field in GameModule AND AdminPageStatus carries inline HTML-comment stating exact current valid options. Missing/stale comment = nonconformance (this comment is the only validation mechanism until dropdown UI exists).		RULE: Every field in GameModule AND AdminPageStatus carries inline HTML-comment stating exact current valid options. Missing/stale comment = nonconformance (this comment is the only validation mechanism until dropdown UI exists).

	RULE: depends_on = real page names only. FORBIDDEN: universal infrastructure (Admin Page Status, GameModule), casual mentions. Must be genuinely load-bearing.		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: 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: 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."		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."
	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 (already correctly wired per page type~~: Standalone/Page Transparency/Subpage Hub-Linked~~)~~. IF section has content THEN drift_report_status MUST include Breadcrumb-Open — mismatch = nonconformance~~. 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: Open Calibration Items ~~— do NOT hardcode~~ a ~~specific log link. Reference the page's own Transparency &~~ Calibration section ~~(already correctly wired per page type: Standalone/Page Transparency/Subpage Hub-Linked) instead of duplicating link logic~~.		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 (already correctly wired per page type when present). 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: 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: 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: 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: 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: Open Calibration Items section, if present with content, requires drift_report_status to include AT LEAST ONE open value (Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, or Disputed) — NOT restricted to Breadcrumb-Open specifically. `None open` may NEVER coexist with any other value, and may never coexist with a populated Open Calibration Items section. Mismatch = nonconformance.
	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.		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.
	RULE: Development Notice `status` parameter canonical value = `Active Development` (exact casing, this form only). Do NOT use variant forms (`active-development`, `active development`, `In Development`, etc.). Casing/naming variance = nonconformance.

	SEQUENCE:		SEQUENCE:
Line 297:		Line 326:
	0.5. Title has no &, no / outside real subpage structure.		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.		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.		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.		3. Content calibration. ONLY this step updates review_date/Last Updated, together, same edit.