CYCLE Calibration position — Active Development This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.

Sovereign-Games-OG-Image.jpg

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 part of a page's permanent calibration history.

Heading Standard

A Calibration Report heading must contain, in this order:

The literal phrase "Calibration Report"
The exact page name (as a searchable substring)
The date in `YYYY-MM-DD` format

An optional short annotation may be added in parentheses at the end (e.g., Structural Freeze, Minor Correction, Round-Robin Convergence).

Examples of valid headings:

`== 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-18 (Tiering Update) ==`

The purpose of this standard is reliable searchability and chronological clarity, not strict punctuation enforcement.

Required Top-of-Report Fields

Immediately below the heading, the following fields must appear in this order:

Page: [Exact page name with wikilink]
Summary: One or two sentences describing what the page is and does.
Reviewer: [Name or identifier]
Review Type: Self-Assessment / Confirmed Rating, with round-robin details if applicable.

Each field must appear on its own line.

Tiered Required Elements

Not every report requires the same depth. The following tiered structure applies:

Core Elements (Always Required) These must be present in every Calibration Report:

Heading meeting the standard above
Page field (with wikilink on shared hub Talk pages)
Summary field (on shared hub Talk pages)
Reviewer field
Review Type field
Summary of Changes
Reasoning / Rationale
Open Items section (may state "None" when applicable)
Closing line: `See the Game. Refuse the Game. Build Better.`

Contextual Elements (Required on Significant Reports) These are required when the report involves material status changes or governance decisions:

What This Report Does NOT Claim — Required on structural freezes, `instrument_grade` or `validation` upgrades, or any decision with broader implications.
instrument_grade or Validation change documentation — Required when these fields are updated.
AI-Reviewer Attribution — Required when AI assistance was used in the review process.

Recommended Elements These are strongly encouraged but not mandatory on minor reports:

Confidence / Certainty Level for the findings in this report
Fields Changed (compact before/after summary)
Process Note (when the method of review itself needs explanation)
Meta-Finding, Worth Recording (when the report surfaces something larger than the immediate change)

Edit Summary Standard

An edit summary and a Calibration Report are a paired, inseparable unit. They serve different audiences:

Edit Summary — Visible in page history and watchlists. Provides immediate triage.
Calibration Report — The permanent, detailed record for future calibration work.

The edit summary is not a shortened version of the report. It must contain:

Page or scope identifier
Version number, if changed
One-line description of the nature of the change
Confirmation that a full Calibration Report exists on the Talk page

Standing Rule: An edit summary must never be created without its paired Calibration Report, and vice versa. Both are generated together.

AI-Reviewer Attribution Standard

When AI assistance is used in the review process, the report must clearly state:

Which model(s) were used
Whether the model reviewed the literal current draft or only a summary of the draft
Whether reviews were conducted independently and in parallel or sequentially

This attribution preserves provenance and prevents ambiguity about the actual review process.

Example Section Headers (Situational Vocabulary)

The headers below are suggestions, not requirements. They represent useful section titles that have emerged from real calibration reports across this project. Use them when they genuinely improve clarity. You are not expected to include all (or even most) of them in every report.

Summary of Changes (Core)
Process Note
instrument_grade: [Old] → [New]
Validation: [Old] → [New]
Fields Changed
The Full Arc, Summarized
What Each Reviewer Contributed
Why This Decision Is Trusted
Meta-Finding, Worth Recording
Open Items (Core)
What This Report Does NOT Claim (Contextual)

What Disqualifies an Entry From Being Official

An entry does not qualify as an official Calibration Report if it is missing any of the following:

A heading containing "Calibration Report", the page name, and the date
A stated Reviewer
A stated Review Type
AI attribution when AI assistance was used
A Summary of Changes
An Open Items section
A paired edit summary (or vice versa)
Direct editing of a previous report instead of adding a new dated entry

Relationship to Other Standards

This page defines the shape and minimum content of individual Calibration Reports and their paired edit summaries. It does not define when a report is required (see Decision Records: Governance Memory) or where reports should be stored (see Calibration Log: When to Create One).

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 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

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.

Page Reference

Title	Calibration Report Standard Format
URL	https://www.thesovereigngames.com/wiki/Calibration_Report_Standard_Format
Description	Defines the required elements of an official Calibration Report and its paired Edit Summary, including heading standards, tiered applicability, AI attribution, and negative-scope discipline.
Category	Meta & Framework

Meta

Menu