Guardrail and Failure-Mode Register got-v1-part-2-support-guardrail-and-failure-mode-register | Support document | Issue 1 https://goto-go.com/machine/documents/got-v1-part-2-support-guardrail-and-failure-mode-register/ Guardrail and Failure-Mode Register Part 2 (2a-2b): Informational Architecture; Knowledge, Intelligence, and Observation | Issue 1 TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t01 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r01 Control field: Document ID Value: P2-2A2B-SD03-GUARDRAIL RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r02 Control field: Version / issue Value: Issue 1 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r03 Control field: Date Value: 2026-09-23 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r04 Control field: Status Value: Final Issue 1 support release covering all ten Part 2 canonical papers, including the released Paper 1c scholarly apparatus. Secondary to canonical papers. Exact paper and support file identities are recorded in the release manifest; scholarly scope limits remain explicit. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r05 Control field: Supersedes Value: The preceding Issue 1 copy of this support document and its earlier pre-release inputs. Immediate release input: Part 2 - Guardrail and Failure-Mode Register - Issue 1.docx | sha16 f7f146829f058b20. Earlier source files and release history are retained. This reissue aligns support to the minimally amended Papers 2, 4a and 4c; it makes no further paper edits. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r06 Control field: Function Value: Records Part-level conceptual guardrails, failure modes, severity classes, corrections, and diagnostic questions while preserving distinct Part 2a and Part 2b failure-control regions. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r07 Control field: Canonical rule Value: Canonical primary and extension papers govern technical definitions. Paper 1 owns the RRP architecture; Paper 1a signal; Paper 1b reference-indexed realism and closure; Paper 1c the relational index, embodiment, derived reachability, Relational Form, and propagation; Paper 2 knowledge; Paper 3 intelligence; Paper 4 observation; Paper 4a abstraction and perspective; Paper 4b scale and measurement; Paper 4c the observation-program operational envelope. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r08 Control field: Internal split rule Value: Part 2a and Part 2b remain distinct canonical regions inside one Part-level support control. Part 2b inherits Part 2a architecture; downstream material does not retroactively redefine upstream canonical terms. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r09 Control field: Source-lock rule Value: Use the ten Issue 1 paper identities in 0.1 and the directional support-control chain in 0.2. Part_2_Issue_1_Support_Manifest.json distinguishes recalculated SHA-256 digests from unchanged recorded locks carried forward without byte verification. Historical predecessor locks remain evidence only. Every later saved edit requires rehashing and downstream reconciliation. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t01-r10 Control field: Template rule Value: Retain the consolidated support schema, record IDs and GOT-SFMT-01 visual family. Preserve Paper 1c content and canonical definitions. This reconciliation updates release controls and the limited Paper 1c support alignment; it adds no external publication or independent technical definition. 0. Part-level consolidation and source discipline This clean Issue 1 support reissue reconciles Part 2a and Part 2b with the completed, limited Paper 1c integrations in Papers 2, 4a and 4c. The ten-paper sequence, canonical ownership and internal split are preserved. Source-lock verification and carried-forward limits are distinguished in 0.1. This support pass makes no further primary- or extension-paper edits. The Issue 1 canonical paper sequence is 1, 1a, 1b, 1c, 2, 3, 4, 4a, 4b, 4c. Paper 1c - Relational Form is an attached extension of Paper 1, placed after 1b. The Part 2b sequence remains Knowledge (2), Intelligence (3), Observation (4), Limits (4a), Scale (4b), and Operational Envelope (4c). 0.1 Canonical source register - Issue 1 release lock TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t02 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r01 Seq.: Part 2a / Paper 1 Released source / current and historical locks: GOT-V1-2a-1 - Relative Reference Points - Issue 1.docx Issue 1 SHA-256 (first 16): d786d0683fca89f8 Historical predecessor only: 1. Relative Reference Points P2v8.docx | sha16 36cab03f9d685afb Canonical paper: Relative Reference Points Canonical ownership / use: Reference-indexed informational architecture; Relational Access Principle; RRP and RRP Set; OP, OA, OR, RAS, RSD; local locus discipline; scoped operational information for a locus. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r02 Seq.: Part 2a / Paper 1a Released source / current and historical locks: GOT-V1-2a-1a - From Noise Cometh Signal - Issue 1.docx Issue 1 SHA-256 (first 16): 295caad5ca395d00 Historical predecessor only: 1a. From Noise Cometh Signal - P2v11.docx | sha16 dc80b50275c6ac95 Canonical paper: From Noise Cometh Signal Canonical ownership / use: Physical pathway of availability; variation, preserved contrast, signal, channel-relative discriminability, Locus Event Horizon, signal/information separation, and ingress into OP. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r03 Seq.: Part 2a / Paper 1b Released source / current and historical locks: GOT-V1-2a-1b - Reference-Indexed Realism - Issue 1.docx Issue 1 SHA-256 (first 16): 259f3a4db7bf6aed Historical predecessor only: 1b. Reference Indexed Realism - P2v7.docx | sha16 28306cc5f13cf769 Canonical paper: Reference-Indexed Realism Canonical ownership / use: Reference-indexed realism; broad bounded-registration bridge use; ontological target, finite model, residual, access scaffold, and discipline of closure. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r04 Seq.: Part 2a / Paper 1c Released source / current and historical locks: GOT-V1-2a-1c - Relational Form - Issue 1.docx Issue 1 SHA-256 (first 16): 47757d7fbce15332 Historical lineage: added during the Part 2 support reconciliation; the earlier Draft v3 and Apparatus working copies are superseded release inputs, not current canonical locks. Canonical paper: Relational Form Canonical ownership / use: Relational index; target and locus as local physical cuts; coupling; embodiment of OA-keyed RAS; derived Relational Reachability; Relational Form and physically supported potential; relational propagation; relation before representation. RRP Set primitives remain owned by Paper 1. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r05 Seq.: Part 2b / Paper 2 Released source / current and historical locks: GOT-V1-2b-2 - On the Origin of Knowledge - Issue 1.docx Issue 1 SHA-256 (first 16): 1c8023254b9e9e1c Historical predecessor only: 2. On the Origin of Knowledge - P2v8.docx | sha16 22932c7f9d238909 Canonical paper: On the Origin of Knowledge Canonical ownership / use: Knowledge as retained distinction; RAS as canonical minimal carrier; TK, KIP, NTK; record-status separated from truth, warrant, objectivity, and justification. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r06 Seq.: Part 2b / Paper 3 Released source / current and historical locks: GOT-V1-2b-3 - On the Origin of Intelligence - Issue 1.docx Issue 1 SHA-256 (first 16): 38f1b0e3d69c60e2 Historical predecessor only: 3. On the Origin of Intelligence - P2v5.docx | sha16 30b095be2bf4bde5 Canonical paper: On the Origin of Intelligence Canonical ownership / use: Intelligence as applied distinction; finite branch-space; passive/active information; passive/active intelligence; NTI; provenance, comparator, and locus discipline. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r07 Seq.: Part 2b / Paper 4 Released source / current and historical locks: GOT-V1-2b-4 - On the Origin of Observation - Issue 1.docx Issue 1 SHA-256 (first 16): 183e222a589a6bc4 Historical predecessor only: 4. On the Origin of Observation - P2v8.docx | sha16 6bf3d4081841fd63 Canonical paper: On the Origin of Observation Canonical ownership / use: Observation as bounded registration; OR event; RAS record; Pre-TO, TO, OIP, NTO; observer-locus, Observer, Observer Event Horizon, and record-provenance. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r08 Seq.: Part 2b / Paper 4a Released source / current and historical locks: GOT-V1-2b-4a - The Limits of Observation - Issue 1.docx Issue 1 SHA-256 (first 16): f99af6b8df811fa6 Historical predecessor only: 4a. The Limits of Observation - P2v4.docx | sha16 6783e2a4c2434fdb Canonical paper: The Limits of Observation Canonical ownership / use: Cut, abstraction regime, perspective, event-horizon profile, Abstraction Gap, relational uncertainty, and objectivity as disciplined correction. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r09 Seq.: Part 2b / Paper 4b Released source / current and historical locks: GOT-V1-2b-4b - The Scale of Observation - Issue 1.docx Issue 1 SHA-256 (first 16): 184d8bcc2ca708ea Historical predecessor only: 4b. The Scale of Observation - P2v5.docx | sha16 1113c05ac8df8cce Canonical paper: The Scale of Observation Canonical ownership / use: Scale as stabilised comparability; magnitude, reference scale, operative scale, measurement, Scale Gap, scalar alignment, and scalar objectivity. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t02-r10 Seq.: Part 2b / Paper 4c Released source / current and historical locks: GOT-V1-2b-4c - The Operational Envelope of Observation - Issue 1.docx Issue 1 SHA-256 (first 16): aa383c443babd127 Historical predecessor only: 4c. The Operational Envelope of Observation - P2v9.docx | sha16 02a8f4e8d57e80d5 Canonical paper: The Operational Envelope of Observation Canonical ownership / use: Observation program and descriptor layer; OH, CH, RF, OBW, OD, OG, ODr, OL, OCx; threshold/performance separation and failure localisation. Source identity note: the current first-16 SHA-256 values for Paper 1c and all six Part 2b papers were recalculated from the available DOCX files, using the reissued Papers 2, 4a and 4c. Papers 1, 1a and 1b retain their recorded Issue 1 locks; their bytes and the earlier full manifests were not supplied for this reconciliation. Part_2_Issue_1_Support_Manifest.json records the verified full digests and marks those three retained locks without reconstructing missing digests. Historical predecessor locks and earlier change-log entries remain historical evidence. Paper 1c release alignment: the canonical Issue 1 manuscript contains 21 native endnotes, nine internal series references and six reused external works. Its direct conceptual sources are Papers 1, 1a and 1b; Part 2b references are downstream handoffs. The support stack preserves the manuscript's compositional scope and explicit evidence limits, including endnote 10 on the unsupported Plato attribution. Release identity does not establish that attribution, validate the illustrations empirically, or constitute a new external discovery audit. Bibliographic roles and limits are recorded in SD-04 as the downstream consolidation record, not as an upstream definition or hash dependency. 0.2 Part-level support-control chain TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t03 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t03-r01 Control ID: P2-SD01 Released control file / source lock: Part 2 - Concept Compression Map - Issue 1.docx Issue 1 SHA-256 (first 16): eee99287e2cfaa10 Historical predecessor only: Part 2 (2a-2b) - Informational Architecture and Knowledge Intelligence and Observation - Concept Compression Map - Issue 1.docx | sha16 55c6d7f2e885ce66 Permitted use: Architecture compression and Part-level source-discipline control. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t03-r02 Control ID: P2-SD02 Released control file / source lock: Part 2 - Glossary - Issue 1.docx Issue 1 SHA-256 (first 16): b144e7dc2eac7133 Historical predecessor only: Part 2 (2a-2b) - Informational Architecture and Knowledge Intelligence and Observation - Series Master Glossary - Issue 1.docx | sha16 b56df66b7bab72f5 Permitted use: Controlled vocabulary and canonical-home cross-check. Inherited Part 1 support controls remain limited to the uses already permitted by the source documents: NTC, BD, IPL, comparator/localisation discipline, and support-document template/control practice. Part 1 life-attribution classes are not imported into Part 2 statuses. Excluded source class: superseded Part 2 paper revisions; separate pre-release Part 2a/Part 2b support wording where it conflicts with current canonical papers or this consolidated control path; exported full-series TEM material; future Part 3 unknown-handling procedures except explicit handoff; prior generated answers; and unverified or unadmitted external material. Bibliographic apparatus does not create technical inheritance or move canonical ownership. 0.3 Internal subdivision map Part 2a - Informational Architecture: Papers 1, 1a, 1b, and 1c. Part 2b - Knowledge, Intelligence, and Observation: Papers 2, 3, 4, 4a, 4b, and 4c. The internal sections below retain the pre-release subpart support architecture under this single Part-level control. Part 2a - Informational Architecture Internal Part 2a support section. Papers 1, 1a, 1b, and 1c govern this region. Part 2b terms may appear only as downstream handoff unless the source text explicitly marks a broader bridge use. 1. Purpose and governing rule This document records the main conceptual guardrails for Part 2a: Informational Architecture (From Substrate to Phenomenology). It protects the four canonical papers - Paper 1 and attached extensions 1a, 1b, and 1c - as they are compressed, cross-indexed, applied, and carried into the Part 2b support region. It protects the architecture from pan-informational attribution, information-scope collapse, signal inflation, persistence-stage inflation, persistent-state/RAS collapse, external-interpreter substitution, locus drift, RRP subjectivism, empty constructivism, naive possession, signal-as-semantics error, Shannon overextension, Locus Event Horizon overreading, target/model collapse, residual laundering, and premature closure. Paper 1c adds controls against index/Form/model collapse, embodiment-stage inflation, ingress/reachability collapse, unsupported potential, semantic transfer, and target-related error being mistaken for a true target property. Primary guardrail: do not let physical difference, physical persistence, propagation, residue, preserved contrast, external describability, measurement output, model success, observer interpretation, or realism-language replace the discriminator conditions that earn RRP-indexed informational availability for a locus, signal status, RRP Set status, indexed reality-claim, target/model adequacy, or closure. Do not use the scoped RRP definition to revoke other legitimate informational regimes. 2. Canonical ownership guardrail Rule: Paper 1 defines the informational architecture and scoped operational information for a locus; Paper 1a defines the physical pathway of availability; Paper 1b defines reference-indexed realism and closure; Paper 1c gives the physical account of relational index, embodiment, derived reachability, Form, and propagation. Support compression must not move that ownership or add a primitive. Paper 1c does not replace the Part 2b technical status ladders. TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t04 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r01 Architecture region: Informational architecture, RRP, OP, OA, OR, RAS, RSD Canonical home: Paper 1 Guardrail: Do not redefine information for a locus, RRP, OP, OA, OR, RAS, or RSD in signal, realism, glossary, guardrail, or later Part 2b documents; do not turn the scoped RRP definition into a universal revocation of other information disciplines. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r02 Architecture region: Physical pathway into availability Canonical home: Paper 1a Guardrail: Do not treat signal, physical persistence, propagation, residue, channel-discriminability, or the Locus Event Horizon as independent replacement definitions for RRP-indexed information. Persistence, propagation, and residue are not structural stages. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r03 Architecture region: Reference-indexed realism and closure discipline Canonical home: Paper 1b Guardrail: Do not treat support compression as complete ontology, broad observation as unmediated certainty, or any finite model as a substitute for target/model/residual analysis. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r04 Architecture region: Relational index, embodiment, reachability, Form, and propagation Canonical home: Paper 1c, headings 1-5 and 7.1 Guardrail: Keep the physical index, local target/locus, primitive RAS, embodiment, derived formation capacity, distributed Form, finite model, and residual distinct. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r05 Architecture region: Knowledge, intelligence, and technical observation status terms Canonical home: Part 2b handoff Guardrail: Do not assign Part 2b statuses inside Part 2a. Preserve Paper 1b broad observation-as-bounded-registration language only as realism-facing bridge use. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t04-r06 Architecture region: Support-document compression and support-stack alignment Canonical home: SD-01 Guardrail: Do not treat support documents as canonical redefinitions. Primary papers govern technical use. 3. Severity classes TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t05 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t05-r01 Class: Class A - Mechanical inconsistency Meaning: Breaks the architecture. Examples: Calling all difference RRP-indexed information; treating all signal as information for the evaluated locus; treating persistence or residue as RAS; making RRP subjective; collapsing target into model; hiding residual inside closure. Required response: Correct before finalisation. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t05-r02 Class: Class B - Terminology drift Meaning: Creates ambiguity or future misuse. Examples: Using information without its regime or locus; using signal without preserved contrast; using locus without specifying the evaluated relation; using realism without target/model/residual; using broad observation as the technical Part 2b status. Required response: Correct before compression or publication. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t05-r03 Class: Class C - Presentation ambiguity Meaning: May mislead despite intact architecture. Examples: Event horizon sounds like metaphysical edge; residual sounds like failure; relative sounds like arbitrary; support document sounds canonical. Required response: Clarify through wording, heading, ownership note, residual statement, or diagnostic question. 4. Master guardrail table TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t06 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r01 Failure mode: Source-lock drift Error: Part 2b papers, later observation papers, older drafts, exported TEM material, or prior generated answers re-enter Part 2a as conceptual sources. Correction: Return to the four supplied Part 2a files in 0.1 and SD-01 as support control only. Paper 1c is an authorised source addition; historical P2 filenames and sha16 values are not current release locks. Severity: A RECORD got-v1-part-2-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-2-support-guardrail-and-failure-mode-register-t06-r03 Failure mode: Part 2b import drift Error: Knowledge, intelligence, or technical observation status ladders are used to define Part 2a concepts. Correction: Treat Part 2b statuses as downstream handoff only; preserve Paper 1b broad observation-as-bounded-registration use without importing the later status ladder. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r04 Failure mode: Pan-informational collapse Error: Every physical difference is treated as RRP-indexed information for the evaluated locus because it exists, persists, differs, or can be described. Correction: Require RRP-indexed availability as operational distinction for the specified locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r05 Failure mode: External-interpreter substitution Error: A relation is attributed to the system because an external analyst can describe or use it. Correction: Specify the evaluated locus and show availability, classing, registration, retention, or redeployment for that locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r06 Failure mode: RRP subjectivism Error: RRP-relative is read as subjective, arbitrary, or mind-created. Correction: Restore the realist guardrail: the relation is relative, the constraint is real. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r07 Failure mode: RRP absolutism Error: A distinction available to one locus is treated as universally available. Correction: Specify locus, interface, scale, horizon, discrimination regime, abstraction, and path conditions. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r08 Failure mode: Locus drift Error: The explanatory work moves silently between source, carrier, receiver, user, institution, environment, and analyst. Correction: Use local locus discipline; redraw the locus only when the evaluated relation changes and state the transfer. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r09 Failure mode: OP inflation Error: A persistent or propagating physical state, residue, or merely possible contrast is treated as OP before availability at an interface is shown. Correction: Require available contrast for a specified locus under reference conditions. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r10 Failure mode: OA omission Error: Available contrast is treated as registerable without a classing regime. Correction: Identify the abstraction or partition that makes alternatives same/different, signal/noise, present/absent, or within/outside tolerance. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r11 Failure mode: OR inflation Error: Perturbation, coupling, physical persistence, or state change is treated as registration. Correction: Require selection of one OP-supported, OA-classed alternative into state. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r12 Failure mode: RAS inflation Error: Any persistent physical state, mark, memory-like condition, archive, or residue is treated as RAS. Correction: Require an OA-keyed, OR-produced retained token over the specified horizon and scale. Paper 1c, heading 6 permits table-local RAS only when the local OP/OA/OR relation is established; persistence alone is not enough. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r13 Failure mode: RSD inflation Error: Any downstream effect is treated as redeployment. Correction: Require later transition, inference, action, control, correction, or branch-realisation to depend on the retained distinction. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r14 Failure mode: Signal primitive error Error: Signal is treated as the primitive ground of all information. Correction: Begin below signal: interaction produces variation; variation may persist, propagate, or leave residue; signal begins only where contrast is preserved through a medium under possible discrimination conditions. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r15 Failure mode: Signal inflation Error: Every interaction, variation, persistent state, propagation, residue, or transmission is treated as signal. Correction: Require preserved contrast through a medium under possible discrimination conditions. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r16 Failure mode: Information inflation from signal Error: Every signal-bearing contrast is treated as RRP-indexed information for the evaluated locus. Correction: Require the contrast to become available as distinction for that locus under RRP conditions. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r17 Failure mode: Information-scope collapse Error: The RRP definition of information for a locus is treated as revoking thermodynamic, statistical, physical, Shannon, or other legitimate informational regimes. Correction: Restore scope: those regimes retain their own conditions; RRP asks the further question of operational availability within the evaluated relation. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r18 Failure mode: Persistence/propagation stage inflation Error: Persistence, propagation, or residue is reintroduced as an independent stage between variation and signal or between registration and retained state. Correction: Treat them as physical properties. Signal begins at preserved contrast; RAS begins at an OA-keyed, OR-produced state retained over the relevant horizon. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r19 Failure mode: Shannon overextension Error: SIT is treated as the complete theory of information. Correction: Keep SIT to channel-relative uncertainty, coding, noise, symbols, bits, and transmission under specified conditions; preserve the further RRP availability question. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r20 Failure mode: Semantic signal error Error: Signal is treated as content, message, or meaning by itself. Correction: Return to physical preserved contrast; semantic content requires later regimes of classing, retention, and redeployment. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r21 Failure mode: Locus Event Horizon overread Error: The Locus Event Horizon is read as an edge of reality, absolute unknowability, or black-hole physics literalism. Correction: Define it as ingress-boundary of possible relation for a finite locus under a regime. Severity: C RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r22 Failure mode: Event horizon/profile confusion Error: Locus Event Horizon is confused with later Observer Event Horizon or operational performance descriptors. Correction: Use Locus Event Horizon for pre-OP ingress. Paper 1c Relational Reachability concerns formation; the Observer Event Horizon is a downstream facet name, while OH is a program-performance limit. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r23 Failure mode: Naive possession Error: A measurement, record, model, or observer is treated as possessing the target whole. Correction: Restore the access scaffold: finite loci encounter reality through boundary, interface, channel, threshold, scale, abstraction, registration, retention, and possible redeployment. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r24 Failure mode: Empty constructivism Error: Because access is indexed, the target is treated as constructed by the observer. Correction: Restore target constraint. Mediation does not create the target by itself. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r25 Failure mode: Sceptical collapse Error: Because access is mediated, no model is treated as reality-tracking. Correction: Restore corrigible modelling: mediation is not unreality; models vary in fidelity, range, resilience, and residual. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r26 Failure mode: Unindexed realism Error: A claim asks whether something is real without specifying real as what, for what locus, access relation, scale, horizon, comparator, and residual. Correction: Index the realism claim before closing it. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r27 Failure mode: Real/unreal flattening Error: Everything consequential is called real in the same way. Correction: Index the respect: real as experience, risk, institutional force, model, absence, fiction, error condition, etc. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r28 Failure mode: Target/model collapse Error: A finite model, record, category, or measurement is treated as the ontological target itself. Correction: Separate target, access scaffold, finite model, and residual. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r29 Failure mode: Residual laundering Error: Unresolved remainder is hidden inside confidence, closure, or broad realism-language. Correction: State the residual and its update condition; do not convert it into a verdict. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r30 Failure mode: Premature closure Error: The claim closes beyond what access, comparator, scale, horizon, and residual discipline warrant. Correction: Weaken the claim; carry residual forward; identify what would update the closure. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r31 Failure mode: Reference-index / relational-index collapse Error: The finite reference conditions of a claim are treated as the whole physical relational index, or the index is treated as an observer inventory. Correction: Keep the RRP reference node and claim index distinct from the wider physical relations within which targets and loci occur (Paper 1c, headings 1.1-1.3). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r32 Failure mode: Index / Form collapse Error: Every antecedent physical relation is treated as part of the Relational Form of the selected target distinction. Correction: The index includes deeper relations that need not track that distinction; Form is the target-tracking structure (Paper 1c, headings 1.2 and 7.1). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r33 Failure mode: Embodiment-stage inflation Error: Embodiment is inserted after RAS as a new primitive, further retention test, or stronger information status. Correction: Treat embodiment as the physical description already entailed by OA-keyed retention; RAS remains primitive (Paper 1c, heading 2.3). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r34 Failure mode: Coupling / completed-content error Error: Coupling is described as copying a relation already completed wholly within either target or locus. Correction: Their histories condition interaction, but the coupling produces a new local relation (Paper 1c, heading 2.1). Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r35 Failure mode: Ingress / reachability collapse Error: Access to an object, carrier, or signal is assumed to make every target-relative relation formable. Correction: Separate incoming contrast from the organisation needed to stabilise the particular relation (Paper 1c, heading 2.4). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r36 Failure mode: Absolute unreachability Error: A relation not presently formable for one locus is called unreal, impossible for every locus, or permanently inaccessible. Correction: Index reachability to locus, regime, history, scaffold, and horizon; identify physically supported conditions that could change it (Paper 1c, heading 2.4). Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r37 Failure mode: Unsupported constructive reach Error: An imagined sequence of concepts or tools is treated as a physically available scaffold. Correction: Require the supported intermediate couplings and changes of organisation; mere conceivability is not enough (Paper 1c, heading 2.4). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r38 Failure mode: Form / finite-model possession Error: A finite model, one carrier, one observer, or one accessible subset is identified with the whole Relational Form. Correction: Keep ontological extent, locally reachable subset, finite abstraction, and residual separate (Paper 1c, headings 3.1 and 5.2). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r39 Failure mode: Potential / actual-instance collapse Error: Physically supported future instantiation is treated as an already present object or a disembodied ideal template. Correction: Potential must be causally organised; a later instance is not present as a hidden miniature (Paper 1c, headings 3.3-3.4). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r40 Failure mode: Representation-first requirement Error: Relation, classed registration, or retention is denied unless a carrier intentionally or semantically stands for its target. Correction: Relation and earned embodiment can precede representation; standing-for is a later relation (Paper 1c, heading 4.1). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r41 Failure mode: Intact semantic transfer Error: Meaning or a completed concept is treated as moving unchanged across carriers and receiving loci. Correction: Trace selective physical preservation and the receiving organisation's own classing and reconstruction (Paper 1c, heading 4.2). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r42 Failure mode: Provenance / preservation collapse Error: A distinction is inferred from a trace merely because it occurred somewhere in that trace's causal history. Correction: Distinguish contrast preserved, contrast lost in transformation, and difference that never entered the path; the kettle-brand and sock-colour cases are different (Paper 1c, heading 6). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r43 Failure mode: Form / truth collapse Error: Every target-related retained state is treated as an accurate target property, or all erroneous relations are excluded from the physical Form. Correction: Separate physical reality of relation from adequacy of target-tracking; conflict and error can be retained without becoming true target properties (Paper 1c, heading 4.3). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r44 Failure mode: Distributed Form / locus collapse Error: Distribution across carriers is assumed to establish one integrated operative locus. Correction: Localise each access and deployment claim separately; no distributed locus follows from Form alone (Paper 1c, heading 7.1). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t06-r45 Failure mode: Relational Form / RF collision Error: Relational Form is shortened to RF and confused with Registration Fidelity. Correction: Write Relational Form in full. RF remains the Paper 4c reliability descriptor (Paper 4c, heading 3.1). Severity: B The added Paper 1c failure controls use the existing A/B/C severity scheme as support classifications. The source paper supplies the substantive distinctions; it does not supply new bibliographic audit codes or a separate severity taxonomy. 5. Diagnostic spine When a term, claim, model, example, or support document appears to drift, apply the following diagnostic sequence: TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t07 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r01 Step: 1 Diagnostic task: Check source and canonical home. Question: Is the term owned by Paper 1, 1a, 1b, 1c, or by a stated downstream Part 2b paper? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r02 Step: 2 Diagnostic task: Identify the target difference or relation. Question: What physical difference, contrast, target relation, model, or realism claim is at issue? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r03 Step: 3 Diagnostic task: Specify the RRP. Question: For what locus, through what interface, at what scale, over what horizon, under what discrimination/noise and abstraction regime? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r04 Step: 4 Diagnostic task: Locate physical pathway status. Question: Is this interaction, variation, persistence/propagation/residue as a physical property, preserved or signal-bearing contrast, channel-discriminable contrast, or available distinction? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r05 Step: 5 Diagnostic task: Audit RRP Set status. Question: Are OP, OA, OR, RAS, and any RSD established for the specified locus? Is embodiment merely describing an earned RAS, rather than upgrading persistence? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r06 Step: 6 Diagnostic task: Protect locus discipline. Question: Has the claim silently moved from source to carrier, from carrier to user, from system to analyst, or from one locus to another? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r07 Step: 7 Diagnostic task: Index the realism claim. Question: What are the target, access scaffold, finite model, comparator, and residual? Where relevant, how do the wider index and distributed Form differ from the locally reachable subset? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r08 Step: 8 Diagnostic task: Assign closure only where warranted. Question: Does the claim close under the stated reference conditions, or must it remain residual-bearing? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r09 Step: 9 Diagnostic task: Hand off Part 2b statuses only when earned. Question: Do not call retained distinction knowledge, applied distinction intelligence, or bounded registration the completed technical observation status unless downstream conditions are invoked explicitly. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r10 Step: 10 Diagnostic task: Separate ingress from formation. Question: Can the carrier enter while the target relation remains unreachable? What actual organisation or scaffold supports immediate or constructible reach? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r11 Step: 11 Diagnostic task: Trace selective propagation. Question: Which distinction survived, which was lost, and which never coupled into the path? Has the receiver earned its own registration and any retention? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t07-r12 Step: 12 Diagnostic task: Check Form and adequacy. Question: Is the Form confused with a complete model, all causal history, a true-only set, a present potential instance, or a single operative locus? 6. Architecture-specific guardrails TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t08 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r01 Guardrail: Difference-to-information ladder Instruction: Preserve the sequence: interaction produces physical variation; variation may persist, propagate, or leave residue without creating a new informational stage; variation may become signal-bearing where contrast is preserved; signal-bearing contrast may become channel-discriminable; channel-discriminable contrast may become RRP-indexed information for a locus; available distinction may enter OP, OA, OR, RAS, and RSD. Do not skip stages. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r02 Guardrail: RRP-indexed claim first Instruction: No RRP-indexed information, record, model, or realism claim is well-formed until the reference node and reference conditions are specified strongly enough for the claim being made. Other informational regimes remain governed by their own conditions. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r03 Guardrail: Signal physicality Instruction: Signal is a physical mediation of possible relation. It is not semantic content, not the source whole, and not primitive information. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r04 Guardrail: Event horizon discipline Instruction: Use Locus Event Horizon only as the ingress-boundary of possible relation before OP is established for a locus under a regime. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r05 Guardrail: Realist double guardrail Instruction: Reality is not created by the locus. Reality is not possessed whole by the locus. Both sides must remain visible. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r06 Guardrail: Target/model/residual discipline Instruction: Every realism-facing compression should keep ontological target, finite model, access scaffold, and residual separate. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r07 Guardrail: Primitive / derived separation Instruction: RRP/OP/OA/OR/RAS/RSD remain the primitive architecture. Embodiment is an operational description, reachability a derived formation condition, and Form a higher-scale target-tracking structure (Paper 1c, heading 7.1). RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r08 Guardrail: Table-local RAS and later uptake Instruction: The hot-cup case is conditional on local OP/OA/OR and retention. A later observer does not confer an already earned RAS; later uptake is a new relation and does not make the table NTC (Paper 1c, heading 6). RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r09 Guardrail: Reachability and dynamic residual Instruction: Preserve immediate versus constructible reach, supported scaffolding, and the possibility of change in regime. Unestablished reach is carried as residual, not converted to an absolute verdict (Paper 1c, headings 2.4 and 5.2). RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t08-r10 Guardrail: Propagation and representation Instruction: Continuity is selective and causally grounded. Later representation remains answerable to what the path preserved and what the receiver can stabilise (Paper 1c, headings 4.1-4.3). 7. Handoff guardrails for Part 2b TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t09 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t09-r01 Boundary: Knowledge handoff Instruction: Part 2a can say that RAS prepares retained distinction. It should not assign full knowledge-status unless the Part 2b knowledge ladder is invoked. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t09-r02 Boundary: Intelligence handoff Instruction: Part 2a can say that RSD prepares redeployment and branch-realisation. It should not assign intelligence-status unless applied distinction and downstream trajectory selection are evaluated. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t09-r03 Boundary: Observation handoff Instruction: Paper 1b uses bounded registration broadly and Paper 1c supplies physical grounding. Neither replaces Paper 4 technical TO/OIP/NTO, observer-locus, or Observer conditions. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t09-r04 Boundary: Abstraction/scale handoff Instruction: Paper 1c treats physically supported OA, embodiment, and derived reachability. The observation-specific cut/perspective account, scalar measurement, and operational performance retain their homes in Papers 4a, 4b, and 4c. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t09-r05 Boundary: Reachability / deployability handoff Instruction: Do not use relation formation to certify KIP, OIP, realised RSD, OH, or CH. Each downstream condition requires its own locus, pathway, and discriminator. 8. Change log TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t10 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t10-r01 Issue: Issue 1 Date: 2026-08-08 Change: Revised Issue 1 source lock to Papers 1 P2v8, 1a P2v11, and 1b P2v7 and the updated SD-01 Issue 1; preserves scoped-information failure control, non-stage treatment of persistence/propagation/residue, and broad-versus-technical observation separation. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t10-r02 Issue: Issue 1 support - Pass 1 Date: 2026-09-23 Change: Integrated Paper 1c with fifteen Part 2a failure controls, downstream cross-facet checks, and conditional hot-cup/RAS treatment. Preserved existing severity classes, historical change record, original rows and canonical thresholds; final release hashes remain pending. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t10-r03 Issue: Issue 1 - final release Date: 2026-09-23 Change: Bound the register to the final ten-paper baseline, including the apparatus-bearing Paper 1c, and to released SD-01 and SD-02. Replaced obsolete absent-apparatus and pending-release controls with current locks and carried evidence limits. Existing failure modes, corrections and severity classes remain intact. 9. Release/revision checklist Does every guardrail preserve canonical ownership among Papers 1, 1a, 1b, and 1c, with Paper 1 as parent and the extension letters intact? Does the document block physical-difference/information collapse? Does it block variation/persistence/signal/RRP-indexed-information collapse and preserve other legitimate information regimes? Does it preserve OP, OA, OR, RAS, and RSD as separate discriminator stages? Does it preserve local locus discipline and prevent external-interpreter substitution? Does it keep RRP-relative distinct from subjective, arbitrary, or constructivist? Does it treat Locus Event Horizon as an ingress-boundary rather than an edge of reality or performance descriptor? Does it preserve target/model/residual discipline and prevent premature closure? Does it prevent Part 2b statuses from being imported into Part 2a definitions and exclude older drafts, exported TEM material, and prior generated answers as conceptual sources? Paper 1c release check: are primitive versus derived status, ingress versus formation, potential versus instance, selective propagation, target-related error, and the Relational Form / RF distinction explicit? Part 2b - Knowledge, Intelligence, and Observation Internal Part 2b support section. Papers 2, 3, 4, 4a, 4b, and 4c govern this region and inherit the Part 2a informational architecture. All paper-number references in this section use the current sequential numbering. 1. Purpose and governing rule This register prevents familiar mental nouns, epistemic compliments, successful outcomes, useful constraints, visible records, measurement numbers, perspective language, scale labels, or performance descriptors from replacing the discriminator conditions that earn Part 2b statuses and evaluations. It protects the architecture from knowledge-belief and knowledge-truth collapse; information/intelligence and provenance/use collapse; observation-certificate and interaction collapse; record/observer collapse; abstraction and perspective misreadings; magnitude/scale and reference/operative-scale collapse; threshold/performance collapse; descriptor inflation; locus drift; comparator weakness; source drift; and residual laundering. The Paper 1c alignment also blocks embodiment/provenance collapse, reachability/deployability collapse, and distributed Form being treated as an Observer. Primary guardrail: preserve the ordered distinctions among access, registration, retention, grounded deployability, realised redeployment, applied branch-dependence, bounded observation, abstraction, scalar comparability, program performance, correction, and warrant. Where a discriminator or bound is not established, weaken the claim and state the missing condition. 2. Canonical ownership guardrail TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t11 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r01 Architecture region: Inherited access architecture Canonical home: Part 2a Guardrail: Do not redefine RRP, OP, OA, OR, RAS, RSD, signal, or target/model/residual. Paper 1c physical and derived relations are support cross-checks, not new Part 2b threshold requirements. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r02 Architecture region: Knowledge threshold and ladder Canonical home: Paper 2 Guardrail: Do not redefine knowledge as belief, semantic possession, truth, justification, usefulness, or conscious awareness. Do not collapse TK, KIP, and NTK. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r03 Architecture region: Intelligence threshold and provenance/use ladder Canonical home: Paper 3 Guardrail: Do not define intelligence by cognition, usefulness, success, complexity, or resemblance. Active-information provenance belongs to the producing locus, not the later encounter. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r04 Architecture region: Observation threshold, ladder, and observer-status Canonical home: Paper 4 Guardrail: Do not define observation as every interaction, signal reception, trace, memory, measurement, knowledge, intelligence, or warrant. Do not collapse record, observer-locus, and Observer. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r05 Architecture region: Abstraction, perspective, uncertainty, and objectivity Canonical home: Paper 4a Guardrail: Do not treat abstraction as failure or unreality, perspective as opinion, Abstraction Gap as error, or objectivity as consensus or view-from-nowhere. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r06 Architecture region: Scale, measurement, and scalar objectivity Canonical home: Paper 4b Guardrail: Do not reduce scale to size, unit, choice, or precision; do not collapse physical magnitude, reference scale, operative scale, or Scale Gap. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r07 Architecture region: Observation program and descriptor layer Canonical home: Paper 4c Guardrail: Do not grade performance before status, use descriptors as primitives or status substitutes, or turn reach, fidelity, bandwidth, depth, gain, drift, load, or collapse into warrant. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r08 Architecture region: Comparator and localisation control Canonical home: Canonical papers with inherited Part 1 control Guardrail: Use BD-family comparator and IPL/local locus discipline for strong dependence claims; do not import the Part 1 life ladder. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t11-r09 Architecture region: Residual and unknown handoff Canonical home: Part 2a / Part 3 handoff Guardrail: Carry explicit residual and update conditions; do not pretend Part 2b provides the later complete procedure for the unknown. 3. Severity classes TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t12 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t12-r01 Class: Class A - Mechanical inconsistency Meaning: Breaks the architecture. Examples: Redefining a core threshold; assigning active-information provenance to a later encountering locus; calling interaction observation; making any record an Observer; treating magnitude as observer-created; using descriptors to bypass status; hiding residual inside closure. Required response: Correct before finalisation. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t12-r02 Class: Class B - Terminology drift Meaning: Creates ambiguity or future misuse. Examples: Using knowledge without retention; intelligence without application; perspective as viewpoint; scale without reference/operative distinction; OH without separating event horizon or operational horizon; performance terms without bounds. Required response: Correct before compression or publication. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t12-r03 Class: Class C - Presentation ambiguity Meaning: May mislead despite intact architecture. Examples: “Trivial” sounds unimportant; “passive intelligence” sounds inactive; “Observer” sounds conscious; “gap” sounds error; “relative” sounds subjective; “collapse” sounds any failure. Required response: Clarify through wording, canonical-home note, discriminator, residual statement, or diagnostic question. 4. Master guardrail table TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t13 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r01 Failure mode: Source-lock drift Error: Older drafts, superseded support wording, exported TEM material, future Part 3 procedures, or prior generated answers enter as conceptual sources. Correction: Use the six supplied Part 2b papers for facet definitions and the four supplied Part 2a papers for their explicitly scoped architecture and physical-grounding roles. Earlier audits and hashes remain historical; do not infer new dependencies. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r02 Failure mode: Canonical ownership drift Error: A support document becomes a source of technical redefinition. Correction: Return the term to its canonical paper; mark support wording as compression only. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r03 Failure mode: Issue-number drift Error: A bibliography-only source revision is treated as requiring a new conceptual Issue, or a conceptual revision is hidden by retaining the old Issue merely because filenames were preserved. Correction: Keep Issue numbering tied to support-document conceptual scope. Bibliography integration alone may remain Issue 1, but every saved source change must receive a fresh source hash and source-lock reconciliation. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r04 Failure mode: Numbering drift Error: Paper 2/3/4/4a/4b/4c roles are confused or legacy numbering is used without context. Correction: Use the current Part 2b support sequence and preserve each paper title as the canonical locator. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r05 Failure mode: Part 2a inheritance drift Error: Inherited RRP terms are redefined from Part 2b shorthand. Correction: Use Part 2a primary papers and the internal Part 2a support section for inherited architecture; Part 2b only applies the architecture to new facets. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r06 Failure mode: Part 1 import drift Error: Life-attribution classes or closure terms are imported into knowledge, intelligence, or observation statuses. Correction: Use Part 1 support only for NTC, BD, and IPL control; keep life-status separate. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r07 Failure mode: Facet drift Error: Knowledge, intelligence, observation, abstraction, scale, and performance are treated as interchangeable labels. Correction: State the focal question and canonical home before assigning status or descriptor. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r08 Failure mode: Knowledge-belief collapse Error: Minimal knowledge is defined first as belief, assertion, awareness, or justified proposition. Correction: Restore knowledge as retained distinction; treat belief and justification as stronger organisations. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r09 Failure mode: Knowledge-truth collapse Error: A retained record is treated as true, warranted, objective, or justified because it exists or is used. Correction: Separate record-status from truth-status and correction layers. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r10 Failure mode: Persistent-state/RAS collapse Error: Any persistent mark, state, residue, archive, or memory-like condition is treated as RAS. Correction: Require OP, OA, OR, identifiable token-state, reference scale, and operational horizon. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r11 Failure mode: Signal-to-knowledge inflation Error: Signal-bearing contrast is called knowledge without retained registration. Correction: Require an OR-produced RAS retained as present accessible state. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r12 Failure mode: Retention/deployment collapse Error: TK, KIP, and NTK are treated as one condition. Correction: Separate record-presence, grounded consultability, and realised redeployment. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r13 Failure mode: KIP imagination error Error: A record is called deployable because an imagined future observer might use it. Correction: Require a physically or organisationally well-posed consultability pathway for the focal locus. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r14 Failure mode: NTK warrant inflation Error: Realised deployment is treated as truth or justification. Correction: Keep NTK as retained distinction doing work; evaluate target preservation separately. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r15 Failure mode: Intelligence-cognition collapse Error: Intelligence is restricted to consciousness, language, reasoning, self-awareness, or human resemblance. Correction: Restore applied distinction altering downstream trajectory selection for a locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r16 Failure mode: Intelligence-usefulness collapse Error: Any useful structure, regularity, constraint, gradient, or output is called intelligence. Correction: Require application by distinction-conditioned organisation at the evaluated locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r17 Failure mode: Success/resemblance shortcut Error: A system is called intelligent because it succeeds or resembles a human answer. Correction: Test whether branch-realisation depends on the applied distinction under comparator discipline. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r18 Failure mode: Information/intelligence collapse Error: Available or retained distinction is treated as intelligence without present application. Correction: Separate information availability, knowledge retention, and intelligence application. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r19 Failure mode: Passive-information/passive-intelligence collapse Error: Found distinction is called passive intelligence because it helps a locus. Correction: Passive intelligence requires reuse of made distinction; found distinction remains passive information. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r20 Failure mode: Active-information/active-intelligence collapse Error: Made distinction is called active intelligence merely because prior organisation produced it. Correction: Active information is provenance; active intelligence requires current application. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r21 Failure mode: Active-information provenance inversion Error: Made status is assigned by the later locus that encounters or uses the distinction. Correction: Identify the producing locus whose prior distinction-conditioned organisation fixed the form. Later encounter creates access/use, not provenance. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r22 Failure mode: Producer/applicator collapse Error: Producing locus and present applying locus are assumed identical. Correction: Localise provenance and present branch-space separately; they may differ in time, substrate, and organisation. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r23 Failure mode: Producer-extinction error Error: Active-information status is removed because the producing locus no longer exists. Correction: Preserve made provenance while the produced distinction remains physically instantiated under the claim. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r24 Failure mode: Passive-intelligence inactivity error Error: Passive intelligence is read as dormant, inert, or non-operative. Correction: Show the current reuse that alters branch-space without recomputing the original selection problem. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r25 Failure mode: External-interpreter substitution Error: An analyst uses or admires a distinction and attributes intelligence or observation to the target system. Correction: Show the operation claimed for the evaluated locus: application for intelligence; classed registration and retention for observation, with deployability or realised redeployment where the stronger status requires it. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r26 Failure mode: Comparator weakness Error: NTK, NTI, NTO, or OG is claimed without adequate intervention discipline. Correction: Construct a BD-family comparator preserving relevant context or weaken the claim. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r27 Failure mode: IPL/locus vagueness Error: The mediating organisation is diffuse or moves silently between source, carrier, user, environment, institution, and analyst. Correction: Identify what must remain intact or be disabled for the claimed dependence. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r28 Failure mode: Observation-certificate error Error: “Observed” is treated as truth, direct access, epistemic guarantee, or complete target possession. Correction: Restore bounded registration and record-provenance; evaluate warrant through correction and residual. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r29 Failure mode: Observation-interaction collapse Error: Coupling, perturbation, signal reception, physical alteration, or transient tokenisation is treated as observation. Correction: Require OR into a persistent, re-identifiable OA-keyed RAS for TO or above. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r30 Failure mode: Measurement-is-observation shortcut Error: A number or readout is treated as sufficient observation without auditing classing, registration, retention, scale, and locus. Correction: Map the measurement path through RRP, OP, OA, OR, RAS, and where claimed RSD. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r31 Failure mode: Record/observer collapse Error: Any record, archive, log, or record-field is treated as observer-locus. Correction: Require grounded consultability for OIP-status observer-locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r32 Failure mode: observer-locus/Observer collapse Error: Observation-capacity is treated as realised observation. Correction: Require actual RSD-mediated record-operativity and comparator-stable dependence for Observer/NTO. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r33 Failure mode: Distributed-record inflation Error: Distributed records are treated as a distributed Observer without localising integration and redeployment. Correction: Map the observation chain and show grounded consultability and realised dependence at the claimed locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r34 Failure mode: NTO-life collapse Error: NTO or Observer status is treated as sufficient for life. Correction: Keep observation and life thresholds separate; NTO does not entail life. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r35 Failure mode: Observer Event Horizon overread Error: The ingress boundary is treated as an edge of reality or absolute unknowability. Correction: Define it as the present limit of signal-bearing contrast entering OP for the observer-locus. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r36 Failure mode: Abstraction denial Error: Observation is described as raw reception without OA, selection, omission, or compression. Correction: Expose the cut and abstraction regime that make the relation registerable. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r37 Failure mode: Abstraction-as-failure error Error: Any abstraction or omission is treated as falsity or defect. Correction: Treat abstraction as the enabling condition of finite observation; test whether it preserves the relevant relation. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r38 Failure mode: Cut/real collapse Error: The observational cut, category, model, or record is treated as the real whole. Correction: Restore target constraint and model/record incompleteness; carry residual. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r39 Failure mode: Perspective-opinion collapse Error: Perspective is reduced to personal attitude, bias, preference, or subjectivity. Correction: Define perspective as locus-level integration of an abstraction regime and event-horizon profile. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r40 Failure mode: Abstraction Gap/error collapse Error: Abstraction Gap is treated as error by definition. Correction: Reserve error for consequential miscompression; gap is the structural space in which error can arise. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r41 Failure mode: Relational uncertainty globalisation Error: Uncertainty about preservation by one cut is inflated into global scepticism. Correction: Localise the uncertain relation, conditions, comparator, and correction path. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r42 Failure mode: Objectivity-as-view-from-nowhere Error: Objectivity is treated as abstraction-free, perspective-free access. Correction: Use disciplined correction of perspective under constraint. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r43 Failure mode: Objectivity-as-consensus Error: Agreement alone is treated as objectivity. Correction: Require target constraint, comparator pressure, cross-locus correction, and residual discipline. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r44 Failure mode: Scale-size collapse Error: Scale is reduced to physical size. Correction: Use scale as stabilised comparability; size is one possible magnitude condition. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r45 Failure mode: Scale-unit collapse Error: A unit is treated as sufficient scalar adequacy. Correction: Distinguish standardised unit from the operative relation the measurement claims to preserve. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r46 Failure mode: Scale-choice collapse Error: Scale is treated as arbitrary analyst preference. Correction: Show the operative comparability regime achieved by the locus and constrained by the target relation. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r47 Failure mode: Magnitude-scale collapse Error: Physical magnitude is treated as observer-created or identical to operative scale. Correction: Keep magnitude reality-constrained and scale observer-relative as comparability. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r48 Failure mode: Reference/operative-scale collapse Error: The scale stated by the claim is assumed to be the scale the method actually stabilises. Correction: Specify both and test alignment. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r49 Failure mode: Precision/alignment collapse Error: Precise, repeatable, or institutionally enforced measurement is treated as scalar adequacy. Correction: Test whether the measured relation remains stable at the operative scale and under cross-scale correction. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r50 Failure mode: Scale Gap/error collapse Error: Any difference between scales is called error. Correction: Reserve scalar error for consequential misfit; carry Scale Gap where alignment remains incomplete. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r51 Failure mode: Cross-scale export error Error: Population, molecular, legal, local, model, or token-scale relations are exported without a bridge. Correction: Specify a scalar bridge and test preservation under aggregation, individuation, reduction, inflation, or lateral transfer. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r52 Failure mode: Threshold/performance collapse Error: Descriptor grades are used to decide whether observation occurred. Correction: Establish Pre-TO/TO/OIP/NTO first; grade the envelope second. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r53 Failure mode: Descriptor inflation Error: Broad reach, high throughput, depth, gain, or impact is treated as strong observation without registration and dependence. Correction: Return to OP/OA/OR/RAS/OIP/RSD and comparator-stable dependence. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r54 Failure mode: Threshold flattening Error: Minimal threshold success is treated as complete performance across range, time, scale, load, and intervention. Correction: Report descriptor bounds after status. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r55 Failure mode: OH/Observer Event Horizon collapse Error: Program reach is confused with upstream ingress possibility. Correction: Observer Event Horizon bounds entry into OP; OH measures reliable program reach after the program is specified. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r56 Failure mode: OH/operational-horizon collapse Error: Measured reach is confused with the test window. Correction: Operational horizon is an evaluation parameter; OH is a performance descriptor. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r57 Failure mode: OH/CH collapse Error: Reach and admissible intervention range are treated as the same. Correction: OH asks how far the program works; CH asks what can be varied without invalidating comparison. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r58 Failure mode: RF/truth collapse Error: Reliable OA-to-RAS mapping is treated as truth or complete target fidelity. Correction: RF grades registration consistency; abstraction and target adequacy require separate evaluation. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r59 Failure mode: OBW/strength collapse Error: High registration throughput is treated as intelligence, depth, or warrant. Correction: Report bandwidth separately from status, depth, gain, and correction. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r60 Failure mode: OD/record-count collapse Error: Depth is measured by archive size or hierarchy. Correction: OD counts realised consult-and-register links that remain counterfactually significant. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r61 Failure mode: OG/consequence collapse Error: Large downstream effect is called observational gain without retained-discriminator dependence. Correction: Establish comparator-stable dependence before grading OG. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r62 Failure mode: ODr/recalibration collapse Error: Deliberate update is mislabelled drift, or drift is excused as adaptation. Correction: Use ODr for unintended or uncontrolled displacement of mapping or deployment stability. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r63 Failure mode: OL/inefficiency collapse Error: High sustaining cost is treated as automatic failure. Correction: State load relative to capacity, performance, and collapse threshold. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r64 Failure mode: OCx/any-failure collapse Error: Any misregistration, low gain, overload episode, or narrow horizon is called collapse. Correction: Reserve OCx for regime-level loss of content-driven registration or redeployment. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r65 Failure mode: Descriptor-as-primitive error Error: OH, CH, RF, OBW, OD, OG, ODr, OL, or OCx is used as a replacement for RRP-set or status architecture. Correction: Treat descriptors as derived measures over an already specified observation program. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r66 Failure mode: Failure globalisation Error: A local failure at OP, OA, OR, RAS, OIP, RSD, dependence, or one descriptor is treated as total observational failure. Correction: Localise the failed segment and retain supported segments and bounds. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r67 Failure mode: Residual laundering Error: Unresolved retention, provenance, application, registration, perspective, scale, comparator, correction, or envelope conditions are hidden inside a verdict. Correction: State the missing condition, residual, and update condition explicitly. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r68 Failure mode: Part 3 procedure inflation Error: Part 2b failure localisation is presented as the complete later discipline of the unknown. Correction: Limit Part 2b to status, bound, and localised missing condition; defer the full residual procedure. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r69 Failure mode: Source-hash drift Error: A source-locked paper is edited, including endnotes, references, or other bibliographic apparatus, while a downstream control document retains the earlier file hash. Correction: Hash the exact current file instance and propagate the new hash through every downstream source-lock register. A version number need not change for bibliography-only integration, but the hash must. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r70 Failure mode: Embodiment / active-information collapse Error: Any embodied RAS, physical trace, or relation in a Form is called active information. Correction: Require the producing-locus distinction-conditioned provenance specified by Paper 3, heading 4.3. Paper 1c embodiment alone does not supply it. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r71 Failure mode: Reachability / deployability collapse Error: The capacity to form a relation is substituted for grounded consultation of a retained discriminator. Correction: Separate Paper 1c relation formation from Paper 2 KIP and Paper 4 OIP admissible RSD pathways. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r72 Failure mode: Reachability / realised-operation collapse Error: A supported possible construction or consultability path is treated as an actual NTK/NTI/NTO episode. Correction: Show the realised distinction-dependent operation and the comparator burden of the claimed facet; possibility does not show operation. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r73 Failure mode: Form / distributed-Observer collapse Error: A distributed target-tracking structure is assumed to be an observation-capable or record-operative whole. Correction: Localise record, consultability, realised redeployment, and comparator-stable dependence. Paper 1c, heading 7.1 does not infer a distributed locus. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r74 Failure mode: Receiver / producer relation collapse Error: Receiving a carrier is assumed to copy the source distinction intact or to supply the original producing provenance. Correction: Trace receiving OP/OA/OR/RAS and any application separately from producing provenance (Paper 1c, heading 4.2; Paper 3, headings 3.1 and 4.3). Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r75 Failure mode: Reachability / OH / CH collapse Error: Historical formation capacity is treated as reliable program reach or admissible comparator intervention. Correction: Keep Paper 1c Relational Reachability distinct from Paper 4c OH, CH, and the operational test horizon. Severity: A RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r76 Failure mode: RF collision Error: RF is read as Relational Form rather than the observation-program reliability descriptor. Correction: Reserve RF for Registration Fidelity and write Relational Form in full. Severity: B RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t13-r77 Failure mode: Durable-retention prerequisite for all intelligence Error: Every intelligence episode is required to pass a prior RAS/knowledge threshold. Correction: Paper 3, heading 3.3 permits immediate, embodied, morphological, reactive, or currently registered application without durable retention. Require RAS for retained-record claims, not every applied distinction. Severity: A 5. Diagnostic questions TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t14 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r01 Diagnostic area: Source and scope Question: Do the six Part 2b papers govern local facets, while the four Part 2a papers govern explicitly scoped upstream architecture and Paper 1c alignment? Are historical source locks clearly separated from current Issue 1 release locks? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r02 Diagnostic area: Facet and locus Question: Is the claim about retention, application, bounded registration, abstraction, scale, or program performance? Which locus carries each relation? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r03 Diagnostic area: Access architecture Question: Are RRP, boundary, interface, OP, OA, scale, horizon, noise regime, abstraction, and comparator assumptions specified? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r04 Diagnostic area: Knowledge Question: Has an OR-produced, OA-keyed RAS been retained? Is the status TK, KIP, or NTK? Is warrant being claimed separately? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r05 Diagnostic area: Provenance Question: Was the distinction found or made? Which producing locus fixed made status? Is later use being confused with production? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r06 Diagnostic area: Intelligence Question: Does distinction-conditioned organisation alter downstream trajectory selection for the evaluated locus? Is NTI comparator-stable? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r07 Diagnostic area: Observation Question: Did bounded registration produce a retained RAS? Is the status Pre-TO, TO, OIP, or NTO? Is observer-locus or Observer status earned? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r08 Diagnostic area: Abstraction Question: What cut and abstraction regime made the relation registerable? What is omitted, compressed, stabilised, or excluded? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r09 Diagnostic area: Perspective and objectivity Question: What perspective and event-horizon profile are operative? What correction, comparator, cross-locus, and residual pathways are available? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r10 Diagnostic area: Scale Question: What physical magnitude is at issue? What are the reference and operative scales? Are they aligned? What Scale Gap or scalar bridge remains? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r11 Diagnostic area: Measurement Question: Can the measurement be mapped through RRP, OP, OA, OR, RAS, and where used RSD? Does precision preserve the target relation at the claimed scale? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r12 Diagnostic area: Program status Question: Has threshold status been established before descriptors are applied? Where does any failure occur in OP/OA/OR/RAS/OIP/RSD/dependence? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r13 Diagnostic area: Envelope Question: What are OH, CH, RF, OBW, OD, OG, ODr, OL, and OCx under the stated regime? Are terms being used with their actual discriminators? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r14 Diagnostic area: Residual and update Question: What condition remains unestablished, and what evidence, intervention, correction, scale bridge, or bound would update the claim? RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t14-r15 Diagnostic area: Paper 1c alignment Question: Are embodiment, producing provenance, receiving reconstruction, formation reachability, KIP/OIP deployability, actual application, and OH/CH performance kept separate? Is distributed Form being mistaken for a single locus? 6. Master guardrail instructions TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t15 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r01 Guardrail: Knowledge Instruction: Assign minimal knowledge only to retained, re-identifiable RAS; keep TK, KIP, and NTK distinct and separate from warrant. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r02 Guardrail: Active-information provenance Instruction: Fix made status at the producing locus; later encounter or reuse does not create the provenance and producer extinction does not erase it while the form remains instantiated. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r03 Guardrail: Intelligence Instruction: Require present application of distinction-conditioned organisation to branch-space for the evaluated locus. Do not require durable prior RAS for every intelligence episode (Paper 3, heading 3.3). RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r04 Guardrail: Observation Instruction: Require bounded registration into retained RAS; use observer-locus for OIP and Observer for realised NTO only. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r05 Guardrail: Abstraction Instruction: Expose the cut and regime; do not equate abstraction, omission, or gap with falsity. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r06 Guardrail: Perspective and objectivity Instruction: Treat perspective as organised abstraction architecture and objectivity as disciplined correction under constraint. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r07 Guardrail: Scale and measurement Instruction: Separate magnitude, reference scale, and operative scale; treat measurement as registration through scale and state Scale Gap where alignment is incomplete. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r08 Guardrail: Operational envelope Instruction: Establish status before applying descriptors; keep OH, CH, RF, OBW, OD, OG, ODr, OL, and OCx distinct. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r09 Guardrail: Comparator and locus Instruction: Use BD/IPL/local-locus discipline for non-trivial and gain claims; do not shift explanatory work silently. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r10 Guardrail: Residual Instruction: Localise the missing condition and state the update condition; do not convert uncertainty into a hidden positive or negative verdict. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t15-r11 Guardrail: Release control Instruction: The authorised ten-paper Issue 1 baseline and directional support chain are frozen in this release. Current source locks identify exact saved bytes. A later edit requires a new digest and downstream reconciliation. Never reuse a historical sha16 as the hash of a changed file. 7. Control interfaces and release checklist TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t16 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t16-r01 Boundary: Part 2a inheritance Instruction: RRP, signal, OP/OA/OR/RAS/RSD, local locus discipline, target/model/residual, and the Paper 1c physical and derived relations remain upstream. Papers 2, 4a and 4c now clarify their local relations to Paper 1c without changing facet thresholds. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t16-r02 Boundary: Part 1 inheritance Instruction: NTC, BD, and IPL only. No import of life-attribution classes into Part 2b status or descriptor claims. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t16-r03 Boundary: Part 3 handoff Instruction: Part 2b localises status and program failures and carries residual; the complete discipline of the unknown remains downstream. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t16-r04 Boundary: Support stack Instruction: SD-01 compresses architecture; SD-02 controls vocabulary; SD-03 controls failures. All remain secondary to canonical papers. TABLE got-v1-part-2-support-guardrail-and-failure-mode-register-t17 RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r01 Checklist item: Canonical source lock Required condition: All ten paper identities remain in 0.1. Digests for available paper bytes and predecessor supports match the companion manifest; the unchanged recorded locks for Papers 1, 1a and 1b are separately identified as not reverified here. Historical predecessor locks remain labelled. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r02 Checklist item: Issue status Required condition: All active support identity fields and running furniture identify Issue 1. Paper 1c's parent relationship and reading position follow the released paper manifest; the preliminary GOT-FMT-01 paper register is not silently amended by this support release. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r03 Checklist item: Ownership Required condition: Each threshold, extension concept, and descriptor remains in its canonical paper. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r04 Checklist item: Provenance Required condition: Active information is attributed to the producing locus; producing and applying loci are not collapsed. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r05 Checklist item: Status discipline Required condition: TK/KIP/NTK and Pre-TO/TO/OIP/NTO remain distinct; status precedes descriptor grading. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r06 Checklist item: Abstraction and scale Required condition: Gap terms are not automatic errors; magnitude, reference scale, and operative scale remain distinct. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r07 Checklist item: Descriptor discipline Required condition: Every operational-envelope term is used with its discriminator and does not replace the inherited stack. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r08 Checklist item: Residual discipline Required condition: Unresolved conditions and update paths are explicit. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r09 Checklist item: Visual QA Required condition: Tables, headers, footers, page breaks, and glyphs render cleanly before delivery. RECORD got-v1-part-2-support-guardrail-and-failure-mode-register-t17-r10 Checklist item: Paper 1c bibliography / audit decision Required condition: The released Paper 1c contains 21 native endnotes and 15 references: nine internal series papers and six existing external works. Preserve its bounded source-reuse roles and explicit evidence limits. The missing original coded-audit protocol remains unrecovered; no new audit maturity or external discovery result is manufactured. Part-level consolidation note Historical Part-level consolidation and the 23 September 2026 Pass 1 Paper 1c integration are retained. This Issue 1 reconciliation checks the existing controls against the limited amendments in Papers 2, 4a and 4c and refreshes release records and predecessor-support locks. All failure modes, corrections, severity classes, diagnostic questions and facet thresholds remain unchanged. Source-verification limits are stated in 0.1; no primary paper or formatting control is edited.