0. Cybernetic Scope Note

This entry is conceptual and systems-oriented.

It does not treat delegation, representation, mediation, automation, dashboards, relays, agents, intermediaries, abstraction, bureaucracy, routing, or proxy structures as inherently failed. Complex systems require intermediaries. Direct state access is often impossible. Delegation can preserve coherence when it maintains traceability, scope, fidelity, consent, boundary integrity, and repair obligation.

The failure begins when the relay stops preserving what it carries.

The issue is not proxies.

The issue is proxy chains that drift from origin while continuing to act with origin authority.

Proxy-Relay Drift occurs when the representation remains empowered after its fidelity to source state, affected-node reality, consent, or responsibility has degraded.

1. Definition

Proxy-relay drift occurs when signal, authority, responsibility, decision context, consent, risk, repair need, or control action passes through intermediaries, representatives, agents, dashboards, policies, automation, or relay layers until the resulting action no longer preserves the original state, intent, boundary, accountability, or repair obligation.

The relay chain may include:

• representatives
• managers
• agents
• proxies
• institutions
• dashboards
• reports
• committees
• contracts
• policies
• models
• automation
• summaries
• interfaces
• vendors
• regulators
• enforcement layers
• AI systems
• security tools
• coordination channels

Each layer may appear legitimate in isolation.

But across relay distance, origin fidelity degrades.

The core failure is:

origin state → proxy layer → relay layer → action
fidelity↓
authority persists
responsibility diffuses
H↑

Proxy-Relay Drift is a cybernetic transmission failure.

The system continues acting on a relayed representation after the representation no longer reliably carries what it claims to represent.

2. Core Pattern

The core pattern is:

1. A system cannot act directly on origin state.
2. It delegates observation, interpretation, decision, enforcement, reporting, consent, or repair through proxy layers.
3. The proxy initially carries useful representation.
4. The relay chain lengthens, abstracts, automates, institutionalizes, or optimizes.
5. Each layer selects, compresses, reframes, delays, translates, filters, or incentivizes the signal.
6. Origin-state fidelity declines.
7. The proxy output continues receiving authority.
8. Responsibility becomes distributed across layers.
9. Affected-node reality becomes harder to recover.
10. Decisions and control actions increasingly serve relay logic rather than origin truth.
11. Harm or hidden debt accumulates.
12. Audit struggles to identify where drift entered the chain.

This failure mode often appears as:

the representative said this, so the represented state is known

or:

the dashboard says this, so the field says this

or:

the delegated authority remains valid because the chain is formally authorized

The restorative question is:

does the proxy still preserve the origin state, boundary, consent, and responsibility it claims to carry?

Proxy-relay systems fail when the relay becomes more authoritative than the source.

3. Failure Signature

Typical signature:

proxy layers↑
origin contact↓
relay transformation↑
authority persists
responsibility traceability↓
consent freshness↓
H↑

Extended signature:

representation remains but represented state drifts
authorization remains but consent decays
reports remain but field truth thins
delegation remains but responsibility dissolves
action continues but origin context is lost

Common forms include:

dashboard summaries replacing field inspection
AI agents acting from compressed user intent
security proxies making decisions without context
representatives claiming authority after affected-node reality changes
vendors absorbing responsibility without accountability
institutions speaking for nodes they no longer contact
policy relays executing outdated consent
justice systems processing harm through representation layers that erase repair need
governance chains where no actor owns final consequences
automation enforcing rules whose original purpose is no longer recoverable

The defining condition is not that a proxy exists.

The defining condition is that proxy authority outlives proxy fidelity.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: delegation protects authority, reduces cost, creates distance, preserves deniability, or scales control.
• U2 — Configuration / Boundaries: proxy chains are configured without adequate fidelity, consent, or responsibility boundaries.
• U3 — Execution / Runtime: relay layers execute decisions, reports, summaries, or control actions.
• U4 — Information / Truth: representation substitutes for source truth.
• U5 — Coordination / Time: relay delay causes stale consent, stale context, or outdated state.
• U6 — Coherence Field: formal delegation creates the feeling of legitimacy.
• U7 — Memory / Recurrence: proxy authority persists after original conditions change.
• U8 — Environment / Field: distributed systems require relay structures that may drift under scale.

Common manifestation layers:

• U2 — Configuration: proxy chains and delegation boundaries are misdesigned.
• U3 — Execution: relayed actions continue.
• U4 — Truth: proxy output substitutes for origin state.
• U5 — Time: consent and context become stale.
• U6 — Coherence Field: formal legitimacy masks drift.
• U7 — Memory: delegated authority becomes inherited.

Proxy-Relay Drift is primarily a U4 / U2 representation-boundary failure.

The system mistakes an authorized relay for a faithful representation.

5. Typical Development Sequence

A common development sequence is:

1. Direct state access is difficult, expensive, slow, risky, or impossible.
2. A proxy or relay is created.
3. The proxy is useful.
4. The proxy becomes trusted.
5. The system scales reliance on the proxy.
6. Relay layers multiply.
7. Signal, consent, responsibility, and context are compressed or transformed at each layer.
8. The proxy chain becomes easier to use than the origin.
9. Origin contact declines.
10. Proxy output becomes authoritative.
11. Drift accumulates.
12. Later harm, misclassification, or failed repair reveals that the proxy chain no longer carried the original state.

The loop often looks like:

origin state → proxy → trust → more delegation → less origin contact → drift

Another common loop is:

proxy challenged → formal authority cited → origin reality remains unaudited → proxy hardens

Proxy-Relay Drift becomes self-protective because each layer can claim it only acted on the information or authority received from another layer.

6. Diagnostic Markers

Diagnostic markers include:

• No actor can reconstruct the original state from the relay output.
• Authority remains clear but responsibility is unclear.
• Consent was valid at one layer but stale or invalid at another.
• Affected nodes must repeatedly correct representatives.
• Summaries become more influential than source material.
• Proxy outputs are easier to access than origin reality.
• Each relay layer introduces small transformations that nobody owns.
• Decision-makers cannot identify where a claim originated.
• Formal authorization is treated as proof of current legitimacy.
• Automation acts on compressed intent that no longer fits the situation.
• Reports cite reports rather than state.
• Repair obligation becomes lost across handoffs.
• Harm is blamed on process, vendor, tool, model, relay, or policy instead of owned.
• The represented node cannot revoke, update, or inspect the proxy relationship.
• Audit finds procedural compliance but broken representation.

Useful diagnostics:

• Proxy Chain Integrity: Measures whether proxy layers preserve origin state.
• Relay Fidelity: Tests information, authority, and context loss across handoffs.
• Authority Traceability: Determines where decision authority originated and how it moved.
• Responsibility Traceability: Determines who owns consequences across the relay.
• Signal-to-Origin Fit: Compares relayed signal to source state.
• Representation / Reality Fit: Tests whether representation matches affected-node reality.
• Consent Preservation: Tests whether consent remains fresh, scoped, revocable, and valid through delegation.
• Auditability: Determines whether the chain can be inspected.
• Hidden Debt: Tracks burden created by relay distortion.
• Repair Obligation Trace: Determines whether repair responsibility survived handoff.

7. Related Gates

Relevant gates include:

• Proxy Gate: Fails when proxy authority exceeds proxy fidelity.
• Relay Gate: Fails when handoffs degrade signal, context, or responsibility.
• Representation Gate: Fails when representation no longer matches represented reality.
• Auditability Gate: Fails when relay chains cannot be traced.
• Consent Gate: Fails when consent decays through delegation.
• Boundary Gate: Fails when origin and proxy boundaries collapse.
• Responsibility Gate: Fails when ownership dissolves across intermediaries.
• Restoration Gate: Fails when repair obligation is lost in the relay.

The first common gate failure is usually the Proxy Gate.

The system empowers a representation before verifying its fidelity.

8. Related Operators

Relevant operators include:

• Ψ — Observation / Interface: Proxies and relays mediate what the system can see.
• Au — Auditability: Determines whether relay transformations can be traced.
• BΣ — Boundary Integrity: Preserves distinction between origin, proxy, relay, and affected node.
• Γ — Selection: Selects which proxy outputs are trusted.
• Λ — Compatibility: Tests whether proxy action remains compatible with origin state.
• Φ — Flow / Resource Movement: Routes authority, responsibility, signal, consent, and repair through intermediary paths.
• H — Hidden Debt: Accumulates when drifted proxy actions create unowned burden.
• O — Coherence: May appear high because formal chains look legitimate.
• R — Restoration Capacity: Declines when repair responsibility becomes diffuse.
• K — Constraint / Load: Increases on affected nodes forced to correct proxy drift.
• Τ — Trajectory / Time: Reveals stale consent, outdated context, and drift across recurrence.
• D — Damping: Can slow relay errors or suppress affected-node correction.
• G — Gain: Can amplify proxy error if proxy output drives strong action.

Common operator pattern:

origin state enters proxy
Ψ receives compressed relay signal
Γ selects formal proxy output
BΣ origin/proxy boundary weakens
Λ fit declines
Φ carries authority forward
Au cannot trace transformations
R cannot locate repair owner
K shifts to affected nodes
H accumulates

The core operator inversion is:

authorized proxy → faithful representation

instead of:

authorized proxy → fidelity audit → scoped authority

Proxy-Relay Drift turns delegation into state substitution.

9. Related Laws and Invariants

Related Laws

• Auditability Collapse: relay chains become impossible to inspect.
• Observability Collapse: origin state disappears behind proxy outputs.
• U4 Truth Substitution: representation substitutes for source truth.
• Hidden Debt Accumulation: unowned distortion creates deferred repair burden.
• Representation / Proxy Abuse: representation is used beyond legitimate scope.
• Consent Drift: consent decays across delegation and time.
• Responsibility Diffusion: ownership dissolves across actors and tools.
• Interface Capture: the relay interface becomes more powerful than the represented state.
• Boundary Collapse: proxy and origin boundaries blur.
• Proxy-Relay Drift: delegated structures drift from state, consent, and responsibility.

Related Invariants

• Proxy Chains Must Preserve State: intermediaries must retain enough contact with origin.
• Delegated Authority Must Remain Auditable: authority handoff must be traceable.
• Representation Must Preserve Affected-Node Reality: proxy claims must remain reality-linked.
• Relay Layers Must Not Erase Responsibility: handoffs must not dissolve ownership.
• Consent Must Survive Delegation: consent must remain scoped, current, revocable, and inspectable.
• Control Paths Must Preserve Boundary Conditions: control authority cannot outrun its boundary.
• Repair Obligation Must Not Dissolve Through Intermediaries: restoration responsibility must survive relay.

10. Common False Positives

Not every proxy chain is Proxy-Relay Drift.

Common false positives include:

• Delegation with clear scope and auditability.
• Representation that remains in contact with affected-node reality.
• Automation with validated intent preservation.
• Dashboards that are treated as limited interfaces, not source truth.
• Proxies that can be revoked, updated, inspected, and challenged.
• Relay chains with strong responsibility mapping.
• Intermediaries that preserve context rather than compress it away.
• Summaries linked to source material.
• Authorized agents operating within fresh consent.
• Complex institutions with active feedback from represented nodes.

Clarifying rule:

This is not Proxy-Relay Drift unless proxy authority, relay output, delegated action, or intermediary representation continues to operate after fidelity to origin state, consent, boundary condition, accountability, or repair obligation has fallen below functional threshold.

11. Common False Repairs

Common false repairs include:

• adding another relay layer
• formalizing the proxy chain without auditing fidelity
• requiring affected nodes to correct the proxy repeatedly
• treating authorization as proof of representation
• adding dashboards over proxy outputs
• assigning responsibility to the process instead of an owner
• using summaries without source recontact
• automating relay action without consent revalidation
• increasing enforcement based on proxy claims
• allowing vendors, agents, or models to absorb accountability
• treating stale consent as durable authorization
• documenting handoffs without repairing state loss
• asking the proxy whether the proxy is accurate
• expanding representation scope because the relay is convenient

False repair often produces the loop:

proxy drift exposed → more formal relay added → origin contact declines → drift deepens

Another common loop is:

harm occurs → each layer cites another layer → responsibility diffuses → repair stalls

The repair fails because it strengthens the relay without restoring origin fidelity.

12. Restoration Direction

Restoration requires tracing proxy chains back to origin state, auditing relay transformations, revalidating consent and authority, and rebinding responsibility and repair obligation.

Primary restoration direction:

trace the relay,
restore origin contact,
revalidate authority,
and rebind responsibility to repair

A fuller restoration path includes:

1. Name the proxy chain. Identify all intermediaries, agents, dashboards, policies, tools, institutions, models, vendors, or representatives involved.
2. Name what is being carried. Clarify whether the relay carries signal, authority, consent, risk, responsibility, control action, or repair obligation.
3. Trace origin state. Reconnect relay output to the original source, affected node, event, consent, or condition.
4. Audit transformations. Identify compression, filtering, delay, reframing, incentive distortion, automation, or handoff loss.
5. Compare proxy output to origin reality. Test representation / reality fit.
6. Revalidate consent. Ensure consent remains current, scoped, informed, revocable, and inspectable.
7. Rebind responsibility. Assign clear ownership for consequences across the chain.
8. Reduce relay distance. Remove unnecessary intermediaries where possible.
9. Restore affected-node update rights. Allow represented nodes to correct, revoke, inspect, and challenge proxy outputs.
10. Limit proxy authority. Bound delegated action to proven fidelity.
11. Restore repair obligation. Ensure harm caused through relay drift routes to repair.
12. Install recurring fidelity audits. Validate proxy chains over time and scale.

A valid restoration path should reduce:

relay distance
origin-state loss
authority overreach
responsibility diffusion
consent staleness
representation / reality gap
repair-obligation loss
hidden debt
affected-node correction burden

Proxy-Relay Drift is not repaired by making the chain more official.

It is repaired by making the chain faithful, inspectable, revocable, and repair-linked.

13. Cross-Module Links

• Cybernetics: Proxy chains mediate observation, feedback, control action, authority, and repair routing.
• Security: Direct link to proxy-relay drift, representation/proxy abuse, authorization misuse, and delegated control failure.
• Diagnostics: Requires proxy-chain, relay-fidelity, authority-trace, responsibility-trace, and consent-preservation diagnostics.
• Justice: Representation failure can dissolve affected-node reality and repair obligation.
• Restoration: Repair fails when responsibility or harm trace disappears through intermediaries.
• AI Governance: AI agents, summaries, classifiers, safety layers, and automated tools can act as proxies for user intent, policy intent, or system state.
• Interfaces: Interfaces are relay layers; they shape what travels and what is lost.
• Control Systems: Control through relays requires fidelity and timely feedback.
• Scaling: Scale often increases proxy distance and relay transformation.
• Coherence: Formal delegation can preserve apparent coherence while origin-state contact declines.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression / Security link

This mode maps upward to:

• FM-SEC-008 — Proxy-Relay Drift
• FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
• FM-CORE-004 — Auditability Collapse
• FM-CORE-006 — U4 Truth Substitution
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Cybernetics modes include:

• FM-C-001 — Observability Collapse
• FM-C-002 — Instrumentation Theater
• FM-C-014 — Topology Brittleness
• FM-C-016 — Mimic Capture
• FM-C-020 — Measurement Back-Action Loop
• FM-C-021 — Parasitic Extraction
• FM-C-022 — Dominance Masquerading as Control
• FM-C-024 — Recapture After Exit

Related cross-family modes include:

• FM-SEC-008 — Proxy-Relay Drift
• FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
• FM-JC-010 — Proxy-Relay Obfuscation
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-AIX-001 — Responsibility Diffusion
• FM-AIX-016 — Standingless Instrumentalization
• FM-AIX-019 — Node Capture
• FM-ISC-009 — Consent Drift
• FM-MT-014 — Institutional Absorption
• FM-REI-007 — Sensemaking Subordination

Aliases preserved from source material:

• Proxy-Relay Drift
• Proxy Relay Drift
• Relay Drift
• Proxy Drift
• Representative Drift
• Intermediary Drift
• Delegation Drift
• Authority Relay Drift
• Responsibility Relay Drift
• Signal Relay Distortion

15. Minimal Entry Version

Definition: Proxy-relay drift occurs when signal, authority, responsibility, decision context, consent, risk, repair need, or control action passes through intermediaries, representatives, agents, dashboards, policies, automation, or relay layers until the resulting action no longer preserves the original state, intent, boundary, accountability, or repair obligation.

Signature:

proxy layers↑
origin contact↓
relay transformation↑
authority persists
responsibility traceability↓
consent freshness↓
H↑

Restoration direction:

• name the proxy chain
• name what is being carried
• trace origin state
• audit transformations
• compare proxy output to origin reality
• revalidate consent
• rebind responsibility
• reduce relay distance
• restore affected-node update rights
• limit proxy authority
• restore repair obligation
• install recurring fidelity audits

16. Machine-Readable Summary

failure_mode:
  id: "FM-C-015"
  name: "Proxy-Relay Drift"
  family: "Cybernetics"
  production_treatment: "Domain Expression / Security link"
  parent_modes:
    - "FM-SEC-008 — Proxy-Relay Drift"
    - "FM-SEC-011 — Representation / Proxy Abuse / AIM Failure"
    - "FM-CORE-004 — Auditability Collapse"
  primary_failure: "Proxy authority, relay output, delegated action, or intermediary representation continues to operate after fidelity to origin state, consent, boundary condition, accountability, or repair obligation has fallen below functional threshold."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-C-015"
  scope_note: "Conceptual and systems-oriented; does not treat delegation, representation, mediation, automation, dashboards, relays, agents, intermediaries, abstraction, bureaucracy, routing, or proxy structures as inherently failed."
  aliases:
    - "Proxy-Relay Drift"
    - "Proxy Relay Drift"
    - "Relay Drift"
    - "Proxy Drift"
    - "Representative Drift"
    - "Intermediary Drift"
    - "Delegation Drift"
    - "Authority Relay Drift"
    - "Responsibility Relay Drift"
    - "Signal Relay Distortion"
  signature:
    - "proxy layers↑"
    - "origin contact↓"
    - "relay transformation↑"
    - "authority persists"
    - "responsibility traceability↓"
    - "consent freshness↓"
    - "H↑"
  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:
      - "U2 — Configuration"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Coherence Field"
      - "U7 — Memory"
  state_variables:
    - "Ψ"
    - "Au"
    - "BΣ"
    - "Γ"
    - "Λ"
    - "Φ"
    - "H"
    - "O"
    - "R"
    - "K"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Proxy Gate"
  restoration:
    - "Proxy Chain Audit"
    - "Relay Fidelity Repair"
    - "Authority Trace Restoration"
    - "Responsibility Rebinding"
    - "Consent Revalidation"
    - "Affected-Node Reality Restoration"
    - "Boundary Reassertion"
    - "Repair Obligation Recovery"
    - "Intermediary Transparency Repair"