When Responsibility No Longer Aligns (how it fragments in multi-agent systems

Designing Responsibility in Multi-Agent Systems ②

1. From “unclear” to “misaligned”

In the previous piece, I argued that responsibility in multi-agent systems does not disappear.
It becomes distributed across the system.

But “distributed” is still too vague.

What actually happens is more specific—and more problematic.

Responsibility does not just spread.
It fragments into different layers that no longer align.

2. What we assume (without noticing)

Most governance models rely—often implicitly—on a simple expectation:

That different aspects of responsibility point to the same place.

The one who knew,
the one who caused,
the one who decided,
and the one who is held accountable—

in many traditional settings, these tend to overlap enough for governance to function.
But that alignment was never guaranteed.
It was a property of the system.

3. A provisional way to see it

This is not meant to be a definitive model of responsibility.

If anything, it is a provisional lens—a way to make visible something that tends to remain collapsed in current discussions.

I suspect that in multi-agent systems, responsibility may need to be understood less as something assigned after the fact, and more as something that is structurally enabled—or constrained—by the system itself.

But before going there, it is useful to at least surface how different aspects of responsibility already begin to diverge.

4. Where responsibility starts to split

One way to make this visible is to look at responsibility along multiple dimensions.

For example:

• Epistemic — who knew, or should have known
  This shapes how information is captured, shared, and made visible across agents.

• Causal — who influenced or contributed to the outcome
  This determines whether interaction chains can be reconstructed, or remain opaque.

• Decision — who enacted or triggered an action
  This affects where execution authority sits—and how actions are attributed in the system.

• Normative — who is expected to answer for it
  This defines how responsibility is surfaced externally—to users, organizations, or regulators.

These are not abstract distinctions.
They map to different parts of system design.

5. A simple way to see the problem

Consider an outcome that emerges from a sequence of interactions:

One agent processes partial information.
Another transforms or amplifies it.
A third executes an action based on that transformed input.
A human operator may or may not be aware of the chain.

If something goes wrong, which layer do we follow?

If we follow knowledge, we trace who had access to relevant information.
If we follow causality, we reconstruct the chain of influence.
If we follow decisions, we look at the point of execution.
If we follow norms, we ask who is expected to be accountable.

These paths do not necessarily converge.

6. Misalignment is not an exception

It is tempting to treat this as an edge case—something that happens only in complex or poorly designed systems.

But in multi-agent environments, this misalignment is not accidental.

It is structural.

As systems become more distributed, more interactive, and more adaptive over time, the alignment between these layers becomes harder to maintain.

At some point, it breaks.

7. Why this matters for governance

Most governance frameworks still assume that responsibility can be stabilized.

That if we define roles clearly enough,
or trace decisions precisely enough,
we can map responsibility back to a coherent point.

But when these layers diverge, that mapping becomes unstable.

We can still assign responsibility.
But the assignment no longer reflects how the system actually works.

This is where governance begins to lose its grip—not because it is absent,
but because it is misaligned with the structure of the system.

8. A shift in focus

If alignment cannot be assumed, then the goal cannot simply be to restore it.

Instead, the question becomes:

How do we design systems where different layers of responsibility
remain traceable—even when they no longer coincide?

This shifts the focus.

From locating responsibility,
to preserving its structure.

Not as a single point,
but as a set of relationships across the system.

Responsibility may not be something we locate—
but something we either make possible, or fail to.

9. What this sets up

This fragmentation is not just a conceptual observation.

It has direct implications for system design:

• how information flows are structured

• how interactions are recorded

• where authority is placed

• and how accountability is surfaced

These questions lead to a different design space—one that moves beyond assigning responsibility, toward structuring it.

10. What comes next

In the next piece, I’ll explore what this shift looks like in practice—
and how it changes the way we think about governance itself.