Guardrail and Failure-Mode Register
got-v1-part-3-support-guardrail-and-failure-mode-register | Support document | Issue 1
https://goto-go.com/machine/documents/got-v1-part-3-support-guardrail-and-failure-mode-register/

Support Document SD-03 - Guardrail and Failure-Mode Register

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


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t01

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r01
Control field: Document ID
Value: TEM-P3-3A3B3C-SD03-GUARDRAIL

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r02
Control field: Version / issue
Value: Issue 1 - aligned to the Issue 1 paper sequence

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r03
Control field: Date
Value: 2026-09-24

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r04
Control field: Status
Value: 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r05
Control field: Supersedes
Value: Guardrail and Failure-Mode Register - 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r06
Control field: Function
Value: Records Part-level guardrails, failure modes, severity classes, corrections, and diagnostic questions while preserving distinct 3a/3b/3c ownership.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r07
Control field: Canonical rule
Value: Primary papers govern technical definitions. Failure-control may expose drift but may not create new technical content.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r08
Control field: Internal split rule
Value: 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r09
Control field: Source-lock rule
Value: Use the eight canonical Part 3 papers and current SD-01/SD-02 as active Part 3 control. Use Parts 1/2 only for inherited terms and guardrails.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t01-r10
Control field: Template rule
Value: 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

Primary guardrail: no claim, horizon label, unknown label, branch field, responsibility noun, trust carrier, formalisation packet, institutional procedure, release, certificate, schema, model, machine output, or method-compliance statement may carry more strength than the recoverable relation and discriminator conditions that earn it.

0.1 Canonical source-lock register

Paper keys 3a-1 <https://goto-go.com/machine/documents/got-v1-3a-1/> to 3c-8 <https://goto-go.com/machine/documents/got-v1-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.


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t02

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r01
Seq.: GOT-V1-3a-1
Current canonical source: GOT-V1-3a-1 - The Gödel Horizon - Issue 1.docx | sha16 44a8b20a68541a55
Canonical paper: The Gödel Horizon
Canonical ownership / use: Horizon grammar: relational availability; availability/closure boundary conditions; Soft Horizon; Gödel Horizon; Procedural Availability Horizon; coupled loci; abstraction boundaries; comparator and stabilisation discipline.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r02
Seq.: GOT-V1-3a-2
Current canonical source: GOT-V1-3a-2 - The Discipline of the Unknown - Issue 1.docx | sha16 04d3becc2b5a5029
Canonical paper: The Discipline of the Unknown
Canonical ownership / use: Unknown-statuses; residual; positive exclusion; live formulations; Best Available Formulation; Weighted Residual; action threshold, safeguard, monitoring, stop condition, update, and branch-memory.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r03
Seq.: GOT-V1-3b-3
Current canonical source: GOT-V1-3b-3 - On the Origin of Power - Issue 1.docx | sha16 d6d961fbb277a77c
Canonical paper: On the Origin of Power
Canonical ownership / use: Primitive Power as IPL-indexed distinction-conditioned branch potential; Counterfactual Inclusion Field; potential/application/consequence separation; Counterfactual Exclusion; thermodynamic grounding.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r04
Seq.: GOT-V1-3b-4
Current canonical source: GOT-V1-3b-4 - On the Origin of Responsibility - Issue 1.docx | sha16 ef17be5480bc49e7
Canonical paper: On the Origin of Responsibility
Canonical ownership / use: Primitive Responsibility as locus-indexed attribution; Responsibility Provenance; distributed and temporal provenance; Responsibility Gradient; Immediate-Frame Principle; Responsibility Warrant.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r05
Seq.: GOT-V1-3b-5
Current canonical source: GOT-V1-3b-5 - On the Origin of Trust - Issue 1.docx | sha16 d8a68ac35982e5a0
Canonical paper: On the Origin of Trust
Canonical ownership / use: 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r06
Seq.: GOT-V1-3c-6
Current canonical source: GOT-V1-3c-6 - The Case for Formalisation - Issue 1.docx | sha16 b4d11bd226838155
Canonical paper: The Case for Formalisation
Canonical ownership / use: 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r07
Seq.: GOT-V1-3c-7
Current canonical source: GOT-V1-3c-7 - The Constitutional Governance of Formalisation - Issue 1.docx | sha16 a3540c539c730360
Canonical paper: The Constitutional Governance of Formalisation
Canonical ownership / use: 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.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t02-r08
Seq.: GOT-V1-3c-8
Current canonical source: GOT-V1-3c-8 - The Epistemic Method - Issue 1.docx | sha16 dc08048b02787be4
Canonical paper: The Epistemic Method
Canonical ownership / use: 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


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t03

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r01
Control ID: P1-SD01
Current source: Part 1 - Concept Compression Map - Issue 1.docx | sha16 a256c5229849f993
Permitted use: Upstream architecture compression for NTC, BD, IPL, DTS, life-threshold and localisation discipline.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r02
Control ID: P1-SD02
Current source: Part 1 - Glossary - Issue 1.docx | sha16 e97712ced4e2b095
Permitted use: Upstream controlled vocabulary for inherited Part 1 terms.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r03
Control ID: P1-SD03
Current source: Part 1 - Guardrail and Failure-Mode Register - Issue 1.docx | sha16 794360cc1ff16519
Permitted use: Upstream comparator, localisation, source-lock, and anti-inflation guardrails.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r04
Control ID: P1-SD04
Current source: Part 1 - Bibliography and Relation Register - Issue 1.docx | sha16 7b0b194c1552979b
Permitted use: Upstream bibliographic relation-control reference only; no citation transfer into Part 3.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r05
Control ID: P2-SD01
Current source: Part 2 - Concept Compression Map - Issue 1.docx | sha16 eee99287e2cfaa10
Permitted use: Upstream control for RRP, signal, OP/OA/OR/RAS/RSD, knowledge, intelligence, observation, abstraction, scale, and observation-program architecture.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r06
Control ID: P2-SD02
Current source: Part 2 - Glossary - Issue 1.docx | sha16 b144e7dc2eac7133
Permitted use: Upstream controlled vocabulary for inherited informational and observational terms.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r07
Control ID: P2-SD03
Current source: Part 2 - Guardrail and Failure-Mode Register - Issue 1.docx | sha16 f955341321f11d30
Permitted use: Upstream failure-control for local locus, information/signal, observation, abstraction, scale, and descriptor discipline.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r08
Control ID: P2-SD04
Current source: Part 2 - Bibliography and Relation Register - Issue 1.docx | sha16 12dc458d0e940e8c
Permitted use: Upstream bibliographic relation-control reference only; no citation transfer into Part 3.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t03-r09
Control ID: Protocol
Current source: Historical reference: GOT - Bibliographic Identification Classification and Adjacency Discovery Protocol - Issue 1(1).docx | sha16 03dec29bfa52830c
Permitted use: 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


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t04

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t04-r01
Control ID: P3-SD01
Current control file: Concept Compression Map - Issue 1.docx | sha16 874e44c76caf3061
Permitted use: Architecture compression and source-discipline control.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t04-r02
Control ID: P3-SD02
Current control file: Glossary - Issue 1.docx | sha16 8e0c4e96367405e7
Permitted use: Controlled vocabulary and canonical-home cross-check.



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. Severity classes


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t05

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t05-r01
Class: Class A - Mechanical inconsistency
Meaning: Breaks the architecture.
Examples: Redefining upstream terms downstream; treating every cause as Power; role as provenance; method-compliance as closure; carrier as warrant.
Required response: Correct before finalisation.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t05-r02
Class: Class B - Terminology drift
Meaning: Creates ambiguity or future misuse.
Examples: Using horizon without availability/closure demand; Power without CIF/locus; Responsibility without attribution target; Trust without closure demand; formalisation without consequence trigger.
Required response: Correct before compression or publication.

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t05-r03
Class: Class C - Presentation ambiguity
Meaning: May mislead despite intact architecture.
Examples: “Unknown” sounds blank; “power” sounds authority; “responsibility” sounds blame; “trust” sounds moral virtue; “constitutional” sounds immutable; “audit” sounds certification.
Required response: Clarify through ownership note, discriminator, residual, or diagnostic question.



2. Cross-Part and cross-section failures


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t06

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r01
Failure mode: Source-lock drift
Error: Superseded papers/support wording or unverified material re-enters as current Part 3 source.
Correction: Return to eight current paper hashes and listed controls.
Severity: A
Diagnostic: Can every technical claim be traced to a current canonical paper or permitted upstream control?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r02
Failure mode: Canonical ownership drift
Error: A support document or later paper silently redefines an earlier canonical term.
Correction: Return the definition to the owning paper; use downstream content only as alignment pressure.
Severity: A
Diagnostic: Which paper owns the discriminator?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r03
Failure mode: Section back-propagation
Error: 3b or 3c vocabulary is pre-installed into 3a because it later proves compatible.
Correction: Preserve directional inheritance; revise upstream only for actual inconsistency in its owned relation.
Severity: A
Diagnostic: Would the upstream paper still state the relation without the later vocabulary?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r04
Failure mode: Inheritance by repetition
Error: Repeated citation or use across papers is treated as Indexed Inheritance.
Correction: Keep citation, comparator, dependency, and inheritance separate.
Severity: A
Diagnostic: Has a separate inheritance audit promoted the relation?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r05
Failure mode: Locus drift
Error: Target, carrier, observer, affected locus, applying locus, and responsible locus are silently merged.
Correction: Re-index the relation at each material transformation.
Severity: A
Diagnostic: For whom/what does the claimed relation hold here?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t06-r06
Failure mode: Scale/horizon drift
Error: A claim travels across scale or horizon without preserving its comparator and access conditions.
Correction: Restate reference scale/horizon and show a valid bridge.
Severity: B
Diagnostic: What changed when the claim moved?



3. Section 3a failure modes


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t07

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r01
Failure mode: Horizon objectification
Error: A horizon is treated as a place, object, metaphysical zone, or fixed edge.
Correction: Restore the availability/closure boundary relation.
Severity: A
Diagnostic: What relation, locus, availability condition, and closure demand produce the boundary?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r02
Failure mode: Gödel inflation
Error: Any uncertainty, difficulty, ignorance, or limitation is labelled a Gödel Horizon.
Correction: Require available/formulable relation plus disclosed failure of closure from the present regime’s own resources.
Severity: A
Diagnostic: Is the closure failure actually internal to the stated regime and demand?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r03
Failure mode: Procedural overclaim
Error: A describable experiment, proof path, evidence path, or process is treated as if realised.
Correction: Mark Procedural Availability Horizon and withhold closure until the path exists.
Severity: A
Diagnostic: Can the required path actually be executed by the locus?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r04
Failure mode: Soft-Horizon reification
Error: Provisional closure travels as final warrant.
Correction: Carry residual, scope, comparator/tolerance, purpose, and update with the closure.
Severity: A
Diagnostic: What remains unresolved and what would force update?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r05
Failure mode: Unknown flattening
Error: All unresolved relation becomes one generic unknown.
Correction: Type unknown-status by availability and closure condition.
Severity: B
Diagnostic: Is the relation unavailable, unrecognised, misclosed, residual, live, weighted, or action-bound?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r06
Failure mode: Residual laundering
Error: Residual is mentioned but allowed to do no limiting work.
Correction: State what stronger claim is blocked and what update would change it.
Severity: A
Diagnostic: Does the residual change claim-strength or action limits?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r07
Failure mode: Live-field equality
Error: All live formulations are treated as equally supported because final closure is absent.
Correction: Weight heterogeneously and retain positive exclusions.
Severity: B
Diagnostic: What evidence/comparator/scale support differentiates them?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r08
Failure mode: BAF closure inflation
Error: Best Available Formulation is treated as final truth.
Correction: Retain its purpose type, residual, alternatives, and update conditions.
Severity: A
Diagnostic: What stronger closure demand remains unmet?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r09
Failure mode: Action-certainty conversion
Error: Action taken under threshold is later narrated as proof or truth.
Correction: Separate action threshold from truth/explanatory closure; preserve branch-memory.
Severity: A
Diagnostic: Would the claim have been equally strong if no action had been required?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t07-r10
Failure mode: Stabilisation hindsight
Error: Realised outcome erases what alternatives were live or knowable beforehand.
Correction: Preserve contemporaneous live field, exclusions, and update history.
Severity: B
Diagnostic: What was actually available to the locus at the time?



4. Section 3b failure modes - Power


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t08

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r01
Failure mode: Cause-to-Power collapse
Error: Any causal contribution is called Power.
Correction: Require IPL-localised distinction-conditioned branch potential under comparator pressure.
Severity: A
Diagnostic: Would the branch field differ because this organisation can make a discrimination operative?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r02
Failure mode: Power-as-force
Error: Energetic magnitude or visible effect substitutes for the discriminator.
Correction: Separate causal magnitude from distinction-conditioned potential.
Severity: A
Diagnostic: Is organised discrimination doing the branch-changing work?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r03
Failure mode: Power-as-authority
Error: Role, office, command, status, permission, or possession is treated as primitive Power.
Correction: Recover the physically supported CIF of the specified locus.
Severity: A
Diagnostic: What branches are actually included by the locus’s organisation?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r04
Failure mode: Imagined-CIF inflation
Error: Exterior analyst imagination populates the CIF with unrealised but physically unsupported futures.
Correction: Include only branches supported by the IPL under stated conditions.
Severity: A
Diagnostic: What physical path makes each claimed branch available?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r05
Failure mode: Potential/application collapse
Error: Possessing a power potential is treated as equivalent to present application or consequence.
Correction: Keep potential, application, and consequence distinct.
Severity: B
Diagnostic: Which part of the relation is currently established?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r06
Failure mode: CE agency inflation
Error: Counterfactual Exclusion is read as conscious choice, rejection, or metaphysical deletion.
Correction: Restore it as the negative side of a realised distinction-conditioned branch event.
Severity: B
Diagnostic: Was a relevant included alternative simply not equivalently realised?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t08-r07
Failure mode: Thermodynamic escape
Error: Branch-changing power is treated as abstract information unconstrained by physical work/entropy.
Correction: Retain physical carriers and lawful thermodynamic accounting.
Severity: A
Diagnostic: What substrate and energetic pathway carry the distinction and transition?



5. Section 3b failure modes - Responsibility


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t09

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r01
Failure mode: Causation-to-Responsibility collapse
Error: Every cause becomes Responsibility.
Correction: Follow only the distinction-conditioned subset of causal provenance.
Severity: A
Diagnostic: What local discrimination/organisation did consequential work?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r02
Failure mode: Blame inflation
Error: Primitive Responsibility is treated as blame, guilt, desert, duty, or legal liability.
Correction: Keep mature warrant regimes downstream of primitive attribution.
Severity: A
Diagnostic: Is the claim causal-attributional or normative/allocative?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r03
Failure mode: Provenance transfer
Error: Responsibility is treated as a token passed from one locus to another.
Correction: Localise each material transformation; provenance composes but does not simply transfer.
Severity: A
Diagnostic: What did each locus actually transform, retain, apply, maintain, or update?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r04
Failure mode: Proximity shortcut
Error: Nearest physical actor is assigned the whole responsibility path.
Correction: Recover upstream and downstream distinction-conditioned transformations.
Severity: A
Diagnostic: Which earlier conditions remained materially operative?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r05
Failure mode: Upstream absorption
Error: An early contributor is made responsible for all later consequences.
Correction: Test whether later loci corrected, replaced, ignored, or transformed the relation.
Severity: A
Diagnostic: Did the upstream distinction remain operative in the later branch?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r06
Failure mode: Exterior hindsight attribution
Error: Evaluator uses information unavailable to the locus at the time.
Correction: Apply the Immediate-Frame Principle.
Severity: A
Diagnostic: Was the relevant relation materially available or recoverable then?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r07
Failure mode: Interior frame laundering
Error: A capable locus retrospectively narrows its stated frame to exclude warnings or alternatives that were actually available.
Correction: Reconstruct frame from recoverable paths, not self-description alone.
Severity: A
Diagnostic: What channels, records, warnings, or correction paths existed?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r08
Failure mode: Warrant-as-provenance
Error: Role, duty, liability, answerability, or institutional allocation is treated as causal provenance.
Correction: Keep Responsibility Warrant separate and explicitly related to provenance.
Severity: A
Diagnostic: What does the warrant allocate, and what causal path does it not establish?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t09-r09
Failure mode: Gradient moralisation
Error: Responsibility Gradient becomes a universal moral score.
Correction: Keep it ordinal/relational and tied to capacity plus actual provenance.
Severity: B
Diagnostic: Is the gradient describing capacity or allocating blame?



6. Section 3b failure modes - Trust


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t10

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r01
Failure mode: Trust-as-certainty
Error: Reliance closure is narrated as proof, confidence without residual, or total transparency.
Correction: Restore residual, threshold, and update.
Severity: A
Diagnostic: What remains unaudited while reliance proceeds?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r02
Failure mode: Trust-carrier reification
Error: Carrier is treated as trust ground because it bears a credential, role, record, or institutional mark.
Correction: Recover the closure process the carrier is standing in for.
Severity: A
Diagnostic: What work did the carrier actually earn?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r03
Failure mode: Trust laundering
Error: Reliance-strength earned in one relation is spent in another.
Correction: Re-index relation, carrier, closure demand, residual, and scope.
Severity: A
Diagnostic: What changed between the relation that earned trust and the relation now relying on it?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r04
Failure mode: Borrowed-closure warrant transfer
Error: Vicarious trust is treated as automatic transfer of warrant or Responsibility Provenance.
Correction: Keep outsourced closure, reliance, and provenance distinct.
Severity: A
Diagnostic: What is merely relied upon versus causally attributable?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r05
Failure mode: Audit/trust opposition
Error: Audit is treated as evidence that trust has failed, or trust as elimination of audit.
Correction: Treat audit as the reopening function that preserves corrigibility.
Severity: B
Diagnostic: What condition should foreground the backgrounded relation again?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r06
Failure mode: Repair by reassurance
Error: Trust repair is asserted by apology, branding, certification, or reassurance without changing the failed relation.
Correction: Recover and alter the failure-generating conditions; narrow/refuse trust if needed.
Severity: A
Diagnostic: What changed in the carrier, process, safeguard, or update path?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r07
Failure mode: Unshared-comparator authority
Error: A locus is preferred for one relation using success on another relation, scale, horizon, or closure demand.
Correction: Recover the shared target relation and comparable closure demand, availability, abstraction, scale, and horizon (3b-5 §8).
Severity: A
Diagnostic: Does the demonstrated advantage concern the relation and use now claimed?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r08
Failure mode: Confidence as epistemic standing
Error: Confidence, precision, quick closure, or reduced expressed doubt is taken as demonstrated epistemic advantage.
Correction: Test relation-preservation and the treatment of residual; no single numerical uncertainty measure is required (3b-5 §8).
Severity: A
Diagnostic: Could the apparently weaker contribution be exposing residual that the confident one conceals?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r09
Failure mode: Relative advantage as sufficient closure
Error: The stronger of two contributions is treated as adequate for a use that neither can support.
Correction: Retain the closure demand and residual limits; actionability cannot replace demonstration (3b-5 §8).
Severity: A
Diagnostic: Is the advantage sufficient for this reliance, or only for further inquiry?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r10
Failure mode: Carrier-path loss of advantage
Error: Standing at the contributing locus is assumed to survive a stale record, altered abstraction, or misleading interface.
Correction: Recover both the target relation and the carrier relation for present use (3b-5 §8; 3c-8 §6).
Severity: A
Diagnostic: What epistemic advantage actually reaches the relying locus?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r11
Failure mode: Recognition as epistemic ground
Error: A contribution acquires supposed standing merely because it is trusted, adopted, or used.
Correction: Separate earned standing from actual reliance. Trust makes standing operative but does not create it (3b-5 §8).
Severity: A
Diagnostic: Would the demonstrated standing remain if the contribution were untrusted or unused?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r12
Failure mode: Authority-type substitution
Error: Structural permission is treated as epistemic standing, or epistemic standing as permission to act or decide.
Correction: Apply the two definitions in 3b-5 §8 independently; retain scoped authorisation and demonstrated relation-preservation.
Severity: A
Diagnostic: Which authority is established, and what would establish the other?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t10-r13
Failure mode: Consequence as epistemic warrant
Error: The occurrence or magnitude of an effect retrospectively establishes the epistemic standing of the relied-upon contribution.
Correction: Apply the Power discriminator to the branch difference and the Epistemic Authority discriminator to standing (3b-5 §8).
Severity: A
Diagnostic: What demonstrated the relation-preserving advantage before consequence was used to validate it?



7. Section 3c failure modes - Formalisation


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t11

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r01
Failure mode: Universal formalisation
Error: All language is forced into rigid formal structure.
Correction: Apply formalisation only where language/output becomes load-bearing and proportionate to consequence.
Severity: B
Diagnostic: What consequential work triggers the formalisation burden?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r02
Failure mode: Form-completion closure
Error: Completed fields/forms are treated as proof that the relation is preserved.
Correction: Audit the relation and paths, not packet completion.
Severity: A
Diagnostic: Could every field be filled while the target relation remains wrong?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r03
Failure mode: Machine execution laundering
Error: Automation or consistency is treated as repair of upstream under-specification.
Correction: Recover training/data/model/interface/decision paths and unresolved abstractions.
Severity: A
Diagnostic: What relation did the machine actually preserve?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r04
Failure mode: Record-as-warrant
Error: A retained record or documented provenance is treated as epistemic warrant by default.
Correction: Separate record/provenance from adequacy and closure.
Severity: A
Diagnostic: What comparator or evidence shows the record preserves the claimed relation?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r05
Failure mode: Epistemic-debt concealment
Error: Deferred grounding burden is hidden behind stable terminology or process.
Correction: Make debt visible as missing relation/path/update obligations.
Severity: B
Diagnostic: What grounding work has been postponed?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r06
Failure mode: Retrospective outcome bias
Error: Good outcome is treated as evidence the original decision path was strong.
Correction: Audit decision quality under the information and conditions available at decision time.
Severity: A
Diagnostic: Would the path still be judged strong under a different outcome?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t11-r07
Failure mode: Authorisation-path substitution
Error: The mandate governing a claim’s use substitutes for the evidence path that supports its epistemic standing.
Correction: Keep structural authorisation and epistemic grounding separately recoverable (3c-6 §1; 3b-5 §8).
Severity: A
Diagnostic: Does permission to use the claim establish why its target relation is preserved?



8. Section 3c failure modes - Governance


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t12

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r01
Failure mode: Adoption-as-validation
Error: Institutional uptake or implementation scale is treated as evidence the method is correct.
Correction: Keep operational adoption distinct from epistemic authority.
Severity: A
Diagnostic: What relation-preservation was demonstrated independently of adoption?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r02
Failure mode: Custodial-authority inflation
Error: Stewardship of releases/archives is treated as ownership of epistemic validity.
Correction: Treat custody as an application of Structural Authority; recover release and correction records without promoting stewardship into epistemic standing (3c-7 §6; 3b-5 §8).
Severity: A
Diagnostic: Could a steward be wrong while remaining the steward?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r03
Failure mode: Operational-authority inflation
Error: Institutional authority to apply the method becomes authority to redefine it epistemically.
Correction: Treat domain authority as an application of Structural Authority; distinguish scoped permission from the epistemic amendment burden (3c-7 §§6–7).
Severity: A
Diagnostic: Is this an application decision or a technical/constitutional revision?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r04
Failure mode: Preference amendment
Error: Method changes because of convenience, vote, politics, adoption pressure, or author preference.
Correction: Require demonstrated relational failure and comparative improvement.
Severity: A
Diagnostic: What relation does the current formulation fail to preserve?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r05
Failure mode: Founding-text ownership
Error: Originating author/text is treated as immune from correction.
Correction: Preserve provenance but deny epistemic ownership.
Severity: A
Diagnostic: Would a demonstrated counterexample force revision regardless of authorship?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r06
Failure mode: Constitutional-label capture
Error: The highest-level label is used to block challenge.
Correction: Raise the burden of revision, not immunity to revision.
Severity: A
Diagnostic: What would count as demonstrated failure of the proposed constitutional element?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r07
Failure mode: Fork-as-truth
Error: Existence or popularity of a competing fork is treated as evidence of superiority.
Correction: Compare relation-preservation, residual, scope, and failure conditions.
Severity: B
Diagnostic: What does the fork preserve better and at what cost?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t12-r08
Failure mode: Certification closure
Error: Certificate becomes general epistemic ground beyond what was assessed.
Correction: Bound certification to assessed relation, scope, residual, and re-audit conditions.
Severity: A
Diagnostic: What exactly was certified, and what was not?



9. Section 3c failure modes - Integrated Method


TABLE got-v1-part-3-support-guardrail-and-failure-mode-register-t13

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r01
Failure mode: Method universalisation
Error: Epistemic Method is used as a substitute for science, law, ethics, judgement, or domain expertise.
Correction: Use it as relational audit discipline only.
Severity: A
Diagnostic: What domain-specific burden remains external to the method?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r02
Failure mode: Method-compliance closure
Error: Method-use or completion is treated as epistemic certificate.
Correction: Return strength to demonstrated relation-preservation.
Severity: A
Diagnostic: What claim would remain weak even after perfect procedural compliance?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r03
Failure mode: Path flattening
Error: Claim path, evidence path, record path, carrier path, and reliance path are collapsed.
Correction: Recover each load-bearing path separately.
Severity: A
Diagnostic: Where did content, evidence, record, authority, and reliance each enter?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r04
Failure mode: Claim/reliance-strength collapse
Error: A strong claim is assumed equally safe to rely upon for every locus/purpose, or vice versa.
Correction: Index reliance to the relying locus’s closure demand and limit.
Severity: A
Diagnostic: Does the reliance purpose require more than the claim itself establishes?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r05
Failure mode: Conditional-path universalisation
Error: CIF/CE or Responsibility Provenance fields are required for claims that do not engage Power/Responsibility.
Correction: Activate relation-specific audits only when the claim triggers them.
Severity: B
Diagnostic: What relation-specific claim is being made?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r06
Failure mode: Audit paralysis
Error: Residual is used to prevent all finite action.
Correction: Permit action under threshold with proportionate safeguards and update where justified.
Severity: B
Diagnostic: What action burden exists despite incomplete closure?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r07
Failure mode: Audit theatre
Error: Visible review process substitutes for discriminatory comparator pressure or correction.
Correction: Require actual potential to expose error, weaken claims, refuse closure, or force update.
Severity: A
Diagnostic: Can the audit produce a materially adverse result for the claim?

RECORD got-v1-part-3-support-guardrail-and-failure-mode-register-t13-r08
Failure mode: Preferential-reliance shortcut
Error: Comparison favours another locus without establishing the advantage for the shared relation and closure demand or its survival through the carrier.
Correction: Apply the comparator burden where preferential reliance is claimed (3c-8 §6), inheriting 3b-5 §8.
Severity: A
Diagnostic: What advantage supports this reliance at the receiving locus?



10. Final release test

• Every major term is traceable to a current canonical paper or permitted upstream control.

• 3a/3b/3c directional inheritance is preserved.

• Power claims recover IPL/CIF and do not collapse into causation, force, or authority.

• Responsibility claims separate Provenance from Warrant and respect Immediate Frame.

• Trust claims retain carrier, closure demand, residual, threshold, audit, safeguard where material, and update.

• Formalisation remains proportional and packet-completion does not become closure.

• Epistemic and Structural Authority remain defined in 3b-5 §8 <https://goto-go.com/machine/documents/got-v1-3b-5/#got-v1-3b-5-h-8>. Governance applies that distinction to custodial and operational authority in 3c-7 §6 <https://goto-go.com/machine/documents/got-v1-3c-7/#got-v1-3c-7-h-6> and retains amendment by demonstrated relation-preservation.

• Paper 3c-8 <https://goto-go.com/machine/documents/got-v1-3c-8/> remains an integration/audit layer rather than a route for redefining Papers 3a-1 <https://goto-go.com/machine/documents/got-v1-3a-1/>–3c-7 <https://goto-go.com/machine/documents/got-v1-3c-7/>.

• Any later source edit triggers fresh hash and downstream support reconciliation.