Revision as of 16:55, 14 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.

Sovereign-Games-OG-Image.jpg

Reference Standards

Status note: This page reflects the finalized taxonomy from a multi-model round-robin session (Claude, ChatGPT, Grok) across five rounds. Remaining open items are marked explicitly. The reasoning behind major decisions is recorded separately — see Standards Taxonomy: Calibration Decision Records.

A note on scope: This page marks a shift from calibrating ideas to calibrating standards — the units of governance underneath ideas and institutions. This page is not only about classifying standards — it is, more fundamentally, about how standards legitimately earn authority: not from tradition, power, popularity, or authorship, but from traceability, calibration, repeated successful application, and continued openness to recalibration. That changes the operating question from "who's right?" to "what standard are we operating under, how traceable is it, and how well is it calibrated?" — a more durable basis for the work than debate alone.

Purpose

Not all standards are created, owned, or maintained the same way. This page distinguishes the major classes of standards that may be calibrated, separates what kind of standard it is from what relationship the calibrator has to it, and clarifies obligations for each. The purpose is not to rank standards, but to calibrate each according to its role, authority, and relationship to observable reality.

Required: Purpose, Success Criterion, Failure Criterion, Scope of Validity

Every standard — regardless of Type — must state its Purpose, Success Criterion, Failure Criterion, and Scope of Validity before it can enter calibration.

The first three establish what the standard is measured against. Scope of Validity establishes where it is not claimed to apply — the operating range outside of which the standard should not be assumed to hold. Without a stated scope, a standard is vulnerable to silent over-generalization: a mechanism validated in one domain gets assumed to transfer cleanly to another without that transfer ever being tested.

This four-part requirement is a precondition for calibration, not optional documentation. Without it, "Failure to Specify" (see Disconfirmation Conditions below) applies by default.

Standard Lifecycle

Proposal → Development → Calibration → Candidate Reference Standard → Operational Use → Monitoring → Drift Detected → Recalibration → Retired / Split / Replaced / Superseded

This section exists to prevent the lifecycle from being defined piecemeal across separate pages. Full specification of each stage is deferred — see Open Questions.

Types of Standards

Personal Standards (Provisional — Open Item)

Standards an individual holds themselves to (e.g. personal conduct standards practiced through Hidden Mastery).

Decision needed: Fifth explicit Type, or already covered under Hidden Mastery without a separate Type entry? Deliberately left undecided pending further practical experience.

Candidate Reference Standards

Currently supported by extensive historical observation, repeated successful calibration, and broad evidence across multiple contexts. Higher starting confidence due to accumulated evidence — but the name deliberately avoids implying permanence. A Candidate Reference Standard remains a candidate indefinitely, subject to the Disconfirmation Conditions below.

Governing Standards

Established by governments, legislatures, regulatory bodies, or public institutions. Calibrator's role is strictly diagnostic — Calibration Reports and Calibration Recommendations only, no enforcement authority. Findings may be used by any party, including political opposition, to advocate for change — entirely outside the calibrator's control.

Organizational Standards

Created by corporations, institutions, professional bodies, nonprofits, or educational systems. Same diagnostic-only role as Governing Standards, one scope level down.

Requested Standards (Under Review)

Standards developed or calibrated at a client or commissioning body's request, possibly privately. May eventually be absorbed into Authority Relationship rather than standing as its own Type. Kept as-is pending real worked examples — see Standards Taxonomy: Calibration Decision Records for the reasoning behind this deferral.

Note: All Types are subject to the same core calibration rules below.

Authority Relationship (Separate Axis)

Every Type above may be evaluated under a different relationship, independent of Type.

Relationship	Description
Self-Calibration	Calibrator and standard-holder are the same person (typically Personal Standards).
Independent Diagnostic	Calibrator evaluates a standard with no authority to enforce changes.
Commissioned Calibration	Calibrator is engaged by the standard's owner to evaluate and improve it.

Rule: Calibration Recommendations Are Always Descriptive

Always use the complete term Calibration Recommendation — never bare "recommendation." The prefix signals the output came from the calibration process itself, not the calibrator's independent opinion.

Conditional on the standard's own stated objective (see Required section above), never a substituted goal:

Correct: "Calibration Recommendation: if the objective is X, observed outcomes indicate mechanism Y consistently underperforms mechanism Z."
Not permitted: "You should replace Y with Z."

Adoption remains entirely the standard-holder's decision.

Rule: Reality Dictates Recalibration

No standard is beyond calibration. When calibration reveals meaningful drift:

Acknowledge the findings.
Document them.
Recalibrate the standard where appropriate.
Preserve the calibration history — nothing gets quietly erased (see Reality Override Game#Partial Update as Camouflage).

This process will be messy while real data is gathered and the framework is young. That messiness does not change the direction being correct.

Recursive Calibration: Standards Calibrating Standards

Standards are not isolated. A Governing Standard may depend on a Candidate Reference Standard, which in turn may be informed by Organizational, Requested, or Personal Standards — a recursive calibration chain ("turtles all the way down").

The framework must remain capable of calibrating the standards used to calibrate other standards, without creating circularity or protected classes. No standard — including a Candidate Reference Standard others depend on — is exempt.

Rule: Transparency Default

Calibration findings are public by default, for every Type, unless a specific documented exception applies (commissioned private work, legal confidentiality, genuine safety concerns).

Transparency has at least three distinct layers, not always identical:

Transparency of method — should remain open nearly always, even when a specific finding is private.
Transparency of finding — subject to documented exceptions above.
Transparency of supporting evidence — may have its own separate constraints distinct from the finding itself.

Severity is explicitly not a tiering factor. The calibrator does not escalate disclosure effort based on its own judgment of severity — that judgment is itself leverage over outcomes. A severe finding publishes exactly the same way a routine one does.

A note on this tension: Strict neutrality is not costless. There is a real, unresolved ethical question in choosing not to escalate disclosure effort even when a finding suggests serious ongoing harm — this page's current position accepts that cost deliberately, in exchange for protecting the calibrator's role from becoming a vector for its own judgment about what matters most. See Standards Taxonomy: Calibration Decision Records for the full record of this disagreement.

Calibration Burden (Draft)

Not every standard requires the same evidentiary weight before its Calibration Recommendations carry influence. Burden is provisionally understood to depend on at least four factors: scope, potential consequence, reversibility, and evidence quality. These are kept as a qualitative checklist, deliberately not a formula, at this stage.

Current status: Qualitative, not quantified — subject to change, not fixed. As real Calibration Burden judgments accumulate and get checked against outcomes, one of three things should happen:

The four factors continue to resist clean combination → stays qualitative, permanently.
The four factors turn out to combine in some testable, specific way → a formula gets adopted, but only after being shown to work.
Real cases reveal the four factors aren't even the right ones → the checklist gets revised before any formula is considered.

Disconfirmation Conditions for Candidate Reference Standards

A Candidate Reference Standard should be downgraded when specific, stated conditions are met — not left permanently unfalsifiable by accumulated historical weight.

Sustained contrary evidence: Contrary results appear in at least three independent calibration passes, conducted by different reviewers, across meaningfully different contexts, with no single pass counted twice. (This threshold is itself provisional, open to revision once real cases test it.)
Context shift: The conditions that generated the original supporting evidence have measurably changed.
Internal contradiction: The standard conflicts with another Candidate Reference Standard or a more rigorously calibrated finding, unresolvable by refining either's scope.
Failure to specify: The standard rests on claims too vague to test — it was never actually calibrated, just an assumption wearing the label.
Superseded: Not wrong, but obsolete — a demonstrably superior standard consistently achieves the same stated Purpose with lower uncertainty, greater robustness, or broader applicability. Categorically distinct from the other four: describes improvement, not failure. Recorded distinctly from failed status in calibration history.

A downgrade of any kind is itself a calibration event, following the same four-step process (acknowledge, document, recalibrate, preserve history) as any other standard.

Relationship to the Master Standard

Every rule on this page ultimately answers to the same master standard as the rest of The Sovereign Games: reality itself, as embodied in the Royal Cubit and expressed in the principle that reality gets final vote. This page's taxonomy, Disconfirmation Conditions, and Transparency Default hold no authority in themselves — they are instruments for measuring how well a given standard tracks reality. If this page's own procedures ever produce findings inconsistent with observed outcomes, this page is subject to the same Reality Dictates Recalibration rule it applies to everything else.

Future organization note: this section may eventually move to its own dedicated page (e.g. "Reality as the Master Standard"), with this page retaining a one-line pointer. Not necessary now — flagged for later, following the same pattern as the Lifecycle question below.

Open Questions

Personal Standards as a Type: Deliberately left undecided.
Severity and disclosure: Unresolved, deliberately — see Decision Records.
Requested Standards as a Type: Deferred pending real worked examples.
Are the five Disconfirmation Conditions sufficient?
Should additional Types eventually be distinguished?
Should Calibration Burden ever become quantified, and what case would justify it?
Should the Standard Lifecycle become its own dedicated page once fully specified?
Should "Relationship to the Master Standard" eventually move to its own page?

Future Development: Worked Examples (Pending)

Status: Deliberately withheld, not yet published. A first-pass worked example (Candidate Reference Standard type) has been run privately and confirmed the core mechanism holds — Calibration Recommendations stayed descriptive throughout, and the exercise surfaced a genuine Disconfirmation Condition finding ("failure to specify") on real content.

Why it isn't published yet: The taxonomy wasn't hardened enough to publish an applied example alongside its full reasoning until this finalization. That condition is now largely met, but publication remains a deliberate, separate decision — not automatic.

Commitment: At least one worked example — on a genuinely contested topic — should be published publicly, alongside its full reasoning, as proof the methodology holds under real scrutiny rather than just internal review.

This section exists specifically so this commitment doesn't quietly get dropped. If deleted without a worked example having been published, that is itself a Reality Override pattern — see Reality Override Game.

Calibration Dependencies

See the Game. Refuse the Game. Build Better.

@@ Line 27: / Line 27: @@
 Every standard — regardless of Type — must state its '''Purpose''', '''Success Criterion''', '''Failure Criterion''', and '''Scope of Validity''' before it can enter calibration.
-The first three establish what the standard is measured against. '''Scope of Validity''' establishes where it is *not* claimed to apply — the operating range outside of which the standard should not be assumed to hold. Without a stated scope, a standard is vulnerable to silent over-generalization: a mechanism validated in one domain gets assumed to transfer cleanly to another without that transfer ever being tested.
+The first three establish what the standard is measured against. '''Scope of Validity''' establishes where it is ''not'' claimed to apply — the operating range outside of which the standard should not be assumed to hold. Without a stated scope, a standard is vulnerable to silent over-generalization: a mechanism validated in one domain gets assumed to transfer cleanly to another without that transfer ever being tested.
 This four-part requirement is a precondition for calibration, not optional documentation. Without it, "Failure to Specify" (see Disconfirmation Conditions below) applies by default.

Type	Meta & Framework
Functional Layer
Application Layer	Framework Infrastructure
Category	Meta & Framework
Version	1.0
Maturity	Confirmed
Last Calibration	2026-07-13
Status	Permanent Beta
Description	Defines the types of standards calibrated by The Sovereign Games, the Authority Relationship axis, and the core rules governing calibration obligations, disclosure, and disconfirmation.

Title	Reference Standards
URL	https://www.thesovereigngames.com/wiki/Reference-Standards
Description	Defines the types of standards calibrated by The Sovereign Games, the Authority Relationship axis, and core rules governing calibration obligations, disclosure, and disconfirmation.
Category	Meta & Framework

Reference Standards: Difference between revisions

Sovereign (talk | contribs)