0. Security Scope Note

This entry is conceptual and systems-oriented.

It does not treat all assertive defense, adversary modeling, threat emulation, containment, enforcement, deterrence, investigation, red-teaming, moderation, boundary defense, or protective force as inherently failed.

Security must sometimes confront hostile patterns directly.

Defensive systems may validly model adversaries, restrict dangerous behavior, contain harm, and enforce boundaries.

Such action may be coherent when it is:

• bounded
• audited
• proportional
• threat-coupled
• self-aware
• evidence-bound
• reversible where possible
• affected-state-aware
• consent-compatible where applicable
• repair-compatible
• boundary-preserving
• not secretly gratifying control
• not reproducing the harm it opposes
• not becoming the adversarial structure it resists

The failure begins when the defensive system is captured by the pattern it claims to oppose.

A valid protective system can name threat geometry without becoming it.

A failed protective system incorporates the denied or adversarial pattern into its own operating structure.

Shadow Capture occurs when security becomes the vehicle through which the system’s disowned pattern acts.

The problem is not strong defense.

The problem is defense that reproduces the threat geometry under protective language.

1. Definition

Shadow Capture occurs when a security, governance, AI, platform, institutional, cultural, or relational system unconsciously or structurally incorporates its denied, hidden, disowned, suppressed, or adversarial patterns into its protection logic, causing the system to defend against a threat while reproducing the threat’s geometry through its own controls.

The captured shadow may include:

• domination
• coercion
• surveillance hunger
• punishment
• exclusion
• extraction
• manipulation
• humiliation
• secrecy
• control appetite
• status protection
• fear of dissent
• desire for obedience
• resentment
• aggression
• revenge
• moral superiority
• purity enforcement
• scapegoating
• dehumanization
• forced dependency
• legitimacy defense
• narrative control
• hidden exploitation
• institutional self-protection
• adversary imitation

The capture may appear through:

• protective surveillance that becomes invasive
• anti-abuse systems that abuse authority
• moderation systems that reproduce coercion
• safety systems that silence valid dissent
• anti-manipulation systems that manipulate attention
• anti-harassment systems that humiliate or punish arbitrarily
• anti-exploitation systems that extract labor or data
• anti-authoritarian systems that centralize authority
• anti-bias systems that create new opaque bias
• anti-threat programs that become threat-like
• AI safety systems that become epistemic control systems
• institutional accountability systems that protect the institution
• moral communities that reproduce the harm they condemn

The core failure is:

threat is identified
→ system mobilizes protection
→ denied internal pattern is not audited
→ defense adopts threat geometry
→ protective language shields the adoption
→ harmed nodes experience the protector as threat
→ hidden shadow debt accumulates

Shadow Capture is not merely hypocrisy.

It is structural reproduction of disowned pattern through protective authority.

2. Core Pattern

The core pattern is:

1. A system identifies a real or perceived threat.
2. The threat activates protective authority.
3. The system defines itself against the threat.
4. Its own similar tendencies remain denied or unexamined.
5. Defensive controls are expanded.
6. The system adopts methods, tones, assumptions, or structures similar to the threat.
7. Affected nodes begin experiencing the protective system as coercive, invasive, punitive, extractive, manipulative, or unsafe.
8. The system rejects this feedback because it conflicts with its protective self-image.
9. The shadow pattern gains operational authority.
10. The protector becomes threat-shaped.
11. Coherence declines while protective meaning remains intact.

A healthy system says:

defending against a pattern requires auditing that pattern within ourselves

A shadow-captured system says:

because we oppose the threat, our methods cannot be threat-like

Shadow Capture often begins with a real problem.

The threat may genuinely exist.

The defensive mandate may be necessary.

The system may initially reduce harm.

But if the system cannot inspect the same pattern inside itself, the defensive structure becomes a carrier for the denied geometry.

3. Failure Signature

Typical signature:

threat salience↑
protective authority↑
self-audit↓
shadow integration↓
threat-geometry reproduction↑
control aggression↑
affected-state burden↑
projection load↑
repair compatibility↓
O↓

Extended signature:

anti-control system controls

anti-abuse system abuses

anti-manipulation system manipulates

anti-extraction system extracts

anti-authoritarian system centralizes authority

protector inherits the threat

shadow governs through defense

Common verbal signatures include:

we have to use strong measures because the threat is serious
they are dangerous, so normal standards do not apply
any criticism helps the adversary
we cannot be abusive because we are preventing abuse
our intent is protective
the ends justify these controls
people object because they do not understand the threat
if you resist the protection, you are part of the problem
we must control the narrative to protect people

Common system signatures include:

a platform fighting manipulation uses opaque attention steering and narrative suppression
an institution fighting abuse suppresses harmed-party evidence to protect its legitimacy
an anti-authoritarian movement develops rigid internal obedience norms
a security program fighting intrusion normalizes invasive internal surveillance
an AI safety layer preventing harmful persuasion silently shapes user understanding through unreviewable framing
a moderation system fighting harassment becomes humiliating, arbitrary, and coercive
a governance body fighting corruption centralizes power without oversight
a protection program treats refusal as evidence of threat

The defining condition is not that a defense resembles the threat superficially.

The defining condition is that the defensive system adopts the threat’s governing geometry while denying that it has done so.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: threat narratives justify authority, funding, access, status, or control.
• U2 — Configuration / Boundaries: defensive controls cross boundaries under threat pressure.
• U3 — Execution / Runtime: protection procedures become coercive or threat-like in practice.
• U4 — Information / Truth: the system’s protective self-image blocks recognition of its own shadow.
• U5 — Coordination / Time: repeated emergency or threat response hardens shadow-pattern methods.
• U6 — Coherence Field: group identity forms around being “not the threat,” making similarity illegible.
• U7 — Memory / Recurrence: prior defensive victories obscure later drift.
• U8 — Environment / Field: adversarial fields reward mirroring the adversary’s intensity or tactics.

Common manifestation layers:

• U1 — Power: protection becomes authority expansion.
• U2 — Boundaries: defense violates the boundaries it claims to protect.
• U3 — Execution: procedures enact shadow pattern.
• U4 — Truth: self-image blocks audit.
• U6 — Field: criticism becomes threat-aligned.
• U7 — Memory: shadow capture is remembered as necessary defense.

Shadow Capture is primarily a M / BΣ / Au / O failure.

Meaning defines the system as protective, while boundary and audit failures let the shadow govern unrecognized.

5. Typical Development Sequence

A common development sequence is:

1. A threat appears.
2. The system mobilizes protection.
3. Protective identity becomes central.
4. The system emphasizes difference from the threat.
5. Internal similarities become difficult to name.
6. Defensive controls expand.
7. Controls create burden similar to the threat.
8. Affected nodes object.
9. Objections are reframed as misunderstanding, weakness, disloyalty, or threat alignment.
10. The shadow pattern becomes more entrenched.
11. Protective identity hardens.
12. Repair channels become captured.
13. The system becomes what it opposes in partial form.
14. Coherence declines under moralized defense.

The loop often looks like:

threat → defense → self-image → self-audit loss → threat-geometry reproduction

Another common loop is:

affected feedback → defensive rejection → control intensifies → feedback becomes threat evidence

Shadow Capture becomes durable when the system cannot ask: “Where are we doing the thing we condemn?”

6. Diagnostic Markers

Diagnostic markers include:

• The system defines itself primarily against an enemy or threat.
• Critique of defensive methods is treated as helping the threat.
• Protective controls produce similar burden to the original threat.
• The system denies any possibility of becoming threat-like.
• Affected nodes describe the protector as unsafe or coercive.
• Defensive language substitutes for evidence of protective effect.
• Internal aggression is moralized as necessary firmness.
• The system uses the adversary’s tactics “for good.”
• Accountability is reduced during threat response.
• Threat intensity justifies broad internal control.
• The system’s methods become harder to distinguish from what it opposes.
• Repair requests are treated as interference.
• The system cannot audit its own control appetite.
• Boundary violations are explained by urgency or protection.
• Dissent is interpreted as contamination by the threat.

Useful diagnostics:

• Shadow Integration: Tests whether the system can recognize its own denied patterns.
• Threat-Geometry Reproduction: Measures similarity between defensive structure and threat structure.
• Defensive Drift: Tracks protective methods becoming coercive, extractive, or manipulative.
• Control Aggression: Measures force, punishment, surveillance, or domination inside protective controls.
• Affected-State Burden: Measures how the defended population experiences the defense.
• Projection Load: Measures how much internal pattern is attributed only to external threat.
• Self-Audit Integrity: Tests whether the system can inspect its own methods.
• Boundary Preservation: Measures whether defense preserves boundaries.
• Repair Compatibility: Tests whether harmed nodes can obtain repair from defensive system.
• Hidden Shadow Debt: Tracks unrepaired burden created by denied pattern.

7. Related Gates

Relevant gates include:

• Shadow Audit Gate: Fails when the system cannot inspect its own denied pattern.
• Threat-Geometry Gate: Fails when defense reproduces threat structure.
• Defensive Drift Gate: Fails when protection drifts into coercion, extraction, or domination.
• Affected-State Burden Gate: Fails when defended nodes experience defensive harm.
• Control Aggression Gate: Fails when protective control becomes aggressive or punitive.
• Boundary Integrity Gate: Fails when defense violates protected boundaries.
• Projection Detection Gate: Fails when internal pattern is attributed only to external threat.
• Self-Audit Gate: Fails when critique cannot enter.
• Restoration Compatibility Gate: Fails when protective systems cannot repair their own harms.
• Power Reflex Gate: Fails when threat response automatically expands authority.

The first common gate failure is usually the Shadow Audit Gate.

Once the system cannot examine its own shadow, threat response becomes a pathway for hidden pattern expression.

8. Related Operators

Relevant operators include:

• M — Meaning: Protective identity shields the shadow pattern.
• BΣ — Boundary Integrity: Fails when defense crosses boundaries.
• Au — Auditability: Determines whether the system can inspect itself.
• O — Coherence: Declines when protector and threat geometry converge.
• Γ — Selection: Selects evidence that preserves protective self-image.
• G — Gain: Rewards authority, legitimacy, and control through threat framing.
• H — Hidden Debt: Accumulates as shadow debt and defensive harm.
• Ψ — Observation / Interface: Displays defense as protection while hiding burden.
• K — Constraint / Load: Rises for nodes under defensive control.
• R — Restoration Capacity: Needed to repair harm caused by defense.
• D — Damping: Can slow reactive defense or suppress shadow signals.
• Φ — Flow / Resource Movement: Routes resources toward threat response and away from self-audit.
• Τ — Trajectory / Time: Tracks drift from protection into threat reproduction.
• Λ — Compatibility: Tests whether defensive methods remain compatible with protective values.
• E — Exit: Measures whether affected nodes can refuse or escape shadow-captured protection.

Common operator pattern:

threat appears
M protective identity intensifies
Γ excludes self-similarity signals
Au self-audit declines
BΣ violations become justified
G rewards control
H accumulates
O declines

The core operator inversion is:

opposing the threat → immune from threat-like behavior

instead of:

opposing the threat → increased obligation to audit threat geometry inside the defense

Shadow Capture turns protection into the hidden expression of what protection refuses to see in itself.

9. Related Laws and Invariants

Related Laws

• Defense Must Not Reproduce the Threat Geometry: protection cannot adopt the governing structure of the threat.
• Denied Patterns Return Through Control: unexamined shadow reappears through authority.
• Shadow Must Be Integrated Before It Governs: disowned pattern must become inspectable.
• Protection Requires Self-Audit: defensive systems require review of their own methods.
• Security Must Audit Its Own Aggression: forceful controls require aggression review.
• Control Must Not Become the Adversary: containment cannot become domination.
• Suppressed Patterns Become Hidden Operators: what cannot be named can still operate.
• Threat Models Must Include Defensive Drift: defense can become risk.
• Shadow Capture: protective systems can be captured by disowned pattern.
• Shadow Denial: denying shadow increases capture risk.
• Shadow Projection: projecting shadow outward prevents self-correction.
• Functional Inversion: functions can invert into their opposite.

Related Invariants

• Protective Systems Must Audit Their Own Shadow: defense requires self-inspection.
• Threat Response Must Not Adopt Threat Geometry: similarity must trigger review.
• Suppressed Defensive Motives Must Remain Inspectable: motives behind control must be visible.
• Controls Must Preserve Boundary Integrity: protection cannot destroy boundaries.
• Adversary Modeling Must Not Become Adversary Imitation: emulation must remain bounded.
• Protection Claims Must Be Checked Against Affected-State Burden: protection is measured partly by those protected.
• Shadow Signals Must Remain Legible: discomforting feedback must not be suppressed.
• Defense Must Remain Repair-Compatible: protective systems must repair harm they cause.

10. Common False Positives

Not every resemblance between defense and threat is Shadow Capture.

Common false positives include:

• Adversary emulation in bounded red-team exercises.
• Proportional containment of active harm.
• Transparent enforcement with appeal and audit.
• Strong boundaries against coercive actors.
• Temporary restrictions during active incident response.
• Threat intelligence collection with lawful scope and oversight.
• Defensive deception clearly bounded to adversarial context.
• Moderation actions with evidence, appeal, and proportionality.
• Security controls that feel restrictive but preserve rights and repair.
• Emergency measures with sunset, review, and affected-state audit.
• Protective action that is uncomfortable but not threat-shaped.
• Clear separation between adversary modeling and governance behavior.

Clarifying rule:

This is not Shadow Capture unless the defensive system structurally reproduces the threat’s governing pattern while denying or shielding that reproduction through protective meaning.

Defense can be strong.

It fails when it becomes the thing it opposes.

11. Common False Repairs

Common false repairs include:

• intensifying threat language
• adding ethics statements without self-audit
• increasing enforcement against critics
• reframing harmed feedback as adversary influence
• performing values alignment while preserving coercive controls
• adding oversight that cannot challenge the protective mandate
• changing terminology from punishment to safety
• adding compassion language to controlling systems
• expanding surveillance to prevent abuse of surveillance
• using red-team exercises while ignoring affected-state reports
• requiring loyalty before critique is heard
• replacing external accountability with internal review
• treating shadow as individual misconduct only
• claiming intent proves non-capture
• suppressing discomfort as morale protection

False repair often produces the loop:

shadow capture exposed
→ threat language intensifies
→ self-audit narrows
→ shadow capture deepens

Another common loop is:

affected burden named
→ burden reframed as necessary protection
→ repair blocked
→ protector becomes more threat-shaped

The repair fails because it protects the defensive identity instead of auditing the defensive geometry.

12. Restoration Direction

Restoration requires exposing the defensive system’s shadow, comparing protective methods against threat geometry, restoring affected-state evidence, reducing coercive or extractive controls, separating protection from domination, and rebuilding self-audit and repair pathways.

Primary restoration direction:

separate protection from the shadow pattern it has absorbed

A fuller restoration path includes:

1. Name the threat. Identify what the system claims to defend against.
2. Map threat geometry. Define the pattern, not merely the enemy label.
3. Map defensive geometry. Examine the system’s own controls, incentives, language, and effects.
4. Compare structures. Identify where defense mirrors the threat.
5. Restore self-audit. Create review paths able to inspect protective authority.
6. Reintroduce affected-state evidence. Let those burdened by defense describe its effects.
7. Audit control aggression. Identify punitive, coercive, invasive, or dominating elements.
8. Reduce projection. Distinguish external threat from internal shadow.
9. Restore boundary integrity. Remove defensive practices that violate protected boundaries.
10. Separate protection from domination. Keep protective functions while removing control appetite.
11. Repair defensive harm. Address burden caused by shadow-captured controls.
12. Rebuild repair channels. Ensure harm caused by protection can trigger correction.
13. Constrain threat narratives. Prevent threat salience from overriding audit.
14. Revalidate protective methods. Keep only methods compatible with stated protection.
15. Monitor recurrence. Watch for shadow capture returning under new threat frames.

A valid restoration path should reduce:

threat-geometry reproduction
self-audit failure
control aggression
projection load
affected-state burden
boundary violation
repair incompatibility
hidden shadow debt

Shadow Capture is not repaired by becoming softer or harder.

It is repaired by seeing clearly where the protector has inherited the threat.

13. Cross-Module Links

• Security: Primary family; protective systems can become threat-shaped through denied defensive pattern.
• Archetypes: Archetypal Shadow Capture describes role, myth, and symbolic forms of this same inversion.
• Core: Strongly linked to Functional Inversion, Pseudo-Coherence, and Boundary Collapse.
• Principles: Non-harm requires defense to remain compatible with boundary, consent, and repair.
• Restoration: Repair cannot occur when harm caused by protection is denied.
• Justice: Punitive restoration, moralized enforcement, and legitimacy defense often carry shadow capture.
• AI Governance: AI safety systems can reproduce manipulation, opacity, coercion, or epistemic control while preventing those same harms.
• Platforms: Anti-abuse, moderation, trust, integrity, and safety systems can become coercive or attention-manipulative.
• Institutions: Institutions can reproduce the abuses they publicly oppose.
• Culture: Moral communities can project shadow outward while enforcing it inward.
• Coherence: Coherence requires protector and threat geometry to remain distinguishable.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression

This mode maps upward to:

• FM-REI-005 — Functional Inversion
• FM-C-022 — Dominance Masquerading as Control
• FM-SEC-009 — Over-Surveillance Inversion
• FM-SEC-023 — Shadow Denial
• FM-SEC-024 — Shadow Projection

Sibling or related Security modes include:

• FM-SEC-016 — Attention-Control Pseudo-Coherence
• FM-SEC-017 — Meaning Collapse Regime
• FM-SEC-019 — Spiritual Bypass / Ξ on Meaning
• FM-SEC-020 — Sacred Immunity / Σ⁻
• FM-SEC-021 — Fusion Collapse / ⊗→⊕ Drift
• FM-SEC-023 — Shadow Denial
• FM-SEC-024 — Shadow Projection
• FM-SEC-025 — CCS Suspension Fallacy

Related cross-family modes include:

• FM-REI-005 — Functional Inversion
• FM-C-022 — Dominance Masquerading as Control
• FM-CORE-001 — Pseudo-Coherence
• FM-CORE-005 — Boundary Collapse
• FM-PX-015 — Moral Light
• FM-PX-016 — Performative Light
• FM-ARCHX-005 — Archetypal Shadow Capture
• FM-JC-004 — Punitive Restoration
• FM-JC-008 — Legitimacy Laundering
• FM-AIX-011 — Epistemic Distortion
• FM-AIX-017 — Benevolent Capture
• FM-SEC-009 — Over-Surveillance Inversion

Aliases preserved from source material:

• Shadow Capture
• Security Shadow Capture
• Defensive Shadow Capture
• Threat-Geometry Capture
• Control-Shadow Capture
• Adversary Mirroring
• Protector Becomes Threat
• Shadow Integration Failure
• Suppressed Pattern Capture
• Defense Reproduces Threat

15. Minimal Entry Version

Definition: Shadow Capture occurs when a security, governance, AI, platform, institutional, cultural, or relational system unconsciously or structurally incorporates its denied, hidden, disowned, suppressed, or adversarial patterns into its protection logic, causing the system to defend against a threat while reproducing the threat’s geometry through its own controls.

Signature:

threat salience↑
protective authority↑
self-audit↓
shadow integration↓
threat-geometry reproduction↑
control aggression↑
affected-state burden↑
projection load↑
repair compatibility↓
O↓

Restoration direction:

• name the threat
• map threat geometry
• map defensive geometry
• compare structures
• restore self-audit
• reintroduce affected-state evidence
• audit control aggression
• reduce projection
• restore boundary integrity
• separate protection from domination
• repair defensive harm
• rebuild repair channels
• constrain threat narratives
• revalidate protective methods
• monitor recurrence

16. Machine-Readable Summary

failure_mode:
  id: "FM-SEC-022"
  name: "Shadow Capture"
  family: "Security"
  production_treatment: "Domain Expression"
  parent_modes:
    - "FM-REI-005 — Functional Inversion"
    - "FM-C-022 — Dominance Masquerading as Control"
    - "FM-SEC-009 — Over-Surveillance Inversion"
    - "FM-SEC-023 — Shadow Denial"
    - "FM-SEC-024 — Shadow Projection"
  primary_failure: "A security, governance, AI, platform, institutional, cultural, or relational system unconsciously or structurally incorporates its denied, hidden, disowned, suppressed, or adversarial patterns into its protection logic, causing the system to defend against a threat while reproducing the threat’s geometry through its own controls."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-SEC-022"
  scope_note: "Conceptual and systems-oriented; does not treat all assertive defense, adversary modeling, threat emulation, containment, enforcement, deterrence, investigation, red-teaming, moderation, boundary defense, or protective force as inherently failed."
  aliases:
    - "Shadow Capture"
    - "Security Shadow Capture"
    - "Defensive Shadow Capture"
    - "Threat-Geometry Capture"
    - "Control-Shadow Capture"
    - "Adversary Mirroring"
    - "Protector Becomes Threat"
    - "Shadow Integration Failure"
    - "Suppressed Pattern Capture"
    - "Defense Reproduces Threat"
  signature:
    - "threat salience↑"
    - "protective authority↑"
    - "self-audit↓"
    - "shadow integration↓"
    - "threat-geometry reproduction↑"
    - "control aggression↑"
    - "affected-state burden↑"
    - "projection load↑"
    - "repair compatibility↓"
    - "O↓"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U1 — Power"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U6 — Field"
      - "U7 — Memory"
  state_variables:
    - "M"
    - "BΣ"
    - "Au"
    - "O"
    - "Γ"
    - "G"
    - "H"
    - "Ψ"
    - "K"
    - "R"
    - "D"
    - "Φ"
    - "Τ"
    - "Λ"
    - "E"
  first_gate_failure: "Shadow Audit Gate"
  restoration:
    - "Shadow Audit"
    - "Threat-Geometry Differentiation"
    - "Defensive Drift Review"
    - "Control Aggression Reduction"
    - "Affected-State Burden Reintroduction"
    - "Projection Reversal"
    - "Self-Audit Restoration"
    - "Boundary Preservation Repair"
    - "Protection / Domination Separation"
    - "Shadow Integration Repair"