1. Definition

Representation or proxy abuse occurs when a system acts for another node without valid contract, auditability, consent, reversibility, or represented-party sovereignty.

This definition describes the structural pattern, not the moral quality of the actors involved.

2. Core Pattern

TBD. Expand the initiating pressure, misclassification or bypass, variable degradation, debt accumulation, and stabilization pattern during editorial review.

3. Failure Signature

Typical signature:

proxy authority↑
represented party Au↓
contract invalid
exit/rollback absent
BΣ violation

4. Primary U-Layer Origin

• U2, U4, U6: Source registry origin layer.

5. Typical Development Sequence

TBD. Add the development sequence during editorial review.

6. Diagnostic Markers

TBD. Add diagnostic markers only when supported by source material or later canon updates.

7. Related Gates

TBD. Add gate links during editorial review.

8. Related Operators

TBD. Add operator links during editorial review.

9. Related Laws and Invariants

TBD. Add law and invariant links during editorial review.

10. Common False Positives

TBD. Add false positives during editorial review.

11. Common False Repairs

TBD. Add false repairs during editorial review.

12. Restoration Direction

• restore auditability to represented party
• validate contract
• enable rollback
• repair boundary violation
• prohibit proxy sovereignty

13. Cross-Module Links

• Security: Source registry related module.
• AI: Source registry related module.
• JGL: Source registry related module.
• ISC: Source registry related module.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression of Parasitic Extraction

Aliases, parent modes, and child modes should be finalized during editorial review.

15. Minimal Entry Version

Definition: Representation or proxy abuse occurs when a system acts for another node without valid contract, auditability, consent, reversibility, or represented-party sovereignty.

Signature:

proxy authority↑
represented party Au↓
contract invalid
exit/rollback absent
BΣ violation

Restoration direction: - restore auditability to represented party

• validate contract
• enable rollback
• repair boundary violation
• prohibit proxy sovereignty

16. Machine-Readable Summary

failure_mode:
  id: "FM-SEC-007"
  name: "Representation / Proxy Abuse"
  family: "Security"
  production_treatment: "Domain Expression of Parasitic Extraction"
  primary_failure: "Representation or proxy abuse occurs when a system acts for another node without valid contract, auditability, consent, reversibility, or represented-party sovereignty."
  source: "FM-REGISTRY-PLAN.md"

17. Quality Control Checklist

TBD. Complete the template quality-control checklist before marking this entry ready.

18. Source Status

This scaffold was generated from FM-REGISTRY-PLAN.md. Matching excerpts from content/archive/failure-modes/registry/index.md were included when available. Sections marked TBD should be expanded only from source material, related canon pages, or later editorial review.

19. Source Excerpt

FM-SEC-007 — Representation / Proxy Abuse

Definition:

Representation or proxy abuse occurs when a system acts for another node without valid contract, auditability, consent, reversibility, or represented-party sovereignty.

Typical signature:

proxy authority↑
represented party Au↓
contract invalid
exit/rollback absent
BΣ violation

Primary variables:

Au, BΣ, µᵢ, MS, H

Common origin layers:

U2, U4, U6

Related modules:

Security · AI · JGL · ISC

Restoration direction:

• restore auditability to represented party
• validate contract
• enable rollback
• repair boundary violation
• prohibit proxy sovereignty