Abstract Definition Mechanics

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

Procedure-specific calibration probes

See the map. Pressure the map. Report the fit. Recommend — do not seize the definition.

Procedure = ordered method. Probes = stage tools. Reports = dated run record. Standards (e.g. Semantic Drift) = named conditions this procedure can detect.

This is a Calibration Procedure (Seed / Self-Assessed). It applies the same spirit as term-level mechanism breakdown one layer up: the object is not only wording inside a definition, but the mapping mechanics by which an abstract claims to track a domain of reality.

Metrology here means reasonable diagnostics, minimal adjustment recommendations when realignment is possible, and declared calibration failure when it is not. Authors of definitions decide whether to fix. Calibrators document. Rules apply to this procedure itself.

Purpose

Make the reality-map of an abstract inspectable, testable, and repeatable so humans and systems can see what the abstract claims to explain, distinguish, predict, include, exclude, and bound — and where that map fails, overreaches, or drifts.

Non-claims

Completing a run does not mean the abstract is “calibrated” in full or that the domain is settled.
This procedure does not transfer authority over the definition to the calibrator.
Listing mechanics does not require infinite coverage; load-bearing claims and declared floors are enough for an honest run.
Automation may assist process completeness; it does not certify truth about open reality.

Relationship to other instruments

Term Decomposition Protocol (TDP) — lower layer: mechanics inside a term definition for measurement use.
Abstract Definition Mechanics (this page) — higher layer: mechanics of the abstract as a map of a domain.
Semantic Drift — a standard / failure condition often detected by this procedure (divergence among dated definition+mechanism, usage, operational effect, and intended domain).
Other failure tags (overload, boundary collapse, missing child instrument, missing exception) may be promoted to standards only after repeated observation.

Procedure

Work in order. Prefer underclaim. Record residual uncertainty.

1. Identity and domain

State the abstract’s intended purpose (one or two sentences).
State the domain it is supposed to map (what kinds of situations, systems, or phenomena).
Note the dated instrument text under test (definition version / page / quote).

2. Load-bearing map claims

List what this definition must get right to serve its purpose. Typical slots (use only those that apply):

Explains …
Distinguishes … from …
Predicts / implies …
Includes …
Excludes …
Bounds / stops at …
Handles exception …

Do not invent a museum of claims. Prefer fewer load-bearing items over fake completeness.

3. Mechanisms

For each load-bearing claim, state the mechanism (how the abstract connects observation → judgment or explanation). If the text has no mechanism, record that as a gap.

4. Confront reality

For each load-bearing claim/mechanism, cite at least one concrete case, pattern, or constraint in the domain (example, counterexample, institutional outcome, known failure mode). Ask:

Does the map cover it?
Does it distort it?
Is a distinction missing?
Has the underlying phenomenon changed while the map stayed fixed?

5. Tag calibration outcomes

Tag only what the run supports:

Fit (local) — claim holds for tested range
Missing mechanism
Conceptual overload
Boundary collapse
Missing child instrument (sense should split)
Missing exception
Semantic Drift (if divergence from dated definition+mechanism vs use/effect is evidenced)
Floor — further push mixes distinct questions or exceeds honest scope
Calibration failure — map cannot be minimally realigned within identity of purpose without laundering

6. Recommendations (not ownership)

Issue only:

Tighten / clarify mechanism
Split / rename child senses
Add boundary or exception
Update dated baseline
Declare failure and leave fix to definition owner

Reject patches that keep the label’s prestige while swapping the payload.

7. Standing and record

Default standing after a run: Self-Assessed unless independent friction is documented.
Produce a short Calibration Report: purpose, domain, claims tested, outcomes, residual uncertainty, recommendations, standing.
One run does not promote this procedure or the abstract to Confirmed.

Floors (honest stops)

Call and document when:

Load-bearing claims cannot be separated without mixing questions
Domain is too wide for one pass — narrow scope rather than fake global coverage
Evidence is only narrative coherence with no external case friction
Disagreement is preference, not map failure

Floors map reality. They do not lessen the value of the procedure when named.

Calibration probes (specific to this standard)

Standard = target of honesty. Probes = how we pressure it. Reports = what the last pressure found.

Selective. Inspectable. Self-Assessed until re-run under friction.

Probe: Map inventory

Forces a finite list of load-bearing mapping claims before debate.

For abstract A with definition text D and purpose P:
1) Domain (one sentence).
2) List 3–7 load-bearing map claims (explain / distinguish / predict / include / exclude / bound).
3) For each, one-line mechanism or "mechanism missing".
4) One claim we must NOT make after only completing this inventory.
Prefer underclaim. No standing language.

Probe: Reality confront

Forces case friction against the map.

Using the claim list for abstract A:
For each load-bearing claim, give one concrete case in-domain.
Mark: fits / distorts / missing distinction / out of scope.
Then: any tag (overload, boundary collapse, drift, floor) with one sentence evidence.
No authority over the definition author — recommendations only.

Probe: Floor / anti-laundering

Same patch law as term-level work.

A gap or flaw appeared in the reality map of abstract A.
Propose instrument adjustments that preserve stated purpose/identity or explicitly split/rename child senses.
Reject any patch that keeps the label’s prestige while changing the payload.
Name the external check that would decide anchored calibration vs unanchored dreaming.

Success criteria for the procedure (not for the abstract)

This procedure is working when runs are:

Repeatable — same steps, comparable report shape
Inspectable — claims and cases visible
Bounded — floors used instead of infinite regress
Non-captured — recommendations without ownership theater

Whether a given abstract “passes” is empirical and local to the tested range.

Permanent Beta

This procedure is subject to the same diagnostics it applies. Improve by documented runs, not by elegance alone.

See the Game. Refuse the Game. Build Better.

Type	Calibration Procedure
Functional Layer	Metrological
Application Layer	Conceptual Instruments / Abstract Definitions
Category	Calibration Procedures
Version	0.1
Maturity	Seed
Last Calibration	2026-07-27
Status	Permanent Beta
Description	Procedure for decomposing an abstract definition as a reality map: list load-bearing mapping mechanics, compare them to the intended domain, and document gaps, floors, and recommendations without claiming ownership of the domain.

Title	Abstract Definition Mechanics
URL	https://www.thesovereigngames.com/wiki/Abstract_Definition_Mechanics
Description	Seed calibration procedure for decomposing an abstract definition as a reality map and documenting fit, gaps, floors, and recommendations.
Category	Calibration Procedures