Metrology of the Abstract — Working Terminology

Version 0.1.1 · Experimental · Self-Assessed · Permanent Beta

This is a discipline glossary, not a casual word list. Many entries are established by repeated project use and only now made explicit. Definitions themselves are calibratable — each may be revised when evidence, pilots, or nonconformances require it. Standing of an entry is not absolute truth.

Format note: Grouped by function for readers. Term/definition pairs use Lingo-compatible markup so a glossary extension can consume them later without retrofit.

Sovereign-Games-OG-Image.jpg

Core discipline

Metrology of the Abstract: The disciplined application of metrological principles — standards hierarchy, traceability, uncertainty, standing, correction memory, and continuous calibration — to abstract and knowledge-producing systems. One discipline; many applications.

Claim: Any statement, conclusion, procedure, model output, interpretation, or representation whose standing can be evaluated through calibration.

Calibration: Evaluating a claim, instrument, standard, or procedure against its appropriate reference and updating it when justified by evidence. Always depends on the reference class of the claim.

Traceability: The documented ability to connect a claim, standard, procedure, or calibration decision back through the standards hierarchy to its supporting references, assumptions, evidence, and governing principles so others can inspect how a result was produced rather than relying only on the result.

Pre-Calibration Check (Pre-Cal): Structural verification before calibration: completeness, formatting, metadata, templates, required fields. Does not evaluate substantive correctness and does not by itself change standing.

Calibration Recommendation: A conditional recommendation tied to the instrument’s stated objective. Form: “If the objective is X, the evidence suggests Y.” Not: “You should…” as unbound prescription.

Calibration Report: Structured record of what was checked, assumed, nonconformances, standing, and next actions. The report carries its own standing, independent of the page or instrument evaluated.

Calibration Note (Cal Note): Lightweight record attached to a task or output (checked, assumed, tier, standard used, standing, open issues). Status labels without these fields are narration, not calibration.

Calibration Layer: Governance work that evaluates instruments and standards rather than producing primary content.

Correction: A documented change made because calibration identified a substantive mismatch between an instrument and its reference. Corrections preserve history through correction memory rather than silently replacing prior states.

Standards

Top-Level Standard: Stable discipline-level principle intended to change rarely (e.g. instrument ≠ reference; self-check ≠ confirmation; standing is tier-qualified).

Working Standard: Versioned procedure for a task class; expected to evolve through use and nonconformances.

User Standard: Standard owned by the user or organization. Default: retrieve → apply; refine only on request or explicit protocol.

Reference: The comparison point appropriate to a particular claim or calibration task. Depending on claim tier, a reference may be observable reality (tier A), a defined corpus or source (tier B), a specification, an accepted standard, or another explicitly identified comparison source. A reference is not automatically a Reference Standard.

Reference Standard: A standard the project treats as a recurring comparison point for calibration because it meets explicit criteria: (1) stated scope and limits, (2) documented up-link in the standards hierarchy where applicable, (3) inspectable body, (4) labeled standing, and (5) openness to recalibration. Earning reference use requires more than naming; outside tier A, reference status is always provisional and must not be confused with certainty. Reference standards remain calibratable.

Standards Hierarchy: Top-level → derived → working standards → task instances, with up-pointers for traceability.

Instruments

Instrument: Any system that produces, evaluates, or transforms knowledge (human, model, organization, procedure, framework). An instrument is not the reference.

Conceptual Instrument: Abstract tool designed for repeated application (diagnostic games, models, calibration procedures, protocols).

Gauge Blank: Conceptual instrument prepared honestly for calibration: clear enough to test, low enough in standing to avoid false authority, complete enough to inspect.

Instrument Grade: Maturity of an instrument along: Experimental → Development → Confirmed → Field Validated → Reference Standard Candidate. Implemented in project metadata (e.g. Admin Page Status); not a synonym for “true.”

Standing and validation

Trust vocabulary crosswalk

These answer different questions. Do not use them as synonyms.

Term	Answers	Typical scope
Standing	How much evidential support does this claim, report, or assessment currently have?	Claims, cal notes, cal reports, specific conclusions
Instrument Grade	How mature is this tool/page as a reusable instrument?	Pages, protocols, games, conceptual instruments (Experimental → … → Reference Standard Candidate)
Validation	How strong is the evidence base for this version (Low / Moderate / High)?	Version of a page or instrument
Calibration Review	Was the review Self-Assessment or a stronger path (e.g. Confirmed Rating)?	Process status on a page (who stood behind the review)

Rule of thumb: Standing for what you asserted; instrument grade for what kind of tool it is; validation for how well-supported this version is; calibration review for how the review was performed.

Standing: Current evidential status of a claim, report, instrument, or standard — how much confidence the calibration process supports, not absolute truth.

Standing Check: Whether standing has been verified beyond the original assessor.

Self-Assessed: Standing based only on the originating assessor or instrument. Legitimate start; not independent confirmation.

Outcome-checked: Standing strengthened by tier-A outcome contact external to the model (test, measurement, reproducible run). May be solo when documented; prefer this label over bare Confirmed for solo outcome contact.

Confirmed: Stronger path (e.g. independent second party or written sampling policy that defines the path). Not correlated self-agreement or same-lineage re-read.

Validation: Strength of evidence for the present version (e.g. Low / Moderate / High). Separate from standing.

Documentation vs Theory: Documentation describes an existing practice or system; theory proposes a mechanism. “Low validation” means different things in each case.

Claim contact

Tier A: Reality-checkable claims; outcome or measurement can vote.

Tier B: Corpus-checkable claims; judged by fidelity to a defined source.

Tier C: Contested claims without a shared external referee; calibration emphasizes traceability, standing, and disagreement — not manufactured certainty.

Diagnostic principles

Observable Behavior Rule: Diagnostics evaluate observable actions and consequences rather than assumed internal intent unless intent is explicitly in scope.

Diagnostic Inversion: Testing whether the same diagnostic standard is applied symmetrically regardless of subject.

Reality Override Game: Protecting an existing model rather than updating it when reality disagrees.

Boundary Conditions: Situations outside an instrument’s intended operating range.

False Positive: Apparent match that fails the instrument’s actual diagnostic criteria.

On Closer Inspection: Review process that separates genuine matches from superficial resemblance.

Calibration findings

Nonconformance: Substantive mismatch between an instrument and its intended standard; requires correction.

Calibration Failure: Failure because the calibration design produced misleading or insufficient results despite operating as designed. Distinct from bug, nonconformance, or feature request.

Drift: Silent divergence between current reality and stored representation (stale ratings, dependencies, metadata).

Governance

Correction Memory: Persistent record of what changed, why, and how it was calibrated.

Decision Record: Preserved explanation of a structural decision.

Development Breadcrumb: Intentionally unresolved question left visible for future calibration.

Permanent Beta: Expectation that instruments remain open to recalibration as evidence improves.

Future Layer: Deliberately postponed architectural idea recorded for later implementation.

Engineering concepts

Retrieve → Apply → Log: Preferred workflow: retrieve an existing standard, apply it, log calibration; avoid reinventing each episode.

Distributed Instrumentation: Instruments carry their own calibration metadata rather than depending only on centralized dashboards.

Sampling Policy: Documented rule for which outputs receive stronger independent review.

Outcome Contact: Direct interaction with reality capable of strengthening standing (especially tier A).

Project / discipline concepts

Primitive Metrology: Existing measurement-like practices in a domain that lack a complete metrological framework (e.g. peer review, version control, audits, benchmarks, citations). These vary in referee strength: some offer hard pass/fail contact (e.g. tests, version control checks); others are weaker or contested (e.g. much peer review). Primitive metrology should not be confused with a complete metrological discipline.

System Completeness: Integration of hierarchy, traceability, standing, uncertainty, correction memory, and continuous calibration into one coherent discipline.

Discipline vs Application: MoA is one discipline; domains (AI, law, organizations, knowledge systems, etc.) are applications — not separate disciplines requiring existential re-proof each time.

Compressed Expertise: Knowledge that has become automatic through experience; decompress into protocols and examples when teaching or review requires inspectability.

Operator Insight: Practical observation from operating in the discipline; not automatically a top-level standard.

Builder Protocol: Implementation procedure that applies discipline principles to real work. Implements doctrine; does not define it.

Continuous improvement

Feature Request: Desired capability confirmed absent from the current implementation.

Insight (Unexpected Benefit): A solution built for one purpose that unexpectedly solves another.

Practice Convention: Repeated habit kept because it improves work; replaceable if a better approach is shown. Not the same as a top-level standard.

See the Game. Refuse the Game. Build Better.: Compressed operator heuristic for a full cycle: name the pattern; refuse participation in the failure mode; make one concrete improvement. Not a standing label, calibration result, or substitute for evidence. If it becomes ritual without diagnostic work, recalibrate or retire it.

Status of this glossary

Field	Value
Version	0.1.1
Maturity	Experimental
Calibration review	Self-Assessment
Validation	Low — lexicon from practice; not independently confirmed entry-by-entry
Role	Working terminology / discipline glossary (not yet a project Reference Standard)

This page is in Permanent Beta. Revise definitions from nonconformances and better evidence — not from synonym inflation.

See the Game. Refuse the Game. Build Better.

Open Calibration Items

Confirm GameModule type value “Working Terminology” against controlled Instrument Type list (may need canonical rename, e.g. Reference Standard / Meta Framework).
Install human-confirmed transparency template variant when lookup table exists; none installed this pass (flag only).
Verify mandatory template set exists on wiki before treating missing transclusions as content defects.
Entry-by-entry standing pass deferred (lexicon Self-Assessed as a whole).

Structural Connections

Admin:Maintenance Dashboard

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:

Page	Priority	Instrument Grade	Last Updated	Cycle Status	Drift Status
Abstract Standards Are Real; the System Was Missing	Core	Experimental	2026-07-23	Current	Breadcrumb-Open
Capability Development Roadmap	Core	Experimental	2026-07-23	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: Metrology of the Abstract • Builder Protocol v0.1: Metrology of the Abstract applied to AI • Permanent Beta • Reference Standards • Diagnostic Inversion Test 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	Metrology of the Abstract — Working Terminology
URL	https://www.thesovereigngames.com/wiki/Metrology_of_the_Abstract_—_Working_Terminology
Description	Working terminology for Metrology of the Abstract and The Sovereign Games. Calibratable discipline glossary with trust-vocabulary crosswalk, claim tiers, and governance terms.
Category	Meta & Framework