The Operational Responsibility Gap.

What is operational responsibility?

Operational responsibility is responsibility for the next required action in a real operational sequence. It concerns a specific event, decision, case, handover or obligation, not only a general role description or policy statement.

A defensible account must be able to show who or what held that responsibility, the authority and scope under which it was held, whether it was accepted, what action followed and how the responsibility ended or transferred.

What is the Operational Responsibility Gap?

The Operational Responsibility Gap is the condition in which an organisation or system cannot independently reconstruct who held responsibility for a specific operational event, on what basis, through which handovers, and with what evidence of acceptance, action and outcome.

An organisation may have governance, named owners, workflow states and extensive audit data while still being unable to answer the operational question: who was responsible for the next required action at that point, and what evidence establishes that conclusion?

Why policies and audit logs may be insufficient

Policies usually describe what should happen. Audit logs usually record activity generated by a system. Neither necessarily records the complete meaning of responsibility.

A login, status change, message or approval can be relevant evidence, but it may not establish assignment, acceptance, authority, continuity, discharge or the relationship between one party's record and another party's record. Evidence becomes especially fragile when work crosses organisational or system boundaries.

What must be reconstructable after an event?

The required account depends on context, but an independently reconstructable responsibility record should be capable of establishing:

• the responsibility that existed and the event or decision to which it related.
• the person, role, organisation or system to which it was assigned.
• the authority and scope under which the responsibility was held.
• whether and when the responsibility was accepted.
• each handover, including the transferring and receiving parties.
• the action, non-action, escalation or discharge that followed.
• the evidence supporting each material state change.
• the outcome and the basis on which responsibility ended or moved.

How responsibility becomes lost during handovers

A handover is not complete merely because one party sent a message or changed a workflow state. The transferring party may record dispatch while the receiving party records nothing, rejects the transfer, lacks authority, or interprets the responsibility differently.

The gap appears when there is no shared, testable account of what moved, from whom, to whom, when, under what authority, whether it was accepted and what state followed. In that condition, each local record may be internally plausible while the responsibility chain remains incomplete.

How the gap differs from governance, accountability and task ownership

How Responsibility Infrastructure addresses the gap

Responsibility Infrastructure provides a common foundation for representing, evidencing, verifying, recognising, resolving and relying upon responsibility across organisational and system boundaries.

The Standard states normative requirements. The Protocol defines how responsibility information can be represented and exchanged while preserving its meaning. Together they are intended to make the responsibility chain inspectable beyond a single local workflow.

How L-SCAN tests whether the gap exists

L-SCAN is a bounded diagnostic method. It tests whether responsibility for a defined operational event can be reconstructed from records that already exist. It examines evidence of assignment, acceptance, authority, handover, action and discharge without assuming that a new system must first be installed.

The diagnostic identifies where the chain is evidenced, where it is ambiguous and where a conclusion cannot be supported. It does not, by itself, certify an organisation or prove that Responsibility Infrastructure has been implemented.

What has and has not yet been independently proven

The Operational Responsibility Gap and Responsibility Infrastructure are presented as a conceptual and testable architecture. The published paper defines the problem, proposes the architecture and states propositions that can be examined through independent tests.

Public materials and an internal prototype demonstrate how the concepts can be represented and tested. They do not establish that the gap is widespread, that Responsibility Infrastructure is effective in every domain, or that an implementation has achieved independent verification, recognition or regulatory standing. External evaluation and domain-specific evidence remain necessary.