>Goto:Go

Support document · Issue 1

Glossary

got-v1-part-3-support-glossary

Plain textOriginal documentPDF
Contents

Support Document SD-02 - Series Master Glossary

Part 3 (Sections 3a–3c): The Epistemic Method | Consolidated controlled vocabulary | Source-locked | Issue 1

Control field

Value

Document ID

TEM-P3-3A3B3C-SD02-GLOSSARY

Version / issue

Issue 1 - aligned to the Issue 1 paper sequence

Date

2026-09-24

Status

Controlled Part 3 support document aligned to the eight Issue 1 canonical papers, GOT-V1-3a-1 through GOT-V1-3c-8. Secondary to the canonical papers.

Supersedes

Glossary - Issue 1 - Formatted.docx. This content reconciliation preserves the eight-paper sequence and updates source identities, ownership, locators, and support dependencies. Earlier release history remains recoverable in that source copy.

Function

Records controlled definitions, canonical homes, relation notes, and use guardrails across Section 3a, 3b, and 3c. No new concepts are introduced.

Canonical rule

Exact technical definitions remain in the owning canonical paper. This glossary compresses and cross-indexes; it does not redefine.

Internal split rule

Section 3a, Section 3b, and Section 3c remain distinct canonical regions inside one Part-level support control. Downstream papers may inherit and apply upstream architecture but do not retroactively redefine it.

Source-lock rule

Use only the eight current Part 3 papers for Part 3 vocabulary. Upstream Part 1/2 controls may define inherited terms but may not be expanded here.

Template rule

Retain the established support-document layout and control schema. Earlier support copies retain historical evidence; the eight Issue 1 papers govern current content. Parts 1 and 2 remain inherited-control references only.

0. Status, function, and source discipline

A term is permitted only when its discriminator conditions remain visible. Terms naming closure, unknown, power, responsibility, trust, warrant, formalisation, governance, method-use, certification, compliance, or authority must not carry strength beyond the recoverable conditions in the owning paper.

0.1 Canonical source-lock register

Paper keys 3a-1 to 3c-8 abbreviate the full GOT-V1 identifiers below. Section locators refer to the numbered headings in the Issue 1 papers; endnote locators use their Arabic note numbers. SHA16 records the first 16 hexadecimal characters of SHA-256.

Seq.

Current canonical source

Canonical paper

Canonical ownership / use

GOT-V1-3a-1

GOT-V1-3a-1 - The Gödel Horizon - Issue 1.docx | sha16 44a8b20a68541a55

The Gödel Horizon

Horizon grammar: relational availability; availability/closure boundary conditions; Soft Horizon; Gödel Horizon; Procedural Availability Horizon; coupled loci; abstraction boundaries; comparator and stabilisation discipline.

GOT-V1-3a-2

GOT-V1-3a-2 - The Discipline of the Unknown - Issue 1.docx | sha16 04d3becc2b5a5029

The Discipline of the Unknown

Unknown-statuses; residual; positive exclusion; live formulations; Best Available Formulation; Weighted Residual; action threshold, safeguard, monitoring, stop condition, update, and branch-memory.

GOT-V1-3b-3

GOT-V1-3b-3 - On the Origin of Power - Issue 1.docx | sha16 d6d961fbb277a77c

On the Origin of Power

Primitive Power as IPL-indexed distinction-conditioned branch potential; Counterfactual Inclusion Field; potential/application/consequence separation; Counterfactual Exclusion; thermodynamic grounding.

GOT-V1-3b-4

GOT-V1-3b-4 - On the Origin of Responsibility - Issue 1.docx | sha16 ef17be5480bc49e7

On the Origin of Responsibility

Primitive Responsibility as locus-indexed attribution; Responsibility Provenance; distributed and temporal provenance; Responsibility Gradient; Immediate-Frame Principle; Responsibility Warrant.

GOT-V1-3b-5

GOT-V1-3b-5 - On the Origin of Trust - Issue 1.docx | sha16 d8a68ac35982e5a0

On the Origin of Trust

Trust as reliance closure under residual; primitive audit; branch-space economy; trust thresholds; vicarious trust; Epistemic Authority and the minimum Structural Authority distinction (§8); trust carriers; laundering; betrayal, repair, and formalisation handoff.

GOT-V1-3c-6

GOT-V1-3c-6 - The Case for Formalisation - Issue 1.docx | sha16 b4d11bd226838155

The Case for Formalisation

Load-bearing language; recoverable authority; distinct epistemic grounding and structural authorisation (§1); epistemic debt; institutions and machines; formalisation as preservation; auditable claim packet; proportional formalisation; retrospective review.

GOT-V1-3c-7

GOT-V1-3c-7 - The Constitutional Governance of Formalisation - Issue 1.docx | sha16 a3540c539c730360

The Constitutional Governance of Formalisation

Governance of formalisation; constitutional/technical/application levels; application of Epistemic Authority inherited from 3b-5; custodial and operational applications of Structural Authority (§6); amendment, forks, certification, and capture controls.

GOT-V1-3c-8

GOT-V1-3c-8 - The Epistemic Method - Issue 1.docx | sha16 dc08048b02787be4

The Epistemic Method

Integrated relational audit of claim-strength and reliance-strength; indexed relation; claim and reliance paths; comparator, residual, reliance limit; preferential reliance and carrier-path preservation (§6); conditional Power/Responsibility audits; method-compliance is not closure.

0.2 Upstream inherited-control references

Control ID

Current source

Permitted use

P1-SD01

Part 1 - Concept Compression Map - Issue 1.docx | sha16 a256c5229849f993

Upstream architecture compression for NTC, BD, IPL, DTS, life-threshold and localisation discipline.

P1-SD02

Part 1 - Glossary - Issue 1.docx | sha16 e97712ced4e2b095

Upstream controlled vocabulary for inherited Part 1 terms.

P1-SD03

Part 1 - Guardrail and Failure-Mode Register - Issue 1.docx | sha16 794360cc1ff16519

Upstream comparator, localisation, source-lock, and anti-inflation guardrails.

P1-SD04

Part 1 - Bibliography and Relation Register - Issue 1.docx | sha16 7b0b194c1552979b

Upstream bibliographic relation-control reference only; no citation transfer into Part 3.

P2-SD01

Part 2 - Concept Compression Map - Issue 1.docx | sha16 eee99287e2cfaa10

Upstream control for RRP, signal, OP/OA/OR/RAS/RSD, knowledge, intelligence, observation, abstraction, scale, and observation-program architecture.

P2-SD02

Part 2 - Glossary - Issue 1.docx | sha16 b144e7dc2eac7133

Upstream controlled vocabulary for inherited informational and observational terms.

P2-SD03

Part 2 - Guardrail and Failure-Mode Register - Issue 1.docx | sha16 f955341321f11d30

Upstream failure-control for local locus, information/signal, observation, abstraction, scale, and descriptor discipline.

P2-SD04

Part 2 - Bibliography and Relation Register - Issue 1.docx | sha16 12dc458d0e940e8c

Upstream bibliographic relation-control reference only; no citation transfer into Part 3.

Protocol

Historical reference: GOT - Bibliographic Identification Classification and Adjacency Discovery Protocol - Issue 1(1).docx | sha16 03dec29bfa52830c

Retained classification context from the prior support release. This protocol file is not in the current supplied control set; its recorded hash is historical and is not represented as a newly verified source. Existing classifications are retained, with no new promotion of inheritance.

0.3 Part-level support-control chain

Control ID

Current control file

Permitted use

P3-SD01

Concept Compression Map - Issue 1.docx | sha16 874e44c76caf3061

Architecture compression and source-discipline control. Secondary to canonical papers.

Excluded source class: superseded Part 3 paper revisions as current identities; contextual essay-series material; downstream extension proposals; prior generated answers; unverified or unadmitted external material; and any later Part 3 concept not present in the current eight-paper canonical sequence. Bibliographic recurrence does not create technical inheritance.

SD-01, sections 9–10, preserves the identity migration and the deferred Toolkit update control. The eight-paper lock remains active; the future Toolkit does not yet supply a Part 3 definition, guardrail, or bibliography entry.

1. Canonical ownership map

Section

Owner

Controlled region

Guardrail

3a

3a-1

Relational availability, horizon grammar, Soft Horizon, Gödel Horizon, procedural availability, stabilisation.

Do not turn every limit into Gödel diagnosis or every provisional closure into warrant.

3a

3a-2

Unknown-status, residual, positive exclusion, live formulations, weighting, BAF, action under residual, update.

Do not flatten unknowns into one blank or convert action threshold into truth threshold.

3b

3b-3

Primitive Power, CIF, potential/application/consequence, CE, cumulative branch effect.

Do not infer Power from force, authority, success, imagined alternatives, or causation alone.

3b

3b-4

Primitive Responsibility, Provenance, Gradient, Immediate Frame, Warrant, distributed/temporal attribution.

Do not collapse provenance into role, blame, legal liability, proximity, or exterior hindsight.

3b

3b-5

Primitive Trust, primitive audit, reliance closure, carrier, threshold, vicarious trust, Epistemic Authority, minimum Structural Authority, laundering, betrayal/repair.

Trust makes standing operative without creating it. Epistemic standing and structural permission remain distinct; Structural Authority development stays in Volume 2.

3c

3c-6

Load-bearing language, epistemic debt, formalisation, auditable claim packet, proportionality, retrospective review.

Do not treat forms, machine execution, documentation, or auditability as relation-preservation by default.

3c

3c-7

Governance levels; inherited Epistemic Authority; custodial and operational applications of Structural Authority; amendment, forks, release/certification/capture controls.

No steward, institution, vote, certificate, release, or implementation creates epistemic strength.

3c

3c-8

Relational audit, claim/reliance strength, indexed relation, path recovery, non-auditability, integrated outputs.

The integrated method does not erase local discriminators; method-compliance is not closure.

Section 3a - Horizon and Unknown Discipline

Term

Controlled definition

Canonical home / type

Relationship and guardrail

Relational availability

Status of a target relation for a specified locus under stated access conditions before closure is presumed.

3a-1 | Foundational relation

Availability is not existence, registration, knowledge, warrant, or closure.

Availability condition

Specified condition under which a relation can become available to the locus.

3a-1 | Access

Keep boundary, interface, scale, horizon, discrimination, abstraction, and path conditions visible.

Closure demand

The kind and strength of resolution the claim requires: proof, explanation, classification, action, measurement, etc.

3a-1 | Claim status

No horizon diagnosis without the closure demand being stated.

Horizon

Locus-relative boundary in relational availability and closure.

3a-1 | Boundary

Not an object, place, ontological zone, or generic mystery.

Soft Horizon

Provisional, purpose-indexed closure under residual.

3a-1 | Finite continuation

Legitimate only while scope, residual, tolerance/comparator, and update remain attached.

Gödel Horizon

Boundary where relation is available or formulable under a closure demand while the present abstraction regime discloses that it cannot supply closure from its own current resources.

3a-1 | Boundary disclosure

Do not generalise incompleteness into a claim that everything is undecidable.

Procedural Availability Horizon

Condition where an abstraction can state what would count, but the realised process/evidence/instrument/path needed to bring the relation into comparison or closure is unavailable.

3a-1 | Availability-side horizon

Describability is not realised availability.

Misclosure

Closure assigned under a pattern or claim path that does not preserve the target relation strongly enough for the demand being made.

3a-1/3a-2 | Failure

Correction must recover what was available, omitted, or overclaimed.

Latent abstraction boundary

Limit generated by the abstraction regime that may remain invisible until residual, anomaly, comparison, or failure exposes it.

3a-1 | Abstraction boundary

Do not treat a stable category as evidence that its cut is complete.

Counterfactual Comparison Discipline

Requirement that closure strength be tested against relevant alternative formulations or comparator cases.

3a-1 | Method

Epistemic comparator alternatives are not automatically causal CIF branches.

Stabilisation

Process by which one closure, model, pattern, or branch becomes operationally dominant.

3a-1/3a-2 | Dynamics

Stabilisation may be earned or may hide lost alternatives.

Excluded branch-space

Alternatives no longer live or visible after stabilisation.

3a-1 | Branch memory

Distinguish earned exclusion from forgetting, suppression, non-formulation, or path loss.

Unknown-status

Typed unresolved relation indexed to locus, availability condition, and closure demand.

3a-2 | Status

Unknown is not one undifferentiated absence.

Unavailable unknown

Relation outside the present access regime.

3a-2 | Unknown-status

Use access humility; do not infer non-existence.

Available-but-unrecognised unknown

Relation has entered access but has not been stabilised as identity/closure.

3a-2 | Unknown-status

Preserve availability without forcing nearest-pattern closure.

Misclosed unknown

Relation treated as closed under a pattern that later fails or is inadequately grounded.

3a-2 | Unknown-status

Retain correction path and branch-memory.

Residual

Localised remainder left by an unmet closure condition, including what stronger claim is blocked and what would force update.

3a-2 | Residual

Residual is not mysticism, generic uncertainty, or a decorative caveat.

Positive exclusion

Recorded reason a candidate formulation no longer remains live under the stated comparator and evidence conditions.

3a-2 | Branch discipline

Do not confuse excluded alternatives with merely forgotten or unconsidered ones.

Live formulation field

Set of currently admissible formulations remaining live under the indexed conditions.

3a-2 | Alternative field

Not identical to the physically supported CIF of an IPL.

Live Field Contraction

Earned reduction of the live formulation field with reasons and branch-memory preserved.

3a-2 | Update

Contraction is not closure unless the closure demand is also satisfied.

Best Available Formulation (BAF)

Strongest currently supportable formulation for a stated purpose while residual remains explicit.

3a-2 | Soft Horizon

Best available does not mean true, final, or uniquely exhaustive.

Weighted Residual

Structured remainder retaining differential support, exclusions, uncertainty, and update obligations.

3a-2 | Residual

Weighting does not require false numerical precision.

Actionable residual

Residual under which action is required or justified before stronger closure is available.

3a-2 | Action

Action threshold is not truth threshold.

Action threshold

Condition at which action becomes warranted for the stated purpose despite residual.

3a-2 | Decision

Keep consequence-sensitive action separate from epistemic closure.

Safeguard

Constraint limiting harm or overreach when acting under incomplete closure.

3a-2 | Action control

Material where reversibility, exposure, or affected-locus risk requires it.

Monitoring condition

Specified observation required while an action or Soft Horizon remains in force.

3a-2 | Update

Monitoring must be capable of triggering revision.

Stop condition

Condition requiring suspension, withdrawal, escalation, or reversal.

3a-2 | Action control

Do not treat continuation as evidence the original closure was correct.

Update trigger

Recoverable condition that requires the formulation, closure, threshold, or action to be revisited.

3a-2 | Corrigibility

No provisional closure without a route by which it can move.

Stabilisation Bias

Retrospective distortion by which the realised branch makes earlier alternatives or uncertainty appear weaker than they were.

3a-2 | Failure

Preserve what was live and knowable at the relevant time.

Branch-memory

Recoverable record of live, excluded, unavailable, and revised alternatives and the reasons for change.

3a-2 | Audit memory

Required to prevent hindsight reconstruction from erasing the live field.

Section 3b - Power, Responsibility, and Trust

Term

Controlled definition

Canonical home / type

Relationship and guardrail

Primitive Power

Indexed potential of an IPL to alter downstream branch-realisation through organisation-mediated discriminable distinctions under stated conditions.

3b-3 | Causal potential

Force, office, permission, success, or causation alone does not establish Power. The discriminator remains IPL-indexed distinction-conditioned branch potential (3b-3 §§11–12).

Power Relation

Relation among IPL, operative distinctions, CIF, comparator family, reference conditions, and branch consequence.

3b-3 | Audit relation

Specify the physically grounded path; do not infer from labels.

Counterfactual Inclusion Field (CIF)

Locus-indexed field of downstream branch relations physically included within an IPL’s distinction-conditioned potential under stated conditions.

3b-3 | Possibility field

Exterior imagination does not add branches to the CIF.

Power potential

Branch-changing capacity supported before present application.

3b-3 | Potential

Consequence demonstrates potential but does not create it retrospectively.

Power application

Use of an operative distinction through the power-bearing organisation.

3b-3 | Realisation

Application is distinct from possession of potential and from downstream evaluation.

Power consequence

Counterfactually recoverable downstream difference produced by application.

3b-3 | Consequence

Magnitude or success does not define the primitive.

Counterfactual Exclusion (CE)

Negative side of a realised distinction-conditioned branch event: a relevant included alternative is not equivalently realised.

3b-3 | Realisation

Not conscious rejection, metaphysical deletion, or generic elimination of possibilities.

Cumulative Power

Horizon-relative trajectory bias accumulated through repeated branch-changing events.

3b-3 | Dynamics

Individual applications need not deterministically fix the final outcome.

Primitive Responsibility

Locus-indexed attribution of consequential branch-relation dependence to distinction-conditioned organisation.

3b-4 | Attribution

Not first blame, guilt, duty, legal liability, intention, or role.

Responsibility Provenance

Recoverable path of responsibility-bearing distinction-conditioned transformations that materially condition a consequence.

3b-4 | Provenance

Subset of causal provenance; does not simply transfer between loci.

Distributed Responsibility Provenance

Responsibility-bearing path distributed across multiple local transformations and loci.

3b-4 | Provenance

Do not collapse a graph into one responsible noun or conserved scalar.

Temporal Responsibility

Attribution across origin, retention, redeployment, maintenance, and update over time.

3b-4 | Temporal attribution

Earlier origin does not imply permanent ownership of later consequence.

Field-conditioning responsibility

Attributable material change to another locus’s CIF through maintained, withheld, exposed, narrowed, or otherwise governed power-bearing conditions.

3b-4 | Attribution

Responsibility need not wait for CE where the possibility field itself is consequentially conditioned.

Co-realisation incompatibility

Relation in which branches in different locus-indexed CIFs cannot be equivalently realised under shared physical conditions.

3b-4 | Potential relation

Not itself CE because no branch need yet be realised.

Responsibility-relevant capacity

Range/depth of discrimination, retention, abstraction, comparison, projection, correction, residual, control, and power-governance operations relevant to attribution.

3b-4 | Capacity

Do not replace with generic complexity.

Responsibility Gradient

Ordinal relational increase in breadth/depth of responsibility-relevant capacity and recoverable causal contribution.

3b-4 | Gradient

Not a universal scalar moral score.

Immediate-Frame Principle

Responsibility is evaluated against relations materially available or recoverable to the locus under the relevant time and operating conditions.

3b-4 | Temporal/frame discipline

Blocks both exterior hindsight over-attribution and retrospective self-laundering.

Responsibility Warrant

Social, moral, legal, organisational, or institutional allocation of answerability, duty, burden, liability, or decision ownership.

3b-4 | Allocation

May be legitimate without being Responsibility Provenance.

Primitive Trust

Reliance closure under residual by which a finite locus reduces repeated audit enough to continue.

3b-5 | Reliance

Trust is not certainty, proof, belief, moral goodness, or automatic warrant.

Primitive audit

Relation-revalidation that reopens a backgrounded trust relation when mismatch, stakes, anomaly, or changed condition makes reduced audit insufficient.

3b-5 | Correction

Trust and audit are complementary, not opposites.

Reliance closure

Purpose-indexed closure sufficient for dependence, continuation, delegation, inference, or action.

3b-5 | Soft Horizon

Must carry residual and update.

Branch-space economy

Reduction in repeated checking work that lets a finite locus navigate dependencies.

3b-5 | Function

Efficiency does not create epistemic strength.

Trust threshold

Condition at which reliance is satisfactory enough for the relying locus’s closure demand.

3b-5 | Threshold

Need not be probabilistic or interpersonal.

Trust relation

Indexed relation among relying locus, target relation, carrier, closure demand, residual, threshold, safeguard where relevant, and update.

3b-5 | Architecture

Trust is always trust of some relation under conditions.

Trust carrier

Person, role, record, credential, procedure, institution, instrument, model, interface, certificate, standard, archive, platform, or machine output through which reliance-strength travels.

3b-5 | Carrier

Carrier is not trust ground by default.

Vicarious trust

Reliance in which another locus or carrier’s closure process satisfies part of the relying locus’s closure demand.

3b-5 | Outsourced closure

Borrowed closure carries residual and does not transfer responsibility provenance.

Borrowed closure

Closure-work performed elsewhere and relied upon locally.

3b-5 | Reliance

The relying locus must retain scope and reopening conditions.

Epistemic Authority

Defeasible standing of a claim, distinction, or closure-process to guide judgement or reliance, earned through demonstrated preservation of a specified target relation under stated availability conditions and closure demand.

3b-5 §8 | Epistemic standing

Preferential reliance between loci requires demonstrated advantage for a shared target relation and comparable closure demand, preserved through the carrier path. Relative advantage may remain insufficient for use. Trust, confidence, permission, or consequence does not create the standing.

Structural Authority

Permission or mandate to act or decide within a specified scope, conferred or recognised by an organised information-processing structure.

3b-5 §8 | Minimum authority distinction

Structural Authority does not establish Epistemic Authority, and Epistemic Authority does not itself confer Structural Authority. Further development belongs to Volume 2; 3c-7 §6 applies the distinction to custody and domain use.

Trust laundering

Transfer of reliance-strength from a trusted carrier or context to a relation that did not earn equivalent closure.

3b-5 | Failure

A mark, role, institution, or certificate cannot spend trust beyond its grounding.

Distrust

Active withholding or reduction of reliance because the relevant closure demand is not satisfied.

3b-5 | Reliance status

Not identical to absence of trust.

Mistrust

Reliance relation distorted by an inaccurate or misclosed model of the target/carrier.

3b-5 | Failure

Can be over-trust or under-trust depending on the relation.

Betrayal

Agency/norm-sensitive trust failure where relied-upon relation is violated under conditions carrying vulnerability or obligation.

3b-5 | Mature trust failure

Stronger than primitive trust failure.

Trust repair

Restoration, narrowing, or refusal of reduced audit through correction of the failed relation and its safeguards/update conditions.

3b-5 | Repair

Reassurance alone is not repair.

Section 3c - Formalisation, Governance, and the Integrated Method

Term

Controlled definition

Canonical home / type

Relationship and guardrail

Load-bearing language

Language or category doing consequential work inside a decision, classification, governance, enforcement, allocation, certification, or machine path.

3c-6 | Trigger

Ordinary language need not be universally formalised.

Semantic drift

Change in the relation carried by a term while the term remains apparently stable.

3c-6 | Failure

Drift becomes dangerous when authority remains attached to an outdated closure.

Load-bearing drift

Migration of a term/category across consequential contexts without its grounding conditions.

3c-6 | Failure

Authority must not outrun relation-preservation.

Epistemic debt

Deferred grounding cost created when load-bearing claims or linguistic closures circulate as if their grounding burden had already been paid.

3c-6 | Liability

Debt returns as opacity, misclassification, audit failure, or inability to update.

Recoverable authority

Authority whose operative relation and grounding conditions can be reconstructed and audited.

3c-6 | Control

Keep the evidence path supporting Epistemic Authority distinct from any Structural Authority governing its use (3c-6 §1).

Formalisation

Discipline of making load-bearing claim/reliance conditions recoverable at a level proportionate to consequence.

3c-6 | Method

Not freezing all language or replacing judgement with rules.

Auditable claim packet

Recoverable structure containing relation, locus, availability, closure demand, abstraction, evidence/record/carrier paths, comparator, residual, threshold, safeguard, and update as material.

3c-6 | Technical structure

Completion is not closure; packet fields are not proof.

Proportional formalisation

Formalisation burden scaled to consequence, exposure, contestability, reliance, reversibility, and audit need.

3c-6 | Proportionality

Do not impose maximum formalisation on every ordinary claim.

Claim path

Recoverable path by which a claim acquires its present content and strength.

3c-6/3c-8 | Audit path

Keep distinct from reliance path.

Reliance path

Recoverable path by which one locus relies on a claim, carrier, closure process, or output.

3c-6/3c-8 | Audit path

Reliance-strength may differ from claim-strength.

Evidence path

Recoverable relation from evidence source through transformations to the claim.

3c-6/3c-8 | Audit path

Evidence presence does not settle adequacy or warrant.

Record path

Recoverable production, retention, transformation, and use of a record.

3c-6/3c-8 | Audit path

Record provenance is not warrant by default.

Carrier path

Recoverable movement of claim/reliance strength through persons, roles, records, procedures, institutions, models, or machines.

3c-6/3c-8 | Audit path

A demonstrated advantage at the contributing locus must survive the carrier path for preferential reliance to remain supported (3b-5 §8; 3c-8 §6).

Non-auditability

Condition where a load-bearing relation/path cannot be recovered strongly enough for the closure demand being made.

3c-6/3c-8 | Output

Non-auditability may require claim weakening, refusal, action limits, or update obligations.

Adaptive application

Domain-specific use of the method under local conditions without altering the technical or proposed constitutional burdens.

3c-7 | Governance level

Local adaptation is not amendment.

Current technical formalisation

Present auditable structures used to implement proposed constitutional burdens.

3c-7 | Governance level

Technical form may change if relation-preservation is demonstrated.

Proposed constitutional elements

Highest-level proposed burdens intended to govern how the method remains relation-preserving and corrigible.

3c-7 | Governance level

The word constitutional does not make an element immune to demonstrated failure.

Custodial authority

Application of Structural Authority to stewardship of releases, archives, amendment histories, dissent, residual registers, provenance, and fork comparisons.

3c-7 §6 | Governance application; inherits 3b-5 §8

Stable custody preserves recoverability and correction; it does not establish epistemic standing or ownership of validity.

Operational authority

Application of Structural Authority within a particular institution or domain under its mandate and operating conditions.

3c-7 §6 | Governance application; inherits 3b-5 §8

Domain use and permission do not validate the method or a decision; the relevant relation-preserving burden remains.

Demonstrated relation-preservation

Burden showing that a proposed formulation preserves the relevant target relation more strongly under stated conditions and comparator pressure.

3c-7 | Amendment test

Revision must state failure class, reduced residual, introduced residual, and its own failure conditions.

Competitive fork

Explicit rival formalisation developed under retained comparison, provenance, residual, and update conditions.

3c-7 | Corrigibility

A fork is not valid merely because it exists or is popular.

Best Available Formalisation

Strongest current technical formalisation for the stated governance purpose while residual remains explicit.

3c-7 | Soft Horizon

Release status is provisional, not ownership.

Certification closure

Operational reliance closure attached to a certification result.

3c-7 | Governance carrier

Certificate must stay limited to what was actually assessed and remain reopenable.

Constitutional-label capture

Failure in which the label constitutional shields a method element from correction rather than increasing its burden of justification.

3c-7 | Capture

Higher level means higher correction burden, not immunity.

Epistemic Method

Integrated discipline of relational audit under finite conditions.

3c-8 | Integrated method

Not a theory of everything, universal decision procedure, or substitute for domain expertise.

Relational audit

Audit of whether a claim or reliance closure preserves the relation it purports to carry under indexed conditions.

3c-8 | Method

Audit strength follows recoverable relation, not form completion.

Indexed relation

Target relation stated with locus, availability, boundary, scale, horizon, abstraction, and closure demand sufficient to make the claim evaluable.

3c-8 | Audit input

No claim from nowhere.

Relational uncertainty

Uncertainty about whether a claim, closure, reliance relation, or Soft Horizon preserves the relation it purports to carry under indexed conditions.

3c-8 §3 | Explicit audit formulation; used in 3b-5 §§2, 6, 8

Not reducible to subjective doubt or probability deficit.

Claim-strength

Strength earned by a claim insofar as its relation-preserving path survives the relevant audit burden.

3c-8 | Output dimension

Officiality, precision, repetition, or action do not automatically strengthen it.

Reliance-strength

Strength with which a locus may rely on a claim, carrier, or closure process for its closure demand.

3c-8 | Output dimension

May be lower or differently conditioned than claim-strength.

Reliance limit

Boundary beyond which a trusted relation/carrier/closure process no longer satisfies the relying locus’s closure demand.

3c-8 | Reliance control

Must remain recoverable where reliance is load-bearing.

Conditional audit path

Relation-specific extension activated only when a claim engages a specialised architecture such as Power or Responsibility.

3c-8 | Method

Does not make CIF, CE, or Responsibility Provenance universal fields.

Method-compliance is not closure

Rule that completion, conformity, certification, or declared method-use cannot substitute for demonstrated relation-preservation.

3c-8 | Meta-guardrail

The method itself is a Soft Horizon and remains corrigible.

Action under residual

Permitted action where threshold and safeguards justify continuation before stronger closure.

3a-2/3c-8 | Action output

Action does not erase or retroactively settle residual.

2. Cross-Part inherited terms

Inherited term family

Upstream home

Part 3 use rule

NTC, BD, IPL, DTS

Part 1

Use for causal/localisation/thermodynamic burdens only; do not import the Part 1 life-attribution ladder into Part 3.

RRP, OP, OA, OR, RAS, RSD, signal

Part 2a

Use as inherited informational access architecture; Part 3 horizons and audit do not redefine these primitives.

Knowledge, Intelligence, Observation

Part 2b

Use retained/applied/registered distinction statuses as inherited functions; do not use Part 3 Power/Responsibility/Trust to rewrite their thresholds.

Abstraction, perspective, scale, observation envelope

Part 2b

Use to index finite access and audit scope; Part 3 residual and horizon terms do not replace observation-program diagnostics.

3. Release checklist

• Every controlled Part 3 term has an owning canonical paper.

• Section 3a terms are not retrospectively defined through Section 3b/3c vocabulary.

• CIF and CE remain Power-specific unless a later claim explicitly engages that architecture.

• Responsibility Provenance and Responsibility Warrant remain distinct.

• Trust carrier remains distinct from trust ground and from Responsibility Provenance.

• Formalisation structures remain technical carriers rather than epistemic certificates.

• Epistemic Authority and Structural Authority retain their canonical home in 3b-5 §8. Custodial and operational authority remain downstream governance applications in 3c-7 §6.

• The Epistemic Method integrates but does not erase local discriminators.