Archive registry entry

LAW-115 — Surveillance–Restoration Law

Archive registry entry

LAW-115 — Surveillance–Restoration Law

Surveillance without restoration creates enemies, bypass, or legitimacy debt; sensing becomes coherent only when it routes into repair, capacity rebuilding, boundary restoration, and recurrence prevention.

draftid: LAW-115version: 1.0.0updated: 2026-06-17

Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation

Online

The section has a stable overview route and basic reader context.

Technical Layer

Online

A deeper technical overview is available.

Registry

Current

171 registry entries are available.

Cross-links

Curating

Related concepts are being connected conservatively for accuracy.

Jump Through This Page

LAW-114 — Pseudo-Security Law

Registry

LAW-116 — Emergency Normalization Law

0. Plain Statement

Surveillance without restoration creates enemies, bypass, or legitimacy debt.

Plain-language version:

Surveillance is sensing.

Sensing can help a system detect harm, drift, risk, boundary failure, unsafe coupling, or recurrence.

But sensing is not security by itself.

When surveillance only detects, suppresses, classifies, punishes, restricts, or controls — without repair, support, boundary restoration, capacity rebuilding, and recurrence prevention — it becomes incoherent.

Security improves when sensing routes into restoration.

1. Formal Definition

The Surveillance–Restoration Law states that surveillance, monitoring, sensing, detection, logging, tracking, inspection, scanning, and observation become security-coherent only when they route into restoration.

Surveillance may be useful when it helps the system:

detect boundary drift;
detect active harm;
identify unsafe coupling;
reveal hidden debt;
surface early warning signals;
detect recurrence;
improve situational awareness;
preserve auditability;
support harmed nodes;
trigger repair;
improve prevention;
rebuild capacity.

Surveillance becomes incoherent when it only:

detects;
classifies;
suppresses;
punishes;
controls;
restricts;
extracts;
intimidates;
reputationally marks;
escalates enforcement;
expands control density;
normalizes emergency power;
converts humans or nodes into threat objects.

Canonical distinction:

textScroll

surveillance = sensing
security = sensing + boundary + audit + restoration

Therefore:

textScroll

surveillance - ℛ ⇒ H↑ + L↓

Surveillance improves security only when detection routes into repair and recurrence reduction.

2. Canonical Form

Core form:

textScroll

surveillance without restoration creates enemies, bypass, or legitimacy debt

Sensing distinction:

textScroll

surveillance = sensing; sensing ≠ security

Security form:

textScroll

security improves when sensing routes into restoration

Failure form:

textScroll

surveillance - ℛ ⇒ H↑ + L↓

Coherent routing form:

textScroll

detection → classification → support / containment → repair → recurrence prevention

Restoration-valid contrast:

textScroll

surveillance valid when scoped, auditable, boundary-respecting, feedback-bound, and repair-linked over Τ

Related variables:

textScroll

O, H, H_security, ε, ι, Au, Au_eff, µᵢ, BΣ, K, σ, R, R_eff, 𝓑, 𝓓, Φ, Λ, ⊗, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ, FI, MS, L, surveillance_scope, sensing_load, monitoring_coverage, detection_quality, classification_quality, restoration_routing, detection_to_repair_ratio, control_density, enforcement_pressure, consent_validity, affected_node_burden, recurrence_risk

Where:

TableScroll

Variable	Meaning in this law
`surveillance_scope`	Domain, duration, target set, authority, and boundaries of sensing
`sensing_load`	Data, attention, processing, interpretation, and response load created by sensing
`monitoring_coverage`	Extent of sensing across nodes, interfaces, environments, or behaviors
`detection_quality`	Ability to detect relevant signals accurately
`classification_quality`	Ability to classify detected signals without mislabeling nodes or artifacts
`restoration_routing`	Degree to which detections route into repair, support, and recurrence prevention
`detection_to_repair_ratio`	Relationship between what is detected and what is actually restored
`control_density`	Degree of restriction, pressure, policing, or control produced by surveillance
`enforcement_pressure`	Tendency for detections to route into punishment or restriction
`consent_validity`	Whether sensing is compatible with consent, scope, and state-space reality
`affected_node_burden`	Load imposed on those being monitored or classified
`recurrence_risk`	Likelihood detected issues repeat because repair is absent
`O`	Coherence; surveillance is valid only if it preserves or improves coherence
`H / H_security`	Hidden debt; rises when sensing does not repair
`BΣ`	Boundary integrity; surveillance must not dissolve membranes it claims to protect
`Au / Au_eff`	Auditability of sensing, classification, use, access, retention, and effects
`FI`	Feedback integrity; monitored or affected nodes must have correction pathways where appropriate
`MS`	Moral / meaning symmetry; surveillance must not apply asymmetrically without coherent justification
`R / R_eff`	Restoration capacity available to respond to what surveillance reveals
`L`	Legitimacy; decays when surveillance cannot survive audit or repair effects
`µᵢ`	Meaning / agent integrity; security purpose can invert into control
`ι / Ξ`	Inversion when sensing becomes control while claiming protection
`Φ`	Security proxy such as coverage, alerts, detections, or closure counts
`Γ`	Classifies signals, threats, artifacts, risks, affected nodes, and repair requirements
`Π`	Operationalizes sensing, logging, controls, escalation, review, retention, and response workflows
`ℛ`	Restoration triggered by sensing
`Θ`	Humility preventing control inflation and surveillance certainty
`Σ`	Scope, limits, authority, duration, and admissible use of surveillance
`Ψ`	Field and affected-node feedback validating surveillance effects
`Τ`	Time validation of repair, recurrence reduction, and legitimacy

3. Core Mechanism

The law unfolds because surveillance increases visibility and control potential, but does not automatically increase coherence.

Coherent surveillance-to-restoration pathway

textScroll

sensing is scoped
→ signals are detected
→ classification is audited
→ affected boundaries are protected
→ support or containment occurs if needed
→ repair activates
→ recurrence conditions change
→ legitimacy holds over time

Surveillance-without-restoration pathway

textScroll

sensing expands
→ detections increase
→ classification routes into control or punishment
→ repair capacity remains flat
→ affected nodes experience burden / threat / bypass
→ hidden debt and legitimacy debt rise
→ recurrence persists

The core mechanism is:

textScroll

sensing increases responsibility; it does not complete security

Detailed mechanism:

The system increases sensing.

It collects more data, observes more behavior, logs more events, monitors more interfaces, or classifies more nodes.

Visibility increases.

More signals become available, including legitimate threats, noise, artifacts, uncertainty, and ambiguous behavior.

Classification becomes high-stakes.

Detected signals must be distinguished from artifacts, context, legitimate action, distress, recurrence, error, and adversarial action.

Sensing creates response obligation.

Once a system sees debt, harm, or risk, it must have a pathway to repair, support, contain, or prevent recurrence.

Without restoration, surveillance becomes control.

Detected nodes may be punished, suppressed, or marked while origin-layer causes remain unrepaired.

Legitimacy decays.

Monitored nodes and observers lose trust when sensing lacks boundary clarity, appeal, repair, or proportionality.

Coherent security routes sensing into restoration.

Sensing becomes protective when it improves repair, capacity, recurrence prevention, and boundary integrity.

4. When This Law Applies

This law applies whenever a system uses surveillance, monitoring, sensing, logging, tracking, inspection, scanning, observation, telemetry, auditing, anomaly detection, risk scoring, behavioral analysis, or automated classification.

It is especially important when:

monitoring expands;
detection volume increases;
alerts increase without repair;
surveillance is justified as safety;
sensing routes mostly into enforcement;
monitored nodes lack appeal or correction;
users cannot audit surveillance effects;
data retention expands without scope clarity;
AI systems monitor, classify, rank, or restrict users;
institutions collect reports but do not repair;
security systems detect issues but cannot remediate;
surveillance creates fear, evasion, bypass, or adversarial behavior;
high-risk contexts use sensing without consent validity;
legitimacy depends on whether monitoring is trusted.

The law applies strongly when:

textScroll

sensing increases faster than restoration capacity

or when:

textScroll

surveillance is being treated as security proof

Typical domains:

TableScroll

Domain	Surveillance–Restoration Expression
AI systems	Monitoring, refusal classification, abuse detection, user risk scoring, and content moderation require explanation, appeal, correction, rollback, and restoration.
Cybersecurity	Logs, SIEM alerts, EDR, telemetry, and anomaly detection must route into remediation and prevention.
Institutions	Monitoring workers, students, patients, clients, or citizens without repair creates legitimacy debt.
Medicine / biology	Measurement and tracking require treatment, support, recovery, and interpretation discipline.
Economy	Financial monitoring, scoring, compliance checks, and risk models require correction and relief pathways.
Governance	Public surveillance requires strict scope, audit, accountability, repair, and legitimacy safeguards.
Culture	Social surveillance can create conformity, silence, or enemy-making if not repair-bound.
Media / information networks	Monitoring discourse or behavior must not replace trust-building, correction, and restoration.

5. When This Law Does Not Apply

This law should not be used to reject all sensing, monitoring, logging, or detection.

Sensing is often necessary.

A system that cannot sense cannot repair early.

The law says sensing must remain scoped, auditable, boundary-respecting, feedback-bound, and restoration-linked.

False-positive cases:

TableScroll

Case	Why surveillance may be coherent
Active harm requires detection	Sensing may be necessary to stop ongoing harm
Critical infrastructure requires telemetry	Monitoring can protect systems if repair routes exist
Logs preserve auditability	Logging can support accountability and restoration
Anomaly detection catches early risk	Detection is coherent when it triggers repair
Safety monitoring has consent and scope	Monitoring can be valid when bounded and auditable
Threat intelligence identifies adversarial paths	Shadow knowledge supports security when Light governs execution
Temporary monitoring supports restoration	Sensing can be coherent when time-bounded and repair-bound

Important distinction:

Sensing is not incoherent; sensing without restoration becomes incoherent.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

surveillance - ℛ ⇒ H↑ + L↓

Warning signature:

textScroll

monitoring coverage↑
detections↑
restoration routing↓
control density↑
appeal / feedback↓
affected-node burden↑
legitimacy↓
⇒ surveillance without restoration

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`monitoring_coverage`	↑	Sensing surface expands
`sensing_load`	↑	Data and interpretation load increase
`detection_quality`	should ↑	Sensing must detect meaningful signals
`classification_quality`	must remain high	Misclassification creates harm
`restoration_routing`	must ↑	Detections should route into repair
`detection_to_repair_ratio`	should improve	More detection should not outpace repair
`control_density`	watched carefully	Control should not replace restoration
`enforcement_pressure`	should be bounded	Detection should not default to punishment
`consent_validity`	must remain intact where applicable	Sensing requires valid scope and consent conditions
`affected_node_burden`	should not rise without repair	Monitoring should not overload or threaten nodes
`BΣ`	must remain stable	Surveillance must preserve boundaries
`Au`	must remain intact	Surveillance effects must be traceable
`FI`	must remain intact	Appeal, correction, and feedback must exist
`R_eff`	must match sensing load	Repair capacity must scale with visibility
`L`	stable / ↑ if valid	Legitimacy holds when surveillance is repair-bound
`H`	↑ if invalid	Hidden debt rises when sensing does not restore
`Τ`	required	Time validates recurrence reduction and trust

Additional diagnostics:

TableScroll

Diagnostic	Use
Surveillance–Restoration Coupling	Tests whether sensing routes into repair
Sensing Load	Measures load created by monitoring
Monitoring Scope	Tests whether surveillance is bounded
Restoration Routing	Tracks detection-to-repair pathway
Detection-to-Repair Ratio	Tests whether detections become restoration
Boundary Integrity	Detects surveillance boundary damage
Consent Structurality	Tests whether sensing consent is structurally valid
Misclassification Risk	Detects harm from incorrect classification
Over-Surveillance	Detects sensing beyond coherent scope
Control Substitution	Detects surveillance becoming control instead of security
Temporal Proof	Validates repair and recurrence reduction over time

7. Failure Pattern

If ignored, this law allows surveillance to expand while security coherence declines.

General failure pathway:

textScroll

surveillance expands
→ detections increase
→ classification routes into control
→ repair capacity remains insufficient
→ monitored nodes adapt, bypass, or become adversarial
→ hidden debt rises
→ legitimacy decays
→ security worsens

Common failure modes:

Surveillance Without Restoration — sensing detects but does not repair.
Sensing Without Repair — observations create knowledge without restoration pathway.
Monitoring Capture — monitoring becomes the dominant security response.
Over-Surveillance — sensing exceeds legitimate scope, capacity, or repair need.
Control Substitution — restriction or enforcement replaces restoration.
Enemy Creation — monitored nodes become adversarial because surveillance lacks repair and legitimacy.
Bypass Formation — nodes evade sensing instead of repairing causes.
Legitimacy Debt — trust decays because surveillance cannot survive audit.
Boundary Violation — sensing crosses membranes it claims to protect.
Consent Theater — consent to monitoring is formal but not structurally valid.
Misclassification Cascade — flawed sensing repeatedly labels nodes or signals incorrectly.
Feedback Suppression — monitored nodes cannot correct classification or effects.
Pseudo-Security — monitoring coverage is mistaken for security.
Enforcement Substitution — detections route into punishment instead of repair.
Hidden Debt Accumulation — origin-layer conditions remain and debt increases.

Compact failure signature:

textScroll

sensing↑ + ℛ flat + control↑ ⇒ H↑ + L↓

8. Restoration Implications

Restoration requires routing surveillance into repair and reducing control substitution.

The first restoration question is not:

textScroll

Can we see more?

The first restoration question is:

textScroll

When we see something, can we classify it correctly, protect boundaries, repair what caused it, and reduce recurrence?

Restoration priorities:

Identify surveillance scope.
Map what is being sensed and why.
Test consent and boundary validity.
Audit classification quality.
Measure detection-to-repair ratio.
Build restoration routing.
Provide correction, appeal, and feedback channels.
Reduce monitoring that has no repair pathway.
Repair harms caused by surveillance.
Validate recurrence reduction and legitimacy over time.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Surveillance-to-Restoration Routing	Converts sensing into repair pathway
Sensing Scope Repair	Clarifies what is sensed, why, for how long, and under what authority
Detection-to-Repair Sequencing	Ensures detections move into support, containment, repair, and prevention
Boundary Reconstitution	Repairs surveillance boundary damage
Consent Repair	Restores structural consent where monitoring exceeded validity
Feedback Integrity Restoration	Allows monitored or affected nodes to correct classification and effects
Restoration Capacity Increase	Builds repair capacity proportional to sensing load
Misclassification Repair	Corrects harm from false positives, false negatives, or context collapse
Legitimacy Repair	Restores trust after surveillance debt
Control-to-Restoration Re-Sequencing	Moves from punishment/default restriction to repair-linked response
Hidden Debt Reduction	Repairs origin conditions surfaced by sensing
Temporal Validation	Confirms surveillance reduces recurrence and debt over time

Minimal restoration sequence:

textScroll

identify surveillance_scope
→ audit consent + BΣ + Au
→ test Γ classification_quality
→ measure detection_to_repair_ratio
→ build ℛ routing + FI correction
→ reduce control substitution
→ repair surveillance debt
→ validate L/O over Τ

Temporal validation requirement:

textScroll

surveillance scope remains clear
boundary integrity improves
classification errors decrease
detection-to-repair ratio improves
control density decreases where repair can replace it
affected-node burden decreases
hidden debt decreases
recurrence decreases
legitimacy stabilizes
coherence holds under forcing

9. Design Rule

Do not expand surveillance unless detection routes into restoration, correction, and recurrence prevention.

Operational design requirements:

Define surveillance purpose.
Define scope, duration, authority, and limits.
Preserve auditability.
Preserve boundary integrity.
Preserve consent validity where applicable.
Preserve correction and appeal.
Preserve affected-node feedback.
Measure sensing load.
Measure classification quality.
Measure detection-to-repair ratio.
Build restoration pathways.
Build support pathways.
Build recurrence-prevention pathways.
Remove monitoring that cannot route into coherent action.
Validate legitimacy over time.

Avoid:

surveillance as security proof;
monitoring without repair;
detection without support;
sensing without scope;
logging without auditability;
scoring without appeal;
classification without correction;
enforcement-default response;
surveillance used to protect reputation;
formal consent masking state-space coercion;
monitoring harmed nodes without support;
AI user-risk scoring without transparency and repair;
treating evasion as proof of threat when surveillance itself created bypass incentives;
using sensing to preserve pseudo-stability rather than reduce hidden debt.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Measurement of bodies, infrastructure, or environments requires care, maintenance, repair, and recovery routes.
U1 — Energy / capacity	Surveillance consumes attention, compute, staff, money, and response capacity.
U2 — Boundary / interface	Sensing must respect membranes, consent, privacy, access, scope, and exit.
U3 — Process / execution	Surveillance becomes monitoring, logging, triage, escalation, support, containment, repair, and review workflows.
U4 — Classification / claim	Surveillance depends on classification of signals, threats, risks, users, artifacts, and context.
U5 — Time / delay	Monitoring duration, retention, lag, and review timing determine legitimacy and debt.
U6 — Field effect	Outcomes reveal whether surveillance improved coherence or produced control debt.
U7 — Recurrence / memory	Detections must become memory, learning, repair obligations, and recurrence prevention.
U8 — Environment / forcing	Institutions, platforms, AI systems, markets, media, and governance fields shape surveillance incentives and legitimacy.

11. Examples

Example A — Monitoring Without Remediation

Scenario:

A system logs many security issues but lacks staffing, budget, or authority to fix them.

Law expression:

textScroll

detections↑ + ℛ flat ⇒ security debt↑

Interpretation:

Monitoring increased awareness but did not increase security because repair did not follow.

Example B — AI User Risk Scoring

Scenario:

An AI platform risk-scores users and restricts accounts, but users cannot audit, appeal, correct, or understand the classification.

Law expression:

textScroll

AI surveillance + Γ opaque + FI absent ⇒ L↓ + H↑

Interpretation:

Risk scoring becomes incoherent when it lacks transparency, correction, and restoration.

Example C — Workplace Surveillance

Scenario:

An organization monitors workers to detect productivity or compliance issues but does not repair workload, process failure, unclear expectations, or resource constraints.

Law expression:

textScroll

worker monitoring - capacity repair ⇒ bypass + legitimacy debt

Interpretation:

Surveillance substitutes for fixing the conditions that produce the signal.

Example D — Security Camera Without Response

Scenario:

A facility installs cameras but has no process for intervention, harmed-node support, incident repair, or recurrence prevention.

Law expression:

textScroll

visibility↑ + response / ℛ absent ⇒ pseudo-security

Interpretation:

Seeing more does not secure more unless response and repair exist.

Example E — Coherent Cyber Telemetry

Scenario:

A security team collects telemetry, classifies anomalies, supports affected users, patches root causes, audits false positives, and tracks recurrence reduction.

Law expression:

textScroll

sensing → Γ → containment / support → ℛ → recurrence↓

Interpretation:

Surveillance becomes coherent because it routes into restoration.

Example F — Public Surveillance Without Legitimacy

Scenario:

A governance system expands public monitoring for safety but provides weak scope, weak oversight, weak correction, no meaningful repair, and no sunset.

Law expression:

textScroll

surveillance_scope↑ + Au/FI/ℛ↓ ⇒ legitimacy debt

Interpretation:

Public safety sensing loses legitimacy when it becomes unbounded control.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-001 — Coherence Priority Law	Surveillance is valid only when coherence is preserved
LAW-002 — Coherence Trajectory Law	Surveillance must improve trajectory over time
LAW-003 — Success Proxy Divergence Law	Monitoring coverage can diverge from security
LAW-004 — Stability-Coherence Separation Law	Surveillance can create surface order without coherence
LAW-006 — Time Validation Law	Surveillance legitimacy requires temporal proof
LAW-009 — U4 / U6 Truth Law	Surveillance claims require field validation
LAW-010 — Hidden Debt Accumulation Law	Surveillance without repair creates hidden debt
LAW-011 — Hidden Debt Return Law	Unrepaired surveillance debt returns as mistrust, bypass, or incident
LAW-012 — Error Lag Law	Detection can reveal late-stage debt
LAW-013 — Auditability-Debt Law	Surveillance itself must remain auditable
LAW-015 — Suppressed Auditability Debt Law	Opaque surveillance creates debt
LAW-016 — Inversion Formation Law	Protection can invert into control
LAW-017 — Silent Extraction Law	Surveillance can extract data, attention, or compliance silently
LAW-020 — Bandwidth Threshold Law	More sensing can exceed classification and response bandwidth
LAW-023 — Restoration Capacity Load Law	Surveillance increases restoration demand
LAW-030 — Slack Sovereignty Law	Surveillance can consume slack and sovereignty
LAW-031 — Observability Collapse Law	More data does not guarantee effective observability
LAW-036 — Signal Artifact Law	Surveillance must distinguish signal from artifact
LAW-037 — Misclassification Law	Surveillance amplifies classification errors
LAW-040 — Filtering Law	Filtering determines what surveillance admits or hides
LAW-041 — Boundary Membrane Law	Surveillance acts on membranes and can damage them
LAW-042 — Consent Structurality Law	Surveillance consent must be structurally valid
LAW-043 — Safe Coupling Law	Surveillance changes coupling safety
LAW-045 — Force Debt Law	Surveillance-backed enforcement can create force debt
LAW-047 — Controlled Decoupling Law	Sensing may trigger decoupling, which must be repair-bound
LAW-048 — Feedback Integrity Law	Surveillance requires correction and affected-node feedback
LAW-050 — Control-Restoration Separation Law	Surveillance must not become control substituting for restoration
LAW-052 — Stability Proof Law	Surveillance systems must survive perturbation and audit
LAW-057 — Deception Instability Law	Surveillance can detect deception or become deceptive itself
LAW-060 — Interface Legitimacy Law	Surveillance interfaces must be legitimate and understandable
LAW-064 — Restoration Debt Reduction Law	Sensing should reduce debt through repair
LAW-065 — Pseudo-Restoration Law	Surveillance can imitate repair without reducing debt
LAW-066 — Restoration Capacity Sufficiency Law	Repair capacity must match surveillance-discovered load
LAW-067 — Temporal Proof Law	Surveillance must prove recurrence reduction over time
LAW-071 — No Forced Forgiveness Law	Surveillance cannot demand harmed-node closure without repair
LAW-072 — Quiet Minimization Debt Law	Surveillance may minimize or hide costs unless audited
LAW-083 — Normalization Shield Law	Normalized surveillance can shield harm
LAW-102 — Legitimacy Audit Law	Surveillance legitimacy requires audit and affected-node acknowledgment
LAW-103 — Justice Stability Law	Surveillance must support justice, not replace it
LAW-104 — Justice Logistics Law	Surveillance increases justice and repair load
LAW-105 — Repair Before Enforcement Law	Surveillance-triggered enforcement must be repair-linked
LAW-106 — Exposure Legibility Law	Surveillance exposes debt but is not the origin of debt
LAW-107 — Exposure Without Restoration Law	Sensing without repair destabilizes
LAW-108 — Victim Pathway Capacity Law	Surveillance may overburden harmed nodes if pathways are weak
LAW-109 — High-Φ Legitimacy Scaling Law	High-influence surveillance requires stronger audit and repair
LAW-110 — Governance Sequencing Law	Surveillance must be sequenced into governance and restoration
LAW-111 — Meaning Audit Law	Safety and surveillance narratives are not audit-exempt
LAW-112 — Security as Sustained Coherence Law	Surveillance is only one component of coherent security
LAW-113 — Incident Lag Law	Surveillance can reduce lag only if it routes weak signals into repair
LAW-114 — Pseudo-Security Law	Surveillance without restoration becomes pseudo-security
LAW-116 — Emergency Normalization Law	Surveillance introduced during emergency must sunset or repair
LAW-117 — Shadow–Light Security Law	Surveillance must not become shadow capture
LAW-118 — Empathy Security Law	Empathy improves classification and reduces surveillance misclassification
LAW-119 — Basin Self-Defense Law	Basins may use surveillance to preserve attractor geometry
LAW-120 — Security Legibility Law	Surveillance claims require traceability
LAW-121 — AI as Γ-Amplifier Law	AI can amplify surveillance classification power
LAW-122 — AI Error Lag Law	AI surveillance errors may appear late
LAW-123 — AI U4 Truth Discipline Law	AI monitoring claims require field validation
LAW-127 — AI Decision Pipeline Law	AI surveillance outputs must pass through Light before action
LAW-128 — AI Representation Law	AI monitoring on behalf of others requires scope and auditability
LAW-130 — AI Membrane Triage Law	AI surveillance failures may begin at boundary, classifier, or delivery membrane
LAW-131 — Cognitive Infrastructure Scaling Law	Public-cognition surveillance requires proportional governance
LAW-132 — AI Legitimacy Function Law	AI legitimacy requires surveillance to be accountable and repair-linked
LAW-134 — Layered Interception Law	Layered interception should route detections into restoration
LAW-135 — Guardrail Belief-Sculpting Law	Guardrail sensing can shape belief and requires audit
LAW-136 — Invisible Constraint Amplification Law	Invisible surveillance constraints become powerful when unseen

Aliases folded into this law:

Surveillance–Restoration Law
Surveillance Without Restoration Law
Sensing Must Route to Restoration Law
Monitoring Without Repair Law
Surveillance Legitimacy Debt Law
Detection Is Not Restoration Law
Security Sensing Restoration Law

Deduplication note:

This law should remain the root surveillance-to-restoration law. LAW-112 defines security as sustained coherence. LAW-114 defines pseudo-security. LAW-105 defines repair before enforcement. LAW-107 defines exposure without restoration. LAW-120 defines traceability requirements for security claims. AI-specific surveillance and decision pathways are specialized in LAW-121, LAW-127, LAW-128, LAW-130, LAW-131, and LAW-132.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies signals, threats, artifacts, monitored nodes, risk, context, and repair requirements
`Π`	Operationalizes surveillance, logging, monitoring, escalation, enforcement, review, retention, and repair workflows
`Ξ`	Captures inversion when protection becomes control or sensing replaces restoration
`⊗`	Surveillance changes coupling between observer, observed node, authority, data, and repair system
`ℛ`	Routes detected issues into repair, capacity rebuilding, harmed-node support, and recurrence prevention
`Τ`	Validates whether surveillance reduces recurrence and debt over time
`Θ`	Prevents surveillance certainty, control inflation, and classification overreach
`Σ`	Defines scope, authority, duration, data use, retention, and limits of surveillance
`Ψ`	Field and affected-node feedback validates surveillance effects
`Λ`	Tests compatibility between surveillance posture and whole-system coherence

Coherent operator sequence:

textScroll

sensing need appears
→ Θ prevent control inflation
→ Γ classify signal / target / context / repair need
→ Σ define scope, authority, duration, and limits
→ Π collect and classify only within scope
→ Au/FI preserve audit, appeal, and correction
→ ℛ route detections into support, repair, and prevention
→ Ψ validate affected-node effects
→ Τ validate recurrence reduction and L stability

Inverted operator sequence:

textScroll

surveillance expands
→ Γ classifies more nodes as risk
→ Π routes detections into control
→ FI / appeal narrows
→ ℛ absent
→ affected-node burden↑
→ bypass and enemy formation↑
→ H↑
→ Ξ / ι↑
→ L↓

14. Machine-Readable Summary

yamlScroll

id: "LAW-115"
name: "Surveillance–Restoration Law"
type: "law"
status: "draft"
family:
  - "Security Laws"
summary: "Surveillance without restoration creates enemies, bypass, or legitimacy debt; sensing becomes coherent only when it routes into repair, capacity rebuilding, boundary restoration, and recurrence prevention."
canonical_statement: "Surveillance without restoration creates enemies, bypass, or legitimacy debt."
core_form: "surveillance without restoration creates enemies, bypass, or legitimacy debt"
sensing_distinction: "surveillance = sensing; sensing ≠ security"
security_form: "security improves when sensing routes into restoration"
failure_form: "surveillance - ℛ ⇒ H↑ + L↓"
coherent_routing_form: "detection → classification → support / containment → repair → recurrence prevention"
restoration_valid_contrast: "surveillance valid when scoped, auditable, boundary-respecting, feedback-bound, and repair-linked over Τ"
variables:
  primary:
    - "surveillance_scope"
    - "sensing_load"
    - "monitoring_coverage"
    - "detection_quality"
    - "classification_quality"
    - "restoration_routing"
    - "detection_to_repair_ratio"
    - "control_density"
    - "enforcement_pressure"
    - "consent_validity"
    - "affected_node_burden"
    - "recurrence_risk"
    - "BΣ"
    - "Au"
    - "Au_eff"
    - "FI"
    - "R"
    - "R_eff"
    - "L"
    - "H"
  secondary:
    - "O"
    - "H_security"
    - "ε"
    - "ι"
    - "µᵢ"
    - "K"
    - "σ"
    - "𝓑"
    - "𝓓"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Ξ"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
    - "MS"
diagnostics:
  - "Surveillance–Restoration Coupling"
  - "Sensing Load"
  - "Monitoring Scope"
  - "Restoration Routing"
  - "Detection-to-Repair Ratio"
  - "Boundary Integrity"
  - "Consent Structurality"
  - "Feedback Integrity"
  - "Legitimacy Debt"
  - "Misclassification Risk"
  - "Over-Surveillance"
  - "Control Substitution"
  - "Recurrence Risk"
  - "Temporal Proof"
failure_modes:
  - "Surveillance Without Restoration"
  - "Sensing Without Repair"
  - "Monitoring Capture"
  - "Over-Surveillance"
  - "Control Substitution"
  - "Enemy Creation"
  - "Bypass Formation"
  - "Legitimacy Debt"
  - "Boundary Violation"
  - "Consent Theater"
  - "Misclassification Cascade"
  - "Feedback Suppression"
  - "Pseudo-Security"
  - "Enforcement Substitution"
  - "Hidden Debt Accumulation"
restoration_arcs:
  - "Surveillance-to-Restoration Routing"
  - "Sensing Scope Repair"
  - "Detection-to-Repair Sequencing"
  - "Boundary Reconstitution"
  - "Consent Repair"
  - "Feedback Integrity Restoration"
  - "Restoration Capacity Increase"
  - "Misclassification Repair"
  - "Legitimacy Repair"
  - "Control-to-Restoration Re-Sequencing"
  - "Hidden Debt Reduction"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-003"
  - "LAW-004"
  - "LAW-006"
  - "LAW-009"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-017"
  - "LAW-020"
  - "LAW-023"
  - "LAW-030"
  - "LAW-031"
  - "LAW-036"
  - "LAW-037"
  - "LAW-040"
  - "LAW-041"
  - "LAW-042"
  - "LAW-043"
  - "LAW-045"
  - "LAW-047"
  - "LAW-048"
  - "LAW-050"
  - "LAW-052"
  - "LAW-057"
  - "LAW-060"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-071"
  - "LAW-072"
  - "LAW-083"
  - "LAW-102"
  - "LAW-103"
  - "LAW-104"
  - "LAW-105"
  - "LAW-106"
  - "LAW-107"
  - "LAW-108"
  - "LAW-109"
  - "LAW-110"
  - "LAW-111"
  - "LAW-112"
  - "LAW-113"
  - "LAW-114"
  - "LAW-116"
  - "LAW-117"
  - "LAW-118"
  - "LAW-119"
  - "LAW-120"
  - "LAW-121"
  - "LAW-122"
  - "LAW-123"
  - "LAW-127"
  - "LAW-128"
  - "LAW-130"
  - "LAW-131"
  - "LAW-132"
  - "LAW-134"
  - "LAW-135"
  - "LAW-136"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-073"
  - "INV-078"
  - "INV-080"
operator_sequence:
  coherent:
    - "sensing need appears"
    - "Θ prevent control inflation"
    - "Γ classify signal / target / context / repair need"
    - "Σ define scope, authority, duration, and limits"
    - "Π collect and classify only within scope"
    - "Au/FI preserve audit, appeal, and correction"
    - "ℛ route detections into support, repair, and prevention"
    - "Ψ validate affected-node effects"
    - "Τ validate recurrence reduction and L stability"
  inverted:
    - "surveillance expands"
    - "Γ classifies more nodes as risk"
    - "Π routes detections into control"
    - "FI / appeal narrows"
    - "ℛ absent"
    - "affected-node burden↑"
    - "bypass and enemy formation↑"
    - "H↑"
    - "Ξ / ι↑"
    - "L↓"
aliases:
  - "Surveillance–Restoration Law"
  - "Surveillance Without Restoration Law"
  - "Sensing Must Route to Restoration Law"
  - "Monitoring Without Repair Law"
  - "Surveillance Legitimacy Debt Law"
  - "Detection Is Not Restoration Law"
  - "Security Sensing Restoration Law"
deduplication_note: "Root surveillance-to-restoration law. LAW-112 defines security as sustained coherence. LAW-114 defines pseudo-security. LAW-105 defines repair before enforcement. LAW-107 defines exposure without restoration. LAW-120 defines traceability requirements for security claims. AI-specific surveillance and decision pathways are specialized in LAW-121, LAW-127, LAW-128, LAW-130, LAW-131, and LAW-132."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-115 — Surveillance–Restoration Law

Surveillance without restoration creates enemies, bypass, or legitimacy debt.

Core form:

textScroll

surveillance without restoration creates enemies, bypass, or legitimacy debt

Sensing distinction:

textScroll

surveillance = sensing; sensing ≠ security

Plain meaning:

Surveillance is sensing. Sensing can help detect harm, drift, unsafe coupling, or recurrence. But sensing is not security by itself. Security improves when sensing routes into restoration, repair, capacity rebuilding, boundary restoration, and recurrence prevention.

Failure form:

textScroll

surveillance - ℛ ⇒ H↑ + L↓

Coherent routing form:

textScroll

detection → classification → support / containment → repair → recurrence prevention

Primary variables:

surveillance_scope, sensing_load, monitoring_coverage, detection_quality, classification_quality, restoration_routing, detection_to_repair_ratio, control_density, enforcement_pressure, consent_validity, affected_node_burden, recurrence_risk, BΣ, Au, Au_eff, FI, R, R_eff, L, H, Γ, Π, Ξ, ℛ, Θ, Σ, Ψ, Τ

Diagnostic signature:

Monitoring coverage and detections rise while restoration routing falls, control density rises, appeal and feedback weaken, affected-node burden increases, and legitimacy declines. This indicates surveillance without restoration.

Failure risk:

Surveillance without restoration, sensing without repair, monitoring capture, over-surveillance, control substitution, enemy creation, bypass formation, legitimacy debt, boundary violation, consent theater, misclassification cascade, feedback suppression, pseudo-security, enforcement substitution, hidden debt accumulation.

Restoration priority:

Identify surveillance scope, audit consent and boundary validity, test classification quality, measure detection-to-repair ratio, build restoration routing and correction pathways, reduce control substitution, repair surveillance debt, and validate legitimacy and coherence over time.

LAW-114 — Pseudo-Security Law

Registry

LAW-116 — Emergency Normalization Law