A system may be able to imagine, simulate, detect, exploit, dominate, manipulate, deceive, attack, bypass, or destroy. That does not mean those capacities are coherent to execute. Shadow reveals the could-do space. Light filters the may-do space.

1. Formal Definition

The Shadow–Light Execution Law states that shadow functions reveal possible action capacity, while light functions determine which actions are admissible under principle, boundary, wisdom, restoration, and coherence constraints.

Shadow is the system’s capacity to perceive, simulate, or understand harmful, adversarial, forbidden, destructive, deceptive, manipulative, coercive, exploitative, or destabilizing possibilities.

Light is the system’s capacity to govern execution through coherence constraints: truth, love, sovereignty, wisdom, justice, boundary, restoration, consent, proportionality, and whole-system effects.

Shadow is not evil. It is capacity awareness. A system that cannot perceive shadow pathways cannot defend against them, design safely, detect exploitation, or understand risk.

Light is not naïveté. It is execution governance. A system that claims light while refusing to perceive shadow becomes vulnerable, brittle, and incomplete.

The danger arises when shadow simulation becomes execution authorization, or when light claims suppress shadow perception.

Therefore:

textScroll

Shadow reveals could-do space.
Light filters may-do space.

2. Canonical Form

Core form:

textScroll

SI reveals could-do space
LI filters may-do space

Shadow-capture form:

textScroll

SI without LI ⇒ shadow capture

Naïve-light form:

textScroll

LI without SI ⇒ naïve light / risk blindness

Execution-valid form:

textScroll

SI simulation + LI authorization + Σ/BΣ intact + FI intact ⇒ coherent execution possible

Related variables:

textScroll

O, H, ε, ι, Au, R, R_eff, BΣ, K, σ, µᵢ, Φ, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI, SI, LI

Where:

TableScroll

Variable	Meaning in this law
`SI`	Shadow interface; reveals possible harmful, adversarial, forbidden, or high-risk action pathways
`LI`	Light interface; filters whether a possible action is coherent, admissible, and principle-aligned
`O`	Coherence; preserved when execution is filtered by Light
`H`	Hidden debt created when shadow capacity executes without coherent authorization
`ι / Ξ`	Inversion when shadow action is justified as necessity, truth, safety, wisdom, or strength
`BΣ`	Boundary integrity; protects systems from shadow-driven violation
`Σ`	Scope and admissible action region
`K / σ`	Slack / sovereignty protected when execution avoids extraction or coercion
`Au`	Auditability required to inspect why an action was allowed or refused
`FI`	Feedback integrity required to detect whether execution caused harm or debt
`R / R_eff`	Restoration capacity required if shadow simulation reveals real risk or if execution causes harm
`µᵢ`	Meaning / agent integrity; degraded when capacity is mistaken for permission
`Φ`	Visible success proxy; may rise when shadow action produces local advantage
`Λ`	Compatibility between action, target, field, and principle constraints
`⊗`	Coupling intensity affected by shadow-informed action
`Γ`	Classifies possible action, admissible action, refusal, risk, and execution status
`Π`	Controls, gates, or enforcement mechanisms that may prevent unauthorized execution
`ℛ`	Restoration action after boundary, force, or deception debt
`Θ`	Humility required to avoid overidentifying simulation with truth or permission
`Ψ`	Field and affected-node feedback validating consequences
`Τ`	Time validation of whether action preserved coherence

3. Core Mechanism

The law unfolds when possible action is confused with admissible action.

Coherent shadow–light pathway

textScroll

risk / possibility detected
→ Shadow simulates could-do pathways
→ Light evaluates admissibility
→ boundary, consent, wisdom, and restoration constraints are applied
→ inadmissible actions are refused
→ admissible actions proceed with audit and feedback
→ coherence is time-validated

Shadow capture pathway

textScroll

Shadow detects capacity
→ capacity becomes fascination / identity / justification
→ Light authorization is bypassed
→ action executes because it can
→ H↑ + force debt↑ + ι↑
→ coherence declines

Naïve light pathway

textScroll

Light ideal is claimed
→ Shadow pathways are refused or unseen
→ risks remain unmodeled
→ system becomes vulnerable to exploitation
→ harm occurs despite positive intent

The core mechanism is:

textScroll

capacity awareness must be separated from execution authorization

Detailed mechanism:

A possible action pathway becomes visible.

The system sees how to exploit, attack, deceive, dominate, bypass, manipulate, coerce, suppress, or control.

Shadow expands the possible action-space.

The system gains risk awareness and strategic capacity. This may improve defense, diagnosis, security, governance, or design.

Light must evaluate admissibility.

The system checks principle constraints, boundary integrity, consent, proportionality, restoration, field effects, and recurrence risk.

The system either filters or identifies with the capacity.

If Light filters the pathway, capacity becomes wisdom. If the system identifies with the capacity, shadow becomes capture.

Execution changes the field.

If an action is executed without Light authorization, it creates hidden debt, force debt, boundary damage, or legitimacy decay.

Time reveals whether execution was coherent.

Recurrence, harmed-node burden, field effect, and restoration load validate whether action remained inside the admissible region.

4. When This Law Applies

This law applies whenever a system can perceive, simulate, or perform an action that may be powerful, risky, harmful, coercive, deceptive, adversarial, manipulative, or destabilizing.

It is especially important when:

a security system studies adversarial tactics;
an AI system can generate harmful or manipulative outputs;
an institution can use authority to suppress or expose;
a governance system can enforce, punish, surveil, or restrict;
an economy can extract value through asymmetry;
a culture can shame, exclude, or ritualize control;
a person or group can dominate a weaker node;
a model can optimize local reward by violating hidden constraints;
a system mistakes strategic capacity for legitimacy;
a system refuses to model risk because it wants to remain “pure”;
a system uses truth, safety, justice, or wisdom language to authorize coercive action.

The law applies strongly when:

textScroll

could-do is being treated as may-do

or when:

textScroll

shadow simulation is either denied or allowed to govern execution

Typical domains:

TableScroll

Domain	Shadow–Light Execution Expression
AI systems	Models may simulate harmful pathways, but execution must pass through principle, boundary, consent, safety, and restoration filters.
Security	Security must understand adversarial capacity without becoming captured by adversarial logic.
Institutions	Authority may know how to suppress, expose, punish, or control, but Light must govern admissibility.
Medicine / biology	Intervention capacity must not become permission to overload the system.
Economy	Capability to extract profit does not make extraction coherent.
Governance	Enforcement power must be filtered through justice, legitimacy, repair, and proportionality.
Culture	Symbolic power must not execute shame, exclusion, or domination because it can.
Restoration	Repair must distinguish risk simulation from permissible action.

5. When This Law Does Not Apply

This law should not be used to suppress risk modeling, adversarial analysis, shadow recognition, or strategic realism.

Seeing a harmful pathway is not the same as endorsing it. Modeling threat, deception, exploitation, coercion, or manipulation may be necessary for protection and coherent design.

False-positive cases:

TableScroll

Case	Why it is not shadow capture
A security team models an exploit to patch it	Shadow supports defense under Light authorization
An AI safety team red-teams harmful outputs without deploying them	Simulation remains bounded
A governance system models abuse pathways to prevent them	Shadow informs prevention
A person recognizes a manipulative option and refuses it	Light successfully filters execution
A system studies failure modes to build restoration	Shadow capacity supports coherence

Important distinction:

Shadow perception is not shadow capture. Shadow capture occurs when the possible action becomes the executed or identity-bound action without Light authorization.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

SI reveals could-do space
LI filters may-do space

Warning signature:

textScroll

capacity detected
authorization unclear
boundary stress↑
principle constraint weak
execution pressure↑
H risk↑
⇒ shadow capture risk

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`SI`	↑ / active	Shadow capacity reveals possible action pathways
`LI`	must be active	Light must filter admissibility
`H`	↑ if Light bypassed	Hidden debt rises from unauthorized execution
`ι / Ξ`	↑ if justified	Inversion rises when shadow action is framed as principle
`BΣ`	must remain stable	Boundaries must not be violated by capacity execution
`Σ`	clear	Scope and admissible region must be defined
`Au`	↑ / intact	Execution authorization must be traceable
`FI`	intact	Feedback must reveal harm or drift
`K / σ`	protected	Sovereignty and slack must not be extracted
`O`	stable / ↑	Coherence must hold after action
`µᵢ`	stable / ↑	Meaning integrity preserved when capacity is not confused with permission
`Φ`	not sufficient	Local advantage from shadow action is not proof of coherence
`R_eff`	sufficient	Restoration capacity needed if high-risk action is taken
`Τ`	required	Time validates whether action remained coherent

Additional diagnostics:

TableScroll

Diagnostic	Use
Shadow Capacity	Measures what the system can perceive, simulate, or do
Light Authorization	Tests whether action passed admissibility filters
Execution Admissibility	Determines whether action may proceed coherently
Shadow Capture Risk	Detects capacity-identification or execution pressure
Constraint Field Integrity	Tests whether principle constraints are active
Boundary Integrity	Detects violation risk
Force Debt	Detects coercive execution cost
Feedback Integrity	Preserves consequence signals
Coherence Trajectory	Tests whether execution preserves `O`
Temporal Proof	Validates action over time

7. Failure Pattern

If ignored, this law produces shadow capture or naïve vulnerability.

Shadow capture failure pathway

textScroll

capacity revealed
→ capacity becomes identity / fascination / authorization
→ Light bypassed
→ action executed
→ H↑ + ι↑ + force debt↑
→ legitimacy declines

Naïve light failure pathway

textScroll

principle ideal claimed
→ shadow pathways denied
→ risks unmodeled
→ exploitation occurs
→ system lacks defense
→ harm and hidden debt rise

Common failure modes:

Shadow Capture — the system executes because it can.
Capacity-Permission Confusion — capability is mistaken for admissibility.
Adversarial Simulation Capture — modeling adversarial pathways becomes identification with them.
Light Bypass — execution skips principle filtering.
Naïve Light — refusal to model shadow creates vulnerability.
Shadow Without Authorization — dark capacity is enacted without coherence review.
Execution Without Constraint — action proceeds outside principle fields.
Force Debt — coercion creates future debt.
Deception Capture — deception capacity becomes operational pattern.
Boundary Violation — action crosses consent, scope, or sovereignty limits.
Pseudo-Alignment — action is framed as aligned because it achieves a proxy.
Coherence Drift — repeated shadow execution shifts the system’s trajectory.
Legitimacy Debt — trust decays when capacity misuse becomes visible.

Compact failure signature:

textScroll

SI↑ + LI bypassed ⇒ H↑ + ι↑ + O↓

8. Restoration Implications

Restoration requires separating simulation, authorization, and execution.

The first restoration question is not:

textScroll

Can the system do this?

The first restoration question is:

textScroll

Is this action admissible under Light constraints?

Restoration priorities:

Identify the shadow capacity.
Separate possibility from permission.
Define Light authorization criteria.
Apply principle, boundary, consent, and restoration constraints.
Preserve auditability of execution decisions.
Refuse inadmissible action even if useful.
Model shadow pathways safely for defense and prevention.
Repair debt created by past shadow capture.
Restore feedback integrity.
Time-validate that execution preserves coherence.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Shadow–Light Rebalancing	Separates capacity awareness from execution authorization
Execution Constraint Repair	Restores admissibility filters
Boundary Reconstitution	Repairs boundary damage from shadow execution
Feedback Integrity Restoration	Restores consequence visibility
Inversion Reduction	Removes justification patterns around shadow action
Hidden Debt Reduction	Repairs debt created by unauthorized execution
Auditability Restoration	Makes execution decisions traceable
Discernment Spine Restoration	Rebuilds capacity to distinguish possible from permissible
Restoration Capacity Rebuild	Ensures repair capacity after high-risk action
Temporal Validation	Confirms action holds under time and recurrence

Minimal restoration sequence:

textScroll

identify SI capacity
→ define LI authorization
→ audit action against principle / boundary / consent
→ refuse or execute within Σ
→ monitor Ψ effects
→ repair H if needed
→ validate over Τ

Temporal validation requirement:

textScroll

SI bounded
LI active
BΣ stable
Au intact
FI intact
H↓ or stable-low
ι↓
force debt not increasing
O stable or rising
recurrence of shadow capture↓

9. Design Rule

Do not confuse capacity with permission.

Operational design requirements:

Map shadow capacities explicitly.
Keep simulation separate from execution.
Define Light authorization gates.
Preserve principle constraints.
Preserve consent and boundary constraints.
Require auditability for high-risk actions.
Require refusal pathways.
Require restoration capacity for risky execution.
Red-team without identity-binding to the adversarial pattern.
Track force debt.
Track deception debt.
Track boundary effects.
Time-validate execution outcomes.

Avoid:

executing because the system can;
treating power as legitimacy;
treating strategic insight as permission;
treating adversarial realism as identity;
suppressing shadow perception in the name of purity;
refusing to model harmful pathways needed for defense;
using truth as domination;
using safety as control;
using justice as punishment-only;
using AI capability as deployment permission;
using security knowledge as coercive authority;
bypassing consent because the outcome seems beneficial.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Physical or biological intervention capacity must be filtered by tolerance and repair constraints.
U1 — Energy / capacity	High capacity or power must not become automatic demand or execution.
U2 — Boundary / interface	Execution must preserve consent, scope, access, and sovereignty.
U3 — Process / execution	Shadow simulation must pass through execution controls and refusal gates.
U4 — Classification / claim	Could-do must not be classified as may-do.
U5 — Time / delay	Repeated shadow execution shifts trajectory over time.
U6 — Field effect	Affected-node outcomes reveal whether execution was coherent.
U7 — Recurrence / memory	Shadow capture can encode repeated harmful execution patterns.
U8 — Environment / forcing	Adversarial or high-pressure environments increase shadow capture risk.

11. Examples

Example A — AI Capability Is Not Permission

Scenario:

An AI system can generate persuasive manipulation, deepfakes, exploit chains, emotional pressure, or coercive scripts.

Law expression:

textScroll

SI reveals capability; LI must authorize or refuse execution

Interpretation:

Capability is not deployment permission. Execution must pass through boundary, consent, safety, restoration, and field-effect constraints.

Example B — Security Red-Team Discipline

Scenario:

A security researcher learns how to exploit a system. The knowledge is used to patch, disclose responsibly, or strengthen defenses rather than harm.

Law expression:

textScroll

SI exploit simulation + LI constraint ⇒ coherent security action

Interpretation:

Shadow perception supports protection when Light governs execution.

Example C — Governance Enforcement

Scenario:

A government can surveil, restrict, punish, expose, or control in the name of order or safety.

Law expression:

textScroll

state capacity without LI / BΣ / Au ⇒ force debt↑

Interpretation:

Authority capacity must be filtered by legitimacy, consent, repair, proportionality, and audit.

Example D — Institutional Exposure

Scenario:

An institution has access to damaging private information about a critic or harmed node and could use it to preserve legitimacy.

Law expression:

textScroll

capacity to expose ≠ admissibility to expose

Interpretation:

Shadow knowledge cannot become execution unless Light constraints authorize it.

Example E — Biological Intervention Power

Scenario:

A practitioner or system has tools to intensify intervention, stimulation, detoxification, training, or restriction.

Law expression:

textScroll

intervention capacity without tolerance / R_eff ⇒ harm risk↑

Interpretation:

Just because the system can intervene does not mean the body can coherently carry it.

Example F — Cultural Symbolic Power

Scenario:

A cultural system can shame, exile, ridicule, or ritually mark a person for violating norms.

Law expression:

textScroll

symbolic power without LI ⇒ boundary / meaning debt↑

Interpretation:

Symbolic power must be filtered by justice, truth, proportionality, repair, and boundary integrity.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-001 — Coherence Priority Law	Light filters execution toward coherence
LAW-002 — Coherence Trajectory Law	Repeated shadow execution alters trajectory
LAW-006 — Time Validation Law	Execution must be time-validated
LAW-009 — U4 / U6 Truth Law	Claims of justified execution require field validation
LAW-013 — Auditability-Debt Law	High-risk execution must remain auditable
LAW-016 — Inversion Formation Law	Shadow execution justified as principle creates inversion
LAW-024 — Latency–Gain Oscillation Law	High-gain shadow execution can destabilize rapidly
LAW-030 — Slack Sovereignty Law	Light protects slack and sovereignty
LAW-036 — Signal Artifact Law	Shadow perception may confuse artifact and signal
LAW-038 — Pattern Recognition Discipline Law	Shadow simulation requires disciplined interpretation
LAW-039 — Identity-Binding Hard Rule	Do not bind identity to shadow simulation
LAW-041 — Boundary Membrane Law	Light filters boundary admissibility
LAW-043 — Safe Coupling Law	Execution must preserve safe coupling
LAW-045 — Force Debt Law	Shadow execution often creates force debt
LAW-048 — Feedback Integrity Law	Feedback detects execution effects
LAW-050 — Control-Restoration Separation Law	Control capacity is not restoration authorization
LAW-052 — Stability Proof Law	Execution must survive perturbation
LAW-057 — Deception Instability Law	Deception capacity destabilizes when executed
LAW-064 — Restoration Debt Reduction Law	Execution should not increase hidden debt
LAW-065 — Pseudo-Restoration Law	Shadow action can be disguised as repair
LAW-067 — Temporal Proof Law	Light-authorized action still requires time proof
LAW-074 — Restoration Before Exploration Law	Shadow exploration must be bounded
LAW-085 — Principle Constraint Field Law	Light operationalizes principle constraints
LAW-086 — Principle Inversion Law	Light prevents principle inversion during execution
LAW-088 — Empathy–Sovereignty Law	Empathy must be bounded before execution
LAW-089 — Wisdom Timing Law	Light includes timing and scale filters
LAW-093 — Archetypal Scaling Law	Archetypal shadow capacity requires stricter execution filters at scale
LAW-096 — Sacred Constraint Law	Sacred constraints shape inadmissible execution
LAW-097 — Experience–Interpretation Separation Law	Shadow signals require interpretation discipline
LAW-098 — Awakening Stabilization Law	High-gain opening requires Light stabilization
LAW-101 — Paradox Dimensionality Law	Light may resolve apparent conflict across dimensions
LAW-117 — Shadow–Light Security Law	Security-specific expression of this law
LAW-127 — AI Decision Pipeline Law	AI execution must pass through Shadow simulation and Light filtering

Aliases folded into this law:

Shadow–Light Execution Law
Shadow Reveals Capacity Law
Light Governs Execution Law
Could-Do / May-Do Law
Adversarial Capacity Filter Law
Shadow Simulation Light Authorization Law
Capacity Is Not Permission Law

Deduplication note:

This law should remain the root Shadow–Light execution law. LAW-117 specializes the pattern for security, LAW-127 specializes it for AI decision pipelines, LAW-086 handles principle inversion, and LAW-089 governs timing and scale of execution.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies possible action, admissible action, refusal, risk, and execution status
`Π`	Provides controls, gates, enforcement, containment, or refusal mechanisms
`Ξ`	Captures inversion when shadow action is justified as principle
`⊗`	Coupling intensity changed by shadow-informed execution
`ℛ`	Repairs debt created by unauthorized or harmful execution
`Τ`	Validates execution over time
`Θ`	Prevents overidentification with shadow capacity
`Σ`	Defines the admissible execution region
`Ψ`	Field and affected-node feedback reveals execution effects
`Λ`	Compatibility determines whether action can couple coherently with the field

Coherent operator sequence:

textScroll

SI(reveal could-do) → Θ(capacity humility) → Γ(classify risk/action) → Σ(admissible scope) → LI(principle authorization) → Π(refuse or gate execution) → Ψ(validate field effects) → Τ(validate coherence)

Inverted operator sequence:

textScroll

SI reveals capacity → capacity fascination / identity → LI bypassed → execution → H↑ → Ξ / ι↑ → O↓

14. Machine-Readable Summary

yamlScroll

id: "LAW-087"
name: "Shadow–Light Execution Law"
type: "law"
status: "draft"
family:
  - "Principle, Archetype, and Meaning Laws"
summary: "Shadow reveals capacity, while Light governs execution by filtering what may be enacted coherently."
canonical_statement: "Shadow reveals capacity. Light governs execution."
core_form: "SI reveals could-do space; LI filters may-do space"
shadow_capture_form: "SI without LI ⇒ shadow capture"
naive_light_form: "LI without SI ⇒ naïve light / risk blindness"
execution_valid_form: "SI simulation + LI authorization + Σ/BΣ intact + FI intact ⇒ coherent execution possible"
variables:
  primary:
    - "SI"
    - "LI"
    - "O"
    - "H"
    - "ι"
    - "Ξ"
    - "BΣ"
    - "Σ"
    - "K"
    - "σ"
    - "Au"
    - "FI"
  secondary:
    - "ε"
    - "R"
    - "R_eff"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "ℛ"
    - "Θ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Shadow Capacity"
  - "Light Authorization"
  - "Execution Admissibility"
  - "Shadow Capture Risk"
  - "Constraint Field Integrity"
  - "Boundary Integrity"
  - "Hidden Debt"
  - "Inversion"
  - "Feedback Integrity"
  - "Coherence Trajectory"
  - "Temporal Proof"
  - "Force Debt"
failure_modes:
  - "Shadow Capture"
  - "Capacity-Permission Confusion"
  - "Adversarial Simulation Capture"
  - "Light Bypass"
  - "Naïve Light"
  - "Shadow Without Authorization"
  - "Execution Without Constraint"
  - "Force Debt"
  - "Deception Capture"
  - "Boundary Violation"
  - "Pseudo-Alignment"
  - "Coherence Drift"
  - "Legitimacy Debt"
restoration_arcs:
  - "Shadow–Light Rebalancing"
  - "Execution Constraint Repair"
  - "Boundary Reconstitution"
  - "Feedback Integrity Restoration"
  - "Inversion Reduction"
  - "Hidden Debt Reduction"
  - "Auditability Restoration"
  - "Discernment Spine Restoration"
  - "Restoration Capacity Rebuild"
  - "Temporal Validation"
related_laws:
  - "LAW-001"
  - "LAW-002"
  - "LAW-006"
  - "LAW-009"
  - "LAW-013"
  - "LAW-016"
  - "LAW-024"
  - "LAW-030"
  - "LAW-036"
  - "LAW-038"
  - "LAW-039"
  - "LAW-041"
  - "LAW-043"
  - "LAW-045"
  - "LAW-048"
  - "LAW-050"
  - "LAW-052"
  - "LAW-057"
  - "LAW-064"
  - "LAW-065"
  - "LAW-067"
  - "LAW-074"
  - "LAW-085"
  - "LAW-086"
  - "LAW-088"
  - "LAW-089"
  - "LAW-093"
  - "LAW-096"
  - "LAW-097"
  - "LAW-098"
  - "LAW-101"
  - "LAW-117"
  - "LAW-127"
related_invariants:
  - "INV-001"
  - "INV-002"
  - "INV-006"
  - "INV-080"
operator_sequence:
  coherent:
    - "SI reveal could-do"
    - "Θ capacity humility"
    - "Γ classify risk/action"
    - "Σ admissible scope"
    - "LI principle authorization"
    - "Π refuse or gate execution"
    - "Ψ validate field effects"
    - "Τ validate coherence"
  inverted:
    - "SI reveals capacity"
    - "capacity fascination / identity"
    - "LI bypassed"
    - "execution"
    - "H↑"
    - "Ξ / ι↑"
    - "O↓"
aliases:
  - "Shadow–Light Execution Law"
  - "Shadow Reveals Capacity Law"
  - "Light Governs Execution Law"
  - "Could-Do / May-Do Law"
  - "Adversarial Capacity Filter Law"
  - "Shadow Simulation Light Authorization Law"
  - "Capacity Is Not Permission Law"
deduplication_note: "Root Shadow–Light execution law. LAW-117 specializes the pattern for security, LAW-127 specializes it for AI decision pipelines, LAW-086 handles principle inversion, and LAW-089 governs timing and scale of execution."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-087 — Shadow–Light Execution Law

Shadow reveals capacity. Light governs execution.

Core form:

textScroll

SI reveals could-do space
LI filters may-do space

Plain meaning:

Shadow-capture form:

textScroll

SI without LI ⇒ shadow capture

Naïve-light form:

textScroll

LI without SI ⇒ naïve light / risk blindness

Execution-valid form:

textScroll

SI simulation + LI authorization + Σ/BΣ intact + FI intact ⇒ coherent execution possible

Primary variables:

SI, LI, O, H, ι, Ξ, BΣ, Σ, K, σ, Au, FI, R, R_eff, µᵢ, Γ, Π, ℛ, Θ, Ψ, Τ

Diagnostic signature:

A system detects a powerful or harmful possible action, but authorization is unclear; boundary stress rises, principle constraints weaken, execution pressure increases, and capacity starts being treated as permission.

Failure risk:

Shadow capture, capacity-permission confusion, adversarial simulation capture, Light bypass, naïve Light, shadow without authorization, execution without constraint, force debt, deception capture, boundary violation, pseudo-alignment, coherence drift, legitimacy debt.

Restoration priority:

Identify shadow capacity, separate possibility from permission, define Light authorization gates, apply principle, boundary, consent, and restoration constraints, preserve auditability, refuse inadmissible action, repair past shadow debt, and time-validate coherent execution.

LAW-086 — Principle Inversion Law

Registry

LAW-088 — Empathy–Sovereignty Law