Guardrail and Failure-Mode Register got-v1-part-1-support-guardrail-and-failure-mode-register | Support document | Issue 1 https://goto-go.com/machine/documents/got-v1-part-1-support-guardrail-and-failure-mode-register/ Guardrail and Failure-Mode Register Part 1: On the Origin of Life | Failure-control support document | source-locked | Issue 1 TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t01 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r01 Control field: Document ID Value: OOL-P1-SD03-GUARDRAIL RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r02 Control field: Version / issue Value: Issue 1 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r03 Control field: Date Value: 2026-09-22 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r04 Control field: Status Value: Final failure-control support document for Part 1 Issue 1, source-locked to the finalised three-paper set (GOT-V1-1-1 / GOT-V1-1-2 / GOT-V1-1-3), the fixed literal primary-paper heading locators, and final SD-01. Secondary to canonical papers. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r05 Control field: Supersedes Value: Earlier Issue 1 source-lock and numbering-aligned working states. This final Issue 1 release locks the failure-control register to the paper-complete Part 1 source set and final SD-01; no new guardrail or technical concept is introduced. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r06 Control field: Function Value: Records conceptual guardrails, failure modes, severity classes, corrections, and diagnostic questions for Part 1: On the Origin of Life. No new concepts are introduced. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r07 Control field: Canonical rule Value: Primary papers govern technical definitions. Paper 1 defines the life discriminator; Paper 2 defines life attribution; Paper 3 defines the attribution procedure. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r08 Control field: Source-lock rule Value: Use only the finalised three current Part 1 primary papers and the current SD-01 Concept Compression Map Issue 1 as support-control reference. Primary-paper internal references must use the current literal heading locator map; cited locators omit the terminal display full stop. Do not import exported full-series TEM papers, older EDT files, earlier drafts, superseded support maps, superseded support documents, or prior generated answers as conceptual source material. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t01-r09 Control field: Template rule Value: The old Guardrail and Failure-Mode Register document was used for formatting, table pattern, severity-class pattern, and release-control structure only. It is not a conceptual source for this Issue 1 revision. 1. Purpose and governing rule This document records the main conceptual guardrails for Part 1: On the Origin of Life. Its purpose is to prevent drift as the three primary papers are compressed, applied to edge cases, converted into templates, and extended into later work. It protects the architecture from pancomputational overreach, chemistry-only audit collapse, life inflation, matter-state collapse, container collapse, activity collapse, dependence shortcuts, lineage shortcuts, replication shortcuts, potential inflation, dormancy-potential confusion, death-as-class error, closure-output misuse, topology shortcuts, positive-exclusion/residual confusion, procedure inflation, false equivalence, and residual laundering. Primary guardrail: do not let a familiar biological noun, visible matter-state boundary, activity level, dependency relation, lineage label, topology descriptor, or uncertainty label replace the discriminator conditions that earn life-status, attribution, continuity, class, topology, positive exclusion, closure output, or residual. 0.1 Source-lock register TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t02 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t02-r01 Seq.: Paper 1 Latest source file: GOT-V1-1-1 - On the Origin of Life - Issue 1.docx | sha16 b46a62c660223454 Canonical paper: On the Origin of Life Canonical ownership / use: Physical grounding; pancomputation discipline; Trivial Computation; Non-Trivial Computation; Nested Multiscale Framework; evaluation conditions; readout and temporal framing; Baseline Dynamics; Information Processing Locus; Driven Thermodynamic System; life as driven thermodynamic constraint-maintenance supported by IPL-mediated NTC; physics-chemistry-life transition. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t02-r02 Seq.: Paper 2 Latest source file: GOT-V1-1-2 - The Identification of Life - Issue 1.docx | sha16 0f1f564c3786f208 Canonical paper: The Identification of Life Canonical ownership / use: Attribution architecture; candidate frame; reference-indexed attribution; informational regime; life-realisation; maintained boundary; Attribution Locus; DTS completion; organisational identity; intrinsic resumability; potential informational throughput; throughput identity; continuity status; death as branch-closure; closure output; post-death constituent reframing; positive exclusion; residual deferral; relationship topology; formal ladder. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t02-r03 Seq.: Paper 3 Latest source file: GOT-V1-1-3 - The Life Attribution Procedure - Issue 1.docx | sha16 6c6d2b60203198e8 Canonical paper: The Life Attribution Procedure Canonical ownership / use: Diagnostic sequence; reference preflight; candidate framing; life-realisation threshold; Attribution Locus localisation; DTS-completion localisation; identity and continuity determination; primary class assignment or residual deferral; topology assignment; residual inventory and update statement; standard attribution output; closure output form; audit template; exemplar desktop studies; cross-case findings; guardrails and failure modes. TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t03 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t03-r01 Control ID: SD-01 Latest control file: Concept Compression Map - Issue 1.docx | sha16 a256c5229849f993 Permitted use: Architecture compression and support-stack alignment for the finalised source set. Secondary to the primary papers. Template-source use: the prior version of this support document was used for formatting, table pattern, section hierarchy, and release-control structure only. It is not a conceptual source for this Issue 1 revision. Excluded source class: exported full-series TEM papers and concepts, older project files, earlier EDT documents, superseded support-map wording, superseded support-document wording, and prior generated answers are not conceptual sources for this Issue 1 support set. 2. Canonical ownership guardrail Rule: Paper 1 defines the life threshold; Paper 2 defines attribution; Paper 3 defines procedure. A support document may name and compress concepts, but it must not silently move canonical ownership. TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t04 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r01 Architecture region: Physical grounding, NMF, TC/NTC, BD, IPL, DTS Canonical home: Paper 1 Guardrail: Do not redefine computation, NTC, Baseline Dynamics, IPL, DTS, or life in attribution or procedure documents. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r02 Architecture region: Life threshold and physics-chemistry-life transition Canonical home: Paper 1 Guardrail: Do not treat life as complexity, metabolism, reproduction, feedback, adaptation, persistence, lineage, familiarity, intelligence, or NTC alone. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r03 Architecture region: Attribution architecture Canonical home: Paper 2 Guardrail: Do not assign life to the first named object, visible container, or familiar biological noun without Attribution Locus analysis. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r04 Architecture region: Identity, continuity, potential throughput, death/closure, and ladder Canonical home: Paper 2 Guardrail: Do not collapse dormancy, Life-in-Potential, terminal active Life, death/closure, reconstruction, incorporation, Complex Chemistry, and residual into one binary. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r05 Architecture region: Relationship topology Canonical home: Paper 2 Guardrail: Do not let parasite, symbiont, organelle, tumour, scaffold, artificial, or host-dependent label decide primary life-status. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r06 Architecture region: Diagnostic procedure and audit output Canonical home: Paper 3 Guardrail: Do not turn the procedure into the phenomenon or reduce it to a checklist of traits. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t04-r07 Architecture region: Residual inventory and update conditions Canonical home: Paper 3 Guardrail: Do not hide uncertainty inside a verdict; localise the missing discriminator and state the update condition. 3. Severity classes TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t05 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t05-r01 Class: Class A - Mechanical inconsistency Meaning: Breaks the architecture. Examples: Redefining life; treating TC as NTC; assigning Life without IPL-mediated NTC; making death a fourth class; calling reconstruction survival; bypassing Attribution Locus localisation; using uncertainty as a hidden class. Required response: Correct before finalisation. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t05-r02 Class: Class B - Terminology drift Meaning: Creates ambiguity or future misuse. Examples: Using information without regime/throughput; treating dependence as verdict; topology as class; potential as weak life; dormant as merely inactive; maintained-locus wording where final Attribution Locus wording is required. Required response: Correct before compression or publication. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t05-r03 Class: Class C - Presentation ambiguity Meaning: May mislead despite intact architecture. Examples: Procedure sounds mechanical; residual sounds explanatory; support document sounds canonical; examples sound universal rather than reference-indexed; positive exclusion sounds like uncertainty. Required response: Clarify through wording, heading, ownership note, residual statement, or update condition. 4. Master guardrail table TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t06 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r01 Failure mode: Source-lock drift Error: Exported full-series TEM concepts re-enter the split life stack as conceptual sources. Correction: Remove imported material; use old documents only as templates; return to the finalised three primary life papers and SD-01 Issue 1. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r02 Failure mode: Canonical ownership drift Error: A support document becomes a source of technical redefinition. Correction: Return the term to its canonical home; mark support text as compression only. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r03 Failure mode: Redescription collapse Error: TC is treated as NTC, or computational mapping is treated as life. Correction: Require physically enacted discrimination, organisation mediation, downstream dependence, and BD comparator pressure. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r04 Failure mode: NTC inflation Error: Any counterfactual discrimination is treated as Life. Correction: Restore the stricter life condition: driven thermodynamic constraint-maintenance supported by IPL-mediated NTC. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r05 Failure mode: Chemistry-only audit collapse Error: Chemistry is treated as sufficient to audit life-status without the discriminator question. Correction: Preserve physical and chemical continuity, but require assessment of distinction-conditioned driven constraint-maintenance. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r06 Failure mode: Comparator weakness Error: The life or NTC claim survives only because the comparator is vague. Correction: Construct adequate BD-family comparator preserving boundary context, driving, inventory, scale, horizon, and noise assumptions. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r07 Failure mode: IPL vagueness Error: Outcome dependence is attributed to the whole system, environment, or external interpreter without localising the mediating organisation. Correction: Identify what must remain intact, or be ablated, for the distinction to do downstream work. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r08 Failure mode: Life inflation Error: Informational, computational, adaptive, reproductive, or biologically familiar systems are treated as alive. Correction: Require life-realising driven constraint-maintenance through IPL-mediated NTC. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r09 Failure mode: Matter-state collapse Error: Membrane, body, capsid, genome, organ, or biological material is treated as final discriminator. Correction: Move from familiar matter-state barrier to informational regime identification. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r10 Failure mode: Container collapse Error: Life inside a frame is treated as Life of the frame. Correction: Localise the Attribution Locus before primary class assignment. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r11 Failure mode: Attribution Locus bypass Error: The output assigns class before identifying whose regime is being classified. Correction: Localise the bearer of active, dormant, potential, closed, reconstructed, incorporated, excluded, or residual-bearing relation. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r12 Failure mode: Activity collapse Error: Visible metabolism, motion, growth, or reproduction is treated as necessary or sufficient for Life. Correction: Distinguish active Life, dormant Life, terminal active Life, Life-in-Potential, and closure/death. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r13 Failure mode: Dependence shortcut Error: Dependence is treated as automatic non-life or automatic unity. Correction: Decompose resource dependence, scaffolded support, constitutive dependence, host completion, and coupled completion. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r14 Failure mode: Lineage shortcut Error: Descent, copying, or sequence preservation is treated as present life-status. Correction: Use lineage only after organisational identity or throughput identity has been established. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r15 Failure mode: Replication shortcut Error: Replication or reproductive participation is treated as sufficient for Life. Correction: Require life-realisation at the Attribution Locus; host-completed propagation may support Life-in-Potential, not free-phase Life. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r16 Failure mode: Potential inflation Error: Any stored sequence, biological material, trigger, or reconstructable record is treated as Life-in-Potential. Correction: Require identity-bearing potential informational throughput into admissible extrinsic life-realising completion. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r17 Failure mode: Dormancy-potential confusion Error: Intrinsic resumability is confused with extrinsic completion potential. Correction: Preserve dormant Life as Life where intrinsic same-locus resumability remains open. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r18 Failure mode: Terminal-life confusion Error: Terminal phase is treated as death merely because long-term continuation is unlikely. Correction: Classify terminal active Life until branch-realisation closes for the target locus. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r19 Failure mode: Death-as-class error Error: Death is entered into the primary ladder as a fourth class. Correction: Use closure output for closed continuity of a formerly living target locus. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r20 Failure mode: Death overextension Error: Death of a target locus is spread to every constituent inside the former system. Correction: Apply post-death constituent reframing; classify living subloci, potential candidates, and chemistry separately. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r21 Failure mode: Closure-output misuse Error: Closure output is applied to material that was never the formerly living target locus. Correction: Use closure only for formerly living target loci; reframe remnants separately. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r22 Failure mode: Reconstruction-as-survival error Error: Later reconstruction is treated as same-locus return. Correction: Distinguish reconstruction after continuity failure from intrinsic resumption. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r23 Failure mode: Incorporation-as-survival error Error: Material incorporation into another living regime is treated as survival of the prior locus. Correction: Classify incorporation as cross-locus descriptor, not continuity. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r24 Failure mode: Functional sublocus inflation Error: An indispensable component is treated as a living locus at the claimed scale. Correction: Require its own maintained boundary, driven regime, operative distinction, and continuity relation. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r25 Failure mode: Topology shortcut Error: Parasitic, symbiotic, organelle, tumour, artificial, or scaffolded relation becomes the verdict. Correction: Assign topology only after primary class and continuity status are established. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r26 Failure mode: Positive-exclusion confusion Error: A relation that is positively excluded under stated conditions is softened into vague uncertainty. Correction: State positive exclusion where warranted; carry residual only where a discriminator condition remains incomplete. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r27 Failure mode: Residual laundering Error: Unresolved discriminator conditions are converted into explanation or hidden in a familiar class. Correction: State residual locally, inventory the missing condition, and specify update conditions. Severity: A RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r28 Failure mode: False equivalence Error: All unresolved possibilities are treated as equally live. Correction: Preserve discriminator support, strength markers, and update conditions. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r29 Failure mode: False precision Error: A weak audit is made precise by notation or output form. Correction: State strength marker and residual; do not let the form overstate support. Severity: B RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t06-r30 Failure mode: Procedure inflation Error: The diagnostic procedure is treated as an additional life theory. Correction: Separate canon from application; procedure preserves relation order but does not redefine life. Severity: B 5. Diagnostic spine When a term, claim, model, example, or support document appears to drift, apply the following diagnostic sequence: TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t07 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r01 Step: 1 Diagnostic question: What is the candidate frame? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r02 Step: 2 Diagnostic question: What are the reference boundary, focal scale, interface, operational horizon, driving conditions, and discrimination/noise regime? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r03 Step: 3 Diagnostic question: Is the claim testing the Paper 1 life threshold, the Paper 2 attribution relation, or the Paper 3 procedure? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r04 Step: 4 Diagnostic question: Is there a driven constraint-bearing regime? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r05 Step: 5 Diagnostic question: Which distinctions are operative, and what organisation makes downstream outcomes depend on them? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r06 Step: 6 Diagnostic question: What BD-family comparator tests the claimed dependence? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r07 Step: 7 Diagnostic question: Where is the Information Processing Locus? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r08 Step: 8 Diagnostic question: Does life-realisation occur inside the frame? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r09 Step: 9 Diagnostic question: Whose Attribution Locus carries the realised, intrinsically resumable, potential, closed, reconstructed, incorporated, positively excluded, or residual-bearing relation? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r10 Step: 10 Diagnostic question: Where is DTS completion: intrinsic, resource-dependent, scaffolded, constitutively dependent, host-completed, coupled, or no further same-locus completion after closure? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r11 Step: 11 Diagnostic question: What identity relation is preserved: organisational identity, intrinsic resumability, throughput identity, lineage identity, reconstruction, incorporation, or none? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r12 Step: 12 Diagnostic question: Which continuity status is warranted: active, dormant, terminal active, potential, closed, or uncertain with residual? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r13 Step: 13 Diagnostic question: Which primary class is warranted: Complex Chemistry, Life-in-Potential, Life, or primary-class deferral? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r14 Step: 14 Diagnostic question: Is any tested relation positively excluded under the stated reference conditions? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r15 Step: 15 Diagnostic question: What topology modifier follows after attribution? RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t07-r16 Step: 16 Diagnostic question: What residual remains, what inventory type is it, and what would force update? 6. Architecture-specific guardrails TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t08 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r01 Region: TC / NTC Failure risk: Treating lawful redescribability as physically enacted discrimination. Required correction: Require discriminable distinction, organisation-mediated downstream dependence, and BD-family ablation, scrambling, reset, neutralisation, or bypass-control. Compression: Description is not discrimination. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r02 Region: NMF Failure risk: Treating layers as new substances or mere conveniences. Required correction: Keep KMB -> BC -> TSS -> thermodynamic information -> EBC -> CTSS/CTS -> DTSS/DTS -> SIT -> NTC as constrained descriptive regimes. Compression: Higher levels are constrained regimes. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r03 Region: BD Failure risk: Using baseline as vague null condition. Required correction: BD must preserve context while disabling the organisation under test. Compression: BD is disciplined contrast. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r04 Region: IPL Failure risk: Attributing life-relevant computation without localising what does the distinction-conditioned work. Required correction: Identify the organisation whose integrity is required for downstream dependence. Compression: IPL says where the distinction does work. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r05 Region: Life discriminator Failure risk: Treating Life as NTC, self-organisation, metabolism, reproduction, adaptation, or persistence alone. Required correction: Require a DTS whose constraint-maintenance depends on IPL-mediated NTC. Compression: Life is stricter than NTC. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r06 Region: Physics-chemistry-life transition Failure risk: Treating life as leaving chemistry or as only chemistry. Required correction: Keep physical and chemical continuity while adding the discriminator required to audit life-status. Compression: Life is an emergent audit layer. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r07 Region: Candidate frame Failure risk: Treating the first named object as the answer. Required correction: Treat the frame as provisional and correct it by informational regime, boundary, completion, and continuity. Compression: The frame opens the inquiry. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r08 Region: Positive exclusion Failure risk: Using uncertainty language where a relation is negatively warranted under stated conditions. Required correction: State the relation as positively excluded under the stated frame; use residual only for incomplete conditions. Compression: Exclusion is not residual. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r09 Region: Informational regime Failure risk: Treating externally readable content as identity-bearing throughput. Required correction: Require distinctions physically carried by the candidate relation and available to realise, resume, complete, or close a regime. Compression: Information must belong to the regime. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r10 Region: Maintained boundary Failure risk: Treating visible enclosure as identity. Required correction: Ask whether the boundary participates in preserving identity-bearing throughput. Compression: Boundary is not identity. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r11 Region: Attribution Locus Failure risk: Attributing life to broad container or indispensable component. Required correction: Localise the operational unit whose regime is realised, resumed, completed, potentialised, closed, reconstructed, incorporated, excluded, or residual-bearing. Compression: Attribution needs a bearer. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r12 Region: DTS completion Failure risk: Treating dependence as binary independence/dependence. Required correction: Separate resource dependence, scaffolded support, constitutive dependence, host completion, coupled completion, and no further same-locus DTS completion after closure. Compression: Dependence is an attribution variable. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r13 Region: Continuity Failure risk: Confusing organisational identity, intrinsic resumability, throughput identity, lineage, reconstruction, and incorporation. Required correction: Assign the correct continuity relation before class. Compression: Continuity determines branch status. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r14 Region: Formal ladder Failure risk: Adding death as a fourth class or treating Life-in-Potential as weak Life. Required correction: Keep the ladder as Complex Chemistry / Life-in-Potential / Life; death is closure output / continuity status. Compression: Ladder gives class; continuity gives status. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r15 Region: Closure output Failure risk: Using closure output as a replacement primary class or applying it to all remnants. Required correction: Use only for closed continuity of a formerly living target locus and trigger constituent reframing. Compression: Closure is target-locus death. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r16 Region: Topology Failure risk: Using parasite, symbiont, organelle, tumour, or artificial support as primary classification. Required correction: Assign topology after locus, completion, continuity, and class. Compression: Topology follows attribution. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r17 Region: Procedure Failure risk: Turning the diagnostic sequence into a checklist of independent traits. Required correction: Preserve dependency order and field separation. Compression: Procedure protects canon. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t08-r18 Region: Residual inventory Failure risk: Leaving uncertainty vague or using unresolved as a hidden field value. Required correction: Inventory the missing condition and state update conditions. Compression: Residual localises uncertainty. 7. Edge-case guardrails TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t09 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r01 Edge case: Dormant seed, spore, cyst, cryopreserved bacterium Do not infer: Do not infer non-life from low activity. Audit requirement: Test intrinsic resumability in the same Attribution Locus and viability evidence. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r02 Edge case: Terminal organism Do not infer: Do not infer death from terminality or reserve depletion. Audit requirement: Classify terminal active Life until branch-realisation closes for the target locus. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r03 Edge case: Free intact virion-like particle Do not infer: Do not infer Life from sequence or non-life from free-phase inactivity alone. Audit requirement: Test identity-bearing potential throughput into admissible host-completed DTS pathway. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r04 Edge case: Productive infection and lysis Do not infer: Do not assign one status to the whole scene. Audit requirement: Split host-cell closure, released candidate potential throughput, and non-identity-bearing debris. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r05 Edge case: Host-dependent parasite Do not infer: Do not infer non-life from dependence. Audit requirement: Localise parasite Attribution Locus and DTS-completion relation. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r06 Edge case: Organ, tissue, or perfused support case Do not infer: Do not infer organismal Life from living cells or artificial support. Audit requirement: Separate cellular loci, tissue-level relation, scaffolded support, and residual. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r07 Edge case: Mitochondrion or organelle Do not infer: Do not infer status from lineage or organelle name. Audit requirement: Separate functional sublocus, constitutive dependence, maintained organisation, and residual. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r08 Edge case: Corpse or post-death remains Do not infer: Do not spread organismal death to every constituent. Audit requirement: Use closure output for the target locus and perform constituent reframing. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r09 Edge case: Artificial or hybrid system Do not infer: Do not infer life from engineering or deny life from artificial support. Audit requirement: Test whether the candidate itself is the Attribution Locus of driven constraint-maintenance supported by IPL-mediated NTC. RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t09-r10 Edge case: Protocell or origin-of-life model Do not infer: Do not infer Life from chemistry, compartment, replication, or catalysis alone. Audit requirement: Ask whether chemical organisation has crossed into distinction-conditioned maintenance of its own driven regime. 8. Change log TABLE got-v1-part-1-support-guardrail-and-failure-mode-register-t10 RECORD got-v1-part-1-support-guardrail-and-failure-mode-register-t10-r01 Issue: Issue 1 Date: 2026-09-22 Change: Final Issue 1 source-lock release aligned to the fixed literal heading locators, the recorded final filenames and hashes for GOT-V1-1-1, GOT-V1-1-2, and GOT-V1-1-3, and final SD-01. Existing failure controls remain source-supported; no new concepts are introduced. Authority: Finalised source-locked Part 1 primary/support set, Issue 1. 9. Release/revision checklist • Does every guardrail preserve canonical ownership? • Does the document block TC/NTC collapse and NTC/life inflation? • Does the document preserve BD comparator and IPL localisation discipline? • Does it keep chemistry physically continuous with life while preventing chemistry-only audit collapse? • Does it use Attribution Locus for attribution-bearing relation rather than relying on a visible container? • Does it keep Life-in-Potential narrow and distinct from dormancy, reconstruction, and ordinary potential? • Does it keep death out of the primary ladder and route target-locus death through closure output? • Does it separate positive exclusion, uncertain field carried in residual, and classification with residual? • Does every residual require an inventory type and update condition? • Does the document avoid importing exported full-series TEM material or superseded support wording as conceptual source?