Guardrail and Failure-Mode Register

Document ID

P2-2A2B-SD03-GUARDRAIL

Version / issue

Issue 1

Date

2026-09-23

Status

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.

Supersedes

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.

Function

Records Part-level conceptual guardrails, failure modes, severity classes, corrections, and diagnostic questions while preserving distinct Part 2a and Part 2b failure-control regions.

Canonical rule

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.

Internal split rule

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.

Source-lock rule

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.

Template rule

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.

Part 2a / Paper 1

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

Relative Reference Points

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.

Part 2a / Paper 1a

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

From Noise Cometh Signal

Physical pathway of availability; variation, preserved contrast, signal, channel-relative discriminability, Locus Event Horizon, signal/information separation, and ingress into OP.

Part 2a / Paper 1b

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

Reference-Indexed Realism

Reference-indexed realism; broad bounded-registration bridge use; ontological target, finite model, residual, access scaffold, and discipline of closure.

Part 2a / Paper 1c

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.

Relational Form

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.

Part 2b / Paper 2

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

On the Origin of Knowledge

Knowledge as retained distinction; RAS as canonical minimal carrier; TK, KIP, NTK; record-status separated from truth, warrant, objectivity, and justification.

Part 2b / Paper 3

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

On the Origin of Intelligence

Intelligence as applied distinction; finite branch-space; passive/active information; passive/active intelligence; NTI; provenance, comparator, and locus discipline.

Part 2b / Paper 4

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

On the Origin of Observation

Observation as bounded registration; OR event; RAS record; Pre-TO, TO, OIP, NTO; observer-locus, Observer, Observer Event Horizon, and record-provenance.

Part 2b / Paper 4a

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

The Limits of Observation

Cut, abstraction regime, perspective, event-horizon profile, Abstraction Gap, relational uncertainty, and objectivity as disciplined correction.

Part 2b / Paper 4b

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

The Scale of Observation

Scale as stabilised comparability; magnitude, reference scale, operative scale, measurement, Scale Gap, scalar alignment, and scalar objectivity.

Part 2b / Paper 4c

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

The Operational Envelope of Observation

Observation program and descriptor layer; OH, CH, RF, OBW, OD, OG, ODr, OL, OCx; threshold/performance separation and failure localisation.

P2-SD01

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

Architecture compression and Part-level source-discipline control.

P2-SD02

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

Controlled vocabulary and canonical-home cross-check.

Informational architecture, RRP, OP, OA, OR, RAS, RSD

Paper 1

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.

Physical pathway into availability

Paper 1a

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.

Reference-indexed realism and closure discipline

Paper 1b

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.

Relational index, embodiment, reachability, Form, and propagation

Paper 1c, headings 1-5 and 7.1

Keep the physical index, local target/locus, primitive RAS, embodiment, derived formation capacity, distributed Form, finite model, and residual distinct.

Knowledge, intelligence, and technical observation status terms

Part 2b handoff

Do not assign Part 2b statuses inside Part 2a. Preserve Paper 1b broad observation-as-bounded-registration language only as realism-facing bridge use.

Support-document compression and support-stack alignment

SD-01

Do not treat support documents as canonical redefinitions. Primary papers govern technical use.

Class A - Mechanical inconsistency

Breaks the architecture.

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.

Correct before finalisation.

Class B - Terminology drift

Creates ambiguity or future misuse.

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.

Correct before compression or publication.

Class C - Presentation ambiguity

May mislead despite intact architecture.

Event horizon sounds like metaphysical edge; residual sounds like failure; relative sounds like arbitrary; support document sounds canonical.

Clarify through wording, heading, ownership note, residual statement, or diagnostic question.

Source-lock drift

Part 2b papers, later observation papers, older drafts, exported TEM material, or prior generated answers re-enter Part 2a as conceptual sources.

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.

A

Canonical ownership drift

A support document becomes a source of technical redefinition.

Return the term to its canonical home; mark support text as compression only.

A

Part 2b import drift

Knowledge, intelligence, or technical observation status ladders are used to define Part 2a concepts.

Treat Part 2b statuses as downstream handoff only; preserve Paper 1b broad observation-as-bounded-registration use without importing the later status ladder.

B

Pan-informational collapse

Every physical difference is treated as RRP-indexed information for the evaluated locus because it exists, persists, differs, or can be described.

Require RRP-indexed availability as operational distinction for the specified locus.

A

External-interpreter substitution

A relation is attributed to the system because an external analyst can describe or use it.

Specify the evaluated locus and show availability, classing, registration, retention, or redeployment for that locus.

A

RRP subjectivism

RRP-relative is read as subjective, arbitrary, or mind-created.

Restore the realist guardrail: the relation is relative, the constraint is real.

A

RRP absolutism

A distinction available to one locus is treated as universally available.

Specify locus, interface, scale, horizon, discrimination regime, abstraction, and path conditions.

B

Locus drift

The explanatory work moves silently between source, carrier, receiver, user, institution, environment, and analyst.

Use local locus discipline; redraw the locus only when the evaluated relation changes and state the transfer.

A

OP inflation

A persistent or propagating physical state, residue, or merely possible contrast is treated as OP before availability at an interface is shown.

Require available contrast for a specified locus under reference conditions.

A

OA omission

Available contrast is treated as registerable without a classing regime.

Identify the abstraction or partition that makes alternatives same/different, signal/noise, present/absent, or within/outside tolerance.

B

OR inflation

Perturbation, coupling, physical persistence, or state change is treated as registration.

Require selection of one OP-supported, OA-classed alternative into state.

A

RAS inflation

Any persistent physical state, mark, memory-like condition, archive, or residue is treated as RAS.

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.

A

RSD inflation

Any downstream effect is treated as redeployment.

Require later transition, inference, action, control, correction, or branch-realisation to depend on the retained distinction.

A

Signal primitive error

Signal is treated as the primitive ground of all information.

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.

B

Signal inflation

Every interaction, variation, persistent state, propagation, residue, or transmission is treated as signal.

Require preserved contrast through a medium under possible discrimination conditions.

A

Information inflation from signal

Every signal-bearing contrast is treated as RRP-indexed information for the evaluated locus.

Require the contrast to become available as distinction for that locus under RRP conditions.

A

Information-scope collapse

The RRP definition of information for a locus is treated as revoking thermodynamic, statistical, physical, Shannon, or other legitimate informational regimes.

Restore scope: those regimes retain their own conditions; RRP asks the further question of operational availability within the evaluated relation.

A

Persistence/propagation stage inflation

Persistence, propagation, or residue is reintroduced as an independent stage between variation and signal or between registration and retained state.

Treat them as physical properties. Signal begins at preserved contrast; RAS begins at an OA-keyed, OR-produced state retained over the relevant horizon.

A

Shannon overextension

SIT is treated as the complete theory of information.

Keep SIT to channel-relative uncertainty, coding, noise, symbols, bits, and transmission under specified conditions; preserve the further RRP availability question.

B

Semantic signal error

Signal is treated as content, message, or meaning by itself.

Return to physical preserved contrast; semantic content requires later regimes of classing, retention, and redeployment.

A

Locus Event Horizon overread

The Locus Event Horizon is read as an edge of reality, absolute unknowability, or black-hole physics literalism.

Define it as ingress-boundary of possible relation for a finite locus under a regime.

C

Event horizon/profile confusion

Locus Event Horizon is confused with later Observer Event Horizon or operational performance descriptors.

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.

B

Naive possession

A measurement, record, model, or observer is treated as possessing the target whole.

Restore the access scaffold: finite loci encounter reality through boundary, interface, channel, threshold, scale, abstraction, registration, retention, and possible redeployment.

A

Empty constructivism

Because access is indexed, the target is treated as constructed by the observer.

Restore target constraint. Mediation does not create the target by itself.

A

Sceptical collapse

Because access is mediated, no model is treated as reality-tracking.

Restore corrigible modelling: mediation is not unreality; models vary in fidelity, range, resilience, and residual.

B

Unindexed realism

A claim asks whether something is real without specifying real as what, for what locus, access relation, scale, horizon, comparator, and residual.

Index the realism claim before closing it.

A

Real/unreal flattening

Everything consequential is called real in the same way.

Index the respect: real as experience, risk, institutional force, model, absence, fiction, error condition, etc.

B

Target/model collapse

A finite model, record, category, or measurement is treated as the ontological target itself.

Separate target, access scaffold, finite model, and residual.

A

Residual laundering

Unresolved remainder is hidden inside confidence, closure, or broad realism-language.

State the residual and its update condition; do not convert it into a verdict.

A

Premature closure

The claim closes beyond what access, comparator, scale, horizon, and residual discipline warrant.

Weaken the claim; carry residual forward; identify what would update the closure.

A

Reference-index / relational-index collapse

The finite reference conditions of a claim are treated as the whole physical relational index, or the index is treated as an observer inventory.

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).

A

Index / Form collapse

Every antecedent physical relation is treated as part of the Relational Form of the selected target distinction.

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).

A

Embodiment-stage inflation

Embodiment is inserted after RAS as a new primitive, further retention test, or stronger information status.

Treat embodiment as the physical description already entailed by OA-keyed retention; RAS remains primitive (Paper 1c, heading 2.3).

A

Coupling / completed-content error

Coupling is described as copying a relation already completed wholly within either target or locus.

Their histories condition interaction, but the coupling produces a new local relation (Paper 1c, heading 2.1).

B

Ingress / reachability collapse

Access to an object, carrier, or signal is assumed to make every target-relative relation formable.

Separate incoming contrast from the organisation needed to stabilise the particular relation (Paper 1c, heading 2.4).

A

Absolute unreachability

A relation not presently formable for one locus is called unreal, impossible for every locus, or permanently inaccessible.

Index reachability to locus, regime, history, scaffold, and horizon; identify physically supported conditions that could change it (Paper 1c, heading 2.4).

B

Unsupported constructive reach

An imagined sequence of concepts or tools is treated as a physically available scaffold.

Require the supported intermediate couplings and changes of organisation; mere conceivability is not enough (Paper 1c, heading 2.4).

A

Form / finite-model possession

A finite model, one carrier, one observer, or one accessible subset is identified with the whole Relational Form.

Keep ontological extent, locally reachable subset, finite abstraction, and residual separate (Paper 1c, headings 3.1 and 5.2).

A

Potential / actual-instance collapse

Physically supported future instantiation is treated as an already present object or a disembodied ideal template.

Potential must be causally organised; a later instance is not present as a hidden miniature (Paper 1c, headings 3.3-3.4).

A

Representation-first requirement

Relation, classed registration, or retention is denied unless a carrier intentionally or semantically stands for its target.

Relation and earned embodiment can precede representation; standing-for is a later relation (Paper 1c, heading 4.1).

A

Intact semantic transfer

Meaning or a completed concept is treated as moving unchanged across carriers and receiving loci.

Trace selective physical preservation and the receiving organisation's own classing and reconstruction (Paper 1c, heading 4.2).

A

Provenance / preservation collapse

A distinction is inferred from a trace merely because it occurred somewhere in that trace's causal history.

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).

A

Form / truth collapse

Every target-related retained state is treated as an accurate target property, or all erroneous relations are excluded from the physical Form.

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).

A

Distributed Form / locus collapse

Distribution across carriers is assumed to establish one integrated operative locus.

Localise each access and deployment claim separately; no distributed locus follows from Form alone (Paper 1c, heading 7.1).

A

Relational Form / RF collision

Relational Form is shortened to RF and confused with Registration Fidelity.

Write Relational Form in full. RF remains the Paper 4c reliability descriptor (Paper 4c, heading 3.1).

B

1

Check source and canonical home.

Is the term owned by Paper 1, 1a, 1b, 1c, or by a stated downstream Part 2b paper?

2

Identify the target difference or relation.

What physical difference, contrast, target relation, model, or realism claim is at issue?

3

Specify the RRP.

For what locus, through what interface, at what scale, over what horizon, under what discrimination/noise and abstraction regime?

4

Locate physical pathway status.

Is this interaction, variation, persistence/propagation/residue as a physical property, preserved or signal-bearing contrast, channel-discriminable contrast, or available distinction?

5

Audit RRP Set status.

Are OP, OA, OR, RAS, and any RSD established for the specified locus? Is embodiment merely describing an earned RAS, rather than upgrading persistence?

6

Protect locus discipline.

Has the claim silently moved from source to carrier, from carrier to user, from system to analyst, or from one locus to another?

7

Index the realism claim.

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?

8

Assign closure only where warranted.

Does the claim close under the stated reference conditions, or must it remain residual-bearing?

9

Hand off Part 2b statuses only when earned.

Do not call retained distinction knowledge, applied distinction intelligence, or bounded registration the completed technical observation status unless downstream conditions are invoked explicitly.

10

Separate ingress from formation.

Can the carrier enter while the target relation remains unreachable? What actual organisation or scaffold supports immediate or constructible reach?

11

Trace selective propagation.

Which distinction survived, which was lost, and which never coupled into the path? Has the receiver earned its own registration and any retention?

12

Check Form and adequacy.

Is the Form confused with a complete model, all causal history, a true-only set, a present potential instance, or a single operative locus?

Difference-to-information ladder

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.

RRP-indexed claim first

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.

Signal physicality

Signal is a physical mediation of possible relation. It is not semantic content, not the source whole, and not primitive information.

Event horizon discipline

Use Locus Event Horizon only as the ingress-boundary of possible relation before OP is established for a locus under a regime.

Realist double guardrail

Reality is not created by the locus. Reality is not possessed whole by the locus. Both sides must remain visible.

Target/model/residual discipline

Every realism-facing compression should keep ontological target, finite model, access scaffold, and residual separate.

Primitive / derived separation

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).

Table-local RAS and later uptake

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).

Reachability and dynamic residual

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).

Propagation and representation

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).

Knowledge handoff

Part 2a can say that RAS prepares retained distinction. It should not assign full knowledge-status unless the Part 2b knowledge ladder is invoked.

Intelligence handoff

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.

Observation handoff

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.

Abstraction/scale handoff

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.

Reachability / deployability handoff

Do not use relation formation to certify KIP, OIP, realised RSD, OH, or CH. Each downstream condition requires its own locus, pathway, and discriminator.

Issue 1

2026-08-08

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.

Issue 1 support - Pass 1

2026-09-23

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.

Issue 1 - final release

2026-09-23

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.

Inherited access architecture

Part 2a

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.

Knowledge threshold and ladder

Paper 2

Do not redefine knowledge as belief, semantic possession, truth, justification, usefulness, or conscious awareness. Do not collapse TK, KIP, and NTK.

Intelligence threshold and provenance/use ladder

Paper 3

Do not define intelligence by cognition, usefulness, success, complexity, or resemblance. Active-information provenance belongs to the producing locus, not the later encounter.

Observation threshold, ladder, and observer-status

Paper 4

Do not define observation as every interaction, signal reception, trace, memory, measurement, knowledge, intelligence, or warrant. Do not collapse record, observer-locus, and Observer.

Abstraction, perspective, uncertainty, and objectivity

Paper 4a

Do not treat abstraction as failure or unreality, perspective as opinion, Abstraction Gap as error, or objectivity as consensus or view-from-nowhere.

Scale, measurement, and scalar objectivity

Paper 4b

Do not reduce scale to size, unit, choice, or precision; do not collapse physical magnitude, reference scale, operative scale, or Scale Gap.

Observation program and descriptor layer

Paper 4c

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.

Comparator and localisation control

Canonical papers with inherited Part 1 control

Use BD-family comparator and IPL/local locus discipline for strong dependence claims; do not import the Part 1 life ladder.

Residual and unknown handoff

Part 2a / Part 3 handoff

Carry explicit residual and update conditions; do not pretend Part 2b provides the later complete procedure for the unknown.

Class A - Mechanical inconsistency

Breaks the architecture.

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.

Correct before finalisation.

Class B - Terminology drift

Creates ambiguity or future misuse.

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.

Correct before compression or publication.

Class C - Presentation ambiguity

May mislead despite intact architecture.

“Trivial” sounds unimportant; “passive intelligence” sounds inactive; “Observer” sounds conscious; “gap” sounds error; “relative” sounds subjective; “collapse” sounds any failure.

Clarify through wording, canonical-home note, discriminator, residual statement, or diagnostic question.

Source-lock drift

Older drafts, superseded support wording, exported TEM material, future Part 3 procedures, or prior generated answers enter as conceptual sources.

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.

A

Canonical ownership drift

A support document becomes a source of technical redefinition.

Return the term to its canonical paper; mark support wording as compression only.

A

Issue-number drift

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.

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.

B

Numbering drift

Paper 2/3/4/4a/4b/4c roles are confused or legacy numbering is used without context.

Use the current Part 2b support sequence and preserve each paper title as the canonical locator.

B

Part 2a inheritance drift

Inherited RRP terms are redefined from Part 2b shorthand.

Use Part 2a primary papers and the internal Part 2a support section for inherited architecture; Part 2b only applies the architecture to new facets.

A

Part 1 import drift

Life-attribution classes or closure terms are imported into knowledge, intelligence, or observation statuses.

Use Part 1 support only for NTC, BD, and IPL control; keep life-status separate.

A

Facet drift

Knowledge, intelligence, observation, abstraction, scale, and performance are treated as interchangeable labels.

State the focal question and canonical home before assigning status or descriptor.

B

Knowledge-belief collapse

Minimal knowledge is defined first as belief, assertion, awareness, or justified proposition.

Restore knowledge as retained distinction; treat belief and justification as stronger organisations.

A

Knowledge-truth collapse

A retained record is treated as true, warranted, objective, or justified because it exists or is used.

Separate record-status from truth-status and correction layers.

A

Persistent-state/RAS collapse

Any persistent mark, state, residue, archive, or memory-like condition is treated as RAS.

Require OP, OA, OR, identifiable token-state, reference scale, and operational horizon.

A

Signal-to-knowledge inflation

Signal-bearing contrast is called knowledge without retained registration.

Require an OR-produced RAS retained as present accessible state.

A

Retention/deployment collapse

TK, KIP, and NTK are treated as one condition.

Separate record-presence, grounded consultability, and realised redeployment.

B

KIP imagination error

A record is called deployable because an imagined future observer might use it.

Require a physically or organisationally well-posed consultability pathway for the focal locus.

B

NTK warrant inflation

Realised deployment is treated as truth or justification.

Keep NTK as retained distinction doing work; evaluate target preservation separately.

A

Intelligence-cognition collapse

Intelligence is restricted to consciousness, language, reasoning, self-awareness, or human resemblance.

Restore applied distinction altering downstream trajectory selection for a locus.

A

Intelligence-usefulness collapse

Any useful structure, regularity, constraint, gradient, or output is called intelligence.

Require application by distinction-conditioned organisation at the evaluated locus.

A

Success/resemblance shortcut

A system is called intelligent because it succeeds or resembles a human answer.

Test whether branch-realisation depends on the applied distinction under comparator discipline.

A

Information/intelligence collapse

Available or retained distinction is treated as intelligence without present application.

Separate information availability, knowledge retention, and intelligence application.

A

Passive-information/passive-intelligence collapse

Found distinction is called passive intelligence because it helps a locus.

Passive intelligence requires reuse of made distinction; found distinction remains passive information.

A

Active-information/active-intelligence collapse

Made distinction is called active intelligence merely because prior organisation produced it.

Active information is provenance; active intelligence requires current application.

A

Active-information provenance inversion

Made status is assigned by the later locus that encounters or uses the distinction.

Identify the producing locus whose prior distinction-conditioned organisation fixed the form. Later encounter creates access/use, not provenance.

A

Producer/applicator collapse

Producing locus and present applying locus are assumed identical.

Localise provenance and present branch-space separately; they may differ in time, substrate, and organisation.

B

Producer-extinction error

Active-information status is removed because the producing locus no longer exists.

Preserve made provenance while the produced distinction remains physically instantiated under the claim.

A

Passive-intelligence inactivity error

Passive intelligence is read as dormant, inert, or non-operative.

Show the current reuse that alters branch-space without recomputing the original selection problem.

B

External-interpreter substitution

An analyst uses or admires a distinction and attributes intelligence or observation to the target system.

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.

A

Comparator weakness

NTK, NTI, NTO, or OG is claimed without adequate intervention discipline.

Construct a BD-family comparator preserving relevant context or weaken the claim.

A

IPL/locus vagueness

The mediating organisation is diffuse or moves silently between source, carrier, user, environment, institution, and analyst.

Identify what must remain intact or be disabled for the claimed dependence.

A

Observation-certificate error

“Observed” is treated as truth, direct access, epistemic guarantee, or complete target possession.

Restore bounded registration and record-provenance; evaluate warrant through correction and residual.

A

Observation-interaction collapse

Coupling, perturbation, signal reception, physical alteration, or transient tokenisation is treated as observation.

Require OR into a persistent, re-identifiable OA-keyed RAS for TO or above.

A

Measurement-is-observation shortcut

A number or readout is treated as sufficient observation without auditing classing, registration, retention, scale, and locus.

Map the measurement path through RRP, OP, OA, OR, RAS, and where claimed RSD.

A

Record/observer collapse

Any record, archive, log, or record-field is treated as observer-locus.

Require grounded consultability for OIP-status observer-locus.

A

observer-locus/Observer collapse

Observation-capacity is treated as realised observation.

Require actual RSD-mediated record-operativity and comparator-stable dependence for Observer/NTO.

A

Distributed-record inflation

Distributed records are treated as a distributed Observer without localising integration and redeployment.

Map the observation chain and show grounded consultability and realised dependence at the claimed locus.

A

NTO-life collapse

NTO or Observer status is treated as sufficient for life.

Keep observation and life thresholds separate; NTO does not entail life.

A

Observer Event Horizon overread

The ingress boundary is treated as an edge of reality or absolute unknowability.

Define it as the present limit of signal-bearing contrast entering OP for the observer-locus.

B

Abstraction denial

Observation is described as raw reception without OA, selection, omission, or compression.

Expose the cut and abstraction regime that make the relation registerable.

A

Abstraction-as-failure error

Any abstraction or omission is treated as falsity or defect.

Treat abstraction as the enabling condition of finite observation; test whether it preserves the relevant relation.

B

Cut/real collapse

The observational cut, category, model, or record is treated as the real whole.

Restore target constraint and model/record incompleteness; carry residual.

A

Perspective-opinion collapse

Perspective is reduced to personal attitude, bias, preference, or subjectivity.

Define perspective as locus-level integration of an abstraction regime and event-horizon profile.

A

Abstraction Gap/error collapse

Abstraction Gap is treated as error by definition.

Reserve error for consequential miscompression; gap is the structural space in which error can arise.

B

Relational uncertainty globalisation

Uncertainty about preservation by one cut is inflated into global scepticism.

Localise the uncertain relation, conditions, comparator, and correction path.

B

Objectivity-as-view-from-nowhere

Objectivity is treated as abstraction-free, perspective-free access.

Use disciplined correction of perspective under constraint.

A

Objectivity-as-consensus

Agreement alone is treated as objectivity.

Require target constraint, comparator pressure, cross-locus correction, and residual discipline.

B

Scale-size collapse

Scale is reduced to physical size.

Use scale as stabilised comparability; size is one possible magnitude condition.

A

Scale-unit collapse

A unit is treated as sufficient scalar adequacy.

Distinguish standardised unit from the operative relation the measurement claims to preserve.

B

Scale-choice collapse

Scale is treated as arbitrary analyst preference.

Show the operative comparability regime achieved by the locus and constrained by the target relation.

A

Magnitude-scale collapse

Physical magnitude is treated as observer-created or identical to operative scale.

Keep magnitude reality-constrained and scale observer-relative as comparability.

A

Reference/operative-scale collapse

The scale stated by the claim is assumed to be the scale the method actually stabilises.

Specify both and test alignment.

A

Precision/alignment collapse

Precise, repeatable, or institutionally enforced measurement is treated as scalar adequacy.

Test whether the measured relation remains stable at the operative scale and under cross-scale correction.

A

Scale Gap/error collapse

Any difference between scales is called error.

Reserve scalar error for consequential misfit; carry Scale Gap where alignment remains incomplete.

B

Cross-scale export error

Population, molecular, legal, local, model, or token-scale relations are exported without a bridge.

Specify a scalar bridge and test preservation under aggregation, individuation, reduction, inflation, or lateral transfer.

A

Threshold/performance collapse

Descriptor grades are used to decide whether observation occurred.

Establish Pre-TO/TO/OIP/NTO first; grade the envelope second.

A

Descriptor inflation

Broad reach, high throughput, depth, gain, or impact is treated as strong observation without registration and dependence.

Return to OP/OA/OR/RAS/OIP/RSD and comparator-stable dependence.

A

Threshold flattening

Minimal threshold success is treated as complete performance across range, time, scale, load, and intervention.

Report descriptor bounds after status.

B

OH/Observer Event Horizon collapse

Program reach is confused with upstream ingress possibility.

Observer Event Horizon bounds entry into OP; OH measures reliable program reach after the program is specified.

A

OH/operational-horizon collapse

Measured reach is confused with the test window.

Operational horizon is an evaluation parameter; OH is a performance descriptor.

B

OH/CH collapse

Reach and admissible intervention range are treated as the same.

OH asks how far the program works; CH asks what can be varied without invalidating comparison.

B

RF/truth collapse

Reliable OA-to-RAS mapping is treated as truth or complete target fidelity.

RF grades registration consistency; abstraction and target adequacy require separate evaluation.

A

OBW/strength collapse

High registration throughput is treated as intelligence, depth, or warrant.

Report bandwidth separately from status, depth, gain, and correction.

B

OD/record-count collapse

Depth is measured by archive size or hierarchy.

OD counts realised consult-and-register links that remain counterfactually significant.

B

OG/consequence collapse

Large downstream effect is called observational gain without retained-discriminator dependence.

Establish comparator-stable dependence before grading OG.

A

ODr/recalibration collapse

Deliberate update is mislabelled drift, or drift is excused as adaptation.

Use ODr for unintended or uncontrolled displacement of mapping or deployment stability.

B

OL/inefficiency collapse

High sustaining cost is treated as automatic failure.

State load relative to capacity, performance, and collapse threshold.

B

OCx/any-failure collapse

Any misregistration, low gain, overload episode, or narrow horizon is called collapse.

Reserve OCx for regime-level loss of content-driven registration or redeployment.

A

Descriptor-as-primitive error

OH, CH, RF, OBW, OD, OG, ODr, OL, or OCx is used as a replacement for RRP-set or status architecture.

Treat descriptors as derived measures over an already specified observation program.

A

Failure globalisation

A local failure at OP, OA, OR, RAS, OIP, RSD, dependence, or one descriptor is treated as total observational failure.

Localise the failed segment and retain supported segments and bounds.

B

Residual laundering

Unresolved retention, provenance, application, registration, perspective, scale, comparator, correction, or envelope conditions are hidden inside a verdict.

State the missing condition, residual, and update condition explicitly.

A

Part 3 procedure inflation

Part 2b failure localisation is presented as the complete later discipline of the unknown.

Limit Part 2b to status, bound, and localised missing condition; defer the full residual procedure.

B

Source-hash drift

A source-locked paper is edited, including endnotes, references, or other bibliographic apparatus, while a downstream control document retains the earlier file hash.

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.

A

Embodiment / active-information collapse

Any embodied RAS, physical trace, or relation in a Form is called active information.

Require the producing-locus distinction-conditioned provenance specified by Paper 3, heading 4.3. Paper 1c embodiment alone does not supply it.

A

Reachability / deployability collapse

The capacity to form a relation is substituted for grounded consultation of a retained discriminator.

Separate Paper 1c relation formation from Paper 2 KIP and Paper 4 OIP admissible RSD pathways.

A

Reachability / realised-operation collapse

A supported possible construction or consultability path is treated as an actual NTK/NTI/NTO episode.

Show the realised distinction-dependent operation and the comparator burden of the claimed facet; possibility does not show operation.

A

Form / distributed-Observer collapse

A distributed target-tracking structure is assumed to be an observation-capable or record-operative whole.

Localise record, consultability, realised redeployment, and comparator-stable dependence. Paper 1c, heading 7.1 does not infer a distributed locus.

A

Receiver / producer relation collapse

Receiving a carrier is assumed to copy the source distinction intact or to supply the original producing provenance.

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).

A

Reachability / OH / CH collapse

Historical formation capacity is treated as reliable program reach or admissible comparator intervention.

Keep Paper 1c Relational Reachability distinct from Paper 4c OH, CH, and the operational test horizon.

A

RF collision

RF is read as Relational Form rather than the observation-program reliability descriptor.

Reserve RF for Registration Fidelity and write Relational Form in full.

B

Durable-retention prerequisite for all intelligence

Every intelligence episode is required to pass a prior RAS/knowledge threshold.

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.

A

Source and scope

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?

Facet and locus

Is the claim about retention, application, bounded registration, abstraction, scale, or program performance? Which locus carries each relation?

Access architecture

Are RRP, boundary, interface, OP, OA, scale, horizon, noise regime, abstraction, and comparator assumptions specified?

Knowledge

Has an OR-produced, OA-keyed RAS been retained? Is the status TK, KIP, or NTK? Is warrant being claimed separately?

Provenance

Was the distinction found or made? Which producing locus fixed made status? Is later use being confused with production?

Intelligence

Does distinction-conditioned organisation alter downstream trajectory selection for the evaluated locus? Is NTI comparator-stable?

Observation

Did bounded registration produce a retained RAS? Is the status Pre-TO, TO, OIP, or NTO? Is observer-locus or Observer status earned?

Abstraction

What cut and abstraction regime made the relation registerable? What is omitted, compressed, stabilised, or excluded?

Perspective and objectivity

What perspective and event-horizon profile are operative? What correction, comparator, cross-locus, and residual pathways are available?

Scale

What physical magnitude is at issue? What are the reference and operative scales? Are they aligned? What Scale Gap or scalar bridge remains?

Measurement

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?

Program status

Has threshold status been established before descriptors are applied? Where does any failure occur in OP/OA/OR/RAS/OIP/RSD/dependence?

Envelope

What are OH, CH, RF, OBW, OD, OG, ODr, OL, and OCx under the stated regime? Are terms being used with their actual discriminators?

Residual and update

What condition remains unestablished, and what evidence, intervention, correction, scale bridge, or bound would update the claim?

Paper 1c alignment

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?

Knowledge

Assign minimal knowledge only to retained, re-identifiable RAS; keep TK, KIP, and NTK distinct and separate from warrant.

Active-information provenance

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.

Intelligence

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).

Observation

Require bounded registration into retained RAS; use observer-locus for OIP and Observer for realised NTO only.

Abstraction

Expose the cut and regime; do not equate abstraction, omission, or gap with falsity.

Perspective and objectivity

Treat perspective as organised abstraction architecture and objectivity as disciplined correction under constraint.

Scale and measurement

Separate magnitude, reference scale, and operative scale; treat measurement as registration through scale and state Scale Gap where alignment is incomplete.

Operational envelope

Establish status before applying descriptors; keep OH, CH, RF, OBW, OD, OG, ODr, OL, and OCx distinct.

Comparator and locus

Use BD/IPL/local-locus discipline for non-trivial and gain claims; do not shift explanatory work silently.

Residual

Localise the missing condition and state the update condition; do not convert uncertainty into a hidden positive or negative verdict.

Release control

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.

Part 2a inheritance

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.

Part 1 inheritance

NTC, BD, and IPL only. No import of life-attribution classes into Part 2b status or descriptor claims.

Part 3 handoff

Part 2b localises status and program failures and carries residual; the complete discipline of the unknown remains downstream.

Support stack

SD-01 compresses architecture; SD-02 controls vocabulary; SD-03 controls failures. All remain secondary to canonical papers.

Canonical source lock

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.

Issue status

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.

Ownership

Each threshold, extension concept, and descriptor remains in its canonical paper.

Provenance

Active information is attributed to the producing locus; producing and applying loci are not collapsed.

Status discipline

TK/KIP/NTK and Pre-TO/TO/OIP/NTO remain distinct; status precedes descriptor grading.

Abstraction and scale

Gap terms are not automatic errors; magnitude, reference scale, and operative scale remain distinct.

Descriptor discipline

Every operational-envelope term is used with its discriminator and does not replace the inherited stack.

Residual discipline

Unresolved conditions and update paths are explicit.

Visual QA

Tables, headers, footers, page breaks, and glyphs render cleanly before delivery.

Paper 1c bibliography / audit decision

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.