Jump to content

Calibration Report Standard Format: Difference between revisions

From The Sovereign Games (MoA Lab)
← Older editNewer edit →

Sovereign (talk | contribs)

3 user groups
3,681 edits
VisualWikitext
Calibration Report Standard Format v0.4 — Introduced tiering (Core/Contextual/Recommended), softened heading punctuation rule, clarified AI attribution. Full report on Talk page.
Line 8: Line 8:
| Functional Layer = Governance
| Functional Layer = Governance
| Application Layer = Framework Infrastructure
| Application Layer = Framework Infrastructure
| Version = 0.3
| Version = 0.4
| Maturity = Experimental
| Maturity = Experimental
| Last Updated = {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}
| Last Updated = {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}
| description = Defines the required elements of an official Calibration Report and its paired Edit Summary — including exact heading format, AI-reviewer attribution standards, negative-scope discipline, and a non-exhaustive vocabulary of situational section headers for use by any AI or human calibrator.
| description = Defines the required elements of an official Calibration Report and its paired Edit Summary — including heading standards, AI-reviewer attribution, tiered applicability, negative-scope discipline, and a vocabulary of situational section headers.
}}
}}


Line 20: Line 20:
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.
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.


== Required Heading Format ==
== Heading Standard ==


'''Heading format (required, exact):'''  
A Calibration Report heading must contain, in this order:
*`== Calibration Report — [Page] — [Date] ([Annotation]) ==` —
- The literal phrase '''"Calibration Report"'''
*e.g. `== Calibration Report — Slave Owner Game/Effects — 2026-07-14 (Structural Freeze) ==`.
- The exact page name (as a searchable substring)
- The date in `YYYY-MM-DD` format


The page name must appear as a literal substring of the heading itself, not only in a field below it — this is what makes browser Find land exactly on the correct report, every time, with no false matches from casual mentions elsewhere on the page. Annotation (Structural Freeze, Minor Correction, etc.) is optional and omitted if not applicable.
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 ==
== Required Top-of-Report Fields ==


Immediately below the heading, in this exact bulleted order:
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 ==


*Page: [Exact Page Name]
Not every report requires the same depth. The following tiered structure applies:
*Summary: One or two sentences — what the page is/does.
*Reviewer: [Name]
*Review Type: Self-Assessment / Confirmed Rating, plus round-robin details if applicable


Each field on its own bullet, not merged — Reviewer and Review Type are distinct fields (who vouches for this, how much weight that vouching carries) and should never share one line.
### Core Elements (Always Required)
These must be present in every Calibration Report:


== Required Elements ==
* 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.'''`


{| class="wikitable"
### Contextual Elements (Required on Significant Reports)
! Element !! Required? !! Purpose
These are required when the report involves material status changes or governance decisions:
|-
| '''Heading with date, page, annotation''' (exact format above) || Yes || Anchor linking, chronological order, and precise Find-search targeting.
|-
| '''Page''' (real wikilink) || Yes, on any shared hub Talk page || Without this, a report on a multi-page hub log is unattributable.
|-
| '''Summary''' || Yes, on any shared hub Talk page || Lets a reader identify the right report without opening the linked page first.
|-
| '''Reviewer''' || Yes || Attributes the report to a person.
|-
| '''Review Type''' || Yes || States the report's own standing per [[Reference Standards]].
|-
| '''AI-Reviewer Attribution''' (see below) || Yes, if AI-assisted round-robin was involved || Prevents ambiguity about which model reviewed what, and whether literal text or a summary was reviewed.
|-
| '''Summary of Changes''' || Yes || The factual record of what was done.
|-
| '''Reasoning / Rationale''' || Yes || Preserves the "why," distinct from the "what."
|-
| '''Confidence / Certainty Level''' (High / Moderate / Low) for this specific report || Yes || Distinct from `review_confidence` on Admin Page Status — marks how well-supported this particular entry's findings are.
|-
| '''Field ratings addressed''' (`instrument_grade`, `validation`, etc.) || Yes, if any field changed || Ties the report to the actual Admin Page Status change it justifies.
|-
| '''What This Report Does NOT Claim''' || Yes, on significant status changes || Prevents implying more than what was actually established.
|-
| '''Open Items''' || Yes || Prevents implying more finality than earned.
|-
| '''Closing line''' || Yes || `'''See the Game. Refuse the Game. Build Better.'''`
|}


== Edit Summary Standard ==
* '''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.


'''An edit summary and a Calibration Report are a paired, inseparable unit — never one without the other.''' They serve different audiences and different moments of use, not the same purpose at different lengths.
### Recommended Elements
These are strongly encouraged but not mandatory on minor reports:


* '''Calibration Report''' — the permanent, complete record, for someone who has decided to actually read what happened and why.
* Confidence / Certainty Level for the findings in this report
* '''Edit Summary''' — the triage layer, visible in `Special:History`, diffs, and watchlist notifications, '''before''' anyone opens the Talk page.
* 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)


'''The edit summary is not a shrunk-down copy of the report.''' Keep it genuinely minimal and let it point to the report, rather than duplicate it.
== Edit Summary Standard ==


=== Required Elements of an Edit Summary ===
An edit summary and a Calibration Report are a paired, inseparable unit. They serve different audiences:


{| class="wikitable"
* '''Edit Summary''' — Visible in page history and watchlists. Provides immediate triage.
! Element !! Required? !! Purpose
* '''Calibration Report''' — The permanent, detailed record for future calibration work.
|-
| '''Page/scope identifier''' || Yes || What this edit concerns.
|-
| '''Version, if changed''' || Yes, if applicable || Fast visual confirmation of progression.
|-
| '''One-line nature of change''' || Yes || Minimum needed to judge relevance while scanning history.
|-
| '''Pointer confirming a full report exists''' || Yes || Without this, a reader of history alone won't know a fuller record exists.
|}


=== Standing Rule: Generate Both Together, Every Time ===
The edit summary is not a shortened version of the report. It must contain:


'''An edit summary must never be produced without its paired Calibration Report, and vice versa — both generated in the same pass, not as a follow-up request.''' A change with a summary but no report is effectively undocumented once the summary scrolls out of view; a report with no summary is invisible to anyone scanning page history. Treat the two as one inseparable output.
* 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 ==
== AI-Reviewer Attribution Standard ==


'''AI Reviewers:'''
When AI assistance is used in the review process, the report must clearly state:
* [Model name] — reviewed [literal current draft / a summary of the draft]
* [Model name] — reviewed [independently and in parallel / sequentially, after seeing another reviewer's response]


Required because ambiguity here caused at least two real corrections during this project's development — naming this explicitly every time prevents that recurring.
* 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'''


== "What This Report Does NOT Claim" — Guidance ==
This attribution preserves provenance and prevents ambiguity about the actual review process.


* A structural freeze report should state it does '''not''' thereby claim the underlying content is factually correct, only that structural/round-robin convergence occurred.
== Example Section Headers (Situational Vocabulary) ==
* A report raising `instrument_grade` to Confirmed should state whether that confirmation came from independent human review, AI round-robin convergence, or self-assessment alone.
* A minor correction report should state it does '''not''' constitute a full recalibration of the page.


== Example Section Headers (Non-Exhaustive, Situational) ==
The following headers are available for use when a report's content warrants them. They are not mandatory on every report:


The Required Elements above are the floor, not the ceiling. The headers below are drawn from real reports built across this project — a vocabulary to draw from when a report's content genuinely calls for it, not a checklist to fill out every time.
* Summary of Changes (Core)
* Process Note
* instrument_grade: [Old] → [New]
* Validation: [Old] → [New]
* The Full Arc, Summarized
* What Each Reviewer Contributed
* Why This Decision Is Trusted
* Meta-Finding, Worth Recording
* Fields Changed
* Open Items (Core)
* What This Report Does NOT Claim (Contextual)


* '''Summary of Changes''' — the baseline factual record (required).
== What Disqualifies an Entry From Being Official ==
* '''Process Note''' — when something about *how* the report was produced needs its own explanation.
* '''instrument_grade: [Old] → [New]''' with restated `calibration_rationale` — whenever a status field actually changes.
* '''Validation: [Old] → [New]''' — same pattern, for validation specifically.
* '''The Full Arc, Summarized''' / '''The Full Process, Summarized''' — when a page went through multiple development rounds and the whole story matters, not just the latest increment.
* '''What Each Reviewer Contributed''' — when multiple reviewers each added genuinely distinct things worth attributing separately.
* '''Why This Freeze Is Trusted''' — when a freeze decision needs its own justification beyond "round-robin agreed."
* '''Meta-Finding, Worth Recording''' — when the report surfaces something bigger than the immediate change.
* '''Fields Changed''' — a compact before/after list.
* '''Open Items''' (required) — what remains unresolved.
* '''What This Report Does NOT Claim''' — required on significant status changes.


'''Guidance for AI reviewers specifically:''' a short report is not automatically wrong — a minor correction genuinely only needs the required elements. But a structural freeze, a multi-round development arc, or a finding with real implications beyond the immediate page should match the depth shown above, not settle for a thin summary table.
An entry does not qualify as an official Calibration Report if it is missing any of the following:


== What Disqualifies an Entry From Being "Official" ==
* A heading containing "Calibration Report", the page name, and the date
 
* A stated Reviewer
* No heading, or an inconsistent heading format (must include page name as literal substring, per the required format above).
* A stated Review Type
* No stated Reviewer or Review Type.
* AI attribution when AI assistance was used
* AI-assisted feedback presented without attribution to which model, or without stating literal-text-vs-summary.
* A Summary of Changes
* No Open Items section, on a report that clearly isn't final.
* An Open Items section
* No "What This Report Does NOT Claim" section on a significant status change.
* A paired edit summary (or vice versa)
* An edit summary produced without its paired Calibration Report, or vice versa.
* Direct editing of a previous report instead of adding a new dated entry
* Editing a prior report's content directly, rather than adding a new dated entry (see [[Reality Override Game#Partial Update as Camouflage]]).


== Relationship to Other Standards ==
== Relationship to Other Standards ==


This page defines the '''shape''' of an individual report and its paired edit summary. It does not define '''when''' a report is required (see [[Decision Records: Governance Memory]]'s trigger test) or '''where''' reports should be logged (see [[Calibration Log: When to Create One]]).
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.'''
'''See the Game. Refuse the Game. Build Better.'''


{{RelatedPages}}
{{RelatedPages}}
{{Standalone Transparency}}
{{Calibration Maintenance}}
{{Calibration Maintenance}}
{{Calibration Dependent}}
{{Calibration Dependent}}
Line 157: Line 150:
| Title = Calibration Report Standard Format
| Title = Calibration Report Standard Format
| URL = https://www.thesovereigngames.com/wiki/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 exact heading format, AI-reviewer attribution standards, negative-scope discipline, and example section headers.
| 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
| Category = Meta & Framework
}}
}}


{{Admin Page Status
{{Admin Page Status
Line 167: Line 159:
| instrument_grade = Experimental
| instrument_grade = Experimental
| validation = Low
| validation = Low
| calibration_rationale = Third major revision. Added exact heading format (page name as literal substring, for reliable Find-search) with proper Freeze/Annotation separation resolving a syntax collision in the original proposal. Added required top-of-report bulleted field order, correcting a merged Reviewer/Review Type line found in an existing report. Formalized Edit Summary as a paired, required companion to every Calibration Report, with its own required elements and a standing rule against generating one without the other. Added a non-exhaustive vocabulary of situational section headers, drawn from real reports built across this project, specifically to give AI reviewers (who have shown inconsistent report depth) a concrete standard of depth to match rather than an implied one. Not yet round-robin reviewed; existing reports not yet retroactively audited against this version.
| calibration_rationale = Fourth revision. Introduced light tiering (Core / Contextual / Recommended) to reduce risk of performative compliance on minor reports. Softened strict heading punctuation requirement while preserving the core standard of containing "Calibration Report", page name, and date. Improved AI-Reviewer Attribution section for clarity. Removed duplicate entry in depends_on. Not yet round-robin reviewed.
| review_confidence = Moderate
| review_confidence = Moderate
| review_date = {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}
| review_date = {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}
Line 184: Line 176:
| standing_check = Self-assessed only
| standing_check = Self-assessed only
| drift_report_status = None open
| drift_report_status = None open
| depends_on = Decision Records: Governance Memory; Calibration Log: When to Create One; Reference Standards; Reference Standards; Breadcrumb Philosophy; Reality Override Game
| depends_on = Decision Records: Governance Memory; Calibration Log: When to Create One; Reference Standards; Reality Override Game
}}
}}

Revision as of 10:25, 18 July 2026

Welcome to the MoA–TSG Lab. The wiki is the bench. The work is Metrology of the Abstract. Adopt the tools or leave them on the rack — either way, the need doesn't wait.

  • Lab Note: A redlink is not a failure. It identifies Calibration Debt—work waiting to be measured, mapped, and calibrated.

CYCLE Calibration position

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

Meta

Calibration Report Standard Format

Type Meta & Framework
Functional Layer
Application Layer Framework Infrastructure
Category Meta & Framework
Version 0.4
Maturity Experimental
Last Calibration 2026-07-30
Status Permanent Beta
Description Defines the required elements of an official Calibration Report and its paired Edit Summary — including heading standards, AI-reviewer attribution, tiered applicability, negative-scope discipline, and a vocabulary of situational section headers.

Core Principles

  • Reality gets final vote
  • See the Game. Refuse the Game. Build Better.
  • Permanent Beta

Navigation

Related


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

      1. 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.`
      1. 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.
      1. 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 following headers are available for use when a report's content warrants them. They are not mandatory on every report:

  • Summary of Changes (Core)
  • Process Note
  • instrument_grade: [Old] → [New]
  • Validation: [Old] → [New]
  • The Full Arc, Summarized
  • What Each Reviewer Contributed
  • Why This Decision Is Trusted
  • Meta-Finding, Worth Recording
  • Fields Changed
  • 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



Calibration References

This page is calibrated against the following core standards and reference materials:



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




Retrieved from "https://www.thesovereigngames.com/index.php?title=Calibration_Report_Standard_Format&oldid=2983"