Counterparty Obligation Register¶
Accountability mapping — instantiates Rights–Freedoms Obligation Mapping
Turns each recognized claim into a line item with a named duty-owner, a service level, the capacity behind it, and an enforcement hook — so no obligation floats unassigned.
The Counterparty Obligation Register is the ledger that makes a claim operational. Where the matrix shows that a claim entails a duty and the tree shows what type it is, the register answers the accountability questions that make the duty real: who owns it, to what standard, with what capacity behind them, and what happens if they miss. Its defining move is turning each recognized claim into a maintained line item — a named owner, a service-level definition, the staffing or budget that backs it, and an enforcement hook — and refusing to let a duty exist without one. It is forward-looking and standing: not a one-time classification but a live roster that a claim without an owner cannot survive in. Its output is the thing an operations lead can actually be held to.
Example¶
A mid-sized city adopts a policy that residents "have a right to safe drinking water." The phrase has already been typed as a claim; the register is where it stops being a slogan. The analyst opens a line item and starts filling fields. Owner: the municipal water utility's operations director — not "the city," which owns nothing actionable. Standard: contaminant levels tested at defined intervals, results published within a set window. Capacity behind it: the lab throughput, sampling crew, and treatment budget that make the standard physically deliverable — and here the register earns its keep, because the capacity field shows the current lab can test only two-thirds of the required sites on schedule. That gap, invisible in the policy language, is now a budgeted line. Enforcement hook: who a resident notifies on a failed test, who must act, and in what time. The finished line item reads as an accountable commitment: a named director, a measurable standard, a costed capacity, and a route when it breaks — where the policy had said only "right to safe water."
How it works¶
- One line item per recognized claim. A claim with no line, or a line with an empty owner field, is treated as unrecognized until filled.
- Assign a named, specific owner. Not an institution but a role that can actually perform or answer for the duty.
- Define the service level. What counts as the duty being met — thresholds, intervals, response times — so "met" is not a matter of opinion.
- Cost the capacity behind it. Attach the staffing, budget, or infrastructure that makes the standard deliverable; a standard with no backing capacity is flagged as nominal.
- Attach an enforcement hook. Name where a breach is reported and who must respond, so the duty has teeth without the register itself running the case.
Tuning parameters¶
- Owner granularity — a single accountable role versus a full RACI split across contributors. Finer splits reduce finger-pointing but multiply coordination.
- Service-level firmness — hard numeric thresholds versus qualitative commitments. Hard levels are enforceable but can turn into ceilings; soft ones flex but blur "met."
- Capacity-honesty depth — whether the capacity field must reconcile against real budget and headcount, or may state an aspiration. Deeper honesty exposes unfunded mandates but invites political friction.
- Refresh cadence — how often lines are re-owned as reorganizations move duties. Frequent refresh prevents orphaned obligations but costs maintenance.
When it helps, and when it misleads¶
Its strength is that it kills the unowned promise: a claim cannot sit in the register without a named owner, a standard, and a capacity line, so "someone should handle that" becomes "this director, to this level, with this budget." That is the antidote to the unfunded mandate — a recognized obligation with no allocated capacity to deliver it, which the capacity field forces into the open rather than leaving as informal rationing.[n1] Its failure mode is the mirror image: the register can turn a genuine right into a defensive service-level ceiling, where the owner delivers exactly the stated threshold and treats anything beyond it as out of scope, quietly capping a claim that was meant to be a floor. The guarding discipline is to mark each service level explicitly as a minimum floor rather than a target, and to review capacity gaps as commitments to close, not as standing justifications for denial.
How it implements the components¶
counterpart_obligation_map— each line item names the specific actor who bears the duty correlative to a recognized claim, converting an abstract obligation into an owned one.positive_enablement_and_capacity_map— the capacity field attaches the staffing, budget, or infrastructure that makes the duty deliverable, exposing where provision is promised but unfunded.remedy_enforcement_and_review_path— the enforcement hook names where a breach is reported and who must respond, giving the duty a route to be enforced.
The register attaches an enforcement hook but does not follow a breach through to verified closure — that end-to-end assurance, and the change_revocation_and_transition_rule that versions a withdrawn duty, belong to the Remedy Traceability Review, its nearest twin — and it neither surfaces conflicts (normative_conflict_and_interaction_matrix, the Rights-Conflict Scenario Table) nor tests whether a constraint is justified.
Related¶
- Instantiates: Rights–Freedoms Obligation Mapping — the register is where recognized claims become accountable, capacity-backed duties.
- Consumes: Claim–Liberty Classification Tree supplies the typed claims each line item is opened for.
- Sibling mechanisms: Hohfeldian Relation Matrix · Claim–Liberty Classification Tree · Rights-Conflict Scenario Table · Least-Restrictive Alternative Screen · Proportionality Balancing Record · Permission–Entitlement Crosswalk · Remedy Traceability Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Counterparty Obligation Register operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it turns each recognized claim into a line item with a named duty-owner, a service level, the capacity behind it, and an enforcement hook — so no obligation floats unassigned.
Independent corroboration: The frozen evidence defines Counterparty Obligation Register as 'Turns each recognized claim into a line item with a named duty-owner, a service level, the capacity behind it, and an enforcement hook — so no obligation floats unassigned', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Rights and contract law cohered mapping recognized claims to specific duty bearers, enforceable standards, and remedies.
Related originating lineages:
- Organizational & Management Science — Accountability registers supply named owners, service levels, capacity backing, and maintained status.
- Public Administration & Policy — Public-service administration supplies funded mandates, performance obligations, and escalation arrangements.
Review resolution: Both reviewers agree on the legal rights-and-duties primary. Organizational accountability and public-service administration make recognized claims operational, so the register is a genuine synthesis rather than merely a legal list.
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¶
[n1] An unfunded mandate is an obligation imposed on a body without the resources to meet it — a recognized duty whose capacity line is empty. The register's capacity field is designed to make exactly this gap a visible, budgeted item rather than an informal shortfall absorbed by whoever is least able to refuse. ↩