0. Justice Scope Note

This entry is conceptual and systems-oriented.

It does not treat every internal enforcement process, self-regulation mechanism, compliance team, institutional review body, platform moderation system, contract dispute process, private arbitration structure, or industry review mechanism as inherently failed.

Internal enforcement can work.

Self-regulation can work under the right constraints.

Private dispute resolution can be coherent.

Institutional review can be legitimate.

Platform enforcement can be valid.

Governance systems may need domain expertise from the systems they govern.

A coherent enforcement system can remain close to the field it regulates while preserving independence, auditability, remedy authority, override power, conflict protections, evidence access, and affected-state repair.

The failure begins when the enforcement channel becomes dependent on, controlled by, or structurally loyal to the system it must constrain.

Enforcement Capture occurs when enforcement authority exists formally but cannot act against the interests that shape it.

The problem is not proximity.

The problem is constraint losing independence from the thing it must constrain.

1. Definition

Enforcement Capture occurs when a justice, governance, institutional, contractual, platform, security, compliance, legal, AI, or restoration system’s enforcement authority, review pathway, remedy mechanism, audit channel, sanction process, or accountability structure becomes controlled, shaped, constrained, delayed, deflected, or neutralized by the actors, interests, incentives, authorities, funders, platforms, regimes, or basin structures it is supposed to constrain.

The captured enforcement function may include:

• audit
• appeal
• investigation
• sanction
• oversight
• compliance review
• moderation review
• contract enforcement
• grievance process
• arbitration
• safety review
• internal accountability
• external review
• ethics process
• model governance
• platform redress
• institutional review
• legal remedy
• disciplinary process
• regulator action
• public accountability
• restoration process
• recurrence prevention
• boundary correction
• compensation
• affected-state repair

The capture vector may include:

• funding dependence
• employment dependence
• reporting hierarchy
• political dependence
• platform dependence
• data access dependence
• technical access dependence
• legal pressure
• reputational pressure
• industry alignment
• revolving-door incentives
• shared incentives
• social proximity
• loyalty pressure
• conflict of interest
• contractual limitation
• arbitration clause
• confidentiality restriction
• evidence control
• scope control
• timing control
• remedy limitation
• sanction limitation
• veto power
• budget control
• governance capture
• basin preservation pressure

The core failure is:

constraint channel exists
→ constrained actor influences the channel
→ enforcement scope, timing, evidence, remedy, or consequence narrows
→ accountability appears available but cannot bind power
→ affected-state repair fails
→ legitimacy debt accumulates

Enforcement Capture is not merely weak enforcement.

It is enforcement dependence aligned with the interests enforcement must constrain.

2. Core Pattern

The core pattern is:

1. A rule, obligation, right, remedy, standard, audit, or accountability mechanism is created.
2. An enforcement channel is assigned to uphold it.
3. The enforcement channel depends on the system, actor, funder, platform, regime, or basin it must constrain.
4. The captured interest controls access to evidence, budget, timing, scope, authority, staffing, escalation, remedy, or public framing.
5. Enforcement remains visible but loses independence.
6. Cases involving protected interests are delayed, narrowed, privatized, dismissed, softened, redirected, or converted into process.
7. Affected nodes see enforcement fail precisely where power is concentrated.
8. The system cites enforcement availability as proof of legitimacy.
9. Hidden debt accumulates because constraint cannot bind its target.

A healthy system says:

enforcement must retain authority over the enforced

A captured-enforcement system says:

enforcement is legitimate because a review channel exists

The failure is often hard to detect because captured enforcement may still act strongly in low-risk cases.

It may punish weaker actors.

It may enforce against outsiders.

It may process routine violations.

It may produce reports.

It may issue recommendations.

But when the enforcement target is powerful, valuable, politically protected, internally central, or basin-critical, enforcement weakens.

The capture is revealed at the pressure point.

3. Failure Signature

Typical signature:

formal enforcement↑
enforcement independence↓
conflict of interest↑
evidence access asymmetry↑
remedy authority↓
protected-actor accountability↓
selective enforcement↑
hidden justice debt↑
legitimacy claim↑
O↓

Extended signature:

oversight exists,
overseen actor controls scope

audit begins,
audited actor controls evidence

review available,
reviewed system controls remedy

sanction possible,
protected actor exempt

constraint named,
power unbound

Common verbal signatures include:

we investigated ourselves
the review was independent enough
the matter is being handled internally
the committee has no enforcement authority
we can only make recommendations
we do not have access to those records
the scope does not include that issue
the contract limits remedies
the platform retains final discretion
the funder must approve action
legal has advised against disclosure
we cannot comment on personnel matters
the process found no basis for action

Common system signatures include:

an institutional review body reports to the leadership it investigates
a platform appeal system is controlled by the same moderation architecture that caused harm
a contract dispute process is funded and selected by the stronger party
a regulator depends on industry data and cannot independently verify claims
a compliance team lacks authority to stop profitable violations
an AI safety review depends on deployer-controlled model access and metrics
a grievance process can recommend remedy but not require it
a security audit is scoped by the team whose actions are under review
a restoration process is controlled by the basin that benefits from avoiding repair

The defining condition is not that enforcement is imperfect.

The defining condition is that enforcement loses independence from the power it must bind.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: enforcement depends on the funding, authority, permission, data, staffing, or survival of the constrained actor.
• U2 — Configuration / Boundaries: governance boundaries place enforcement inside captured reporting or contract structures.
• U3 — Execution / Runtime: review, sanction, audit, or remedy is softened in practice.
• U4 — Information / Truth: enforcement existence is narrated as accountability while capture is hidden.
• U5 — Coordination / Time: captured enforcement delays action until pressure fades.
• U6 — Coherence Field: legitimacy is maintained through oversight language.
• U7 — Memory / Recurrence: captured outcomes become official precedent.
• U8 — Environment / Field: external incentives reward enforcement that preserves the basin.

Common manifestation layers:

• U1 — Power: enforcement authority is subordinated.
• U2 — Boundaries: independence boundaries fail.
• U3 — Execution: enforcement is neutralized in practice.
• U4 — Truth: oversight language hides capture.
• U6 — Field: legitimacy is restored through captured process.

Enforcement Capture is primarily an Au / Γ / K / O failure.

Auditability is controlled by the audited.

Selection favors enforcement compatible with basin preservation.

Constraint cannot bind power.

5. Typical Development Sequence

A common development sequence is:

1. A system creates enforcement, review, audit, remedy, or oversight.
2. The enforcement channel is placed inside or near the system it must constrain.
3. Dependence forms through funding, authority, data access, staffing, social proximity, contracts, or political pressure.
4. Early or low-risk enforcement may appear functional.
5. A high-power or basin-critical case appears.
6. Scope is narrowed.
7. Evidence access is limited.
8. Remedy authority is restricted.
9. Timing slows.
10. Public language preserves accountability appearance.
11. The affected node receives weak or no repair.
12. The system cites the existence of enforcement as legitimacy.
13. Capture becomes the normal operating condition.

The loop often looks like:

oversight created → dependence forms → powerful case appears → enforcement narrows → legitimacy preserved

Another common loop is:

capture exposed → process independence claimed → authority remains weak → capture persists

Enforcement Capture becomes durable when enforcement can act against low-power targets while remaining unable to bind high-power targets.

6. Diagnostic Markers

Diagnostic markers include:

• The enforcement body depends on the party it oversees.
• The audited system controls evidence access.
• Review scope is set by the reviewed actor.
• Enforcement can recommend but not compel.
• Remedies require approval from the responsible party.
• Funding depends on the system being constrained.
• High-power cases are delayed, narrowed, or privatized.
• Low-power cases are enforced more aggressively.
• Conflicts of interest are disclosed but not removed.
• Oversight language is stronger than actual authority.
• Enforcement findings rarely challenge basin-critical interests.
• Affected nodes cannot contest captured scope.
• Public reports omit protected actors or structural causes.
• The enforcement system cannot act when the violation is profitable, politically useful, or legitimacy-threatening.

Useful diagnostics:

• Enforcement Independence: Measures separation from constrained interests.
• Audit Control Mapping: Identifies who controls evidence, scope, timing, and disclosure.
• Conflict of Interest Load: Measures dependency and loyalty pressure.
• Override Authority: Tests whether enforcement can override the enforced actor.
• Remedy Authority Integrity: Measures whether remedies can be compelled.
• Funding Dependence: Tracks whether budget or survival depends on the constrained party.
• Capture Pressure: Measures incentives to soften, delay, or narrow action.
• Enforcement Neutralization: Tracks cases where authority exists but cannot act.
• Legitimacy Debt: Tracks trust loss from captured enforcement.
• Post-Enforcement Recurrence: Tracks recurrence after captured review.

7. Related Gates

Relevant gates include:

• Enforcement Independence Gate: Fails when enforcement depends on the enforced.
• Audit Independence Gate: Fails when the audited controls audit paths.
• Remedy Authority Gate: Fails when remedy cannot be compelled.
• Constraint Integrity Gate: Fails when the constraint cannot bind power.
• Conflict of Interest Gate: Fails when dependency compromises judgment.
• Override Authority Gate: Fails when enforcement cannot override the reviewed actor.
• Funding Independence Gate: Fails when budget dependence neutralizes enforcement.
• Selective Enforcement Gate: Fails when enforcement works only on low-risk actors.
• Legitimacy Gate: Fails when oversight language substitutes for independent constraint.
• Hidden Debt Gate: Fails when captured non-remedy is not counted.

The first common gate failure is usually the Enforcement Independence Gate.

Once enforcement depends on the enforced, the system may preserve process while losing justice.

8. Related Operators

Relevant operators include:

• Au — Auditability: Primary operator; capture often controls what can be inspected.
• Γ — Selection: Selects which violations, actors, remedies, and evidence are actionable.
• K — Constraint / Load: Constraint fails to bind powerful actors and shifts load elsewhere.
• O — Coherence: Declines when enforcement cannot enforce.
• H — Hidden Debt: Accumulates through unresolved violations and failed remedies.
• BΣ — Boundary Integrity: Boundaries between reviewer and reviewed collapse.
• Φ — Flow / Resource Movement: Funding, authority, evidence, and remedies flow through captured channels.
• M — Meaning: Oversight, independence, accountability, or compliance language masks dependence.
• R — Restoration Capacity: Repair capacity is neutralized when remedies cannot be compelled.
• Ψ — Observation / Interface: Displays enforcement as available while hiding capture.
• E — Exit: Affected nodes may have no route outside captured enforcement.
• Τ — Trajectory / Time: Delay lets capture decay accountability pressure.
• Λ — Compatibility: Tests whether enforcement structure is compatible with independence.
• D — Damping: Can stabilize review or suppress accountability pressure.

Common operator pattern:

Au controlled by audited actor
Γ selects safe cases
K fails against power
M declares oversight
H↑
O↓

The core operator inversion is:

the constrained actor controls the constraint

instead of:

constraint remains independent enough to bind the constrained actor

Enforcement Capture converts accountability into managed exposure.

9. Related Laws and Invariants

Related Laws

• Enforcement Must Be Independent From the Enforced: constraint requires separation from the constrained interest.
• Accountability Requires Constraint Independence: accountability fails when the target controls the channel.
• Remedy Systems Must Not Be Controlled by the Burden Source: repair cannot depend on permission from the harm source.
• Audit Must Not Be Owned by the Audited: auditability collapses when evidence and scope are target-controlled.
• Justice Requires Enforcement Authority: review without authority is theater.
• Captured Enforcement Converts Rules Into Theater: rules fail when enforcement cannot bind power.
• Legitimacy Requires Independent Constraint: legitimacy depends on enforceable limits.
• Power Cannot Self-Certify Constraint: self-certification cannot replace independent verification.
• Selective Enforcement: captured systems enforce asymmetrically.
• Procedural Theater: captured enforcement often preserves procedure without justice.
• Audit-Suppressed Repair: capture suppresses repair verification.
• Hidden Debt Accumulation: unresolved violations accumulate debt.

Related Invariants

• Enforcement Must Retain Independence: the constraint channel must not depend on the constrained target.
• The Audited Must Not Control the Audit: evidence, scope, and disclosure require independence.
• Remedy Authority Must Be Separate From Harm Source: repair must not require approval from the responsible actor.
• Constraint Channels Must Not Be Captured: enforcement must remain capable of binding power.
• Sanction Power Must Remain Auditable: sanction and non-sanction must both be reviewable.
• Review Must Have Authority to Override the Reviewed: review without override is advisory theater.
• Funding Dependence Must Not Neutralize Enforcement: budget dependence is a capture vector.
• Capture Must Be Counted as Legitimacy Debt: captured oversight damages trust even if some cases are handled.

10. Common False Positives

Not every internal or dependent review system is Enforcement Capture.

Common false positives include:

• Internal enforcement with real independence, access, and remedy authority.
• Self-regulation with third-party audit and override mechanisms.
• Industry expertise used without industry control.
• Private arbitration with balanced selection, evidence access, and remedy power.
• Platform review with independent appeal and transparent standards.
• Compliance team embedded in an organization but protected from retaliation and budget control.
• Regulator relying on industry data while independently verifying it.
• Institutional review body with authority to compel evidence and require remedy.
• AI safety review performed by deployer staff but subject to external audit and rollback authority.
• Governance oversight funded by a system but legally or structurally independent.

Clarifying rule:

This is not Enforcement Capture unless enforcement, audit, review, remedy, sanction, or accountability is shaped or neutralized by the interests it is supposed to constrain.

Proximity can be workable.

Capture begins when dependence overrides constraint.

11. Common False Repairs

Common false repairs include:

• renaming the review body independent
• adding advisory members without authority
• disclosing conflicts without removing them
• creating a committee with no remedy power
• publishing oversight reports without evidence access
• adding transparency language while scope remains captured
• allowing internal appeal to the same authority
• outsourcing review to a vendor selected by the constrained party
• adding public comment without enforcement consequence
• increasing documentation while preserving veto power
• giving oversight budget controlled by the reviewed system
• treating recommendations as accountability
• creating ethics boards without stop authority
• allowing the target to redact evidence
• saying enforcement worked because a review occurred

False repair often produces the loop:

enforcement capture exposed
→ oversight structure expanded
→ authority remains captured
→ accountability still fails

Another common loop is:

powerful violation appears
→ scope narrowed
→ no finding issued
→ oversight cited as proof of legitimacy

The repair fails because it improves the image of independence without restoring actual constraint independence.

12. Restoration Direction

Restoration requires decapturing enforcement authority, separating audit from the audited, restoring evidence access, giving review channels remedy power, removing conflicts of interest, reopening captured cases, and making enforcement capable of binding powerful actors.

Primary restoration direction:

restore constraint independence from the constrained power

A fuller restoration path includes:

1. Map the enforcement channel. Identify who controls review, audit, evidence, scope, timing, remedy, sanction, funding, and disclosure.
2. Identify the constrained actor. Name who or what the enforcement system is supposed to bind.
3. Map capture vectors. Identify funding dependence, hierarchy, data control, legal pressure, contract limits, loyalty, or basin preservation incentives.
4. Audit high-power cases. Compare enforcement in protected cases against low-power cases.
5. Restore evidence access. Ensure reviewers can inspect necessary records, logs, contracts, decisions, and affected-state evidence.
6. Restore remedy authority. Give enforcement channels power to require correction, compensation, boundary repair, or recurrence prevention.
7. Remove conflicts of interest. Change reporting lines, funding structures, staffing dependencies, or veto points.
8. Create override authority. Review must be able to override the reviewed actor where warranted.
9. Preserve affected-node contestability. Affected nodes must be able to challenge captured scope or remedy failure.
10. Reopen captured cases. Prior cases handled under capture require review.
11. Count legitimacy debt. Capture harms the whole rule field.
12. Publish appropriate pattern data. Protect privacy while making capture visible.
13. Monitor recurrence. Track whether enforcement weakens again under power pressure.
14. Revalidate enforcement legitimacy. Enforcement becomes legitimate only after it can bind the actors it is meant to constrain.

A valid restoration path should reduce:

capture pressure
conflict of interest load
audit control by target
remedy weakness
scope capture
evidence asymmetry
funding dependence
selective enforcement
legitimacy debt
post-review recurrence

Enforcement Capture is not repaired by adding more oversight language.

It is repaired by making oversight able to act.

13. Cross-Module Links

• Justice: Primary family; justice fails when enforcement cannot bind power.
• Contracts: Contract enforcement can be captured when dispute pathways, arbitration, remedies, or evidence access are controlled by the stronger party.
• Restoration: Restoration fails when the responsible system controls the repair pathway.
• False Repair: Strongly linked to Audit-Suppressed Repair and Basin-Protective Pseudo-Repair.
• Governance: Governance oversight can be captured by funders, incumbents, industry, parties, or institutions.
• Institutions: Internal review and grievance pathways can be captured by hierarchy and reputational protection.
• Platforms: Platform redress can be captured when the platform controls rule, evidence, appeal, and remedy.
• Security: Security audit can be captured by the same authority that performs surveillance, restriction, or enforcement.
• AI Governance: AI audits, evals, redress, model governance, and safety review can be captured by deployer-controlled access, metrics, and disclosure.
• Compliance: Compliance becomes theater when teams lack independence from profit, leadership, or legal containment.
• Economy: Funding dependence can neutralize enforcement.
• Coherence: Coherence requires constraint channels to remain independent enough to bind the constrained system.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-JC-002 — Selective Enforcement
• FM-JC-001 — Procedural Theater
• FM-R-017 — Audit-Suppressed Repair
• FM-R-018 — Basin-Protective Pseudo-Repair
• FM-CORE-004 — Auditability Collapse

Sibling or related Justice & Contract modes include:

• FM-JC-001 — Procedural Theater
• FM-JC-002 — Selective Enforcement
• FM-JC-003 — Punitive Drift
• FM-JC-004 — Under-Resourced Justice
• FM-JC-005 — Amnesty Without Repair
• FM-JC-007 — Manufactured Consent
• FM-JC-010 — Proxy-Relay Obfuscation
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-JC-012 — Parasitic Contracting

Related Restoration modes include:

• FM-R-008 — Audit Evasion in Repair
• FM-R-015 — Secret Settlement as Restoration
• FM-R-017 — Audit-Suppressed Repair
• FM-R-018 — Basin-Protective Pseudo-Repair
• FM-R-019 — Premature Closure

Related Security / Interaction modes include:

• FM-SEC-002 — Audit Suppression Inversion
• FM-SEC-005 — Interface Capture
• FM-SEC-008 — Proxy-Relay Drift
• FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
• FM-ISC-011 — Invisible Intrusion
• FM-ISC-012 — Restoration Lock-In

Related cross-family modes include:

• FM-CORE-004 — Auditability Collapse
• FM-CORE-006 — U4 Truth Substitution
• FM-MT-007 — Resource Gatekeeping Loop
• FM-MT-011 — Managed Optics Failure
• FM-MT-014 — Institutional Absorption
• FM-C-001 — Observability Collapse
• FM-C-018 — Goodhart Collapse
• FM-C-022 — Dominance Masquerading as Control
• FM-AIX-004 — Institutional Optics Attractor
• FM-REI-002 — Reduction-to-Authority Lock

Aliases preserved from source material:

• Enforcement Capture
• Captured Enforcement
• Accountability Capture
• Remedy Capture
• Audit Capture
• Review Capture
• Regulatory Capture
• Institutional Capture of Enforcement
• Self-Policing Failure
• Captured Oversight
• Sanction Capture
• Constraint Capture
• Enforcement Neutralization

15. Minimal Entry Version

Definition: Enforcement Capture occurs when a justice, governance, institutional, contractual, platform, security, compliance, legal, AI, or restoration system’s enforcement authority, review pathway, remedy mechanism, audit channel, sanction process, or accountability structure becomes controlled, shaped, constrained, delayed, deflected, or neutralized by the actors, interests, incentives, authorities, funders, platforms, regimes, or basin structures it is supposed to constrain.

Signature:

formal enforcement↑
enforcement independence↓
conflict of interest↑
evidence access asymmetry↑
remedy authority↓
protected-actor accountability↓
selective enforcement↑
hidden justice debt↑
legitimacy claim↑
O↓

Restoration direction:

• map the enforcement channel
• identify the constrained actor
• map capture vectors
• audit high-power cases
• restore evidence access
• restore remedy authority
• remove conflicts of interest
• create override authority
• preserve affected-node contestability
• reopen captured cases
• count legitimacy debt
• publish appropriate pattern data
• monitor recurrence
• revalidate enforcement legitimacy

16. Machine-Readable Summary

failure_mode:
  id: "FM-JC-009"
  name: "Enforcement Capture"
  family: "Justice & Contracts"
  production_treatment: "Standalone Entry"
  source_lineage:
    - "Justice & Contracts"
    - "JGL Extended"
    - "Restoration / Justice / Contracts Family"
  parent_modes:
    - "FM-JC-002 — Selective Enforcement"
    - "FM-JC-001 — Procedural Theater"
    - "FM-R-017 — Audit-Suppressed Repair"
    - "FM-R-018 — Basin-Protective Pseudo-Repair"
    - "FM-CORE-004 — Auditability Collapse"
  primary_failure: "A justice, governance, institutional, contractual, platform, security, compliance, legal, AI, or restoration system’s enforcement authority, review pathway, remedy mechanism, audit channel, sanction process, or accountability structure becomes controlled, shaped, constrained, delayed, deflected, or neutralized by the actors, interests, incentives, authorities, funders, platforms, regimes, or basin structures it is supposed to constrain."
  scope_note: "Conceptual and systems-oriented; does not treat every internal enforcement process, self-regulation mechanism, compliance team, institutional review body, platform moderation system, contract dispute process, private arbitration structure, or industry review mechanism as inherently failed."
  aliases:
    - "Enforcement Capture"
    - "Captured Enforcement"
    - "Accountability Capture"
    - "Remedy Capture"
    - "Audit Capture"
    - "Review Capture"
    - "Regulatory Capture"
    - "Institutional Capture of Enforcement"
    - "Self-Policing Failure"
    - "Captured Oversight"
    - "Sanction Capture"
    - "Constraint Capture"
    - "Enforcement Neutralization"
  signature:
    - "formal enforcement↑"
    - "enforcement independence↓"
    - "conflict of interest↑"
    - "evidence access asymmetry↑"
    - "remedy authority↓"
    - "protected-actor accountability↓"
    - "selective enforcement↑"
    - "hidden justice debt↑"
    - "legitimacy claim↑"
    - "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"
  state_variables:
    - "Au"
    - "Γ"
    - "K"
    - "O"
    - "H"
    - "BΣ"
    - "Φ"
    - "M"
    - "R"
    - "Ψ"
    - "E"
    - "Τ"
    - "Λ"
    - "D"
  first_gate_failure: "Enforcement Independence Gate"
  restoration:
    - "Enforcement Independence Audit"
    - "Conflict of Interest Removal"
    - "Audit Authority Rebinding"
    - "Remedy Authority Restoration"
    - "Constraint Channel Decapture"
    - "Funding Independence Review"
    - "Override Authority Restoration"
    - "Captured Case Reopening"
    - "Legitimacy Debt Accounting"
    - "Post-Decapture Enforcement Monitoring"