Latest revision as of 07:15, 29 July 2026

CYCLE Calibration position Position — Core procedure · Compiler Cycle — Active Development Status — Stage 0 integrated · Self-Assessed 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.

Abstract Definition Mechanics (ADM) is a Calibration Procedure (Seed / Self-Assessed).

It applies metrological calibration principles to abstract definitions. The calibration target is the mapping mechanism, not the truth, morality, or historical validity of the ideas that later use that mechanism.

Every abstract definition functions as a reality-mapping instrument. Calibration asks whether that instrument maps its intended domain clearly enough to perform its stated purpose — including whether content demonstrably required by that purpose is omitted from the dated text.

The procedure evaluates:

purpose
load-bearing mapping claims
mechanisms
boundaries
neighboring instruments
omissions (material only)
calibration outcomes
recommendations (gated)

The calibration object is the conceptual mechanism, not the ideas, policies, institutions, or historical actors that later employ that mechanism.

Sovereign-Games-OG-Image.jpg

Metrological stance

ADM follows ordinary metrological discipline.

Calibrators:

lock the dated instrument text before interpretation
inspect the instrument
identify strengths, weaknesses, material omissions, and failure conditions
recommend realignment only when a material gap blocks stated purpose
declare calibration failure when necessary

Calibrators do not assume ownership of the definition.

Definition authors and instrument maintainers decide whether recommendations are adopted.

Rules apply equally to this procedure.

Judgment of ideas, ideologies, institutions, or historical actors is not the job of this procedure. Treating calibration as a license to play judge is a catastrophic failure of the metrological stance.

Calibrating a politically live term may have asymmetric downstream effects. ADM claims procedural transparency and re-runnability, not consequence-neutrality.

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
where that map fails, overreaches, or drifts
where content demonstrably required by purpose is omitted from the dated text

Procedure boundaries

This procedure does not:

determine historical guilt
determine moral worth
determine political legitimacy
determine which ideology is “correct”
transfer authority over a definition to the calibrator
certify ideas, policies, institutions, or civilizations by calibrating their vocabulary
police ordinary speech or ban colloquial registers

Those questions belong to downstream disciplines.

A calibrated conceptual instrument improves later historical, empirical, legal, scientific, and ethical analysis.

It does not replace those disciplines.

Protocol vs recommendations

Keep these layers distinct:

Layer	Role
Protocol (required to run ADM)	Stage 0 lock, purpose, claims, mechanism grades A/B/C, material omission check, case friction, structured outcomes, no ownership language, no moral verdicts
Operator rules for a compiled map	Bind to a specific report / IR (e.g. child-lock on this object). Not universal laws of language.
Recommendations	Optional realignment suggestions to maintainers. Gated. Do not raise standing.

Mixing protocol with optional redesign advice creates false authority and invites gatekeeping charges.

Non-claims

Completing a run does not mean the abstract is “calibrated” in full or that the domain is settled.
Listing mechanics does not require infinite coverage; load-bearing claims, material omissions, 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 will decompose cleanly; each layer remains empirical.
Recommendations do not raise standing and do not authorize moral or historical judgment.
Asymmetric political effects of a clear map do not by themselves prove capture; consequence-neutrality is not claimed.
Completing Stage 0 does not grade mechanisms, establish material omissions, or authorize recommendations.

Artifact roles

Procedure (this page) — ordered method for attempting map calibration
Stage 0 lock packet — dated evidence + observed silences only; prerequisite for Stages 1+
Probes — tools that pressure particular stages of the procedure
Reports — dated records of a run (the compiled map / IR)
Standards — named conditions this procedure can detect (e.g. Semantic Drift); not identical with the procedure itself
Calibration Recommendations — optional structured output after a run; gated; not ownership; standing must remain visible

Relationship to other instruments

TDP-001 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 — standard / failure condition this procedure can detect; strong Drift claims remain gated. Multi-sense overload and material omission are often the correct first diagnoses on dictionary and prestige clusters
Calibration Recommendations — pattern for packaging post-run recommendations without seizing the definition
CR-FAIR-001 Fairness Calibration Record — example Calibration Record under TDP; related lineage for term-level runs
Other failure conditions (overload, boundary collapse, missing child instrument, missing exception, material omission) may be promoted to standalone standards only after repeated observation

Measurement

↓

TDP

↓

ADM

↓

Future Procedures

Calibration hierarchy

ADM currently calibrates conceptual mechanisms (definition-as-map).

Future procedures may calibrate ideas, institutions, or higher-order systems using calibrated mechanisms as measurement instruments.

Each layer remains independently empirical.

Calibration at one layer does not certify higher layers.

Same metrology rules. Different object. Lock before meaning. Mechanisms before conclusions.

Procedure

Work in order. Prefer underclaim. Record residual uncertainty.

Hard gate: Stages 1–8 may use only what Stage 0 locked (plus explicit re-lock with version bump). If the calibrator has to make a contested judgment about what the text “really means,” that judgment does not belong in Stage 0.

Stage 0 — Evidence lock (mandatory)

Stage 0 is the evidence lock. Nothing in Stages 1–8 may invent, upgrade, or silently merge sources that were not locked here.

Job of Stage 0: Fix what counts as the instrument under test before interpretation begins.

Gold rule: If the calibrator has to make a judgment, it doesn’t belong in Stage 0. Stage 0 only records what the instrument explicitly says, what is immediately text-bound (no inference chains), or what it explicitly does not say. Prefer explicit over “directly implies.” If a second reader would argue about the implication, it is not Stage 0 evidence.

Stage 0 does not:

state full purpose-as-job (that is Stage 1)
grade mechanisms A/B/C
declare material omissions (only observed silences)
issue recommendations
claim Semantic Drift
assert domain ownership
determine parent/child/orphan structure as findings

When you may run Stage 0

You may start Stage 0 when…	You should not start when…
You have at least one dated text (definition, statute, opinion, standard, policy clause)	You only have a vibe, slogan, or “what people usually mean”
You can name the object in one line (instrument, not a culture war)	The object is “truth about X” or “whether X is good”
You know whether this is single-source or assembly (multi-source)	You plan to “blend the best of several authorities” without listing them
You accept Self-Assessed standing for the run	You need the output to bind a court, agency, or dictionary

Instruction: If the text is not citable with date/version, stop. Stage 0 failed closed.

Stage 0 checklist (complete in order)

Record answers in the run log / report header.

0.1 Object identity

[ ] One-line name of the instrument
[ ] Domain (as claimed or clearly indicated by the text’s setting)
[ ] Register stated (dictionary · statute · case construction · policy · mixed)
[ ] Instrument type noted (single threshold · multi-sense cluster · doctrinal assembly · other)
[ ] Calibration procedure + version (e.g. ADM v0.4.0)
[ ] Explicit: this run measures map quality, not domain ownership
[ ] Standing for this run: default Self-Assessed

0.2 Source inventory (dated only)

[ ] Primary text(s) listed with full citation and date/version
[ ] Optional supporting texts listed separately (examples, restatements, explainers, treatises) — not smuggled into the primary lock
[ ] “Not in evidence” list: materials deliberately excluded for this run
[ ] Quotation discipline: short contiguous quotes preferred over paraphrased authority

0.2b Explicit Evidence inventory (optional completeness list)

Extract only if present in locked text. Do not invent rows. Avoid inventory theater.

[ ] Purpose clues (phrases that hint at job — not purpose-as-job statement)
[ ] Objects (what the instrument applies to)
[ ] Forms / types distinguished in text
[ ] Examples (labeled as examples, not new definitions)
[ ] Conditions / if-then rules stated in text
[ ] Mechanism clues (verbs/operations named: includes, excludes, remedies, etc.)
[ ] Explicit classifications / hierarchy stated in text
[ ] Explicit boundaries stated in text
[ ] Explicit authority named in text
[ ] Explicit legal or operational outcomes tied in text
[ ] Explicit relationships only as written (no steeled-up diagrams)

Relationship inventory (observed only)

[ ] Named concepts in the text
[ ] Neighbor terms referenced
[ ] Referenced instruments / cross-references
[ ] No parent/child/sibling classification yet as a finding

0.3 Authority stack (especially legal / multi-layer objects)

[ ] Rank sources when relevant (e.g. statute → controlling opinion → secondary restatement)
[ ] State which layer is primary for this IR
[ ] Secondary layers cannot override primary unless themselves locked as primary for a different run

0.4 Single-source vs Assembly

[ ] Single-source: one authority owns the IR
[ ] Assembly: two or more texts form a combined IR for this pass only
[ ] If assembly: name the join rule in one sentence
[ ] If assembly: note that split runs + relationship map may be required later; do not pretend components were calibrated alone

0.5 Scope fence

[ ] In-scope claim type / domain stated
[ ] Out-of-scope neighbors listed
[ ] No silent upgrade across registers (dictionary ≠ statute ≠ case gloss ≠ morality)
[ ] Optional: one-line “purpose clues” from explicit text only — not a finished purpose-as-job statement

0.6 Prior baseline (for Drift gate later)

[ ] Is there a recoverable prior map of this same instrument under the same label?
[ ] If none: Semantic Drift starts as not claimable until a baseline exists
[ ] If yes: cite it (version / date / source)
[ ] Multi-sense dictionary clusters: note sense inventory candidates without child calibration yet

0.7 Operator, friction, and standing

[ ] Runner named (or “session operator”)
[ ] Standing for this run: default Self-Assessed
[ ] Multi-AI / human assessors (if used) noted as friction instruments, not votes that confer Confirmed status
[ ] If assessors disagree on what was locked → treat as Stage 0 defect; re-lock before Stage 1

0.8 Exit criteria (Stage 0 complete)

Stage 0 is done only when:

Dated primary text(s) are fixed and citable
Assembly (or single-source) is explicit
Scope fence is written
Authority stack is clear when multi-layer
Operator could hand the lock packet to a second person and they would pressure the same object

If any of (1)–(4) is missing → do not open Stage 1.

Stage 0 outputs

Artifact	Content
Lock packet — Evidence	Citations, dates/versions, quoted primary passages, assembly flag, join rule, authority stack, register, scope fence, baseline note
Lock packet — Observed Silences	Things the locked text does not explicitly address — no material-omission finding, no gap severity, no redesign advice
Explicit Evidence inventory	Purpose clues, objects, forms, examples, conditions, mechanism clues, classifications, boundaries, authority, outcomes — as present
Deferred list	Checked “not performed” items so later stages don’t pretend Stage 0 did them
Header fields for the eventual report	Object, procedure version, standing, ownership = none
Forbidden moves list (short)	e.g. no post-hoc authority, no register climb, no early A/B/C grades, no domain ownership

Two-section rule: Keep Evidence and Observed Silences separate. Silences become material omissions only later, and only with a purpose-checkability sentence in Stages 2–3.

Observed silence prompts (not mandatory findings)

[ ] Missing thresholds / severity
[ ] Missing conditions / causation / intent
[ ] Missing mechanisms
[ ] Missing burdens / who decides
[ ] Missing time horizon / probability
[ ] Other observed silences

Deferred list (do not answer in Stage 0)

[ ] Purpose-as-job statement
[ ] Load-bearing claims
[ ] Mechanism grades A/B/C
[ ] Material omission
[ ] Child / parent / orphan determination
[ ] Neighbor calibration (pathway vs independent, etc.)
[ ] Reality friction
[ ] Semantic Drift / Boundary Collapse / Conceptual Overload (as findings)
[ ] Calibration outcomes
[ ] Recommendations

Stage 0 hard rules

No interpretation in Stage 0. Do not grade mechanisms, do not “steelman the true meaning,” do not fill gaps.
No laundering. Secondary commentary is not primary text unless listed as a locked source.
No material-omission claims in Stage 0. Observed silence only.
No recommendations in Stage 0.
No evaluative language in Evidence or Silences sections.
Assembly is provisional. Combined IR ≠ claim that each component was fully calibrated alone.
Re-lock if sources change. New opinion, amendment, or dictionary edition → new Stage 0 (or explicit version bump).
Friction welcome. Assessor disagreement about what was locked is a Stage 0 defect; fix the lock before debating fit.
Multi-sense objects: inventory sense labels if the dated entry provides them; do not run child calibration inside Stage 0.
Relationship diagrams only if every node is text-backed; otherwise list form only.
Keep Stage 0 short enough for one focused pass.

Stage 0 failure modes

Failure	Symptom	Fix
Fog lock	Object named with no pin to subsection / opinion / dated text	Narrow object + cite
Silent assembly	One authority graded as if it were another	Flag assembly or split
Register climb	Dictionary sense used as statutory test (or equivalent)	Scope fence + register tag
Baseline smuggle	“Everyone knows it used to mean…” with no recoverable map	Drift = not claimable
Early grading	A/B/C mechanism scores in Stage 0	Delete; defer to mechanism stage
Early omission finding	“Material omission” declared before purpose lock	Downgrade to observed silence
Secondary promotion	Blog/explainer treated as controlling primary	Demote to supporting or re-lock with honesty
Scope leak	Moral/historical verdict language in the lock	Cut; belongs outside ADM
Implication laundering	“Directly implies” used for contested readings	Downgrade to silence or defer to Stage 1+
Inventory theater	Every noun forced into Objects/Forms	Extract load-bearing explicit items only
Weak primary	Secondary restatement locked as if controlling	Authority stack + demote supporting

Stage 0 one-line operator rule

Lock the text, the authority stack, and the join rule before you touch meaning. If it isn’t dated and fenced, it isn’t evidence.

With the evidence packet locked, interpretation begins at Stage 1.

Stage 1 — Identity and domain

State the abstract’s intended purpose as the job the instrument must perform — one or two sentences.
Do not substitute a restatement of the definition for purpose. Definition names the phenomenon; purpose states the work naming must enable.
State the domain it is supposed to map.
Confirm the dated instrument text under test from the Stage 0 lock packet.
Narrow the tested domain for the run when the broad domain would force fake coverage.

Stage 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 …

Prefer fewer load-bearing items over fake completeness.

Stage 3 — Mechanisms

For each load-bearing claim, state the mechanism by which the abstract connects observations, conditions, relationships, or evidence to classification, distinction, explanation, prediction, 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 clear enough to apply
(B) Incompletely operationalized — path implied or named, not operable
(C) Missing — no mechanism expressed or reasonably traceable from the text

Material omission check (required): For each load-bearing claim, ask:

> What bound, meter, threshold, agent, scope, or firewall must be present for this claim to be checkable given the stated purpose?

If the dated text is silent, write one sentence:

> Purpose P requires checkability of X; text is silent on X.

Only then tag omission (material).

If that sentence cannot be written honestly, record ordinary underspecification or an open question — not omission-as-failure.

Do not treat silence as agreement. Do not fill omissions with preferred theory inside the diagnostic record.

Stage 0 observed silences may inform candidates; they become material omissions only here, under the purpose-checkability sentence.

Stage 4 — Boundaries and neighboring instruments

Identify closest parent, child, sibling, or competing abstractions
State required distinctions
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 pathway vs co-occurring vs independent neighbor conditions — do not collapse by default
On multi-sense or prestige headwords, prefer split children when one purpose cannot hold without overload
Colloquial, derogatory, or register-tagged senses are first-class jobs, not lesser meanings. They may be used fully as that job. They must not silently upgrade into technical mechanism claims

Stage 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 = friction, not general validation
Increase case diversity before broader domain claims
Ask: cover, distort, miss distinction, material omission, or fixed map while phenomenon changed?

Stage 6 — Record calibration outcomes

Keep tag types separated.

Local result

Fit (local)
Distortion
Unsupported
Out of scope
Indeterminate

Mechanism quality (per claim, from Stage 3)

Operable in text
Incompletely operationalized
Missing

Observed failure condition / gap (if any)

Missing mechanism
Mechanism incompletely operationalized (when load-bearing for purpose)
Omission (material) — bound, meter, threshold, agent, scope, or firewall demonstrably required by stated purpose is absent from the dated text (supported by the one-sentence materiality line)
Ordinary underspecification (not elevated to omission)
Conceptual overload
Boundary collapse
Missing child instrument
Missing exception
Semantic Drift (only when baseline and recoverable prior map support the claim)

Run boundary

None
Floor
Insufficient evidence
Domain too broad

Instrument-level finding

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

Stage 7 — Recommendations (not ownership)

Recommendations are optional and gated. Prefer Calibration Recommendations for multi-pass or high-stakes runs.

Recommendation gate — issue a change recommendation only if both hold:

1. A material omission or gap demonstrably blocks the stated purpose, and 2. The proposed fix is framed as owner-may-add text, split, bound, or exception — not as a filled preferred theory

Otherwise: document the gap only. No redesign recommendation.

Typical recommendation types (when gated through):

Tighten / clarify mechanism (B → A without laundering)
State material omitted bounds as gaps the maintainer may close
Split / rename child senses
Add boundary or exception
Update dated baseline
Clarify neighbor relation rules
Declare failure; leave fix to definition owner

Severity (optional, when recommending):

L1 Clarification · L2 Boundary/scope · L3 Child split · L4 Structural revision · L5 Calibration failure

Evidence strength: one friction case → local recommendation only; broader wording requires more cases or explicit underclaim.

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

Header discipline: every recommendation package must show standing, procedure version, and that the instance is not a universal methodology.

Stage 8 — Standing and record

Default standing: Self-Assessed unless independent friction is documented
Produce a Calibration Report with Stage 0 lock pointer, map output, outcomes, residual uncertainty, recommendations (if any), and standing
One run does not promote this procedure or the abstract under test to Confirmed
Operator rules derived from a report bind to that IR, not to language in general

Required map output

Abstract: [name]
├── Stage 0 lock (citations, date/version, assembly/join, scope fence)
├── 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
├── Omissions (material only; each with purpose-checkability sentence)
├── Underspecification / open questions (non-material)
├── 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 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
Purpose requires checkable bounds that remain omitted and cannot be supplied without inventing content
Omission-maximalism would replace material gaps with an infinite wishlist
Stage 0 cannot lock a dated primary text — run fails closed before mapping

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

Multi-cycle note (prestige / multi-sense objects)

Overloaded public definitions often need more than one pass:

Cycle 1 — Stage 0 + whole entry + per-child split (purpose, claims, mechanisms, material omission)
Cycle 2 — cross-child cases (collapse and lawful co-application)
Cycle 3 — interconnect (shared terms, co-application matrix, where downstream evaluation is allowed)

Stop when new evidence classes stop appearing. Permanent Beta is not infinite re-analysis of the same page.

Procedure-specific calibration probes

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

Probe: Stage 0 lock integrity

For instrument I under ADM Stage 0:
1) List primary dated citations and versions.
2) Single-source or assembly? If assembly, state join rule in one sentence.
3) Scope fence: in / out.
4) Authority stack primary layer (if multi-layer).
5) One thing a second operator must NOT treat as locked evidence.
6) Confirm: no A/B/C grades, no material-omission findings, no recommendations in this packet.
Prefer underclaim. No standing inflation.

Probe: Map inventory

For abstract A with definition text D and purpose P (Stage 0 complete):
1) Purpose as job (not a restatement of D); domain; tested scope if narrowed.
2) List 3–7 load-bearing map claims.
3) For each, mechanism grade A/B/C — do not invent.
4) Material omission check: for each candidate gap, write
   "Purpose P requires checkability of X; text is silent on X."
   If that sentence fails, record underspecification/open question — not omission.
5) Closest neighboring instruments and required distinctions.
6) One claim we must NOT make after only this inventory.
Prefer underclaim. No standing language. No moral verdicts.

Probe: Reality confront

Using the claim list for abstract A:
For each load-bearing claim, one concrete in-domain case.
Local result: fits / distortion / unsupported / out of scope / indeterminate.
Restate mechanism grade A/B/C (do not upgrade without new text evidence).
Restate material omissions only (do not fill them in the diagnostic).
Assign failure condition, run boundary, and instrument-level finding with one sentence evidence each.
One case = friction, not general validation.
Recommendations only if recommendation gate passes — no ownership of the definition.

Probe: Floor / anti-laundering

A gap, material omission, or flaw appeared in the reality map of abstract A.
If recommending change: confirm both gate conditions (blocks purpose; non-laundering fix).
Otherwise document gap only.
Reject patches that keep the label’s prestige while changing the payload.
Do not fill omissions with preferred theory under the guise of clarification.
Name the external check that would decide anchored calibration vs unanchored dreaming.

Probe: Mechanism grade

For each load-bearing claim, grade mechanism A/B/C.
Do not invent mechanisms. One sentence evidence each.
Separately list material omissions (each with purpose-checkability sentence)
and ordinary underspecification/open questions.

Success criteria for the procedure (not for the abstract)

This procedure is working when runs are:

Locked — Stage 0 packet complete before interpretation
Repeatable — same steps, comparable report shape and map output
Inspectable — claims, neighbors, mechanism grades, material omissions, and cases visible
Bounded — floors and materiality rules used instead of infinite critique
Non-captured — gated recommendations without ownership theater or moral theater
Standing-honest — presentation does not outrun Self-Assessed / experimental status

Whether a given abstract’s map “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.

Stage 0 was promoted from Development Notes into normative procedure text at v0.4.0 after live-run discipline. Further patches require documented friction.

See the Game. Refuse the Game. Build Better.

Page Reference

Title	Abstract Definition Mechanics
URL	https://www.thesovereigngames.com/wiki/Abstract_Definition_Mechanics
Description	Seed calibration procedure (v0.4.0) for mapping mechanisms of abstract definitions: mandatory Stage 0 evidence lock, material omission, recommendation gate, protocol vs recommendations, register-as-job, standing hygiene, and separation of mechanism calibration from idea or moral judgment.
Category	Calibration Procedures

Sovereign (talk | contribs)