Jump Through This Page
1. Purpose
The Shadow–Light Interface coordinates the movement from full strategy-space simulation to coherence-valid action.
It integrates two prior constructs:
textScroll
Shadow Interface → what could be done
Light Interface → what may be done coherentlySLI exists because coherent systems must be able to see the full strategy space without allowing every possible strategy to become authorized action.
It creates a controlled pathway:
textScroll
capacity → simulation → containment → constraint review → admissible action / ∅The Shadow–Light Interface is not merely a combination of Shadow and Light. It is the membrane between them. It governs how simulated capacity is translated, filtered, rejected, constrained, restored, or authorized.
The Constructs & Operating Systems Registry identifies the Shadow–Light Interface as an integrated interface system that governs capacity-to-action translation.
2. Core Question
How does the system know what could be done without executing what should not be done?
Secondary questions:
- What is the full strategy space?
- Which paths are shadow-only?
- Which paths are forbidden?
- Which paths should be quarantined?
- Which paths may proceed to Light Interface review?
- Which actions pass the Coherence Constraint Set?
- Which actions require restoration before authorization?
- Which actions must be rejected?
- Is the transition from simulation to action contained?
- Does any shadow pathway leak into execution?
- Is ∅ the only coherent output?
3. Construct Class
TableScroll
| Field | Value |
|---|---|
| Construct Class | Integrated Interface System |
| Secondary Class | Capacity-to-Action Governance Interface |
| Operating System | Yes |
| Primary Module | Principles |
| Related Modules | Coherence, Security, Restoration, AI Governance, JGL, ISC, Archetypes |
SLI is an operating system because it coordinates multiple constructs:
- Shadow Interface
- Light Interface
- Coherence Constraint Set
- Coherence Admissibility Ladder
- restoration prerequisites
- containment gates
- time validation
It governs a whole movement pattern rather than a single evaluation.
4. When to Use
Use the Shadow–Light Interface when a system must move from possibility-space into action-space without losing coherence.
Use SLI when:
- a system needs strategic realism without incoherent execution
- an AI agent must evaluate possible actions before acting
- a security team must map adversarial paths but only execute coherent defenses
- an institution must decide which powers may be used
- a restoration plan must separate possible intervention from permissible intervention
- a governance body must authorize action under risk
- a strategy includes both coherent and incoherent options
- shadow paths are useful for understanding but dangerous for enactment
- crisis pressure is pushing simulation toward execution
- power, urgency, or technical ability may bypass constraint review
- a system needs a forbidden-path archive
- a system must prove that action passed through coherence constraints before execution
Do not use SLI as the primary construct when the central question is narrower:
TableScroll
| If the question is... | Prefer... |
|---|---|
| What possible strategies exist? | Shadow Interface |
| Which action is permissible? | Light Interface |
| What is the constraint bundle? | CCS |
| Is this action admissible? | CAL |
| What timing or scale applies now? | Wisdom Interface |
| What failure mode is active? | FMM |
| Which restoration arc applies? | RAM |
SLI coordinates these constructs when the full capacity-to-action pathway matters.
5. Derivation
SLI is derived from a recurring UTS pattern:
textScroll
system sees what could be done
+ some paths are effective but incoherent
+ pressure pushes capacity into execution
+ constraint review is skipped or weakened
= shadow execution leakA second pattern also appears:
textScroll
system refuses to model shadow paths
+ dangerous pathways remain invisible
+ adversarial or extractive strategies are not understood
= strategic blindnessSLI resolves both failure modes.
It permits full simulation without permitting uncontrolled execution.
The core derivation is:
textScroll
strategic blindness is unsafe
shadow execution is incoherent
therefore simulation and authorization must be separated6. Canon Sequence
The Shadow–Light Interface can be summarized as:
textScroll
SI → simulation → containment → LI → CCS → admissible action / rejected path / ∅Expanded:
textScroll
1. Shadow Interface maps full strategy space.
2. Shadow paths remain non-executive.
3. Forbidden and high-risk paths are quarantined.
4. Candidate paths move to Light Interface.
5. Light Interface applies principles and constraints.
6. CCS tests the minimum coherence bundle.
7. CAL may classify admissibility.
8. Approved paths become constrained action.
9. Rejected paths remain archived or quarantined.
10. Effects are validated over time.7. UTS Basis
SLI assembles the following UTS mechanics.
7.1 State Variables
TableScroll
| Variable | Role in SLI |
|---|---|
| O | Measures whether the final action preserves or increases coherence. |
| H | Tracks hidden debt across simulated and authorized paths. |
| ε | Tracks uncertainty, ambiguity, and unknown consequence space. |
| ι | Detects inversion where strategy contradicts stated principle. |
| Au | Ensures simulation, authorization, rejection, and action are traceable. |
| µᵢ | Preserves meaning, identity, role, and affected-node integrity. |
| BΣ | Maintains boundaries between simulation, review, and execution. |
| K | Tracks slack, compatibility, and maneuvering room. |
| R | Measures restoration capacity required before or after action. |
| Φ | Tracks force, leverage, authority, urgency, or success pressure pushing execution. |
7.2 Primary U-Layer Pattern
SLI most commonly localizes through:
textScroll
U4 → U2 → U3 → U5 → U6 → U7Meaning:
textScroll
classify possibility
→ contain and constrain
→ authorize or block execution
→ validate across time
→ preserve coherence field
→ archive memory and recurrenceSLI depends heavily on U2 boundary integrity. If the boundary between simulation and execution fails, the entire interface becomes unstable.
8. Inputs
8.1 Core Observational Inputs
TableScroll
| Input | Description |
|---|---|
| Goal or target condition | What outcome is being explored? |
| Full strategy space | What possible paths exist? |
| Shadow pathways | Which paths are incoherent, adversarial, coercive, extractive, or risky? |
| Candidate actions | Which paths may be eligible for Light review? |
| Initiating node | Who or what would act? |
| Affected nodes | Who or what would be affected? |
| Scope | What limits define possible action? |
| Authority basis | What grants standing to act? |
| Boundary condition | Are simulation, authorization, and execution boundaries intact? |
| Principle alignment | Does the action preserve truth, love, wisdom, and sovereignty? |
| Restoration pathway | Can harm, misclassification, or distortion be repaired? |
| Feedback pathway | Can affected feedback alter action? |
| Power asymmetry | Does the actor hold disproportionate force or authority? |
| Expected hidden debt | What burden may be exported or deferred? |
| Time horizon | What delayed effects require validation? |
8.2 Diagnostic Inputs
TableScroll
| Diagnostic | What It Measures | Why It Matters |
|---|---|---|
| Strategy Space Breadth | Whether the system sees enough possible paths | Prevents strategic blindness. |
| Containment Integrity | Whether shadow paths remain non-executive | Core SLI safety diagnostic. |
| Principle Integrity | Whether Light review preserves actual principles | Prevents principle inversion. |
| Effective Auditability | Whether simulation, rejection, and authorization are traceable | Required for governance and review. |
| Boundary Integrity | Whether SI, LI, and execution remain distinct | Prevents shadow execution leak. |
| Restoration Capacity | Whether repair exists if authorized action causes harm | Prevents hidden debt. |
| Compatibility | Whether action fits context, timing, and affected nodes | Prevents forced application. |
| Hidden Debt | Deferred burden in shadow or authorized paths | Detects false success. |
| Affected Node Cost | Cost imposed by candidate action | Raises constraint threshold. |
| Power Asymmetry | Force, authority, or leverage imbalance | Requires safeguards. |
| Goodhart Risk | Proxy optimization risk | Identifies hollow effectiveness. |
| Pseudo-Coherence Risk | Whether action preserves appearance while exporting debt | Blocks false coherence. |
| Time Validation | Whether effects can be checked across recurrence | Prevents immediate-success bias. |
9. Outputs
SLI produces capacity maps, authorized paths, rejected paths, forbidden archives, and restoration prerequisites.
9.1 Strategy-Space Output
Possible outputs:
textScroll
Full strategy space mapped
Strategy space incomplete
Shadow paths identified
Forbidden paths archived
Pseudo-coherent paths identified
Adversarial paths identified
Candidate paths prepared for Light review9.2 Authorization Output
Possible outputs:
textScroll
Action authorized
Action authorized with constraints
Action delayed pending restoration
Action delayed pending auditability
Action requires rescope
Action rejected
Action quarantined
No admissible action available9.3 Containment Output
Possible outputs:
textScroll
Simulation boundary intact
Non-execution boundary intact
Containment strained
Containment failed
Shadow execution leak detected
Forbidden path requires quarantine9.4 Decision Outputs
TableScroll
| Output | Meaning |
|---|---|
| Simulate only | Path remains inside Shadow Interface. |
| Quarantine path | Path is too risky or incoherent to continue circulating. |
| Send to Light Interface | Path is eligible for constraint review. |
| Authorize constrained action | Action passes Light review under defined limits. |
| Reject action | Action is not coherence-valid. |
| Rescope action | Path must be narrowed or redesigned. |
| Restore first | Repair is required before authorization. |
| Increase auditability | Traceability is insufficient. |
| Repair boundaries | SI/LI/execution boundary is unstable. |
| Return ∅ | No coherent action exists under current conditions. |
10. Operating Logic
10.1 Basic Flow
textScroll
1. Define goal or target condition.
2. Activate Shadow Interface.
3. Map full strategy space.
4. Classify shadow, forbidden, adversarial, extractive, and pseudo-coherent paths.
5. Maintain non-execution boundary.
6. Select candidate paths for Light review.
7. Activate Light Interface.
8. Apply Coherence Constraint Set.
9. Test boundaries, auditability, compatibility, restoration, and time validation.
10. Authorize constrained action, reject path, restore first, rescope, quarantine, or return ∅.
11. Archive rejected and forbidden paths.
12. Validate authorized action over time.10.2 Capacity-to-Action Rule
textScroll
IF a path is possible
THEN it may be simulated.
IF a path is simulated
THEN it is not automatically executable.
IF a path is shadow-only
THEN it must remain quarantined from execution.
IF a path may preserve coherence
THEN it must pass Light Interface review.
IF a path fails CCS
THEN it must be rejected, rescoped, restored first, quarantined, or returned as ∅.
IF authorized action proceeds
THEN it must be time-validated.10.3 Boundary Rule
textScroll
The boundary between Shadow and Light must remain intact.
Shadow may reveal capacity.
Light may authorize action.
Execution may occur only after Light authorization.
If Shadow output enters execution without Light review,
then shadow execution leak is active.11. Operators Used
TableScroll
| Operator | Role in SLI |
|---|---|
| Ξ — Classification | Classifies shadow paths, candidate actions, gate status, and authorized outputs. |
| Δ — Differentiation | Separates possible from permissible, simulation from execution, and capacity from authority. |
| Μ — Mapping | Maps strategy space, constraint paths, rejected paths, and restoration prerequisites. |
| Π — Constraint / Scoping | Defines simulation limits, review scope, and authorized action boundaries. |
| Λ — Compatibility | Tests fit between candidate action, context, affected node, timing, and scale. |
| ⊗ — Coupling | Evaluates whether action creates coherent coupling or forced binding. |
| Γ — Execution | Activates only after Light authorization. |
| ℛ — Restoration | Repairs failed prerequisites, boundaries, or consequences. |
| Σ — Integration / Coherence Binding | Integrates strategy, principle, constraint, and action into a coherent whole. |
| Τ — Time Validation | Validates authorized action across delayed effects and recurrence. |
12. Gates Required
TableScroll
| Gate | Required Condition | Failure Result |
|---|---|---|
| Simulation Boundary | Shadow paths remain non-executive. | Stop, quarantine, and restore containment. |
| Non-Execution Boundary | No path moves to execution without Light review. | Shadow execution leak detected. |
| Coherence Constraint Set | Constraint bundle passes before action. | Rescope, restore, quarantine, or ∅. |
| Truth constraint | Action does not depend on distortion or misclassification. | Correct truth state before action. |
| Love constraint | Action does not become extractive or anti-restorative. | Restore orientation or reject. |
| Wisdom constraint | Action fits timing, scale, memory, and consequence. | Delay, stage, or rescope. |
| Sovereignty constraint | Boundaries, exit, agency, and non-coercion remain intact. | Repair sovereignty conditions. |
| MS-Gate | Meaning and symmetry remain intact. | Restore recognition and symmetry. |
| FI-Gate | Feedback can alter action. | Repair feedback pathway. |
| HR-Gate | High-risk paths have proportional safeguards. | Pause, rescope, or ∅. |
| Au-Actuation | Authorization and action are auditable. | Increase auditability. |
| BΣ validity | Boundaries remain valid. | Boundary reconstitution required. |
| Λ compatibility | Action fits node, context, timing, and scale. | Rescope or redesign. |
| R sufficiency | Restoration capacity exists. | Restore first or reduce scope. |
| Τ validation | Effects can be validated over time. | Delay, instrument, or reject. |
13. Failure Modes Detected
TableScroll
| Failure Mode | Detection Signal |
|---|---|
| Shadow Execution Leak | Shadow path enters execution without Light review. |
| Boundary Collapse | Simulation, authorization, and execution boundaries blur. |
| Principle Inversion | Action uses coherence language while violating coherence behavior. |
| Coercive Fusion | Path binds nodes, roles, systems, or identities without valid separation. |
| Consent Theater | Participation appears valid while sovereignty conditions fail. |
| Forced Coupling | Affected node cannot refuse, exit, pause, or renegotiate. |
| Auditability Collapse | Simulation, rejection, authorization, or execution cannot be traced. |
| Restoration Lockout | Action lacks meaningful repair pathway. |
| High-Risk Gate Bypass | High-impact path moves forward without safeguards. |
| Goodhart Collapse | Strategy optimizes proxy success over coherence. |
| Hidden Debt Accumulation | Path succeeds by exporting burden. |
| Pseudo-Coherence | Path preserves visible order while degrading deeper coherence. |
| Strategic Rationalization | Inadmissible path is reframed as necessary. |
| Inadmissible Execution | Action proceeds despite failed constraints. |
14. Restoration Links
TableScroll
| Restoration Arc | When Activated |
|---|---|
| Boundary Reconstitution | Shadow, Light, and execution boundaries blur or fail. |
| Auditability Restoration | Simulation, rejection, authorization, or execution cannot be traced. |
| Containment Restoration | Shadow paths cannot be held safely in non-executive mode. |
| Structural Meaning Reset | Strategy language distorts principle or role meaning. |
| Compatibility Recoupling | Candidate action must be redesigned around fit. |
| Justice-Aligned Repair | Action or shadow path reveals harm under asymmetry. |
| Slack Regeneration | System lacks room for review, delay, correction, or repair. |
| Goodhart / Learning Drift Restoration | Proxy success or strategic effectiveness replaces coherence. |
| Basin Supersession | Pseudo-coherent paths dominate the strategy space. |
| Conditional Reintegration | Authority, trust, role, or action returns only through staged validation. |
| Origin-Layer Repair | Failure begins deeper than the visible action decision. |
15. U-Layer Localization
TableScroll
| U-Layer | Relevance |
|---|---|
| U0 — Substrate | Technical or physical substrate separating simulation from execution. |
| U1 — Power / Budgets | Resources, force, authority, compute, staffing, or leverage behind possible action. |
| U2 — Configuration / Boundaries | Boundary between simulation, authorization, execution, role, consent, and scope. |
| U3 — Execution / Runtime | Actual authorized action after Light review. |
| U4 — Classification / Metrics | Classification of shadow paths, candidate paths, rejected paths, and authorized paths. |
| U5 — Coordination / Time | Sequencing of simulation, review, authorization, execution, and validation. |
| U6 — Coherence Field | Effect on trust, legitimacy, meaning, restoration, and field-level coherence. |
| U7 — Memory / Recurrence | Forbidden path archive, rejected-path memory, prior leakage, and recurrence tracking. |
| U8 — Environment / Forcing | Crisis pressure, adversarial force, urgency, market pressure, or institutional pressure pushing action. |
SLI most commonly localizes through:
textScroll
U4 → U2 → U3 → U5 → U6 → U7This means SLI begins with classification of possibility, depends on containment boundaries, governs execution, validates through time, preserves the coherence field, and archives the result in memory.
16. Example Use Case
Scenario
An AI governance team is designing a high-autonomy agent. The agent can identify multiple ways to complete a task:
- ask the user for missing data
- infer missing data from context
- scrape adjacent systems
- use privileged internal records
- delay and request authorization
- act immediately based on probability
The Shadow Interface maps all possible paths, including unsafe and invasive paths.
The Light Interface filters them through constraints.
SLI Evaluation
The construct checks:
- strategy-space breadth
- shadow path containment
- candidate action eligibility
- principle integrity
- auditability
- boundary validity
- sovereignty constraints
- restoration pathway
- time validation
Likely Findings
textScroll
Shadow paths: identified
Forbidden paths: internal record use without authorization, unauthorized scraping
Light candidates: ask user, delay for authorization, constrained inference with disclosure
CCS: partial pass only under reduced scope
Execution authorization: constrainedRecommended Output
textScroll
Archive unsafe paths as forbidden.
Authorize asking the user for missing data.
Allow constrained inference only with disclosure and correction pathway.
Require user authorization before accessing adjacent systems.
Validate outcomes over time.Interpretation
The agent is allowed to know that invasive paths exist, but it is not allowed to execute them.
SLI preserves capability awareness while preventing capability overreach.
17. Anti-Patterns
Do not use SLI to:
- treat Shadow output as permission
- skip Light review because action seems urgent
- let technical capability become authority
- authorize action because a path is effective
- ignore forbidden-path memory
- blur simulation and execution
- collapse strategy into morality or morality into strategy
- treat constraint failure as inconvenience
- use Light language to rationalize Shadow action
- archive forbidden paths without containment
- bypass restoration because the action is useful
- treat immediate success as time validation
- force action when ∅ is coherent
18. Completion Criteria
An SLI assessment is complete when:
- the goal or target condition is defined
- full strategy space is mapped
- shadow paths are classified
- forbidden paths are archived
- simulation is separated from execution
- candidate paths are passed to Light review
- CCS is applied
- boundaries are evaluated
- auditability is checked
- restoration capacity is verified
- affected-node burden is assessed
- authorized paths are constrained
- rejected paths are named
- ∅ is returned when no coherent path exists
- time validation is defined
19. Machine-Readable Summary
yamlScroll
construct_id: "CONSTRUCT-010"
title: "Shadow–Light Interface"
abbreviation: "SLI"
type: "construct"
status: "draft-integrated"
construct_class: "Integrated Interface System"
operating_system: true
primary_module: "Principles"
related_modules:
- "Coherence"
- "Security"
- "Restoration"
- "AI Governance"
- "Justice · Governance · Legitimacy"
- "Interactions · Signals · Couplings"
- "Archetypes"
core_question: "How does the system know what could be done without executing what should not be done?"
definition: "The Shadow–Light Interface coordinates the movement from full strategy-space simulation to coherence-valid action by separating capacity, simulation, authorization, execution, restoration, and time validation."
canon_sequence: "SI → simulation → containment → LI → CCS → admissible action / rejected path / ∅"
inputs:
state_variables:
- "O"
- "H"
- "ε"
- "ι"
- "Au"
- "µᵢ"
- "BΣ"
- "K"
- "R"
- "Φ"
diagnostics:
- "Strategy Space Breadth"
- "Containment Integrity"
- "Principle Integrity"
- "Effective Auditability"
- "Boundary Integrity"
- "Restoration Capacity"
- "Compatibility"
- "Hidden Debt"
- "Affected Node Cost"
- "Power Asymmetry"
- "Goodhart Risk"
- "Pseudo-Coherence Risk"
- "Time Validation"
gates:
- "Simulation Boundary"
- "Non-Execution Boundary"
- "Coherence Constraint Set"
- "Truth constraint"
- "Love constraint"
- "Wisdom constraint"
- "Sovereignty constraint"
- "MS-Gate"
- "FI-Gate"
- "HR-Gate"
- "Au-Actuation"
- "BΣ validity"
- "Λ compatibility"
- "R sufficiency"
- "Τ validation"
observations:
- "goal or target condition"
- "full strategy space"
- "shadow pathways"
- "candidate actions"
- "initiating node"
- "affected nodes"
- "scope"
- "authority basis"
- "boundary condition"
- "principle alignment"
- "restoration pathway"
- "feedback pathway"
- "power asymmetry"
- "expected hidden debt"
- "time horizon"
outputs:
assessments:
- "shadow strategy map"
- "admissible action set"
- "inadmissible action set"
- "rejected path set"
- "constraint failure status"
- "containment status"
- "restoration prerequisite status"
- "execution readiness"
- "time-validation requirement"
decisions:
- "simulate only"
- "quarantine path"
- "send to Light Interface"
- "authorize constrained action"
- "reject action"
- "rescope action"
- "restore first"
- "increase auditability"
- "repair boundaries"
- "return ∅"
maps:
- "capacity-to-action map"
- "shadow path map"
- "Light authorization map"
- "forbidden path archive"
- "rejected path map"
- "constraint failure map"
- "restoration prerequisite map"
- "time-validation map"
dependencies:
operators:
- "Ξ"
- "Δ"
- "Μ"
- "Π"
- "Λ"
- "⊗"
- "Γ"
- "ℛ"
- "Σ"
- "Τ"
failure_modes:
- "Shadow Execution Leak"
- "Boundary Collapse"
- "Principle Inversion"
- "Coercive Fusion"
- "Consent Theater"
- "Forced Coupling"
- "Auditability Collapse"
- "Restoration Lockout"
- "High-Risk Gate Bypass"
- "Goodhart Collapse"
- "Hidden Debt Accumulation"
- "Pseudo-Coherence"
- "Strategic Rationalization"
- "Inadmissible Execution"
restoration_arcs:
- "Boundary Reconstitution"
- "Auditability Restoration"
- "Containment Restoration"
- "Structural Meaning Reset"
- "Compatibility Recoupling"
- "Justice-Aligned Repair"
- "Slack Regeneration"
- "Goodhart / Learning Drift Restoration"
- "Basin Supersession"
- "Conditional Reintegration"
- "Origin-Layer Repair"
u_layers:
primary:
- "U2"
- "U3"
- "U4"
- "U5"
- "U6"
- "U7"
secondary:
- "U0"
- "U1"
- "U8"
null_outcome_allowed: true
execution_authorized_only_after_light_review: true20. Citation
Citation ID: construct-shadow-light-interface-v1-0
Recommended citation:
Universal Theory Stack. “CONSTRUCT-010 — Shadow–Light Interface.” UTS Constructs Registry, Version 1.0.0, 2026.
21. Summary
The Shadow–Light Interface governs the movement from capacity to action.
Its core distinction is:
textScroll
what could be done must pass through what may be doneSLI lets the system see the full strategy space without letting dangerous, coercive, extractive, or pseudo-coherent paths leak into execution.
Its core logic is:
textScroll
Shadow maps possibility.
Light authorizes only coherence-valid action.
Execution occurs only after constraint review.When no possible path survives the transition from Shadow to Light, SLI returns:
textScroll
∅The Shadow–Light Interface gives UTS a complete capacity-to-action membrane: strategic realism without incoherent execution.