TDP-001 Term Decomposition Protocol

CYCLE Calibration position — Foundational Draft — 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.

Term Decomposition Protocol

Canonical Question: What is the formal, versioned procedure for decomposing a contested abstract term into a testable mechanism, subjecting it to adversarial counterexamples, and locating either survival or a genuine floor?

The Term Decomposition Protocol (TDP-001) is a Working Standard of Metrology of the Abstract. It treats abstract terms the way physical metrology treats measurement instruments: propose a mechanism, test it against deliberately hostile counterexamples, patch only against documented failures, and continue until the mechanism survives serious pressure or a genuine floor is reached and correctly characterized.

Core principle: Mechanism is the hypothesis. The adversarial counterexample is the instrument. The floor is legitimate calibration output, not failure.

Current standing of the protocol itself: Self-Assessed / Provisional Working Standard. Independent re-runs are required before any promotion.

Download current version: Media:TDP-001 Term Decomposition Protocol v0.1.2.docx

Sovereign-Games-OG-Image.jpg

How to Use

Operator: Anyone running a term into a Calibration Record (human primary; AI may support sequential steps but does not create Confirmed standing).

When to use:

A high-stakes abstract term is contested, overloaded, or drifting in use (policy, law, institutional standards, framework vocabulary, AI reasoning).
You need a versioned, auditable mechanism — not a persuasive essay definition.
You are willing to accept a floor as a valid result when the term will not collapse further without mixing questions.

Inputs: Target term; scope notes (domain / excluded senses); any prior mechanism or dictionary gloss you are testing against (optional).

Outputs (minimum for a serious run):

Versioned mechanism text (and patches tied to documented counterexamples)
Counterexample set that meets the Quality Gate
Survival or floor characterization (with residual uncertainty)
Structured Calibration Record (see standard document and CR pattern, e.g. CR-FAIR-001 Fairness Calibration Record)
Explicit standing: Self-Assessed until independent re-run

Stop conditions:

Mechanism survives the adversarial gate under stated Survival minimum → record survival + residual uncertainty.
Irreducible fork reached under floor rules → record floor (not failure) and separate adjacent questions.
Quality Gate not met → do not claim a completed run; fix evidence, not rhetoric.

Do not: Treat a single Self-Assessed or AI-only pass as Confirmed; skip the Counterexample Quality Gate; inflate grade beyond the record.

Full normative text, schema fields, and step sequence live in the downloadable Working Standard. This page is the site instrument entry: orientation, use path, boundaries, and lineage — not a substitute for the controlled document.

Technical Breakdown (Normative Intent)

TDP-001 is a compiler-style pipeline for abstract terms: natural language in → transparent, adversarially pressure-tested conceptual instrument out.

Elements the Working Standard binds together (detail and mandatory sequence in the v0.1.2 document):

Atomicity / bundle check — Detect composite terms before writing a single mechanism; refuse silent overloading.
Mechanism as hypothesis — Proposed logic flow is a testable claim, not a final definition. Separate definitional gloss from mechanism where the standard requires it.
Adversarial Counterexample Quality Gate — Hostile cases aimed at falsification; weak or friendly examples do not pass the gate.
Patch discipline — Change the mechanism only against documented failures; keep version history.
Survival minimum — Explicit bar for what counts as holding under pressure (not vibes).
Floor as legitimate output — Irreducible forks and decision-theoretic limits are measured results; characterize them; do not force a false unity.
Mid-run corrections field — Record material course-corrections inside the run without rewriting history as if the first draft had always held.
Versioned Calibration Record — Auditable artifact: mechanism versions, patches, counterexamples, composition rules, residual uncertainty, standing.

Standing ladder (protocol and runs): Self-Assessed → independent re-run required before Confirmed. AI round-robin does not create Confirmed standing.

Typical Failure Modes

Often confused with: A philosophical essay, a finished definition system, or an authority that “settles” the meaning of words.
Should NOT be used for: Producing permanent or authoritative definitions; moral or political prescription; claims of universal applicability without independent confirmation.
Common misuse: Treating a single Self-Assessed run (especially AI-only) as Confirmed standing; skipping the Counterexample Quality Gate; declaring a floor without separating adjacent questions; inflating instrument_grade beyond documented evidence.
Common misread: Completing a pass means “T is calibrated.”

Correct: Completing a pass yields a procedure-bound instrument record for a stated sense. The wider abstract may remain open. Standing stays Self-Assessed until independent pressure says otherwise.

Context, Prior Work, and Importance

TDP-001 is a metrological protocol for converting natural-language terms into explicit, versioned, adversarially tested mechanisms. It is not presented as an unprecedented invention. Multiple mature fields have already attacked pieces of the same problem. TDP-001’s value lies in integrating several previously separate practices into a single, auditable calibration pipeline and in treating certain outputs (especially floors) as first-class results rather than process failures.

Related Prior Work

Formal Concept Analysis (FCA) — Strong on hierarchical object–attribute structure; weak on mechanistic testing, adversarial falsification, and explicit failure-mode characterization for natural-language mechanisms.
Natural Semantic Metalanguage (NSM) — Strong on reductive paraphrase toward semantic primes; remains largely text-to-text and does not emit executable decision procedures or a full adversarial calibration record.
Description logics / ontology engineering (OWL, RDF) — Strong taxonomic consistency; limited adversarial stress-testing of everyday abstract terms or floor-as-primary-output.
Property-based / invariant testing (e.g. QuickCheck lineage) — Generate–test–shrink is close in spirit to a counterexample quality gate; historically aimed at programs, not abstract natural-language mechanisms.
Operational definitions (Bridgman and later adaptations) — Tie concepts to operations; rarely yield a general, versioned, multi-instrument calibration record for contested civil vocabulary.
ISO terminology work (e.g. ISO 704 / ISO 1087 family) — Concept systems and terminological consistency; not an adversarial mechanism-testing loop with floor characterization as a primary output.
AI red-teaming — Hostile inputs to surface failure modes; usually targets model behavior rather than the conceptual instrument itself.

What TDP-001 Integrates

None of the above fully combine: atomicity/bundle discipline, mechanism-as-hypothesis, adversarial quality gate, floor-as-result, mid-run correction trace, and a versioned Calibration Record with explicit standing. TDP-001 is that integration claim — testable by re-running the protocol, not by citation count.

Importance

Law, policy, institutional standards, technical glossaries, and AI reasoning continually accumulate unexamined semantic drift, overloaded definitions, and invisible mechanism changes. Prior methods improve taxonomy, paraphrase, formal consistency, or empirical robustness in isolation. TDP-001 supplies a repeatable procedure those systems can use, challenge, or ignore. Standing of any resulting instrument remains open to independent re-run and evidence-based revision.

See also: Prior Art and Gaps in Conceptual Instrumentation (detailed comparative notes, when present).

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: Use vs object

Forces split between procedure-bound use and unfinished abstract. Does not by itself raise standing.

For term T under protocol P:
1) What operational steps does P give a user when they encounter T?
2) What part of “T” is thereby constrained (use, mechanism, boundaries)?
3) What part of the abstract remains unconstrained?
4) List one claim we must NOT make solely because P ran once.
Answer in four short labeled blocks. Prefer underclaim.

Probe: Floor / anti-laundering

Legal patches only (tighten, split, rename, retire). Requires an external check before standing moves.

A floor or logic flaw appeared for definition D of term T.
Propose instrument adjustments that:
- preserve stated purpose/identity of D, or
- explicitly split/rename child senses.
Reject any patch that keeps the label’s prestige while changing the payload.
Then: is further iteration “anchored calibration” or “unanchored dreaming”? Name the external check that would decide.

Revision Trigger

This page and the controlled document should be reconsidered when:

An independent re-run of the protocol or of CR-FAIR-001 produces a material divergence.
A second term is fully decomposed and reveals a structural gap in TDP-001 itself.
The Counterexample Quality Gate, Survival minimum, or floor-standing rule is shown insufficient under load.
A machine-readable schema annex is issued.

See the Game. Refuse the Game. Build Better.

Structural Connections

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 Definition Mechanics (Seed)	Core	Experimental	2026-07-27	Current	None open
Vision and Phased Roadmap	Supporting	Experimental	2026-07-25	Current	Breadcrumb-Open
CR-FAIR-001 Fairness Calibration Record	Supporting	Experimental	2026-07-25	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: Permanent Beta • Metrology of the Abstract • CR-FAIR-001 Fairness Calibration Record 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	TDP-001 Term Decomposition Protocol
URL	https://www.thesovereigngames.com/wiki/TDP-001_Term_Decomposition_Protocol
Description	Site entry for Working Standard TDP-001 (Provisional, Self-Assessed): how to use, normative intent, failure modes, prior-work context, and link to the controlled v0.1.2 document.
Category	Working Standards