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

Calibration Debt

In the Metrology of the Abstract (MoA), missing or incomplete conceptual work is not treated only as a defect of presentation.

It is treated as Calibration Debt: known absence or under-calibration that has been identified and should remain visible until resolved, retired, or explicitly deferred.

Traditional knowledge systems often treat a missing page as simple deficiency (“this should exist”). MoA treats many such gaps as measurable, prioritizable calibration work — closer in spirit to technical debt in engineering than to a broken link list alone.

Purpose

Make unfinished calibration observable instead of implied or shame-hidden
Support systematic prioritization of conceptual work
Preserve traceability between what is claimed and what is still open
Reduce false maturity (pages that look complete while critical instruments remain undefined)

What Calibration Debt Is

Calibration Debt is the documented gap between:

the current calibration state of a conceptual system (or instrument), and
the identified instruments, dependencies, analyses, reports, or resolutions still required for the claims in use

Debt is known work, not ambient ignorance. If nobody has recognized the gap, it is not yet logged debt — it is undiscovered error or unexamined scope.

Examples

Missing conceptual instruments (including wiki red links to needed pages)
Undefined or unstated dependencies
Uncalibrated mechanisms (named but not adversarially tested)
Missing or overdue Calibration Reports / calibration logs
Missing child instruments after a composite term is split (see Term Decomposition Protocol)
Known semantic ambiguities left unresolved while the parent term is still in use
Incomplete dependency or impact analysis
Outstanding Calibration Recommendations not accepted, rejected, or deferred
Planned standards or procedures referenced in use but not yet written
Open readiness gaps and Development Breadcrumbs (e.g. Admin `drift_report_status = Breadcrumb-Open`)
Inflated standing or grade relative to evidence (standing debt)
Broken or unverified outbound claims that affect calibration (`outbound_links_valid`, WantedPages, etc.)

What Calibration Debt Is Not

Not every empty search result or casual “wouldn’t it be nice” idea
Not automatic moral failure or proof the project is unserious
Not a demand that every red link be filled immediately
Not a substitute for prioritization, retirement, or “won’t do” decisions
Not identical to software technical debt (related metaphor; different object)

Explicitly deferring or retiring a gap converts debt into a decision record. Silence leaves debt ambiguous.

Red Links

In wiki implementations of MoA, red links are a primary surface of Calibration Debt.

A red link often means:

the instrument or artifact has been recognized in context,
some relationship to existing instruments is already implied,
calibration (or even a Seed page) has not been completed.

So a red link is not merely “page missing.” It is a visible placeholder for identified future calibration work — unless the link was accidental, outdated, or should be removed.

Disciplined use of red links

Prefer red links when the dependency is real and should stay on the ledger
Remove or reword links that create false debt (optional asides, abandoned names)
A Seed-stage stub can reduce link-debt while honestly declaring low maturity (Seed to Fruit Development)
Special pages such as WantedPages / LonelyPages support debt inventory; they do not by themselves prioritize work

Other Visible Debt Surfaces

Surface	Typical debt signal
Red links / WantedPages	Missing instruments
Admin `depends_on` without targets	Dependency debt
`drift_report_status = Breadcrumb-Open`	Logged open calibration issues
`instrument_grade` / standing vs evidence	Standing or grade debt
Missing Calibration Log / report after material change	Report debt
Composite term without child runs / composition rule	Decomposition debt (TDP)
Category / outline gaps	Navigational and coverage debt
Overdue review cycle	Temporal calibration debt

Calibration Planning

Because debt can be listed, it can be planned.

Implementations may rank work by:

dependency criticality (what breaks if this stays missing)
uncertainty injected into active claims
blast radius (how many instruments inherit the gap)
available evidence and cost to Seed vs deeper calibrate
sandbox or domain goals (e.g. Human Systems Metrology priorities inside The Sovereign Games)
risk of false confidence if left implicit

Reactive filling of every red link is not the goal. Explicit prioritization is.

Principle

Calibration Debt is not hidden debt. It is visible debt.

A transparent calibration system makes unfinished work observable. Visibility enables prioritization. Prioritization enables calibration. Calibration reduces uncertainty — or records a floor, deferral, or retirement.

Hiding gaps to appear complete increases error. Showing gaps is part of the instrument.

Relationship to MoA and Sandboxes

Calibration Debt is an MoA-level concept: any conceptual system (law, medicine, AI ontologies, education, civilizational diagnostics) can carry it.

The Sovereign Games, as a sandbox, will accumulate domain-specific debt (games, strategies, reports). MoA cares that debt is named and trackable; sandboxes decide which debt to pay first under their own goals.

Open Issues

No single numeric “debt score” is defined; inventory + priority beats false precision for now
Not all red links are equal debt — classification (must / should / remove) is still informal
Cross-sandbox debt comparison is undefined

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: None found. Either nothing currently depends on this page, or no dependent page has yet listed it in their `depends_on` field.

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: Metrology of the Abstract • Seed to Fruit Development • Versioning • Term Decomposition Protocol 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 Debt
URL	https://www.thesovereigngames.com/wiki/Calibration_Debt
Description	Known, documented gap between current calibration state and required instruments, dependencies, reports, or analyses. Red links often surface this debt. Visibility enables prioritization; hiding unfinished work is the anti-pattern.
Category	Meta & Framework

Meta

Menu