Explainer

Error-Bearing Parties

The people who absorb a system's errors are the first to see failures and the last able to act, unless standing gives them a route in.

Definition

Short definition

Two-to-four sentences you can drop into briefs or specs.

An error-bearing party is anyone who absorbs the consequences of a system's errors: the people its decisions fall on, and the staff whose corrective labor the system depends on in order to stay usable.

Naming them is the precondition for standing. Exposure that has no procedural route into the system is signal the institution has chosen not to receive.

Canonical entry: Error-Bearing Parties in the glossary.

Example

Example use case

A concrete scenario to ground the term in operations.

A benefits eligibility system lists two error-bearing parties per decision class: the claimant whose payment is withheld, and the caseworker who spends unrecorded hours reversing miscategorized claims. Both can raise a challenge through the same mechanism.

Implementation

Distinct implementation signals

Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.

What to check

The standing register names parties by role for each decision class, including internal operators, and each named party can reach the system's own challenge channel without escalating through a manager.

Common failure pattern

Only external users are counted. The exception-handling labor that keeps the system looking reliable stays invisible, so the institution never sees the failure rate it is actually absorbing.

Evidence to ship

Report the share of decision classes with at least one named error-bearing party, and the volume of corrective labor attributed rather than absorbed.

CTAs

Related artifacts

Standards, bindings, and evidence packs to move from concept to adoption.

Doctrine

Law VII: standing proportional to exposure

Standing is procedural force, not veto, and it follows exposure rather than seniority.

Read the laws

Eval

Standing

Test whether exposure can enter the system as an event with a named responder and a clock.

Open the suite

Research

Dependence without standing

The theory essay on what happens when reliance grows and standing does not.

Read the essay

FAQ

Quick answers

Short replies for common implementation questions.

Why include staff as error-bearing parties?

Because the system depends on their corrective labor to remain usable. If that labor is uncounted, the institution is reading a reliability figure that other people are paying for.

Does standing mean a veto?

No. It means a challenge must be received, answered by a named responder on a clock, and capable of producing a state change. It need not prevail.