Jump to content

Calibration Log: When to Create One: Difference between revisions

From The Sovereign Games

Sovereign (talk | contribs)

3 user groups
3,599 edits
VisualWikitext
Created page with "{{Development Notice |status = Active Development }} {{GameModule | type = Meta & Framework | category = Meta & Framework | Functional Layer = Governance | Application Layer = Framework Infrastructure | Version = 0.3 | Maturity = Developing | Last Updated = 2026-07-12 | description = Decision procedure for determining whether a page needs a dedicated /Calibration Log subpage or whether Talk page Calibration Reports alone are sufficient. }}..."
 
Calibration Report | 2026-07-24 | v0.4-dev | Self-Assessment | Calibration Log: When to Create One Structural cleanup + examples (Talk-only for site logs/standards). Report shape deferred to Report Standard. Dates unchanged. Breadcrumb-Open for example/link follow-ups.
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
|status = Active Development
|status = Active Development
}}
}}
 
'''Canonical Question:''' When does a page need a dedicated <code>/Calibration Log</code> subpage, and when are Talk-page Calibration Reports enough?
= Calibration Log: When to Create One =
Decision procedure for choosing '''Talk reports only''' versus a dedicated <code>/Calibration Log</code> subpage. Official report '''shape''' is defined by [[Calibration Report Standard Format]] — this page only answers '''where''' reports and current-state notes live.
{{GameModule
{{GameModule
| type = Meta & Framework
| type = Meta & Framework
<!-- HIDDEN GUIDE: existing controlled vocabulary only -->
| category = [[:Category:Meta & Framework|Meta & Framework]]
| category = [[:Category:Meta & Framework|Meta & Framework]]
| Functional Layer = Governance
| Calibration Type = Governance
<!-- HIDDEN GUIDE: Governance, Diagnostic, Maintenance, Framework, Calibration — param name Calibration Type; displays as Functional Layer. Do not rename the stored parameter. -->
| Application Layer = Framework Infrastructure
| Application Layer = Framework Infrastructure
| Version = 0.3
<!-- HIDDEN GUIDE: Multi-Layer, Framework Infrastructure, Individual, Institutional, Civilizational -->
| Maturity = Developing
| Version = 0.4
| Last Updated = 2026-07-12
| Maturity = Development
| description = Decision procedure for determining whether a page needs a dedicated /Calibration Log subpage or whether Talk page Calibration Reports alone are sufficient.
<!-- HIDDEN GUIDE: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| Last Updated = 2026-07-13
<!-- CRITICAL: static only. Must match review_date. FORBIDDEN: magic words -->
| description = Decision procedure: dedicated /Calibration Log subpage vs Talk-only Calibration Reports. Report format is separate (Calibration Report Standard Format).
}}
}}
 
== Review philosophy ==
== Calibration Log: When to Create One ==
A <code>/Calibration Log</code> is '''not''' an archive of every review and '''not''' a dump of all project reports.
 
It exists when the page’s '''current calibrated state''' (version, grade, maintenance posture, open structural notes) is useful '''apart from''' any single report’s narrative.
This page defines when a dedicated `/Calibration Log` subpage is warranted versus using Talk page Calibration Reports only.
Talk holds the '''event history''' (official reports). The log subpage, when warranted, holds a '''maintained current-state hub''' plus pointers into that history — not a second full copy of every report.
 
== The distinction ==
== Review Philosophy ==
'''Create <code>/Calibration Log</code> when:''' the page’s payload is a diagnostic or conceptual claim about reality — diagnostic game, calibration procedure, reference standard, load-bearing hypothesis — and a separately maintained current-state summary is genuinely useful beyond “read the latest Talk report.”
The purpose of a /Calibration Log is not to archive every review. It exists to maintain the current calibrated state of pages whose maturity and status cannot be fully understood from any single report alone.
'''Talk reports only when:''' the page is infrastructure, procedural, governance, tracking, or site-maintenance content — templates, standards, dashboards, known-issues logs, scar indexes. Calibration means “does this mechanism or rule still work as intended?”; the latest official report is usually enough.
 
== Decision procedure ==
== The Distinction ==
# Read the page and its most recent official Calibration Report (if any).
 
# Ask: '''If someone read only the most recent report, would they fully understand the page’s current state — or is there a meaningful current-state summary that should exist independently of any single report?'''
'''Use a `/Calibration Log` subpage when:''' the page's content is itself a diagnostic or conceptual claim about reality — a calibration procedure, a diagnostic game, a reference standard, or a hypothesis. These pages benefit from a separately maintained ''current state'' summary (version, instrument grade, maintenance notes) distinct from the history of how that state was reached.
# '''Latest report is enough''' → Talk only. Do not create a log subpage for bureaucracy.
 
# '''Independent current-state summary is genuinely useful''' → create <code>/Calibration Log</code>.
'''Use Talk page Calibration Reports only when:''' the page is infrastructure, procedural, or governance content — a template, a doc page, or a workflow standard. Here, calibration means "does the mechanism work as intended," and the latest report is usually sufficient.
# When unsure, default to '''Talk only'''; add a log later if complexity proves it (see below).
 
== Decision Procedure ==
 
# Read the page and its most recent Calibration Report.
# Ask: '''"If someone read only the most recent report, would they fully understand the page's current state — or is there a meaningful summary that exists independently of any single report?"'''
# '''Yes, the latest report is enough''' → use Talk page reports only.
# '''No, an independent summary is genuinely useful''' → create the `/Calibration Log` subpage.
 
== Examples ==
== Examples ==
{| class="wikitable"
{| class="wikitable"
! Page Type !! Recommendation !! Why
! Page type !! Recommendation !! Why
|-
|-
| Calibration Procedure || `/Calibration Log` subpage || Complex claim, benefits from a maintained summary separate from report history
| Diagnostic Game (e.g. Reality Override, Slave Owner module pages)
| <code>/Calibration Log</code>
| Content maturity and maintenance notes worth tracking apart from report history
|-
|-
| Diagnostic Game (e.g. Reality Override Game) || `/Calibration Log` subpage || Content maturity is worth tracking independently
| Calibration procedure / reference standard
| <code>/Calibration Log</code>
| Load-bearing claims; other pages depend on current state
|-
|-
| Reference Standard || `/Calibration Log` subpage || High-stakes, load-bearing content other pages depend on
| Template documentation (e.g. Admin Page Status/doc)
| Talk only
| Procedural; latest report sufficient
|-
|-
| Template documentation (e.g. Admin Page Status/doc) || Talk page only || Procedural; latest report is sufficient
| Governance / workflow standard (this page, Report Standard, NCR procedure)
| Talk only
| No independent “instrument state” beyond the latest report and the page text
|-
|-
| Governance/workflow standard || Talk page only || No independent state to summarize beyond the latest report
| [[Known Site Issues & Fixes]]
| Talk only
| Article = issue entries; Talk = discussion/reports
|-
| [[Calibration Failure Log]] (scar index)
| Talk only
| Thin index; not a report archive
|-
| [[Breadcrumb Tracking]], Maintenance Dashboard
| Talk only
| Index/dashboard infrastructure
|-
| [[Decision Records: Governance Memory]]
| Talk only (unless Index complexity later demands a log)
| Decision memory, not a diagnostic instrument page
|}
|}
 
== Navigation templates ==
== Navigation Templates ==
Nesting and transparency patterns: see project navigation / [[Template:Calibration Template]] (or current equivalent) for which templates apply at article vs log vs Talk depth. Pre-cal mandatory footer order remains governed by [[Page Structure Calibration Checklist]].
 
== Changing your mind later ==
See [[Template:Calibration Template]] for the full quick-reference on which navigation templates to use at different nesting levels.
Decisions are not permanent. Talk-only pages may gain a <code>/Calibration Log</code> if current-state summary becomes real. Retiring an unused empty log is allowed; do not keep empty logs “for symmetry.”
 
== Relationship to other standards ==
== Changing Your Mind Later ==
* [[Calibration Report Standard Format]] — what an official report contains
 
* [[Page Structure Calibration Checklist]] — structural pre-cal; template order
Decisions are not permanent. If a Talk-only page later develops content complex enough to warrant a subpage, creating the log retroactively is fine. The reverse is rarer but allowed.
* [[Nonconformance Reporting Procedure]] — NCR routing (not where-to-put-every-report)
 
* [[Calibration Dependencies: Standards and Process]] — dependency vs cross-reference
== Calibration dependencies ==
Intellectual dependencies for this decision procedure:
* [[Calibration Report Standard Format]]
* [[Calibration Dependencies: Standards and Process]]
Scaffolding templates (GameModule, Admin Page Status) are structural infrastructure, not listed as intellectual dependencies. Mere “see also” links are not dependencies.
'''See the Game. Refuse the Game. Build Better.'''
'''See the Game. Refuse the Game. Build Better.'''
 
== Open Calibration Items ==
This page is in '''Permanent Beta'''.
* After a few more module logs exist, confirm examples still match practice; adjust table if a class was miscategorized.
 
* Resolve any stale link if Template:Calibration Template was renamed — point to current nav doc.
''See the Page Transparency & Calibration section above for this page's Calibration Log / Decision Records / Talk links.''
{{RelatedPages}}
{{Standalone Transparency}}
{{Calibration Dependent}}
{{Calibration Dependencies Display}}
{{Calibration Maintenance}}
{{Framework Reference}}
{{Calibration Procedure Reference}}
{{Tracking Logs Reference}}
[[Category:Meta & Framework]]
[[Category:Meta & Framework]]
 
[[Category:Site Maintenance]]
<div style="display:none;">
{{Resource
{{Resource
| Title = Calibration Log: When to Create One
| Title = Calibration Log: When to Create One
| URL = https://www.thesovereigngames.com/wiki/Calibration_Log:_When_to_Create_One
| URL = https://www.thesovereigngames.com/wiki/Calibration_Log:_When_to_Create_One
| Description = Decision procedure for determining whether a page needs a dedicated /Calibration Log subpage or whether Talk page reports are sufficient.
| Description = Decision procedure for dedicated /Calibration Log subpage vs Talk-only Calibration Reports. Report format is defined elsewhere.
| Category = Meta & Framework
| Category = Meta & Framework
}}
}}
</div>
{{Admin Page Status
{{Admin Page Status
<!-- options: Done, Needs review, Not started -->
| categorization = Done
| categorization = Done
<!-- options: Self-Assessment, Confirmed Rating -->
| calibration_review = Self-Assessment
| calibration_review = Self-Assessment
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| instrument_grade = Development
| instrument_grade = Development
<!-- options: Low, Moderate, High -->
| validation = Moderate
| validation = Moderate
| review_date = 2026-07-12
| calibration_rationale = Structural cleanup: Calibration Type param, Maturity vocabulary, visible Resource, mandatory footer order, examples aligned to Known Site Issues / scar index / standards = Talk only. Purpose narrowed to where-to-store, not report shape. Cycle dates unchanged (developmental alignment of procedure text).
| review_confidence = Moderate
| review_date = 2026-07-13
| reviewed_by = Sovereign
| reviewed_by = Sovereign
| priority = Core
| priority = Core
Line 92: Line 129:
| terminology_consistent = Yes
| terminology_consistent = Yes
| standing_check = Self-assessed only
| standing_check = Self-assessed only
| drift_report_status = None open
| drift_report_status = Breadcrumb-Open
| depends_on = None
| depends_on = Calibration Report Standard Format; Calibration Dependencies: Standards and Process; Page Structure Calibration Checklist
}}
}}

Latest revision as of 10:22, 24 July 2026

CYCLE Calibration position — Active Development

This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit.

Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.



Canonical Question: When does a page need a dedicated /Calibration Log subpage, and when are Talk-page Calibration Reports enough?

Calibration Log: When to Create One

Decision procedure for choosing Talk reports only versus a dedicated /Calibration Log subpage. Official report shape is defined by Calibration Report Standard Format — this page only answers where reports and current-state notes live.



Sovereign-Games-OG-Image.jpg

Meta

Calibration Log: When to Create One

Type Meta & Framework
Functional Layer Governance
Application Layer Framework Infrastructure
Category Meta & Framework
Version 0.4
Maturity Development
Last Calibration 2026-07-13
Status Permanent Beta
Description Decision procedure: dedicated /Calibration Log subpage vs Talk-only Calibration Reports. Report format is separate (Calibration Report Standard Format).

Core Principles

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

Navigation

Related


Review philosophy

A /Calibration Log is not an archive of every review and not a dump of all project reports. It exists when the page’s current calibrated state (version, grade, maintenance posture, open structural notes) is useful apart from any single report’s narrative. Talk holds the event history (official reports). The log subpage, when warranted, holds a maintained current-state hub plus pointers into that history — not a second full copy of every report.

The distinction

Create /Calibration Log when: the page’s payload is a diagnostic or conceptual claim about reality — diagnostic game, calibration procedure, reference standard, load-bearing hypothesis — and a separately maintained current-state summary is genuinely useful beyond “read the latest Talk report.” Talk reports only when: the page is infrastructure, procedural, governance, tracking, or site-maintenance content — templates, standards, dashboards, known-issues logs, scar indexes. Calibration means “does this mechanism or rule still work as intended?”; the latest official report is usually enough.

Decision procedure

  1. Read the page and its most recent official Calibration Report (if any).
  2. Ask: If someone read only the most recent report, would they fully understand the page’s current state — or is there a meaningful current-state summary that should exist independently of any single report?
  3. Latest report is enough → Talk only. Do not create a log subpage for bureaucracy.
  4. Independent current-state summary is genuinely useful → create /Calibration Log.
  5. When unsure, default to Talk only; add a log later if complexity proves it (see below).

Examples

Page type Recommendation Why
Diagnostic Game (e.g. Reality Override, Slave Owner module pages) /Calibration Log Content maturity and maintenance notes worth tracking apart from report history
Calibration procedure / reference standard /Calibration Log Load-bearing claims; other pages depend on current state
Template documentation (e.g. Admin Page Status/doc) Talk only Procedural; latest report sufficient
Governance / workflow standard (this page, Report Standard, NCR procedure) Talk only No independent “instrument state” beyond the latest report and the page text
Known Site Issues & Fixes Talk only Article = issue entries; Talk = discussion/reports
Calibration Failure Log (scar index) Talk only Thin index; not a report archive
Breadcrumb Tracking, Maintenance Dashboard Talk only Index/dashboard infrastructure
Decision Records: Governance Memory Talk only (unless Index complexity later demands a log) Decision memory, not a diagnostic instrument page

Nesting and transparency patterns: see project navigation / Template:Calibration Template (or current equivalent) for which templates apply at article vs log vs Talk depth. Pre-cal mandatory footer order remains governed by Page Structure Calibration Checklist.

Changing your mind later

Decisions are not permanent. Talk-only pages may gain a /Calibration Log if current-state summary becomes real. Retiring an unused empty log is allowed; do not keep empty logs “for symmetry.”

Relationship to other standards

Calibration dependencies

Intellectual dependencies for this decision procedure:

Scaffolding templates (GameModule, Admin Page Status) are structural infrastructure, not listed as intellectual dependencies. Mere “see also” links are not dependencies. See the Game. Refuse the Game. Build Better.

Open Calibration Items

  • After a few more module logs exist, confirm examples still match practice; adjust table if a class was miscategorized.
  • Resolve any stale link if Template:Calibration Template was renamed — point to current nav doc.

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


Structural Connections


Page Transparency & Calibration

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
Calibration Report Standard Format Core Experimental 2026-07-20 Current Breadcrumb-Open
Decision Records: Governance Memory Core Development 2026-07-14 Current Breadcrumb-Open
Page Structure Calibration Checklist Core Development 2026-07-14 Current Breadcrumb-Open
Template:Calibration Template 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: Calibration Report Standard Format • Calibration Dependencies: Standards and Process • Page Structure Calibration Checklist 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:



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



Page Reference

Title Calibration Log: When to Create One
URL https://www.thesovereigngames.com/wiki/Calibration_Log:_When_to_Create_One
Description Decision procedure for dedicated /Calibration Log subpage vs Talk-only Calibration Reports. Report format is defined elsewhere.
Category Meta & Framework



Retrieved from "https://www.thesovereigngames.com/index.php?title=Calibration_Log:_When_to_Create_One&oldid=3523"