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.

Canonical Question: What does a Talk page entry need to contain before it counts as an official Calibration Report, rather than informal discussion?

Calibration Report Standard Format

Not everything written on a Calibration Log or hub Talk page is a Calibration Report. This page defines the required elements that make an entry official — findable, attributable, and usable as permanent calibration history — and the event-centric shape that scales from structural pre-cal to full development freezes. Visible reporting link: Operators file reports on the page’s Talk and/or Calibration Log per Calibration Log: When to Create One; this page only defines shape and minimums.

Sovereign-Games-OG-Image.jpg

Principles

Report the calibration event, not only a software-style changelog.
Method (how reviewed) and Standing (Self-Assessment vs Confirmed Rating) are different fields.
AI round-robin or multi-model agreement does not by itself create Confirmed standing.
Validation may stay Low while structure is frozen — different quality dimensions advance independently.
Narrative once; drift_report_status for query visibility — no triple-log into Breadcrumb Tracking.
Conditional sections (Nonconformance, Breadcrumb, Readiness Gap, Fields table): omit entirely when unused — do not force empty “None” headings (exception: Open Items may explicitly state none / structural-only none where the tier requires the section).
Minor edit with no claim, rating, or status effect → edit summary only (no full report).

Heading standard

A Calibration Report heading must contain, in this order:

The literal phrase Calibration Report
The exact page name (searchable substring)
The date in YYYY-MM-DD

Optional annotation in parentheses: report type / tier (e.g. Structural Pre-Cal, Structural Freeze, Confirmation, Ripple-Triggered, Nonconformance). Valid examples:

== Calibration Report — Slave Owner Game/Effects — 2026-07-14 ==
== Calibration Report — Slave Owner Game/Effects — 2026-07-14 (Structural Freeze) ==
== Calibration Report — Calibration Report Standard Format — 2026-07-24 (Standard merge) ==

Calibration procedure types

Type	Trigger	Touches review_date / Last Calibration?	Report weight
Pre-Calibration Check (pre-cal)	Before content/governance work; structure only	Never	Light tier (below)
Development	Building or revising claims, definitions, structure	Yes, when this pass is a real content/governance calibration	Full core + contextual as applicable
Confirmation	Cycle due / overdue; re-verify without intending content change	Yes, when re-verification is performed (including “nothing wrong”)	Short confirmation tier — silent “all fine” is not allowed
Ripple-Triggered	Upstream Core dependency calibration per dependency rules	Per whether content/status actually changed	Must cite upstream page and change; weight matches work done

Pre-cal is not a calibration. Confirmation without a short report defeats cycle tracking.

Required event header (all official reports)

Immediately under the heading, use this table (or the same fields in this order as labeled lines if a table is impractical on a given Talk skin):

{| class="wikitable"
! colspan="2" | Calibration event
|-
| '''Page''' || [[Exact page name]]
|-
| '''Date''' || YYYY-MM-DD
|-
| '''Report type / tier''' || Structural pre-cal / Development / Confirmation / Ripple-Triggered / Nonconformance / … 
|-
| '''Calibration objective''' || Why this pass existed (1–2 sentences)
|-
| '''Reviewer''' || Name; AI models + role if any
|-
| '''Method''' || Solo / Round-robin / Challenge review / Checklist-only / Mixed
|-
| '''Standing (this report)''' || Self-Assessment / Confirmed Rating
|-
| '''Standing impact''' || No standing change / … (explicit)
|-
| '''Evidence basis''' || Checklist, template verification, structural inspection, AI challenge (literal draft or summary — state which), manual test, query, …
|}

Summary: one to five sentences on outcome of this event (not a generic page blurb only — on shared hub Talk, include enough page identity to scan).

AI-reviewer attribution (when AI used)

Must state:

Which model(s)
Whether each reviewed the literal current draft or only a summary
Independent parallel vs sequential review

Tiered body elements

Light tier — Structural pre-cal

Required: Heading; event header; Summary; Actions performed (or equivalent); Open Items (may read “None — structural only”); closing line; paired edit summary noting structural-only / dates not advanced. Not required: Full “What this report does NOT claim” unless a grade or governance claim moved; instrument_grade upgrade docs; heavy rationale essays. Forbidden in pre-cal: Changing review_date / Last Updated to a new calibration stamp; rating upgrades.

Full tier — Development (and material freezes)

Always: Heading; event header; Summary; Actions performed; Reasoning / rationale as needed; Open Items; closing line; paired edit summary. When material status or governance decisions: What this report does NOT claim; instrument_grade / validation change docs; Fields before/after table if fields moved. Conditional (omit if unused): Nonconformance block; Development Breadcrumb block; Readiness Gap (“why not advanced”).

Short tier — Confirmation

Required: Heading (annotation Confirmation); event header with objective “re-verify on cycle”; Evidence basis; Standing impact (usually no change or list findings); Open Items; statement that re-verification occurred even if nothing failed; paired edit summary; closing line.

Ripple-Triggered

Same weight as the work done, plus explicit upstream citation (page + change that triggered review).

Edit summary standard

Edit summary and Calibration Report are a paired unit when a full report is required:

Summary: scope, version if changed, one-line nature of change, pointer that full report exists on Talk/log
Report: permanent detail

Standing rule: Do not create a full official report without its paired edit summary, or an edit summary that claims a full calibration without the report — when the pass is in a tier that requires a report. Pure minor edits remain summary-only.

Situational section headers (vocabulary, not mandatory list)

Use when they improve clarity: Actions performed; Process note; instrument_grade / Validation change; Fields changed; What each reviewer contributed; Why this decision is trusted; Meta-finding worth recording; Open Items; What this report does NOT claim; Nonconformance; Development Breadcrumb; Readiness Gap.

What disqualifies an entry from being official

Missing any of: heading with “Calibration Report” + page name + date; Reviewer; Method and Standing (or legacy Review Type clearly stating both); AI attribution when AI was used; Actions / Summary of changes; Open Items section where the tier requires it; paired edit summary where the tier requires a full report; editing a previous report in place instead of a new dated entry.

Copy-paste skeleton (full tier)

== Calibration Report — [[PAGE]] — YYYY-MM-DD (Report type) ==
{| class="wikitable"
! colspan="2" | Calibration event
|-
| '''Page''' || [[PAGE]]
|-
| '''Date''' || YYYY-MM-DD
|-
| '''Report type / tier''' || …
|-
| '''Calibration objective''' || …
|-
| '''Reviewer''' || …
|-
| '''Method''' || …
|-
| '''Standing (this report)''' || Self-Assessment / Confirmed Rating
|-
| '''Standing impact''' || …
|-
| '''Evidence basis''' || …
|}
'''Summary:''' …

=== Actions performed ===
* …

=== Fields and ratings (only if changed) ===
{| class="wikitable"
! Field !! Before !! After
|-
| … || … || …
|}
'''calibration_rationale:''' …
'''review_confidence:''' High / Moderate / Low

=== Nonconformance ===
<!-- omit if none -->

=== Development Breadcrumb ===
<!-- omit if none -->

=== Readiness Gap ===
<!-- omit if none -->

=== Open Items ===
* …

=== What this report does NOT claim ===
* AI round-robin does not by itself create Confirmed standing.
* …
'''See the Game. Refuse the Game. Build Better.'''
~~~~

Relationship to other standards

This page: shape and minimums of official reports and paired summaries.
Page Structure Calibration Checklist: Step 0 structure — pre-cal verifies it; does not replace this report standard.
Calibration Log: When to Create One: where reports live.
Decision Records: Governance Memory: when certain decisions require records beyond routine cal.
Nonconformance Reporting Procedure / Breadcrumb Tracking / Calibration Failure Log: specialized homes; event write-up still follows this format when a full report is filed.

Open Calibration Items

After a few Confirmation and Ripple reports exist, add one worked example of each light tier on Talk of this page.
Align any remaining “Review Type only” examples in the wild to Method + Standing on contact.

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

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
Nonconformance Reporting Procedure	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
Framework Features Reference	Supporting	Development	2026-07-20	Current	Breadcrumb-Open
Template:Calibration Maintenance Log	Supporting	Development	2026-07-14	Current	Breadcrumb-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: Decision Records: Governance Memory • Calibration Log: When to Create One • Page Structure Calibration Checklist • Nonconformance Reporting Procedure 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	Calibration Report Standard Format
URL	https://www.thesovereigngames.com/wiki/Calibration_Report_Standard_Format
Description	Official Calibration Report shape: heading rules, event header, procedure tiers, edit-summary pairing, AI attribution, conditional sections, anti-overclaim discipline.
Category	Meta & Framework