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.

Abstract Definition Mechanics

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

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.

Every abstract definition is a reality-mapping instrument. Its calibration depends not only on the correctness of its wording, but on the completeness and accuracy of the mapping mechanics by which it represents its intended domain.

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.

Sovereign-Games-OG-Image.jpg

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.
One concrete case provides friction, not general validation.
Automation may assist process completeness; it does not certify truth about open reality.
Success of this procedure as a method does not prove that every higher abstraction (framework, system, civilization) will decompose cleanly; each layer remains empirical. Higher-layer recursion is a method under test, not a certified ladder.

Artifact roles

Procedure (this page) — ordered method for attempting map calibration.
Probes — tools that pressure particular stages of the procedure.
Reports — dated records of a run.
Standards — named conditions this procedure can detect (e.g. Semantic Drift); not identical with the procedure itself.

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 conditions (overload, boundary collapse, missing child instrument, missing exception) may be promoted to standalone standards only after repeated observation.

Procedure

Work in order. Prefer underclaim. Record residual uncertainty.

1. Identity and domain

State the abstract’s intended purpose as the job the instrument must perform (why it exists / what it must enable) — one or two sentences.
Do not substitute a restatement of the definition for purpose. Definition answers what phenomenon is named; purpose answers what work naming it must enable.
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).
Narrow the tested domain for the run when the broad domain would force fake coverage.

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 by which the abstract converts or connects observations, conditions, relationships, or evidence into classification, distinction, explanation, prediction, judgment, coordination, regulation, or action.

Grade each claim’s mechanism (do not invent mechanics the text does not support):

(A) Operable in text — steps or rules are stated clearly enough to apply.
(B) Incompletely operationalized — a path is implied or named, but not stated in operable steps.
(C) Missing — no mechanism is expressed or reasonably traceable from the instrument text.

If none is expressed or reasonably traceable, record mechanism missing. If implied but not operable, record mechanism incompletely operationalized — do not treat as fully present or wholly absent.

4. Boundaries and neighboring instruments

Identify the closest related parent, child, sibling, or competing abstractions.
State what this instrument must distinguish itself from.
Note shared territory, dependency, overlap, or inheritance.
Record whether a missing distinction belongs inside this instrument, in an exception, or in a separate child instrument.
Note whether neighbor conditions are pathways, co-occurring failures, or independent conditions — do not collapse them by default.

Complex abstracts often fail through relationships, not only internal wording.

5. Confront reality

For each load-bearing claim or mechanism, cite at least one concrete case, counterexample, pattern, institutional outcome, or domain constraint.

One case provides friction, not general validation.
Increase case diversity before making broader claims about the domain.
Ask: Does the map cover it? Distort it? Miss a distinction? Has the underlying phenomenon changed while the map stayed fixed?

6. Record calibration outcomes

Prefer a structured assignment per claim or for the instrument as a whole. Tags are not all the same kind of thing — keep them separated.

Local result

Fit (local)
Distortion
Unsupported
Out of scope
Indeterminate

Mechanism quality (per claim, from §3)

Operable in text
Incompletely operationalized
Missing

Observed failure condition (if any)

Missing mechanism
Mechanism incompletely operationalized (when that incompleteness is load-bearing for purpose)
Conceptual overload
Boundary collapse
Missing child instrument
Missing exception
Semantic Drift

Run boundary

None
Floor
Insufficient evidence
Domain too broad

Instrument-level finding

Minimally realignable
Requires structural revision
Calibration failure — the map cannot be minimally realigned while preserving its declared identity and purpose; proposed repairs would retain the label while replacing the underlying conceptual payload (conceptual laundering)

7. Recommendations (not ownership)

Issue only instrument recommendations:

Tighten / clarify mechanism (move B → A where possible without laundering)
Split / rename child senses
Add boundary or exception
Update dated baseline
Clarify neighbor relation rules on the definition under test
Declare failure and leave fix to definition owner

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

8. Standing and record

Default standing after a run: Self-Assessed unless independent friction is documented.
Produce a Calibration Report including the required map output, outcomes, residual uncertainty, recommendations, and standing.
One run does not promote this procedure or the abstract under test to Confirmed.

Required map output

Each run should produce a compact map in this form (fill only branches that apply; mark missing rather than inventing):

Abstract: [name]
├── Purpose (job, not a restated definition)
├── Domain (broad + tested scope for this run)
├── Dated instrument text (ref)
├── Explains
├── Distinguishes
├── Predicts / implies
├── Includes
├── Excludes
├── Boundaries
├── Exceptions
├── Mechanisms (A operable / B incompletely operationalized / C missing)
└── Neighboring instruments (pathway vs independent, if known)

Floors (honest stops)

Call and document when:

Load-bearing claims cannot be separated without mixing distinct 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
Further repair would require conceptual laundering

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

Procedure-specific calibration probes

Procedure = ordered method. Probes = tools used to pressure particular stages. Reports = dated run records. Standards = named conditions (e.g. Semantic Drift) this procedure can detect.

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) Purpose as job (not a restatement of D); domain (one sentence); tested scope if narrowed.
2) List 3–7 load-bearing map claims (explain / distinguish / predict / include / exclude / bound).
3) For each, mechanism grade: (A) operable in text (B) incompletely operationalized (C) missing — do not invent.
4) Closest neighboring instruments (if any) and required distinctions.
5) 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 local result: fits / distortion / unsupported / out of scope / indeterminate.
Restate mechanism grade A/B/C from inventory (do not upgrade without new text evidence).
Then assign any failure condition, run boundary, and instrument-level finding with one sentence evidence each.
One case = friction, not general validation.
No authority over the definition author — recommendations only.

Probe: Floor / anti-laundering

Legal patches only.

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.

Probe: Mechanism grade

Refines §3 without inventing mechanisms.

For each load-bearing claim, grade mechanism as:
(A) operable in text (B) incompletely operationalized (C) missing.
Do not invent mechanisms. One sentence evidence each.

Success criteria for the procedure (not for the abstract)

This procedure is working when runs are:

Repeatable — same steps, comparable report shape and map output
Inspectable — claims, neighbors, mechanism grades, 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. Recursive application to higher layers (framework, system, institution) is a method under test, not a guaranteed success ladder.

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.3
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 neighboring instruments, and document local results, failure conditions, 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 (v0.3) for decomposing an abstract definition as a reality map, including purpose-vs-definition, mechanism grades A/B/C, neighboring instruments, structured outcomes, and recommendation-only discipline.
Category	Calibration Procedures

Abstract Definition Mechanics (Seed)