VIII · Safety & ControlEmerging★

Priority Matrix (Conflict Resolution)

also known as Conflict Resolution Lookup Table, Pre-Defined Goal-Priority Matrix

Pre-define how the agent must resolve specific classes of goal conflicts via a human-authored lookup table — transforming the agent from a decision-maker (where it fails on competing objectives) into a decision-implementer.

Context

An agent is given multi-objective tasks where the objectives can directly conflict (transparency vs security, completeness vs file-size limit, speed vs compliance). The agent demonstrates conflict-competency-gap: it either falls into decision-paralysis or into false-resolution, neither of which is acceptable.

Problem

Letting the agent reason through goal conflicts on the fly produces unreliable outputs because LLMs lack the contextual judgment to weigh competing objectives. Asking it to 'try harder' does not help — the limitation is architectural. But removing multi-objective tasks entirely throws out the use cases that motivated the agent.

Forces

  • Pre-defining every possible conflict resolution is impossible for open-ended domains.
  • Static lookup tables decay as business priorities shift.
  • Humans must commit to priority orderings in advance, which is politically difficult.

Example

A regulatory document-processing agent at a pharma company faces conflicts: speed (CEO needs in 2 hours), security (24h review required), completeness (legal needs all sections). Priority Matrix entry for 'urgent-CEO-vs-compliance-review': resolution = release a compliance-cleared executive summary in 2 hours, full document after 24h review. Agent looks up, implements. Pre-matrix attempts caused decision-paralysis; post-matrix the agent reliably executes.

Diagram

Solution

Therefore:

Identify the conflict classes the agent will encounter (compliance vs speed, security vs completeness, etc.). For each, build a Priority Matrix: rows are conflict-type entries, columns are the resolution rule. The agent's role becomes: detect the conflict class, look up the matrix entry, execute the prescribed resolution. Cases not in the matrix escalate to human. Pair with conflict-competency-gap awareness, policy-as-code-gate, supervisor-plus-gate, human-in-the-loop.

What this pattern forbids. The agent may not improvise resolution of conflicts within declared conflict classes; only matrix-prescribed resolutions or human escalations are allowed.

And the patterns that stand alongside it, or against it —

  • alternative-toConflict Competency Gap✕— Architectural gap: current agents cannot resolve complex goal conflicts the way humans do through experience and contextual judgment, even at Progression-Framework Level 3.
  • alternative-toDecision Paralysis✕— Anti-pattern: when given equally-weighted conflicting goals, the agent either gets stuck trying to satisfy all simultaneously or oscillates between solutions without converging — the most common LLM response to genuine goal conflicts.
  • alternative-toFalse Resolution✕— The agent proposes a compromise that addresses each constraint individually but subtly violates one in joint interpretation, shipping as success but discovered as failure at audit.
  • complementsPolicy-as-Code Gate★— Evaluate every proposed agent action against externally-managed machine-readable policies before dispatch, so compliance authorship lives outside the prompt and outside the agent code.
  • complementsHuman-in-the-Loop★★— Require explicit human approval at defined points before the agent performs an action.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance