1) Diagnostic Identity

Diagnostic Name: Signal Localization Quality

Short Name / Symbol: signal_localization_quality

Diagnostic Class: Signal Localization / Source Attribution / Layer Mapping / Causal Routing / Classification Readiness

Primary Function: Estimate whether a signal has been mapped to the correct source, node, boundary, subsystem, U-layer, cause, timescale, or coupling pathway.

Primary Use: Determine whether the system is interpreting a signal at the right location before classification, repair, attribution, constraint design, memory binding, or escalation.

Core Risk if Ignored: The system may correctly detect a signal but repair, classify, blame, constrain, or remember the wrong thing, causing misrepair, false attribution, boundary error, recurrence, and hidden debt.

Core Risk if Overtrusted: Once a signal appears localized, the system may stop searching for layered, distributed, coupled, delayed, or upstream causes.

2) Mechanical Definition

signal_localization_quality measures how accurately a signal is mapped to the place, layer, source, timescale, interface, or causal pathway from which it actually arises.

signal_localization_quality answers:

Are we locating this signal where it truly belongs?

This diagnostic is distinct from signal_quality.

• signal_quality asks whether the signal itself is clean, reliable, timely, and usable.
• signal_localization_quality asks whether the signal is being assigned to the correct source, U-layer, subsystem, node, or cause.

A signal may be high quality but poorly localized.

Example:

The report accurately shows recurring execution failure at U3,
but the origin is actually a U2 permission design flaw or U4 classification error.

In that case, signal_quality may be high, but signal_localization_quality is low.

Localization matters because repair must occur at the same or lower U-layer than the failure origin. If the signal is localized incorrectly, the system may repeatedly repair symptoms while the origin layer continues producing recurrence.

3) What the Diagnostic Measures

Direct Measurement Target

signal_localization_quality measures:

• source localization
• U-layer localization
• causal localization
• subsystem localization
• node localization
• boundary localization
• coupling-path localization
• timescale localization
• recurrence localization
• failure-origin localization
• symptom-versus-cause distinction
• whether signal belongs to local behavior or upstream structure
• whether signal belongs to a node, interface, environment, or coupling pattern
• whether repair target matches signal origin
• whether attribution follows actual causal location

Indirect / Proxy Signals

signal_localization_quality can be estimated from:

• recurrence after repair
• repair working only temporarily
• repeated misclassification
• same signal appearing across multiple nodes
• signal moving through a coupling path
• mismatch between local fix and global recurrence
• affected-node reports pointing to different origin than official classification
• high-quality signal producing low-quality repair
• visible symptom disappearing while hidden debt persists
• delayed cause-effect timing
• cross-layer contradictions
• U3 behavior explained by U2 permissions
• U4 narrative error producing U3 execution failure
• U8 forcing mistaken for internal failure
• one node being blamed for system-wide signal
• signal disappearing only when upstream condition changes

What It Does Not Measure

signal_localization_quality does not directly measure:

• whether the signal is clean
• whether the signal is true
• whether a signal is important
• whether a repair is available
• whether the localized node is morally responsible
• whether attribution is complete
• whether one localization explains all causes
• whether localization should be permanent
• whether a signal has only one source
• whether a high-confidence localization is final
• whether the system should ignore diffuse causes

High signal_localization_quality means the system likely knows where the signal originates or where it should be repaired.

It does not mean the signal has only one cause.

Low signal_localization_quality means the system may be acting at the wrong layer, node, or pathway.

It does not mean the signal itself is invalid.

4) Canonical State Variables Involved

Canonical state vector:

S = {O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ}

Primary Variables

• Au: localization depends on traceability across source, timing, layer, and consequence
• H: hidden debt often persists when signal is repaired at the wrong location
• ε: visible error is frequently a symptom, not origin
• R: restoration capacity must reach the correct layer to reduce recurrence
• O: coherence depends on matching interpretation and repair to actual origin
• K: coupled systems require localization across interface pathways

Secondary Variables

• ι: inversion risk rises when mislocalized signal supports false coherence or false blame
• µᵢ: agent integrity is damaged when actions or responsibility are assigned to the wrong source
• BΣ: boundary strain may be mislocalized as individual failure, conflict, or noise
• Φ: proxy pressure may localize signals where repair is cheapest or reputation-preserving rather than accurate

Variables Commonly Confused With signal_localization_quality

5) Localization Signature

Primary Legibility Layers

• U3 — Execution: where symptoms often appear as behavior, output, delay, error, or deviation
• U4 — Classification / Metrics / Narratives: where signal may be misread, labeled, or assigned
• U5 — Coordination / Time: where sequence, delay, handoff, and timing reveal origin
• U6 — Coherence Field: where distributed or emergent causes become visible
• U7 — Memory / Recurrence: where recurring patterns reveal prior mislocalization
• U8 — Environment / Forcing: where external pressure may be mistaken for internal failure

Primary Leverage Layers

• U2: inspect configuration, permissions, constraints, gates, and boundary rules
• U3: inspect runtime behavior and execution pathways
• U4: inspect classification, metrics, models, and narrative mapping
• U5: inspect timing, coordination, escalation, and sequence
• U6: inspect cross-domain coherence effects
• U7: inspect recurrence and prior repair history
• U8: inspect external shocks, adversarial pressure, and environmental load

Verification Layers

• U3: does the visible symptom match the proposed origin?
• U4: is the signal being classified at the correct layer?
• U5: does timing support the proposed causal sequence?
• U6: does whole-system coherence improve after local repair?
• U7: does recurrence decline when the proposed origin is repaired?
• U8: does the signal disappear when external forcing changes?

Common Mislocalizations

• Treating U3 symptom as U3 cause
• Treating U4 classification failure as U3 behavior failure
• Treating U2 boundary design failure as individual noncompliance
• Treating U5 coordination delay as lack of will
• Treating U8 forcing as internal defect
• Treating system-wide signal as one-node failure
• Treating interface failure as node failure
• Treating recurring pattern as new isolated event
• Treating boundary strain as relational conflict
• Treating proxy divergence as performance problem only
• Treating affected-node report as merely subjective when it localizes real burden
• Treating official metric location as actual cause location

6) Input Requirements

Required Inputs

To estimate signal_localization_quality, the system needs:

• signal being localized
• visible symptom location
• suspected origin location
• candidate U-layers
• affected variables in S
• timing / sequence data
• source path
• coupling path
• boundary conditions
• prior recurrence history
• prior repair attempts
• affected-node feedback
• current classification
• evidence for and against each candidate localization
• proposed repair target
• whether repair at the proposed location reduces recurrence

Optional Inputs

These improve precision:

• causal map
• dependency map
• interface map
• U-layer trace
• event timeline
• historical incident records
• stress-test results
• external forcing timeline
• source-to-summary trail
• logs and execution traces
• permission / configuration history
• metric lineage
• appeal or correction history
• affected-node cost distribution
• cross-node comparison
• repair outcome data
• counterfactual tests
• local-versus-global signal comparison

Missing Input Behavior

If signal_localization_quality inputs are missing:

• If timing is missing, avoid strong causal localization
• If candidate layers are not mapped, do not assume U3 symptom is origin
• If recurrence data is missing, treat repair-target confidence as provisional
• If affected-node feedback is missing, burden location may be under-sampled
• If coupling path is unknown, avoid assigning cause to one node only
• If U8 forcing is unknown, avoid internal-only localization
• If prior repair attempts are unknown, recurrence may be misread as new failure
• If Au_eff is low, treat localization confidence as low
• If AP(t) is high, check for blame-driven localization distortion

Default missing-input posture:

map symptom → map candidate origins → check U-layer/timing/coupling → repair provisionally → validate recurrence

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Signal is mapped to the correct origin, layer, pathway, or repair target with enough confidence for action.

Signals:

• symptom and origin are distinguished
• U-layer is identified
• timing supports causal path
• coupling path is visible
• affected-node reports align with localization or are explained
• repair at origin reduces recurrence
• local fix improves whole-system coherence
• attribution does not outrun causal mapping
• U7 memory stores localization with provenance
• external forcing is accounted for

Recommended posture:

Μ causal mapping can proceed
Γ repair target selection allowed
ℛ at origin layer
U7 localization memory update
bounded Δ retest

Watch Range

Localization is plausible but partial, uncertain, layered, or not yet recurrence-tested.

Signals:

• multiple candidate origins remain
• U-layer is suspected but not confirmed
• timing is incomplete
• coupling path is partly visible
• repair may be addressing symptom
• recurrence window has not passed
• affected-node feedback suggests unresolved origin
• local improvement occurs but global coherence is unverified

Recommended posture:

keep classification provisional
increase Au_eff
run Δ localization tests
avoid hard attribution
delay durable U7 binding

Degraded Range

Signal is likely being localized incorrectly.

Signals:

• same failure recurs after repair
• local fix does not improve system coherence
• blame concentrates on visible symptom node
• U3 behavior is repeatedly repaired while U2/U4/U5 causes persist
• official localization conflicts with affected-node burden
• signal appears across multiple nodes
• repair reduces visible ε but H remains
• attribution hardens before causal map stabilizes
• wrong layer receives resources

Recommended posture:

pause repair-complete claims
reopen localization
activate Au / Ξ
map U-layers and coupling paths
repair at origin layer

Contraindicated:

punitive attribution
hard Γ from current localization
irreversible Π
durable U7 memory binding
scaling repair pattern
deep coupling based on false localization

Critical / Collapse-Prone Range

Signal localization is captured, inverted, or systematically wrong.

Signals:

• wrong nodes repeatedly carry blame or repair burden
• true origin is protected by rank, structure, metric, or narrative
• repair repeatedly fails but localization does not change
• official memory stores false cause
• hidden debt accumulates around mislocalized repair
• recurrence becomes normalized
• affected-node reality is overwritten
• system cannot name origin without legitimacy shock
• external audit is required to reconstruct cause

Recommended posture:

freeze attribution and closure
preserve evidence
activate Ξ / Au / FI / MS
reconstruct causal map
repair memory contamination
redirect ℛ to origin layer
validate over recurrence

False Positive Risk

signal_localization_quality may appear high when:

• local repair temporarily suppresses symptoms
• visible node is easiest to inspect
• official metrics point to symptom location
• high-status source confirms preferred localization
• recurrence window has not passed
• affected-node reports are absent
• external forcing is temporarily reduced
• hidden upstream cause has not reactivated
• repair at wrong layer improves Φ but not O

False Negative Risk

signal_localization_quality may appear low when:

• cause is genuinely distributed
• multiple layers contribute
• repair at one layer has delayed effects
• recurrence reflects old debt surfacing during real repair
• affected-node reports conflict because burden is distributed
• external forcing changes signal expression
• localization is correct but R_eff is too low for visible improvement
• signal origin shifts over time

8) Leading Indicators

signal_localization_quality degradation appears early as:

• repair targets symptoms repeatedly
• different teams name different origins
• visible node receives most scrutiny
• affected-node reports point elsewhere
• recurrence appears after “fix”
• U-layer language is absent
• timelines are vague
• blame emerges before causal map
• “root cause” is named too quickly
• metrics point to one place while behavior points to another
• repair resources go to the most visible layer
• external forcing is ignored
• interface effects are treated as node defects
• same pattern appears in multiple places
• local success fails to propagate

9) Lagging Indicators

signal_localization_quality failure has already accumulated debt when:

• recurrence becomes normal
• repair backlog grows around the wrong layer
• affected nodes stop trusting diagnosis
• false attribution becomes durable memory
• hidden debt surfaces from protected origin
• external audit overturns causal story
• local patches become permanent
• wrong nodes exit or carry repeated burden
• system cannot explain why repairs fail
• legitimacy shock follows origin exposure
• repair cost rises because early localization was wrong
• old signal is revealed as upstream, systemic, or environmental

10) Interpretation Rules

How to Read signal_localization_quality

signal_localization_quality should be read as:

context-specific accuracy of source, layer, pathway, and repair-target mapping

It is not a claim that one origin explains all signal.

A system may have:

• high signal_quality and low localization quality
• low signal_quality but useful localization clue
• local symptom at U3 with origin at U2
• visible failure at one node with cause in interface design
• correct localization but insufficient R_eff
• distributed localization across layers and nodes
• shifting localization as recurrence reveals deeper origin

What Changes Its Meaning

signal_localization_quality changes meaning under:

• low Au_eff
• high AP(t)
• high Φ − O
• high X_c(t)
• high Cv(t)
• low EB
• weak FI_integrity
• low M_int(t)
• high dependency_load
• high coupling depth
• high U8 forcing
• rank asymmetry
• short τ_resp(t) pressure
• durable U7 memory risk
• previous repair failure

Context Modifiers

Low Au_eff: origin cannot be traced reliably.

High AP(t): attribution pressure may localize toward convenient blame.

High Φ−O: metrics may point to proxy location, not coherence origin.

High X_c(t): complex rules may obscure actual source.

High Cv(t): pressure may force premature localization.

Low EB: missing signals may hide true origin.

Weak FI: wrong localization may not be falsified.

Low M_int(t): prior false localization may contaminate current diagnosis.

High U8 forcing: environmental pressure may be mistaken for internal failure.

Domain Calibration Notes

signal_localization_quality should be calibrated by domain:

• in engineering: mapping bugs to code, architecture, configuration, dependency, environment, or process
• in AI: mapping failures to model, prompt, retrieval, tool, memory, policy, evaluation, or user-context layer
• in institutions: mapping failure to individual action, policy, incentive, process, authority, resource, or culture
• in governance: mapping outcomes to law, implementation, enforcement, budget, agency, environment, or public interface
• in relationships: mapping conflict to action, boundary, timing, assumption, pattern, interface, or external pressure
• in archives: mapping drift to glossary, spec, cross-link, canon status, source loss, or summary compression

11) Operator Sequencing Implications

If signal_localization_quality Is Healthy

Allowed with ordinary gate checks:

• Μ can build causal model from localized signal
• Γ can select repair target
• Π can redesign constraints at the correct layer
• ℛ can repair origin rather than symptom
• Δ can retest localization
• AP(t) can be handled with lower distortion risk
• U7 can store localization memory with provenance

Recommended:

signal → localization map → Μ causal model → Γ repair target → ℛ origin-layer repair → Δ recurrence test → U7 update

If signal_localization_quality Is Low

Recommended:

pause closure → preserve evidence → map candidate origins → inspect U-layers/coupling/timing → test localization → then repair

Or:

treat current location as symptom → search for origin → keep attribution provisional

Avoid or delay:

• hard attribution
• punitive action
• irreversible Π
• repair-complete claims
• durable U7 cause memory
• deep ⊗ based on diagnosis
• scaling the repair pattern
• narrowing to one cause too early

Operators Recommended Under Low signal_localization_quality

• Ψ: increase direct observation across layers
• Au: reconstruct causal trace
• Μ: build provisional multi-candidate model
• Θ: damp certainty
• Δ: test candidate localizations
• Ξ: detect false localization or protected origin
• Γ: select reversible investigation steps
• ℛ: repair only after origin confidence improves

Operators Contraindicated Under Low signal_localization_quality

• Γ hard selection: may select wrong repair target
• Π irreversible constraint: may encode misdiagnosis
• ⊗ deep coupling: may spread unresolved origin debt
• ⊕ composition: may embed false causal memory
• Τ acceleration: outruns diagnosis
• Σ escalation: may sacralize wrong cause
• ✕ force: may punish or override at wrong location

12) Gate Implications

Gates Strengthened By Reliable signal_localization_quality

• FI-Gate: feedback can falsify wrong localization
• Au-Actuation: traceability supports origin-layer action
• HR-Gate: prevents identity-bound conclusions from mislocalized signal
• MS-Gate: checks whether localization burden or blame is symmetrical
• ☷ᵢ: principle constraints can target the correct layer and boundary

Gates Weakened If signal_localization_quality Is Poor or Unknown

If localization quality is low:

• FI may receive signal but route it to wrong target
• Au may trace symptoms without finding origin
• HR may bind identity to a mislocalized cause
• MS may miss false blame or burden export
• ☷ᵢ may constrain the wrong layer
• Π may harden around symptoms
• Γ may select ineffective repair
• ℛ may reduce ε while H persists

Gate Outcomes Affected

Low signal_localization_quality should push gates toward:

• Pause
• Require U-layer mapping
• Require timing reconstruction
• Require candidate-origin review
• Require recurrence validation
• Deny hard attribution
• Deny repair-complete claims
• Deny durable cause memory
• ∅ for high-impact action when origin localization is uncertain

13) Scaling Behavior

signal_localization_quality becomes harder under scale because signals travel through layered systems, multiple agents, interfaces, abstractions, metrics, and time delays.

As systems scale:

• symptoms appear far from causes
• signal passes through many relays
• summaries strip localization data
• local nodes are blamed for upstream design
• interfaces hide coupling effects
• U8 forcing is hard to separate from internal failure
• metrics point to measurement location rather than cause
• recurrence appears under different names
• repair targets the most visible node
• accountability pressure pushes convenient localization
• low-rank nodes carry visible symptoms
• high-rank decisions become hard to localize
• memory stores simplified root-cause stories

Scaling Risks

• false root cause
• misrepair
• scapegoating
• protected-origin failure
• symptom patching
• recurrence
• memory contamination
• repair theater
• interface blindness
• metric-location bias
• official diagnosis drift
• hidden debt accumulation
• legitimacy shock after true origin exposure
• affected-node burden export
• systemic cause individualized

Scaling Requirements

To scale localization safely, systems need:

• U-layer mapping
• causal tracing
• timing preservation
• coupling maps
• dependency maps
• source-to-summary lineage
• affected-node signal access
• recurrence tracking
• repair outcome validation
• candidate-origin review
• external forcing analysis
• interface diagnosis
• protected-origin checks
• rank-symmetry review
• memory provenance for root-cause claims
• post-repair stress testing

Scaling Rule

Signal localization must scale with coupling depth, system layering, consequence severity, and repair irreversibility.

Sanity constraint:

Low signal_localization_quality + high R_eff claim ⇒ repair theater risk ↑

If origin localization is poor, claimed repair may target the wrong thing.

Second constraint:

Low signal_localization_quality + high AP(t) ⇒ false attribution risk ↑

If localization is uncertain and attribution pressure is high, blame or responsibility assignment becomes unstable.

Third constraint:

Low signal_localization_quality + durable U7 binding ⇒ false-cause memory risk ↑

If poor localization becomes memory, future diagnosis inherits distortion.

14) Interaction / Coupling Behavior

signal_localization_quality reveals whether a relation, institution, interface, AI system, or archive can distinguish where a signal truly originates.

What It Reveals About Coupling

• whether a signal belongs to one node or the interface
• whether one node is reacting to another’s downstream symptom
• whether coupling transmits hidden debt
• whether repair burden is being assigned to the visible node
• whether external forcing is entering through the relation
• whether boundary strain is being mislocalized as behavior
• whether compatibility is being judged from misread signal
• whether recurrence belongs to a node, pattern, or shared interface

What It Reveals About Boundary Integrity

Boundary integrity depends on correct localization.

When localization is poor:

• boundary breach may be misread as conflict
• refusal may be misread as hostility
• strain may be blamed on the wrong node
• permission design may be ignored
• BΣ repair may target behavior rather than boundary conditions
• repeated boundary signals may be treated as new issues
• crossing effects may be misassigned

What It Reveals About Compatibility

Compatibility requires accurate localization of difference.

A coupling may be unsafe if:

each node localizes the same signal to the other node rather than the interface

or:

the relation repeatedly repairs symptoms while the origin remains in timing, permission, expectation, or boundary design

Healthy compatibility requires the capacity to locate signal without immediate blame or abstraction.

Relevant Interface Acts

• ↺ Reflection: compare where each node locates the signal
• ⇩ Relaxation: reduce pressure so localization can improve
• ⊘ Attenuation: reduce coupling while origin is uncertain
• ⊙ Alignment: inspect one’s own layer before assigning outward cause
• →? Invitation: invite clarification rather than impose localization
• ⚕︎ Restorative Override: requires post-action localization audit
• ✕ Force: high risk when localization is uncertain

15) Failure Modes Detected

Primary Failure Modes

signal_localization_quality detects or predicts:

• misrepair
• false attribution
• symptom patching
• recurrence
• protected-origin failure
• interface blindness
• U-layer confusion
• root-cause drift
• boundary misread
• metric-location bias
• affected-node burden export
• false-cause memory
• repair theater
• escalation at wrong layer
• system failure individualized
• environmental forcing misread as internal failure
• classification lock-in from wrong source

Composite Regimes Where signal_localization_quality Matters

• Crisis Loop: repair targets symptom, recurrence returns
• Goodhart Collapse: metrics localize attention to proxy rather than coherence origin
• LOS: formal diagnosis misses latent operational cause
• Extraction Regime: cost-bearing node is blamed for upstream structure
• Coercive Fusion: interface signal is assigned to one node’s identity
• Mission Lock: signals challenging trajectory are localized elsewhere
• Taboo Lock: protected origin cannot be named
• Pseudo-Coherent Basin: wrong localization stabilizes apparent order
• Repair Theater: repair claims target visible layer while origin persists

16) Accountability & Reintegration Implications

If signal_localization_quality Was Ignored

Likely consequences:

• repair targeted the wrong layer
• visible node carried false responsibility
• recurrence persisted
• hidden debt accumulated
• official memory stored false cause
• attribution became distorted
• affected-node burden increased
• boundary issues were misclassified
• system continued scaling a flawed repair pattern
• true origin became harder to name later

Accountability questions:

• Where did the signal appear?
• Where did it originate?
• What U-layer produced it?
• What pathway transmitted it?
• Was the visible node also the cause?
• Did repair at the chosen location reduce recurrence?
• Were affected-node reports included?
• Was external forcing considered?
• Did AP(t) distort localization?
• Did memory store localization as fact too early?
• Who carried cost of mislocalization?

If signal_localization_quality Was Misread

Possible misread forms:

• symptom mistaken for cause
• local node blamed for systemic origin
• interface problem attributed to one side
• external forcing mistaken for internal failure
• upstream policy error treated as execution error
• boundary design failure treated as attitude
• metric location treated as causal location
• distributed cause forced into one node
• delayed effect mistaken for unrelated signal
• correct localization dismissed because visible symptom is elsewhere

Required Restoration

When signal_localization_quality failure is found:

recover signal history
→ distinguish symptom from origin
→ map U-layers and coupling paths
→ review prior repairs and recurrence
→ correct false attribution
→ repair U7 localization memory
→ redirect ℛ to origin layer
→ retest recurrence

If mislocalization assigned burden asymmetrically, MS-Gate should review consequence, repair burden, and attribution distribution.

17) Cross-Domain Examples

Technical / Engineering

A recurring production bug appears in the frontend, but the real cause is an unstable backend contract and unclear API versioning.

Diagnostic implication: visible U3 symptom was localized to the wrong subsystem.

Operator sequence: trace dependency → localize interface contract → Π version constraint → ℛ backend/API repair → Δ regression test.

Institutional / Governance

A service failure is attributed to frontline workers, but the origin is impossible policy constraints, insufficient staffing, and contradictory escalation rules.

Diagnostic implication: visible behavior was mislocalized as individual failure instead of U1/U2/U5 constraint failure.

Operator sequence: Au timeline → U-layer map → MS burden review → Π policy repair → R_eff allocation.

AI / Algorithmic

A bad AI answer is blamed on the model, but the actual failure came from stale retrieval, tool error, memory contamination, or policy overconstraint.

Diagnostic implication: output symptom was mislocalized to model behavior alone.

Operator sequence: trace prompt/retrieval/tool/memory/policy → localize layer → ℛ target repair → Δ eval retest.

Interaction / Relational

A repeated conflict is blamed on tone, but the origin is unclear expectations and boundary timing.

Diagnostic implication: U3 expression symptom is being localized to personality or style while origin sits in U2/U5 coordination.

Operator sequence: ↺ reflection → map timing/expectation/boundary → Π agreement repair → Λ re-test.

Archive / Framework Design

Reader confusion is blamed on a specific spec sheet, but the real origin is inconsistent glossary terms across multiple modules.

Diagnostic implication: local document symptom is caused by U7/U4 archive memory drift.

Operator sequence: glossary audit → cross-link repair → Π naming constraint → U7 version update → Δ reader test.

18) Test Protocols

1. Symptom / Origin Test

Is the visible signal location the same as the failure origin?

Failure signal: repair at visible location does not reduce recurrence.

2. U-Layer Test

Which U-layer produced the signal?

Failure signal: U3 action is blamed while U2/U4/U5 origin remains unexamined.

3. Coupling Path Test

Did the signal travel through an interface or dependency?

Failure signal: interface effect is assigned to one node.

4. Timing Test

Does the sequence of events support the proposed localization?

Failure signal: cause is assigned after the effect or without timing support.

5. Recurrence Test

Does repairing the proposed origin reduce recurrence?

Failure signal: same pattern returns.

6. External Forcing Test

Did U8 pressure produce or amplify the signal?

Failure signal: environmental load is treated as internal failure.

7. Affected-Node Test

Do affected nodes identify a different origin or burden path?

Failure signal: official localization excludes exposed-node reality.

8. Metric Location Test

Does the metric show where measurement occurs or where cause originates?

Failure signal: dashboard location is treated as causal location.

9. Prior Repair Test

Have previous repairs at this location failed?

Failure signal: repeated same-layer repair with recurrence.

10. Memory Binding Test

Has the cause already been stored in U7?

Failure signal: old false localization biases current diagnosis.

19) Anti-Patterns

• Symptom as cause
• Metric location as cause location
• Visible node as responsible node
• Frontline signal as frontline failure
• Interface failure as one-node defect
• U8 forcing as internal defect
• Boundary strain as attitude
• Coordination delay as unwillingness
• Policy failure as execution failure
• Repeated recurrence as new event
• Local patch as root-cause repair
• Attribution before localization
• Protected-origin blindness
• Affected-node signal ignored
• Official diagnosis as true origin
• High-quality signal as correctly localized signal
• One-cause compression
• Repair at easiest layer
• Memory of old cause as current cause
• External audit needed because internal localization froze

20) Spec Validation Check

• Is this truly a diagnostic, not an operator? Yes.
• Does it measure state, capacity, risk, or response rather than act directly? Yes.
• Does it map to S? Yes.
• Are U-layers specified? Yes.
• Are leading and lagging indicators separated? Yes.
• Are interpretation risks defined? Yes.
• Are operator sequencing implications clear? Yes.
• Are gate implications clear? Yes.
• Are scaling risks included? Yes.
• Are interaction implications included? Yes.
• Does it avoid new primitives? Yes.

Condensed Archive Summary

signal_localization_quality is the diagnostic estimate of whether a signal has been accurately mapped to the correct source, node, U-layer, boundary, interface, coupling pathway, timescale, or causal origin. It differs from signal_quality: a signal can be clean and reliable while still being mislocalized. Low signal_localization_quality indicates risk of misrepair, false attribution, symptom patching, recurrence, protected-origin failure, boundary misread, interface blindness, memory contamination, and hidden debt accumulation. Under low signal_localization_quality, evidence preservation, U-layer mapping, timing reconstruction, coupling-path review, affected-node signal, Au reconstruction, Ξ false-localization checks, and Δ localization testing should precede hard attribution, irreversible Π, repair-complete claims, durable U7 cause memory, deep ⊗, punitive action, or scaling a repair pattern.