Master Guardrail and Failure-Mode Register

Document ID

GOT-V1-MSD03

Authority

Series support consolidation. Canonical definitions remain with the owning Part 1, 2 or 3 paper.

Scope

Part 0 is the storage location only. Part 0 content, essays and TET are outside this canon. The deferred Toolkit contributes no active content.

Source control

Twelve Issue 1 part-level support documents; 21 current technical papers. Current hashes and source paths are recorded in MSD00 and the companion manifest.

MI01

Part 1 to Parts 2 and 3

Inherit NTC, BD, IPL and physical grounding where the claim requires them. Keep life-attribution classes local.

P1-SD01 T06; P2-SD03 T09; P3-SD02 T09

MI02

Part 2a to Part 2b

Earn retention, application and observation status in the owning facet. Signal, residue, Form or reachability does not bypass the discriminator.

P2-SD01 T22; P2-SD03 T06, T13

MI03

Within Part 2b

Separate a diagnostic order from a universal temporal prerequisite. Durable retention is not required for every intelligence episode.

P2-SD03 T13 R77; GOT-V1-2b-3 heading 3.3

MI04

Part 2 to Part 3

Carry finite access, target constraint, scale and residual forward. Do not rewrite earlier statuses through later closure or unknown-handling vocabulary.

P3-SD01 section 5; P3-SD03 T06

MI05

Across horizon vocabularies

Index ingress, observer-record access, reliable program reach, intervention reach, procedural availability and closure separately.

P2-SD03 T13; P3-SD03 T07

MI06

Across loci and carriers

Identify producing, applying, attributing, observing and relying loci. A carrier does not transport completed meaning, warranted status or causal provenance automatically.

P2-SD03 T06, T13; P3-SD03 T09, T10

MI07

Power and Responsibility

Recover physically supported, distinction-conditioned branch potential and attributable consequential contribution only where those claims are made.

P3-SD03 T08, T09, T13

MI08

Trust authority and governance

Epistemic Authority and the minimum Structural Authority distinction remain owned by 3b-5 section 8. Governance applies them; recognition or mandate does not establish epistemic strength.

P3-SD02 T07, T08; P3-SD03 T10, T12

MI09

Across residual and action

Keep the missing relation, blocked stronger claim and update condition local. Acting or relying under residual does not resolve it.

P1-SD02 T08; P2-SD02 T07, T20; P3-SD02 T06

MI10

Bibliographic consolidation

Merge publication identity only. Preserve local relation, maturity, locator, inheritance value, hold and residual separately.

P1-SD04 section 1; P2-SD04 sections 1 and 5; P3-SD04 section 9

MI11

Canon and source identity

Use Parts 1–3 only. Part 0, essays, TET and the deferred Toolkit remain outside the active conceptual source set.

Master scope control; P3-SD01 section 10 exclusion status

MI12

Method integration

The Epistemic Method audits claim and reliance strength while retaining earlier local tests; a completed packet or compliant process does not earn closure.

P3-SD01 section 5; P3-SD03 T11, T13

Scope and identity

The claim resolves to a current canonical paper and its part support record. Excluded content has not entered through an older series master or a deferred control.

Ownership

Definition, inheritance, handoff and application are distinguished. Any local Paper label is resolved within its part.

Reference and locus

Boundary, scale, horizon, comparator and locus match the claim being made. Source, carrier, receiver and applying locus are not silently substituted.

Discriminator

The correct life, informational, facet, horizon, Power, Responsibility or reliance conditions are recovered.

Strength and residual

The stated outcome does not exceed what the evidence, comparator and carrier path establish. Missing conditions and update remain visible.

Source relation

Publication identity and paper-local scholarly relation remain separate. Holds, exclusions and search residuals remain recorded.

Part 1

Paper 1 / Paper 2 / Paper 3

GOT-V1-1-1 / GOT-V1-1-2 / GOT-V1-1-3

Part 2a

Paper 1 / 1a / 1b / 1c

GOT-V1-2a-1 / 2a-1a / 2a-1b / 2a-1c

Part 2b

Paper 2 / 3 / 4 / 4a / 4b / 4c

GOT-V1-2b-2 / 2b-3 / 2b-4 / 2b-4a / 2b-4b / 2b-4c

Part 3

3a-1 through 3c-8

Prefix the local key with GOT-V1-; retain the full 3a, 3b or 3c section key.

Physical grounding, NMF, TC/NTC, BD, IPL, DTS

Paper 1

Do not redefine computation, NTC, Baseline Dynamics, IPL, DTS, or life in attribution or procedure documents.

Life threshold and physics-chemistry-life transition

Paper 1

Do not treat life as complexity, metabolism, reproduction, feedback, adaptation, persistence, lineage, familiarity, intelligence, or NTC alone.

Attribution architecture

Paper 2

Do not assign life to the first named object, visible container, or familiar biological noun without Attribution Locus analysis.

Identity, continuity, potential throughput, death/closure, and ladder

Paper 2

Do not collapse dormancy, Life-in-Potential, terminal active Life, death/closure, reconstruction, incorporation, Complex Chemistry, and residual into one binary.

Relationship topology

Paper 2

Do not let parasite, symbiont, organelle, tumour, scaffold, artificial, or host-dependent label decide primary life-status.

Diagnostic procedure and audit output

Paper 3

Do not turn the procedure into the phenomenon or reduce it to a checklist of traits.

Residual inventory and update conditions

Paper 3

Do not hide uncertainty inside a verdict; localise the missing discriminator and state the update condition.

Class A - Mechanical inconsistency

Breaks the architecture.

Redefining life; treating TC as NTC; assigning Life without IPL-mediated NTC; making death a fourth class; calling reconstruction survival; bypassing Attribution Locus localisation; using uncertainty as a hidden class.

Correct before finalisation.

Class B - Terminology drift

Creates ambiguity or future misuse.

Using information without regime/throughput; treating dependence as verdict; topology as class; potential as weak life; dormant as merely inactive; maintained-locus wording where final Attribution Locus wording is required.

Correct before compression or publication.

Class C - Presentation ambiguity

May mislead despite intact architecture.

Procedure sounds mechanical; residual sounds explanatory; support document sounds canonical; examples sound universal rather than reference-indexed; positive exclusion sounds like uncertainty.

Clarify through wording, heading, ownership note, residual statement, or update condition.

Source-lock drift
P1-SD03 T06 R01

Exported full-series TEM concepts re-enter the split life stack as conceptual sources.

Remove imported material; use old documents only as templates; return to the finalised three primary life papers and SD-01 Issue 1.

A

Canonical ownership drift
P1-SD03 T06 R02

A support document becomes a source of technical redefinition.

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

A

Redescription collapse
P1-SD03 T06 R03

TC is treated as NTC, or computational mapping is treated as life.

Require physically enacted discrimination, organisation mediation, downstream dependence, and BD comparator pressure.

A

NTC inflation
P1-SD03 T06 R04

Any counterfactual discrimination is treated as Life.

Restore the stricter life condition: driven thermodynamic constraint-maintenance supported by IPL-mediated NTC.

A

Chemistry-only audit collapse
P1-SD03 T06 R05

Chemistry is treated as sufficient to audit life-status without the discriminator question.

Preserve physical and chemical continuity, but require assessment of distinction-conditioned driven constraint-maintenance.

A

Comparator weakness
P1-SD03 T06 R06

The life or NTC claim survives only because the comparator is vague.

Construct adequate BD-family comparator preserving boundary context, driving, inventory, scale, horizon, and noise assumptions.

A

IPL vagueness
P1-SD03 T06 R07

Outcome dependence is attributed to the whole system, environment, or external interpreter without localising the mediating organisation.

Identify what must remain intact, or be ablated, for the distinction to do downstream work.

A

Life inflation
P1-SD03 T06 R08

Informational, computational, adaptive, reproductive, or biologically familiar systems are treated as alive.

Require life-realising driven constraint-maintenance through IPL-mediated NTC.

A

Matter-state collapse
P1-SD03 T06 R09

Membrane, body, capsid, genome, organ, or biological material is treated as final discriminator.

Move from familiar matter-state barrier to informational regime identification.

A

Container collapse
P1-SD03 T06 R10

Life inside a frame is treated as Life of the frame.

Localise the Attribution Locus before primary class assignment.

A

Attribution Locus bypass
P1-SD03 T06 R11

The output assigns class before identifying whose regime is being classified.

Localise the bearer of active, dormant, potential, closed, reconstructed, incorporated, excluded, or residual-bearing relation.

A

Activity collapse
P1-SD03 T06 R12

Visible metabolism, motion, growth, or reproduction is treated as necessary or sufficient for Life.

Distinguish active Life, dormant Life, terminal active Life, Life-in-Potential, and closure/death.

A

Dependence shortcut
P1-SD03 T06 R13

Dependence is treated as automatic non-life or automatic unity.

Decompose resource dependence, scaffolded support, constitutive dependence, host completion, and coupled completion.

A

Lineage shortcut
P1-SD03 T06 R14

Descent, copying, or sequence preservation is treated as present life-status.

Use lineage only after organisational identity or throughput identity has been established.

B

Replication shortcut
P1-SD03 T06 R15

Replication or reproductive participation is treated as sufficient for Life.

Require life-realisation at the Attribution Locus; host-completed propagation may support Life-in-Potential, not free-phase Life.

A

Potential inflation
P1-SD03 T06 R16

Any stored sequence, biological material, trigger, or reconstructable record is treated as Life-in-Potential.

Require identity-bearing potential informational throughput into admissible extrinsic life-realising completion.

A

Dormancy-potential confusion
P1-SD03 T06 R17

Intrinsic resumability is confused with extrinsic completion potential.

Preserve dormant Life as Life where intrinsic same-locus resumability remains open.

A

Terminal-life confusion
P1-SD03 T06 R18

Terminal phase is treated as death merely because long-term continuation is unlikely.

Classify terminal active Life until branch-realisation closes for the target locus.

A

Death-as-class error
P1-SD03 T06 R19

Death is entered into the primary ladder as a fourth class.

Use closure output for closed continuity of a formerly living target locus.

A

Death overextension
P1-SD03 T06 R20

Death of a target locus is spread to every constituent inside the former system.

Apply post-death constituent reframing; classify living subloci, potential candidates, and chemistry separately.

A

Closure-output misuse
P1-SD03 T06 R21

Closure output is applied to material that was never the formerly living target locus.

Use closure only for formerly living target loci; reframe remnants separately.

A

Reconstruction-as-survival error
P1-SD03 T06 R22

Later reconstruction is treated as same-locus return.

Distinguish reconstruction after continuity failure from intrinsic resumption.

A

Incorporation-as-survival error
P1-SD03 T06 R23

Material incorporation into another living regime is treated as survival of the prior locus.

Classify incorporation as cross-locus descriptor, not continuity.

B

Functional sublocus inflation
P1-SD03 T06 R24

An indispensable component is treated as a living locus at the claimed scale.

Require its own maintained boundary, driven regime, operative distinction, and continuity relation.

B

Topology shortcut
P1-SD03 T06 R25

Parasitic, symbiotic, organelle, tumour, artificial, or scaffolded relation becomes the verdict.

Assign topology only after primary class and continuity status are established.

A

Positive-exclusion confusion
P1-SD03 T06 R26

A relation that is positively excluded under stated conditions is softened into vague uncertainty.

State positive exclusion where warranted; carry residual only where a discriminator condition remains incomplete.

B

Residual laundering
P1-SD03 T06 R27

Unresolved discriminator conditions are converted into explanation or hidden in a familiar class.

State residual locally, inventory the missing condition, and specify update conditions.

A

False equivalence
P1-SD03 T06 R28

All unresolved possibilities are treated as equally live.

Preserve discriminator support, strength markers, and update conditions.

B

False precision
P1-SD03 T06 R29

A weak audit is made precise by notation or output form.

State strength marker and residual; do not let the form overstate support.

B

Procedure inflation
P1-SD03 T06 R30

The diagnostic procedure is treated as an additional life theory.

Separate canon from application; procedure preserves relation order but does not redefine life.

B

1

What is the candidate frame?

2

What are the reference boundary, focal scale, interface, operational horizon, driving conditions, and discrimination/noise regime?

3

Is the claim testing the Paper 1 life threshold, the Paper 2 attribution relation, or the Paper 3 procedure?

4

Is there a driven constraint-bearing regime?

5

Which distinctions are operative, and what organisation makes downstream outcomes depend on them?

6

What BD-family comparator tests the claimed dependence?

7

Where is the Information Processing Locus?

8

Does life-realisation occur inside the frame?

9

Whose Attribution Locus carries the realised, intrinsically resumable, potential, closed, reconstructed, incorporated, positively excluded, or residual-bearing relation?

10

Where is DTS completion: intrinsic, resource-dependent, scaffolded, constitutively dependent, host-completed, coupled, or no further same-locus completion after closure?

11

What identity relation is preserved: organisational identity, intrinsic resumability, throughput identity, lineage identity, reconstruction, incorporation, or none?

12

Which continuity status is warranted: active, dormant, terminal active, potential, closed, or uncertain with residual?

13

Which primary class is warranted: Complex Chemistry, Life-in-Potential, Life, or primary-class deferral?

14

Is any tested relation positively excluded under the stated reference conditions?

15

What topology modifier follows after attribution?

16

What residual remains, what inventory type is it, and what would force update?

TC / NTC

Treating lawful redescribability as physically enacted discrimination.

Require discriminable distinction, organisation-mediated downstream dependence, and BD-family ablation, scrambling, reset, neutralisation, or bypass-control.

Description is not discrimination.

NMF

Treating layers as new substances or mere conveniences.

Keep KMB -> BC -> TSS -> thermodynamic information -> EBC -> CTSS/CTS -> DTSS/DTS -> SIT -> NTC as constrained descriptive regimes.

Higher levels are constrained regimes.

BD

Using baseline as vague null condition.

BD must preserve context while disabling the organisation under test.

BD is disciplined contrast.

IPL

Attributing life-relevant computation without localising what does the distinction-conditioned work.

Identify the organisation whose integrity is required for downstream dependence.

IPL says where the distinction does work.

Life discriminator

Treating Life as NTC, self-organisation, metabolism, reproduction, adaptation, or persistence alone.

Require a DTS whose constraint-maintenance depends on IPL-mediated NTC.

Life is stricter than NTC.

Physics-chemistry-life transition

Treating life as leaving chemistry or as only chemistry.

Keep physical and chemical continuity while adding the discriminator required to audit life-status.

Life is an emergent audit layer.

Candidate frame

Treating the first named object as the answer.

Treat the frame as provisional and correct it by informational regime, boundary, completion, and continuity.

The frame opens the inquiry.

Positive exclusion

Using uncertainty language where a relation is negatively warranted under stated conditions.

State the relation as positively excluded under the stated frame; use residual only for incomplete conditions.

Exclusion is not residual.

Informational regime

Treating externally readable content as identity-bearing throughput.

Require distinctions physically carried by the candidate relation and available to realise, resume, complete, or close a regime.

Information must belong to the regime.

Maintained boundary

Treating visible enclosure as identity.

Ask whether the boundary participates in preserving identity-bearing throughput.

Boundary is not identity.

Attribution Locus

Attributing life to broad container or indispensable component.

Localise the operational unit whose regime is realised, resumed, completed, potentialised, closed, reconstructed, incorporated, excluded, or residual-bearing.

Attribution needs a bearer.

DTS completion

Treating dependence as binary independence/dependence.

Separate resource dependence, scaffolded support, constitutive dependence, host completion, coupled completion, and no further same-locus DTS completion after closure.

Dependence is an attribution variable.

Continuity

Confusing organisational identity, intrinsic resumability, throughput identity, lineage, reconstruction, and incorporation.

Assign the correct continuity relation before class.

Continuity determines branch status.

Formal ladder

Adding death as a fourth class or treating Life-in-Potential as weak Life.

Keep the ladder as Complex Chemistry / Life-in-Potential / Life; death is closure output / continuity status.

Ladder gives class; continuity gives status.

Closure output

Using closure output as a replacement primary class or applying it to all remnants.

Use only for closed continuity of a formerly living target locus and trigger constituent reframing.

Closure is target-locus death.

Topology

Using parasite, symbiont, organelle, tumour, or artificial support as primary classification.

Assign topology after locus, completion, continuity, and class.

Topology follows attribution.

Procedure

Turning the diagnostic sequence into a checklist of independent traits.

Preserve dependency order and field separation.

Procedure protects canon.

Residual inventory

Leaving uncertainty vague or using unresolved as a hidden field value.

Inventory the missing condition and state update conditions.

Residual localises uncertainty.

Dormant seed, spore, cyst, cryopreserved bacterium

Do not infer non-life from low activity.

Test intrinsic resumability in the same Attribution Locus and viability evidence.

Terminal organism

Do not infer death from terminality or reserve depletion.

Classify terminal active Life until branch-realisation closes for the target locus.

Free intact virion-like particle

Do not infer Life from sequence or non-life from free-phase inactivity alone.

Test identity-bearing potential throughput into admissible host-completed DTS pathway.

Productive infection and lysis

Do not assign one status to the whole scene.

Split host-cell closure, released candidate potential throughput, and non-identity-bearing debris.

Host-dependent parasite

Do not infer non-life from dependence.

Localise parasite Attribution Locus and DTS-completion relation.

Organ, tissue, or perfused support case

Do not infer organismal Life from living cells or artificial support.

Separate cellular loci, tissue-level relation, scaffolded support, and residual.

Mitochondrion or organelle

Do not infer status from lineage or organelle name.

Separate functional sublocus, constitutive dependence, maintained organisation, and residual.

Corpse or post-death remains

Do not spread organismal death to every constituent.

Use closure output for the target locus and perform constituent reframing.

Artificial or hybrid system

Do not infer life from engineering or deny life from artificial support.

Test whether the candidate itself is the Attribution Locus of driven constraint-maintenance supported by IPL-mediated NTC.

Protocell or origin-of-life model

Do not infer Life from chemistry, compartment, replication, or catalysis alone.

Ask whether chemical organisation has crossed into distinction-conditioned maintenance of its own driven regime.

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
P2-SD03 T06 R01

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
P2-SD03 T06 R02

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
P2-SD03 T06 R03

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
P2-SD03 T06 R04

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
P2-SD03 T06 R05

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
P2-SD03 T06 R06

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
P2-SD03 T06 R07

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
P2-SD03 T06 R08

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
P2-SD03 T06 R09

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
P2-SD03 T06 R10

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
P2-SD03 T06 R11

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
P2-SD03 T06 R12

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
P2-SD03 T06 R13

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
P2-SD03 T06 R14

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
P2-SD03 T06 R15

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
P2-SD03 T06 R16

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
P2-SD03 T06 R17

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
P2-SD03 T06 R18

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
P2-SD03 T06 R19

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
P2-SD03 T06 R20

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
P2-SD03 T06 R21

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
P2-SD03 T06 R22

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
P2-SD03 T06 R23

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
P2-SD03 T06 R24

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
P2-SD03 T06 R25

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
P2-SD03 T06 R26

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
P2-SD03 T06 R27

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
P2-SD03 T06 R28

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
P2-SD03 T06 R29

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
P2-SD03 T06 R30

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
P2-SD03 T06 R31

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
P2-SD03 T06 R32

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
P2-SD03 T06 R33

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
P2-SD03 T06 R34

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
P2-SD03 T06 R35

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
P2-SD03 T06 R36

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
P2-SD03 T06 R37

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
P2-SD03 T06 R38

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
P2-SD03 T06 R39

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
P2-SD03 T06 R40

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
P2-SD03 T06 R41

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
P2-SD03 T06 R42

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
P2-SD03 T06 R43

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
P2-SD03 T06 R44

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
P2-SD03 T06 R45

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.

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
P2-SD03 T13 R01

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
P2-SD03 T13 R02

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
P2-SD03 T13 R03

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
P2-SD03 T13 R04

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
P2-SD03 T13 R05

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
P2-SD03 T13 R06

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
P2-SD03 T13 R07

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
P2-SD03 T13 R08

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
P2-SD03 T13 R09

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
P2-SD03 T13 R10

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
P2-SD03 T13 R11

Signal-bearing contrast is called knowledge without retained registration.

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

A

Retention/deployment collapse
P2-SD03 T13 R12

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

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

B

KIP imagination error
P2-SD03 T13 R13

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
P2-SD03 T13 R14

Realised deployment is treated as truth or justification.

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

A

Intelligence-cognition collapse
P2-SD03 T13 R15

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
P2-SD03 T13 R16

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
P2-SD03 T13 R17

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
P2-SD03 T13 R18

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
P2-SD03 T13 R19

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
P2-SD03 T13 R20

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
P2-SD03 T13 R21

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
P2-SD03 T13 R22

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
P2-SD03 T13 R23

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
P2-SD03 T13 R24

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
P2-SD03 T13 R25

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
P2-SD03 T13 R26

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
P2-SD03 T13 R27

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
P2-SD03 T13 R28

“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
P2-SD03 T13 R29

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
P2-SD03 T13 R30

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
P2-SD03 T13 R31

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
P2-SD03 T13 R32

Observation-capacity is treated as realised observation.

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

A

Distributed-record inflation
P2-SD03 T13 R33

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
P2-SD03 T13 R34

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
P2-SD03 T13 R35

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
P2-SD03 T13 R36

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
P2-SD03 T13 R37

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
P2-SD03 T13 R38

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
P2-SD03 T13 R39

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
P2-SD03 T13 R40

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
P2-SD03 T13 R41

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
P2-SD03 T13 R42

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

Use disciplined correction of perspective under constraint.

A

Objectivity-as-consensus
P2-SD03 T13 R43

Agreement alone is treated as objectivity.

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

B

Scale-size collapse
P2-SD03 T13 R44

Scale is reduced to physical size.

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

A

Scale-unit collapse
P2-SD03 T13 R45

A unit is treated as sufficient scalar adequacy.

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

B

Scale-choice collapse
P2-SD03 T13 R46

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
P2-SD03 T13 R47

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
P2-SD03 T13 R48

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
P2-SD03 T13 R49

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
P2-SD03 T13 R50

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
P2-SD03 T13 R51

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
P2-SD03 T13 R52

Descriptor grades are used to decide whether observation occurred.

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

A

Descriptor inflation
P2-SD03 T13 R53

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
P2-SD03 T13 R54

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
P2-SD03 T13 R55

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
P2-SD03 T13 R56

Measured reach is confused with the test window.

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

B

OH/CH collapse
P2-SD03 T13 R57

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
P2-SD03 T13 R58

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
P2-SD03 T13 R59

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

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

B

OD/record-count collapse
P2-SD03 T13 R60

Depth is measured by archive size or hierarchy.

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

B

OG/consequence collapse
P2-SD03 T13 R61

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

Establish comparator-stable dependence before grading OG.

A

ODr/recalibration collapse
P2-SD03 T13 R62

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
P2-SD03 T13 R63

High sustaining cost is treated as automatic failure.

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

B

OCx/any-failure collapse
P2-SD03 T13 R64

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
P2-SD03 T13 R65

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
P2-SD03 T13 R66

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
P2-SD03 T13 R67

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
P2-SD03 T13 R68

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
P2-SD03 T13 R69

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
P2-SD03 T13 R70

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
P2-SD03 T13 R71

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
P2-SD03 T13 R72

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
P2-SD03 T13 R73

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
P2-SD03 T13 R74

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
P2-SD03 T13 R75

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
P2-SD03 T13 R76

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
P2-SD03 T13 R77

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.

Class A - Mechanical inconsistency

Breaks the architecture.

Redefining upstream terms downstream; treating every cause as Power; role as provenance; method-compliance as closure; carrier as warrant.

Correct before finalisation.

Class B - Terminology drift

Creates ambiguity or future misuse.

Using horizon without availability/closure demand; Power without CIF/locus; Responsibility without attribution target; Trust without closure demand; formalisation without consequence trigger.

Correct before compression or publication.

Class C - Presentation ambiguity

May mislead despite intact architecture.

“Unknown” sounds blank; “power” sounds authority; “responsibility” sounds blame; “trust” sounds moral virtue; “constitutional” sounds immutable; “audit” sounds certification.

Clarify through ownership note, discriminator, residual, or diagnostic question.

Source-lock drift
P3-SD03 T06 R01

Superseded papers/support wording or unverified material re-enters as current Part 3 source.

Return to eight current paper hashes and listed controls.

A

Can every technical claim be traced to a current canonical paper or permitted upstream control?

Canonical ownership drift
P3-SD03 T06 R02

A support document or later paper silently redefines an earlier canonical term.

Return the definition to the owning paper; use downstream content only as alignment pressure.

A

Which paper owns the discriminator?

Section back-propagation
P3-SD03 T06 R03

3b or 3c vocabulary is pre-installed into 3a because it later proves compatible.

Preserve directional inheritance; revise upstream only for actual inconsistency in its owned relation.

A

Would the upstream paper still state the relation without the later vocabulary?

Inheritance by repetition
P3-SD03 T06 R04

Repeated citation or use across papers is treated as Indexed Inheritance.

Keep citation, comparator, dependency, and inheritance separate.

A

Has a separate inheritance audit promoted the relation?

Locus drift
P3-SD03 T06 R05

Target, carrier, observer, affected locus, applying locus, and responsible locus are silently merged.

Re-index the relation at each material transformation.

A

For whom/what does the claimed relation hold here?

Scale/horizon drift
P3-SD03 T06 R06

A claim travels across scale or horizon without preserving its comparator and access conditions.

Restate reference scale/horizon and show a valid bridge.

B

What changed when the claim moved?

Horizon objectification
P3-SD03 T07 R01

A horizon is treated as a place, object, metaphysical zone, or fixed edge.

Restore the availability/closure boundary relation.

A

What relation, locus, availability condition, and closure demand produce the boundary?

Gödel inflation
P3-SD03 T07 R02

Any uncertainty, difficulty, ignorance, or limitation is labelled a Gödel Horizon.

Require available/formulable relation plus disclosed failure of closure from the present regime’s own resources.

A

Is the closure failure actually internal to the stated regime and demand?

Procedural overclaim
P3-SD03 T07 R03

A describable experiment, proof path, evidence path, or process is treated as if realised.

Mark Procedural Availability Horizon and withhold closure until the path exists.

A

Can the required path actually be executed by the locus?

Soft-Horizon reification
P3-SD03 T07 R04

Provisional closure travels as final warrant.

Carry residual, scope, comparator/tolerance, purpose, and update with the closure.

A

What remains unresolved and what would force update?

Unknown flattening
P3-SD03 T07 R05

All unresolved relation becomes one generic unknown.

Type unknown-status by availability and closure condition.

B

Is the relation unavailable, unrecognised, misclosed, residual, live, weighted, or action-bound?

Residual laundering
P3-SD03 T07 R06

Residual is mentioned but allowed to do no limiting work.

State what stronger claim is blocked and what update would change it.

A

Does the residual change claim-strength or action limits?

Live-field equality
P3-SD03 T07 R07

All live formulations are treated as equally supported because final closure is absent.

Weight heterogeneously and retain positive exclusions.

B

What evidence/comparator/scale support differentiates them?

BAF closure inflation
P3-SD03 T07 R08

Best Available Formulation is treated as final truth.

Retain its purpose type, residual, alternatives, and update conditions.

A

What stronger closure demand remains unmet?

Action-certainty conversion
P3-SD03 T07 R09

Action taken under threshold is later narrated as proof or truth.

Separate action threshold from truth/explanatory closure; preserve branch-memory.

A

Would the claim have been equally strong if no action had been required?

Stabilisation hindsight
P3-SD03 T07 R10

Realised outcome erases what alternatives were live or knowable beforehand.

Preserve contemporaneous live field, exclusions, and update history.

B

What was actually available to the locus at the time?

Cause-to-Power collapse
P3-SD03 T08 R01

Any causal contribution is called Power.

Require IPL-localised distinction-conditioned branch potential under comparator pressure.

A

Would the branch field differ because this organisation can make a discrimination operative?

Power-as-force
P3-SD03 T08 R02

Energetic magnitude or visible effect substitutes for the discriminator.

Separate causal magnitude from distinction-conditioned potential.

A

Is organised discrimination doing the branch-changing work?

Power-as-authority
P3-SD03 T08 R03

Role, office, command, status, permission, or possession is treated as primitive Power.

Recover the physically supported CIF of the specified locus.

A

What branches are actually included by the locus’s organisation?

Imagined-CIF inflation
P3-SD03 T08 R04

Exterior analyst imagination populates the CIF with unrealised but physically unsupported futures.

Include only branches supported by the IPL under stated conditions.

A

What physical path makes each claimed branch available?

Potential/application collapse
P3-SD03 T08 R05

Possessing a power potential is treated as equivalent to present application or consequence.

Keep potential, application, and consequence distinct.

B

Which part of the relation is currently established?

CE agency inflation
P3-SD03 T08 R06

Counterfactual Exclusion is read as conscious choice, rejection, or metaphysical deletion.

Restore it as the negative side of a realised distinction-conditioned branch event.

B

Was a relevant included alternative simply not equivalently realised?

Thermodynamic escape
P3-SD03 T08 R07

Branch-changing power is treated as abstract information unconstrained by physical work/entropy.

Retain physical carriers and lawful thermodynamic accounting.

A

What substrate and energetic pathway carry the distinction and transition?

Causation-to-Responsibility collapse
P3-SD03 T09 R01

Every cause becomes Responsibility.

Follow only the distinction-conditioned subset of causal provenance.

A

What local discrimination/organisation did consequential work?

Blame inflation
P3-SD03 T09 R02

Primitive Responsibility is treated as blame, guilt, desert, duty, or legal liability.

Keep mature warrant regimes downstream of primitive attribution.

A

Is the claim causal-attributional or normative/allocative?

Provenance transfer
P3-SD03 T09 R03

Responsibility is treated as a token passed from one locus to another.

Localise each material transformation; provenance composes but does not simply transfer.

A

What did each locus actually transform, retain, apply, maintain, or update?

Proximity shortcut
P3-SD03 T09 R04

Nearest physical actor is assigned the whole responsibility path.

Recover upstream and downstream distinction-conditioned transformations.

A

Which earlier conditions remained materially operative?

Upstream absorption
P3-SD03 T09 R05

An early contributor is made responsible for all later consequences.

Test whether later loci corrected, replaced, ignored, or transformed the relation.

A

Did the upstream distinction remain operative in the later branch?

Exterior hindsight attribution
P3-SD03 T09 R06

Evaluator uses information unavailable to the locus at the time.

Apply the Immediate-Frame Principle.

A

Was the relevant relation materially available or recoverable then?

Interior frame laundering
P3-SD03 T09 R07

A capable locus retrospectively narrows its stated frame to exclude warnings or alternatives that were actually available.

Reconstruct frame from recoverable paths, not self-description alone.

A

What channels, records, warnings, or correction paths existed?

Warrant-as-provenance
P3-SD03 T09 R08

Role, duty, liability, answerability, or institutional allocation is treated as causal provenance.

Keep Responsibility Warrant separate and explicitly related to provenance.

A

What does the warrant allocate, and what causal path does it not establish?

Gradient moralisation
P3-SD03 T09 R09

Responsibility Gradient becomes a universal moral score.

Keep it ordinal/relational and tied to capacity plus actual provenance.

B

Is the gradient describing capacity or allocating blame?

Trust-as-certainty
P3-SD03 T10 R01

Reliance closure is narrated as proof, confidence without residual, or total transparency.

Restore residual, threshold, and update.

A

What remains unaudited while reliance proceeds?

Trust-carrier reification
P3-SD03 T10 R02

Carrier is treated as trust ground because it bears a credential, role, record, or institutional mark.

Recover the closure process the carrier is standing in for.

A

What work did the carrier actually earn?

Trust laundering
P3-SD03 T10 R03

Reliance-strength earned in one relation is spent in another.

Re-index relation, carrier, closure demand, residual, and scope.

A

What changed between the relation that earned trust and the relation now relying on it?

Borrowed-closure warrant transfer
P3-SD03 T10 R04

Vicarious trust is treated as automatic transfer of warrant or Responsibility Provenance.

Keep outsourced closure, reliance, and provenance distinct.

A

What is merely relied upon versus causally attributable?

Audit/trust opposition
P3-SD03 T10 R05

Audit is treated as evidence that trust has failed, or trust as elimination of audit.

Treat audit as the reopening function that preserves corrigibility.

B

What condition should foreground the backgrounded relation again?

Repair by reassurance
P3-SD03 T10 R06

Trust repair is asserted by apology, branding, certification, or reassurance without changing the failed relation.

Recover and alter the failure-generating conditions; narrow/refuse trust if needed.

A

What changed in the carrier, process, safeguard, or update path?

Unshared-comparator authority
P3-SD03 T10 R07

A locus is preferred for one relation using success on another relation, scale, horizon, or closure demand.

Recover the shared target relation and comparable closure demand, availability, abstraction, scale, and horizon (3b-5 §8).

A

Does the demonstrated advantage concern the relation and use now claimed?

Confidence as epistemic standing
P3-SD03 T10 R08

Confidence, precision, quick closure, or reduced expressed doubt is taken as demonstrated epistemic advantage.

Test relation-preservation and the treatment of residual; no single numerical uncertainty measure is required (3b-5 §8).

A

Could the apparently weaker contribution be exposing residual that the confident one conceals?

Relative advantage as sufficient closure
P3-SD03 T10 R09

The stronger of two contributions is treated as adequate for a use that neither can support.

Retain the closure demand and residual limits; actionability cannot replace demonstration (3b-5 §8).

A

Is the advantage sufficient for this reliance, or only for further inquiry?

Carrier-path loss of advantage
P3-SD03 T10 R10

Standing at the contributing locus is assumed to survive a stale record, altered abstraction, or misleading interface.

Recover both the target relation and the carrier relation for present use (3b-5 §8; 3c-8 §6).

A

What epistemic advantage actually reaches the relying locus?

Recognition as epistemic ground
P3-SD03 T10 R11

A contribution acquires supposed standing merely because it is trusted, adopted, or used.

Separate earned standing from actual reliance. Trust makes standing operative but does not create it (3b-5 §8).

A

Would the demonstrated standing remain if the contribution were untrusted or unused?

Authority-type substitution
P3-SD03 T10 R12

Structural permission is treated as epistemic standing, or epistemic standing as permission to act or decide.

Apply the two definitions in 3b-5 §8 independently; retain scoped authorisation and demonstrated relation-preservation.

A

Which authority is established, and what would establish the other?

Consequence as epistemic warrant
P3-SD03 T10 R13

The occurrence or magnitude of an effect retrospectively establishes the epistemic standing of the relied-upon contribution.

Apply the Power discriminator to the branch difference and the Epistemic Authority discriminator to standing (3b-5 §8).

A

What demonstrated the relation-preserving advantage before consequence was used to validate it?

Universal formalisation
P3-SD03 T11 R01

All language is forced into rigid formal structure.

Apply formalisation only where language/output becomes load-bearing and proportionate to consequence.

B

What consequential work triggers the formalisation burden?

Form-completion closure
P3-SD03 T11 R02

Completed fields/forms are treated as proof that the relation is preserved.

Audit the relation and paths, not packet completion.

A

Could every field be filled while the target relation remains wrong?

Machine execution laundering
P3-SD03 T11 R03

Automation or consistency is treated as repair of upstream under-specification.

Recover training/data/model/interface/decision paths and unresolved abstractions.

A

What relation did the machine actually preserve?

Record-as-warrant
P3-SD03 T11 R04

A retained record or documented provenance is treated as epistemic warrant by default.

Separate record/provenance from adequacy and closure.

A

What comparator or evidence shows the record preserves the claimed relation?

Epistemic-debt concealment
P3-SD03 T11 R05

Deferred grounding burden is hidden behind stable terminology or process.

Make debt visible as missing relation/path/update obligations.

B

What grounding work has been postponed?

Retrospective outcome bias
P3-SD03 T11 R06

Good outcome is treated as evidence the original decision path was strong.

Audit decision quality under the information and conditions available at decision time.

A

Would the path still be judged strong under a different outcome?

Authorisation-path substitution
P3-SD03 T11 R07

The mandate governing a claim’s use substitutes for the evidence path that supports its epistemic standing.

Keep structural authorisation and epistemic grounding separately recoverable (3c-6 §1; 3b-5 §8).

A

Does permission to use the claim establish why its target relation is preserved?

Adoption-as-validation
P3-SD03 T12 R01

Institutional uptake or implementation scale is treated as evidence the method is correct.

Keep operational adoption distinct from epistemic authority.

A

What relation-preservation was demonstrated independently of adoption?

Custodial-authority inflation
P3-SD03 T12 R02

Stewardship of releases/archives is treated as ownership of epistemic validity.

Treat custody as an application of Structural Authority; recover release and correction records without promoting stewardship into epistemic standing (3c-7 §6; 3b-5 §8).

A

Could a steward be wrong while remaining the steward?

Operational-authority inflation
P3-SD03 T12 R03

Institutional authority to apply the method becomes authority to redefine it epistemically.

Treat domain authority as an application of Structural Authority; distinguish scoped permission from the epistemic amendment burden (3c-7 §§6–7).

A

Is this an application decision or a technical/constitutional revision?

Preference amendment
P3-SD03 T12 R04

Method changes because of convenience, vote, politics, adoption pressure, or author preference.

Require demonstrated relational failure and comparative improvement.

A

What relation does the current formulation fail to preserve?

Founding-text ownership
P3-SD03 T12 R05

Originating author/text is treated as immune from correction.

Preserve provenance but deny epistemic ownership.

A

Would a demonstrated counterexample force revision regardless of authorship?

Constitutional-label capture
P3-SD03 T12 R06

The highest-level label is used to block challenge.

Raise the burden of revision, not immunity to revision.

A

What would count as demonstrated failure of the proposed constitutional element?

Fork-as-truth
P3-SD03 T12 R07

Existence or popularity of a competing fork is treated as evidence of superiority.

Compare relation-preservation, residual, scope, and failure conditions.

B

What does the fork preserve better and at what cost?

Certification closure
P3-SD03 T12 R08

Certificate becomes general epistemic ground beyond what was assessed.

Bound certification to assessed relation, scope, residual, and re-audit conditions.

A

What exactly was certified, and what was not?

Method universalisation
P3-SD03 T13 R01

Epistemic Method is used as a substitute for science, law, ethics, judgement, or domain expertise.

Use it as relational audit discipline only.

A

What domain-specific burden remains external to the method?

Method-compliance closure
P3-SD03 T13 R02

Method-use or completion is treated as epistemic certificate.

Return strength to demonstrated relation-preservation.

A

What claim would remain weak even after perfect procedural compliance?

Path flattening
P3-SD03 T13 R03

Claim path, evidence path, record path, carrier path, and reliance path are collapsed.

Recover each load-bearing path separately.

A

Where did content, evidence, record, authority, and reliance each enter?

Claim/reliance-strength collapse
P3-SD03 T13 R04

A strong claim is assumed equally safe to rely upon for every locus/purpose, or vice versa.

Index reliance to the relying locus’s closure demand and limit.

A

Does the reliance purpose require more than the claim itself establishes?

Conditional-path universalisation
P3-SD03 T13 R05

CIF/CE or Responsibility Provenance fields are required for claims that do not engage Power/Responsibility.

Activate relation-specific audits only when the claim triggers them.

B

What relation-specific claim is being made?

Audit paralysis
P3-SD03 T13 R06

Residual is used to prevent all finite action.

Permit action under threshold with proportionate safeguards and update where justified.

B

What action burden exists despite incomplete closure?

Audit theatre
P3-SD03 T13 R07

Visible review process substitutes for discriminatory comparator pressure or correction.

Require actual potential to expose error, weaken claims, refuse closure, or force update.

A

Can the audit produce a materially adverse result for the claim?

Preferential-reliance shortcut
P3-SD03 T13 R08

Comparison favours another locus without establishing the advantage for the shared relation and closure demand or its survival through the carrier.

Apply the comparator burden where preferential reliance is claimed (3c-8 §6), inheriting 3b-5 §8.

A

What advantage supports this reliance at the receiving locus?