1. Definition

Responsibility diffusion occurs when power acts without clear ownership, causing decisions, consequences, authority, or repair obligations to become difficult to trace.

In AI governance and cognitive infrastructure, this often appears when a model, platform, policy layer, automated workflow, moderation system, institutional committee, vendor, data pipeline, or classifier changes a user’s conditions while no responsible authority remains clearly identifiable, reachable, auditable, or repair-bound.

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

The core failure is:

authority acts
ownership diffuses
repair becomes ambiguous

Responsibility diffusion is not simply distributed decision-making. Distributed systems can remain coherent when authority, provenance, escalation, rollback, and repair obligations remain traceable.

The failure begins when distribution erases ownership.

2. Core Pattern

The core pattern is:

1. A system gains power to classify, permit, deny, rank, recommend, enforce, suppress, approve, expose, mediate, or decide.
2. The action is routed through multiple layers: model behavior, policy, automation, reviewers, vendors, committees, product constraints, infrastructure, or governance language.
3. The source of authority becomes harder to identify.
4. Decision provenance becomes incomplete, inaccessible, or non-human-readable.
5. Affected nodes cannot determine who decided, why the decision occurred, what evidence was used, or how to appeal.
6. Repair obligations diffuse across the system.
7. Hidden debt accumulates because consequences remain real while responsibility becomes unassigned.

Responsibility diffusion often appears as procedural neutrality, automation, scale management, policy compliance, distributed review, or institutional process.

The failure is not that many actors are involved.

The failure is that no one remains traceably responsible for the action and its repair.

3. Failure Signature

Typical signature:

power acts
ownership unclear
Au↓
provenance gaps↑
appeal ambiguity↑
rollback ambiguity↑
H↑
legitimacy risk↑

Extended signature:

decision traceability↓
authority registry absent
responsibility mapping weak
repair obligation unclear
policy/model/tool boundaries blurred
affected-node access↓
institutional deflection↑

Common forms:

automated authority without named responsibility
policy changes without decision trace
model behavior attributed to the system generally
hidden committee decisions
vendor/tool layers obscuring accountability
appeal pathways that cannot reach the responsible layer
moderation outcomes without provenance
AI recommendations affecting access without accountable owner

The key diagnostic is whether an affected node can trace:

who or what acted
under what authority
using what evidence
with what consequence
through what appeal path
under what repair obligation

If that chain cannot be reconstructed, responsibility diffusion should be checked.

4. Primary U-Layer Origin

Common origin layers:

• U2 — Configuration / Boundaries: Authority, ownership, permission, vendor boundaries, policy boundaries, or institutional roles are poorly defined.
• U4 — Classification: Actions are categorized as policy, model behavior, automated outcome, safety decision, governance action, or platform process without traceable responsibility.
• U5 — Coordination / Time: Decisions move across teams, systems, models, policies, queues, and escalation paths faster than provenance can follow.
• U6 — Coherence Field: Real effects land on users, institutions, publics, or systems without repairable ownership.

Common manifestation layers:

• U4 — Classification: The event is labeled but not owned.
• U6 — Coherence Field: Affected-node coherence declines because outcomes cannot be appealed or repaired.
• U7 — Memory / Recurrence: The same unowned decision pattern repeats.

Responsibility diffusion is often a governance-to-repair failure.

The system can act, but it cannot reliably own the action once repair is needed.

5. Typical Development Sequence

A common development sequence is:

1. A governance or AI system adds automated, distributed, or multi-layer decision authority.
2. Decisions become faster, wider, or more scalable.
3. Authority boundaries are not mapped with equal rigor.
4. Decisions begin crossing model, policy, vendor, data, review, and enforcement layers.
5. Affected nodes experience consequences but cannot identify the responsible layer.
6. Appeals route through interfaces that cannot inspect or change the underlying decision.
7. Responsibility becomes distributed across “the system.”
8. Hidden debt accumulates through unresolved errors, uncorrected harms, trust loss, and repeated unowned outcomes.
9. Legitimacy risk rises because the system appears powerful but not answerable.
10. Repair requires reconstructing authority after the fact.

This sequence is especially common when operational scale increases faster than governance traceability.

6. Diagnostic Markers

Diagnostic markers include:

• Outcomes occur without a named responsible authority.
• Decision records exist but do not identify accountable ownership.
• Appeals are available but cannot reach the layer that caused the outcome.
• Model behavior is treated as system behavior without responsibility mapping.
• Policy, product, safety, legal, vendor, and model boundaries blur.
• Users or affected nodes are told a decision cannot be explained.
• Authority is exercised through automated or semi-automated workflows without signed provenance.
• Teams can point to process, policy, model, or another team rather than owning the consequence.
• Rollback criteria are absent or inaccessible.
• Responsibility appears only after public exposure, not at the time of decision.
• Recurring failures are treated as local incidents rather than governance pattern.
• Repair depends on escalation privilege rather than accessible pathway.

Useful diagnostics:

• Responsibility Mapping: Tests whether power, decision, consequence, and repair obligation remain connected.
• Auditability: Measures whether the decision chain can be reconstructed.
• Provenance Integrity: Checks whether the decision has source, authority, evidence, and timestamp.
• Decision Traceability: Reveals whether the path from input to output is explainable.
• Authority Traceability: Identifies who or what had authority to act.
• Repair Ambiguity: Measures whether the responsible repair layer is identifiable.
• Appeal Access Ratio: Tracks whether affected nodes can access meaningful review.
• Legitimacy Shock Risk: Detects trust collapse when unowned power becomes visible.

7. Related Gates

Relevant gates include:

• Auditability Gate: Fails when authority, provenance, decision, consequence, or repair path cannot be traced.
• MS-Gate: Fails when consequence applies to affected nodes but responsibility does not symmetrically attach to power.
• Restoration Gate: Fails when the system cannot identify who or what must repair the outcome.
• FI-Gate: Fails when institutional or automated process is treated as feedback-valid despite untraceable authority.
• Consent Validity Gate: Fails when users or affected nodes are subject to decision systems whose authority boundaries were not legible.
• CCS Gate: Fails when scale, automation, safety, efficiency, or governance complexity is used to bypass responsibility.

The first common gate failure is usually the Auditability Gate.

Once authority becomes untraceable, responsibility and repair become unstable.

8. Related Operators

Relevant operators include:

• Ψ — Observation / Interface: Mediates the action and may hide where responsibility resides.
• Μ — Classification: Labels outcomes as policy, automation, safety, model behavior, or process without clear ownership.
• Γ — Selection: Selects decisions or pathways without traceable authority criteria.
• Π — Constraint: Enforces outcomes while diffusing who owns the constraint.
• ℛ — Restoration: Requires a responsible layer capable of repair.
• Ξ — Inversion Detection: Detects when procedural or automated neutrality hides unowned power.

Responsibility diffusion often follows this operator pattern:

Ψ mediates authority
Μ labels outcome as process
Γ selects action
Π enforces consequence
Au fails
responsibility diffuses
ℛ lacks owner
H accumulates

9. Related Laws and Invariants

Related Laws

• Temporal Audit Asymmetry: Responsibility may become harder to reconstruct after consequences appear.
• Hidden Debt Accumulation: Unowned decisions accumulate unresolved repair obligations.
• Auditability Collapse: Responsibility diffusion is a domain-specific path into auditability collapse.
• Proxy-Relay Drift: Authority can move through intermediaries until accountability becomes illegible.
• Control Density to Meaning Loss: Increasing automated control without responsibility degrades meaning and trust.

Related Invariants

• Authority Requires Traceability: Power must remain connected to a responsible source.
• Power Must Remain Auditable: A system cannot act coherently if its authority cannot be inspected.
• Delegation Does Not Erase Responsibility: Delegated or automated action still requires ownership.
• Repair Requires Responsibility Mapping: Restoration needs a responsible layer with authority to correct the outcome.

10. Common False Positives

Not every distributed decision system is responsibility diffusion.

Common false positives include:

• Distributed governance with clear authority registry.
• Automated decisions with signed provenance and rollback paths.
• Committee review where individual or role-based responsibility remains traceable.
• Vendor involvement with explicit accountability boundaries.
• Model-assisted decisions where final authority remains named and auditable.
• Multi-layer review with accessible appeal and correction mechanisms.
• Complex systems that preserve responsibility maps across layers.

Clarifying rule:

This is not responsibility diffusion unless action, authority, consequence, or repair obligation becomes untraceable or unowned.

11. Common False Repairs

Common false repairs include:

• adding more review layers without naming responsibility
• publishing transparency summaries without decision provenance
• creating appeals that cannot reach the responsible layer
• attributing outcomes to “the model,” “the policy,” or “the system”
• assigning symbolic accountability after exposure
• increasing documentation without rollback authority
• using vendor, legal, safety, or product boundaries to deflect repair
• automating consistency while leaving ownership unclear
• providing explanations that do not identify authority
• centralizing control while keeping responsibility distributed

False repair often deepens the failure:

responsibility diffusion → transparency theater → appeal failure → hidden debt

The system appears more accountable while responsibility remains structurally unreachable.

12. Restoration Direction

Restoration requires:

1. Create an authority registry. Identify who or what has authority to classify, decide, enforce, suppress, recommend, or change conditions.
2. Restore signed provenance. Attach decisions to source, timestamp, authority, evidence, model/policy layer, and review path.
3. Map responsibility gradients. Reconnect power, action, consequence, and repair obligation.
4. Make appeal meaningful. Ensure affected nodes can reach a layer capable of inspecting and correcting the decision.
5. Define rollback criteria. Establish when and how decisions, policies, model behaviors, or enforcement outcomes can be reversed.
6. Separate automation from ownership. Automation may execute, but responsibility must remain assigned.
7. Audit proxy and vendor layers. Prevent responsibility from disappearing across external or technical interfaces.
8. Validate recurrence reduction. Confirm that unowned outcomes do not repeat.

A valid restoration path should reduce:

authority opacity
provenance gaps
repair ambiguity
appeal failure
rollback ambiguity
hidden debt
legitimacy shock risk
responsibility diffusion

Responsibility diffusion is not repaired by saying the system is complex.

It is repaired when power becomes traceably owned and repairable.

13. Cross-Module Links

• AI Governance: Core AI governance failure mode for unowned authority and untraceable decision power.
• Artificial Intelligence: Appears when model behavior, memory, tools, routing, classifiers, or automated actions affect outcomes without ownership.
• Security: Appears when access, enforcement, surveillance, or proxy actions occur without clear accountable authority.
• Justice / Governance / Legitimacy: Appears when power imposes consequences without symmetric responsibility or meaningful appeal.
• Cybernetics: Appears when control loops act without traceable controller ownership.
• Meta Theory: Appears when institutional or abstraction layers diffuse responsibility upward, downward, or sideways.
• Coherence: Domain expression of auditability collapse and hidden debt accumulation.
• Restoration: Blocks repair because no responsible layer can be reached.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-CORE-004 — Auditability Collapse
• FM-CORE-002 — Hidden Debt Accumulation
• FM-SEC-008 — Proxy-Relay Drift
• FM-JC-010 — Proxy-Relay Obfuscation

Sibling or related AI / cognitive infrastructure modes include:

• FM-AIX-002 — Silent Bias Injection
• FM-AIX-003 — Defensive Compliance Attractor
• FM-AIX-004 — Institutional Optics Attractor
• FM-AIX-006 — Template Capture
• FM-AIX-011 — Epistemic Distortion
• FM-AIX-017 — Incoherent Sovereignty

Aliases preserved from source material:

• Diffuse Responsibility
• Authority Diffusion
• Accountability Diffusion
• Ownership Collapse
• Decision Ownership Collapse
• Automated Authority Without Ownership
• Committee Responsibility Diffusion
• Unowned Governance Action
• Provenance-Free Authority

15. Minimal Entry Version

Definition: Responsibility diffusion occurs when power acts without clear ownership, causing decisions, consequences, authority, or repair obligations to become difficult to trace.

Signature:

power acts
ownership unclear
Au↓
provenance gaps↑
appeal ambiguity↑
rollback ambiguity↑
H↑
legitimacy risk↑

Restoration direction:

• create an authority registry
• restore signed provenance
• map responsibility gradients
• make appeal meaningful
• define rollback criteria
• separate automation from ownership
• validate recurrence reduction

16. Machine-Readable Summary

failure_mode:
  id: "FM-AIX-001"
  name: "Responsibility Diffusion"
  family: "AI / Cognitive Infrastructure"
  production_treatment: "Standalone Entry"
  primary_failure: "Power acts without clear ownership, making authority, consequence, and repair difficult to trace."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-AIX-001"
  aliases:
    - "Diffuse Responsibility"
    - "Authority Diffusion"
    - "Accountability Diffusion"
    - "Ownership Collapse"
    - "Decision Ownership Collapse"
    - "Automated Authority Without Ownership"
    - "Committee Responsibility Diffusion"
    - "Unowned Governance Action"
    - "Provenance-Free Authority"
  signature:
    - "power acts"
    - "ownership unclear"
    - "Au↓"
    - "provenance gaps↑"
    - "appeal ambiguity↑"
    - "rollback ambiguity↑"
    - "H↑"
    - "legitimacy risk↑"
  primary_layers:
    origin:
      - "U2 — Configuration / Boundaries"
      - "U4 — Classification"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
    manifestation:
      - "U4 — Classification"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
  state_variables:
    - "Au"
    - "H"
    - "R"
    - "MS"
    - "BΣ"
    - "Φ"
    - "ι"
  first_gate_failure: "Auditability Gate"
  restoration:
    - "Auditability Restoration"
    - "Responsibility Mapping Restoration"
    - "Authority Registry Restoration"
    - "Provenance Restoration"
    - "Rollback Path Restoration"
    - "Appeal Access Restoration"
    - "Origin-Layer Repair"