Role–Duty Mapping¶
Governance artifact — instantiates Outcome Responsibility Attribution Calibration
Lays out, before any verdict, which agents held which duties, authority, and expected actions — the outcome-blind baseline every later attribution step is measured against.
Before you can say who is answerable for an outcome, you need a picture of who was supposed to do what — drawn without yet knowing how things turned out. Role–Duty Mapping is that picture: for each agent in scope it records the role they held, the duty or standard that role carried, the scope of authority that came with it, and the specific action expected of them. Its defining move is that it is normative and outcome-blind — it describes obligations as they stood at the time, independent of the result. It does not measure what any agent actually caused, controlled, or knew; it fixes the yardstick those later steps read against, so responsibility can be traced to a duty rather than to whoever is most visible after the fact.
Example¶
A retaining wall on a road-widening project fails after a heavy storm. Before anyone asks "whose fault," the review builds a Role–Duty Mapping of the parties as their obligations stood when the wall was designed and built: the geotechnical engineer (duty — specify drainage to the design code; authority — to require a redesign), the site contractor (duty — build to the approved drawings and flag field conditions that contradict them), the independent checker (duty — verify the design against the standard before sign-off), and the client's project manager (duty — not to compress the schedule past the point where that verification can happen). Each row cites the source of the duty — the contract, the design code, the professional scope — rather than a guess.
The output is a table of owed obligations with one revealing empty cell: no role carried a standing duty to monitor drainage performance after handover. That gap — an unowned duty — is as important as the filled rows: it tells the later steps that part of the outcome traces to a hole in the role structure, not to any agent's breach. What the mapping deliberately does not say is who caused the failure; it only says who owed what.
How it works¶
- Enumerate the candidate agents in scope of the outcome — people, roles, teams, and institutions — before narrowing to the "obvious" one.
- Attach a duty and standard to each, drawn from a real source: a contract clause, a regulation, a professional standard, a documented policy, or an established custom. A duty with no source is flagged, not assumed.
- Record authority scope and expected action — what the role was empowered to do, and the specific act the standard required — so each duty is bounded by the power that came with it.
- Mark the gaps. Where a foreseeable risk maps to no role's duty, record the unowned duty explicitly; diffuse responsibility often hides in exactly these cells.
Everything is written as of the time of the decision and outcome-blind — that discipline is what makes the map a check on hindsight rather than a product of it.
Tuning parameters¶
- Role granularity — individuals, named roles, or whole institutions. Finer rows locate duty precisely but can fracture a shared obligation into deniable slivers.
- Standard source — formal (contract, regulation, code) versus customary ("how it's always done"). Formal sources are defensible; customary ones capture real expectations the paperwork missed, at the cost of contestability.
- As-of date — duties as they stood at the time versus as revised afterward. Freezing them at the moment of the decision is what keeps hindsight out.
- Gap treatment — whether unowned duties are recorded as findings or quietly dropped. Recording them turns the map into a design tool, not just an attribution input.
- Authority coupling — how tightly each duty is tied to the authority to discharge it. Duties assigned without matching authority are a classic source of unfair blame.
When it helps, and when it misleads¶
Its strength is that it anchors the whole calibration to duty rather than to salience, seniority, or who acted last — and it does so before the result can colour the reading, which is the structural guard against outcome bias.[n1] It also surfaces unowned risks and duty/authority mismatches that no causal analysis alone would reveal.
Its failure mode is that a map of who should have done what can quietly be mistaken for an account of what did happen. A tidy table can encode a fiction of accountability — the de jure org chart — that the actual work never followed, and it can be run backwards to pin an outcome on whoever appears on paper regardless of whether they had the control or knowledge to prevent it. The discipline that guards against this is to treat the mapping strictly as the normative baseline: it says what was owed, and hands the questions of causation, control, and knowledge to the mechanisms built for them.
How it implements the components¶
Role–Duty Mapping fills the normative-baseline components of the archetype — the ones a governance artifact can fix before any evidence about the outcome is weighed:
candidate_agent_set— its first act is to enumerate every agent, role, and institution in scope, resisting premature narrowing to the obvious actor.role_duty_standard— the core of the artifact: each agent is bound to a sourced duty, authority scope, and expected action, forming the standard later steps measure conduct against.
It does not establish what any agent actually caused (causal_contribution_timeline), what lay within their control (counterfactual_control_test), what they knew or could foresee (omission_commission_parity_check), or how the dimensions combine into a verdict (responsibility_attribution_matrix).
Related¶
- Instantiates: Outcome Responsibility Attribution Calibration — Role–Duty Mapping supplies the outcome-blind duty baseline the rest of the appraisal reads against.
- Sibling mechanisms: Responsibility Attribution Matrix · Omission–Commission Parity Check · Responsibility Diffusion Check · Scapegoat Screening Review · Causal Contribution Timeline · Counterfactual Control Test
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Role–Duty Mapping operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it lays out, before any verdict, which agents held which duties, authority, and expected actions — the outcome-blind baseline every later attribution step is measured against.
Independent corroboration: The frozen evidence defines Role–Duty Mapping as 'Lays out, before any verdict, which agents held which duties, authority, and expected actions — the outcome-blind baseline every later attribution step is measured against', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Establishing duties and authority before attributing fault is foundational legal responsibility analysis.
Related originating lineages:
- Organizational & Management Science — Role-accountability mapping materially supplies expected organizational actions.
- Philosophy — Moral responsibility theory independently separates duty from outcome hindsight.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: lays out, before any verdict, which agents held which duties, authority, and expected actions — the outcome-blind baseline every later attribution step is measured against.
Review resolution: Both blind reviewers agree that law_governance is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement, domain reach disagreement starts from reviewer_a’s mechanism-specific evidence: Establishing duties and authority before attributing fault is foundational legal responsibility analysis. Reviewer A proposed alternates=organizational_management, philosophy, origin_mode=convergent, domain_reach=universal, and encyclopedia_synthesis=true; reviewer B proposed alternates=organizational_management, public_administration_policy, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (organizational_management, philosophy, public_administration_policy) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and keeps domain_reach=universal and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Role–Duty Mapping is deliberately outcome-blind and ex ante: it is written as duties stood at the time, before the result is known. That is exactly what lets it act as a brake on hindsight — but it also means a mapping revised after the outcome has lost its main virtue. Build it (or freeze it) from the record as it was, and resist backfilling duties that only became "obvious" once the outcome was in.
[n1] Outcome bias — judging the quality of a decision, or the responsibility of an actor, by how the outcome turned out rather than by what was known and owed at the time. Fixing duties in advance, outcome-blind, is a direct structural guard against it. ↩