Skip to content

Collateral-Harm Escalation Trigger

Monitor — instantiates Attrition Contest Exit Design

Tracks the damage the contest is inflicting on third parties and fires a mandatory escalation to a neutral authority once that harm crosses a preset line — so bystanders' losses can't be ignored indefinitely.

Version
v1 · 2026-08-24 · History
Mechanism #
1481
Type
Monitor
Form family
Control, Automation & Runtime
Solution family
Planning & Staging
Problem family
Incentive Conflict, Gaming & Collective-Action Failure
Problem subfamily
Rivalry, Bargaining & Escalation Trap
Origin domain
Law & Governance
Also from
Military & Strategic Studies
Instantiates
Attrition Contest Exit Design

Combatants in an attrition contest watch their own costs and the prize; they rarely watch what the fight does to the people standing nearby. Collateral-Harm Escalation Trigger is the monitor that watches on the bystanders' behalf. It maintains a register of the harm the contest imposes on third parties — customers, employees, users, the public — and, when that harm crosses a preset threshold, automatically escalates the matter out of the combatants' hands to a named neutral authority. Its distinguishing feature is that its trigger is keyed to third-party damage rather than the combatants' own burn: it exists to put a ceiling on what the fight is allowed to cost the people it steps on.

Example

Two maintainers of a widely-used open-source library fall into a governance war — competing forks, blocked releases, and a stalled critical security patch. The combatants are the maintainers; the bystanders are the thousands of downstream projects depending on the library. The hosting foundation sets up a collateral-harm escalation trigger: it registers harm signals — open critical CVEs aging past a set number of days, downstream build-breakage reports — and pre-wires a rule that if an unpatched critical CVE crosses ≈45 days, governance of the repository automatically transfers to the foundation's neutral technical board, removing the decision from the feuding maintainers. When the security patch stalls behind the dispute, the trigger fires, the board takes control, and the patch ships — the users' harm capped regardless of how the maintainers' fight plays out.

How it works

  • Define the bystanders and their harm. Name who is being hurt by the contest and choose concrete, observable harm metrics.
  • Maintain a live register. Continuously track those harm signals as they accrue.
  • Set a bright-line threshold. Fix the level of harm at which the trigger fires — unambiguous, not discretionary.
  • Pre-wire an automatic handoff. On breach, control transfers to a named, pre-agreed neutral authority; the escalation is not left to the combatants' judgment.

Tuning parameters

  • Harm metrics — which observable signals stand in for bystander damage; hard-to-fake metrics resist gaming.
  • Threshold height — low enough to protect bystanders, high enough not to fire on noise.
  • Escalation target — who inherits control on breach, and how genuinely neutral they are.
  • Automatic vs advisory — whether the handoff is mandatory or merely recommended; automaticity is what gives it teeth.
  • Register transparency — whether the harm ledger is public (pressuring the combatants) or internal.

When it helps, and when it misleads

Its strength is that it internalizes an externality[n1] the combatants otherwise ignore — the harm their contest sheds onto third parties — and, by pre-wiring an automatic neutral handoff, puts a hard ceiling on that harm.

It misleads when its metrics or threshold are wrong or gameable. Harm that can be hidden or relabeled slips under the register; a threshold set too high never fires; and the trigger can itself be weaponized — a party manufacturing apparent "harm" to force a handoff it expects to win. The discipline that guards against this is to choose harm signals that are hard to fake, name an escalation target that is genuinely neutral, and set the threshold with the bystanders themselves at the table.

How it implements the components

  • collateral_harm_register — the live ledger of damage the contest imposes on third parties.
  • neutral_settlement_or_adjudication_channel — the pre-wired, automatic handoff of control to a neutral authority when harm breaches the threshold.

It does not track the combatants' own burn — that is Attrition Burn-Rate Dashboard — and it does not watch for the fight reigniting after it ends — that is Post-Exit Non-Retaliation Commitment. This monitor guards the bystanders during the contest; others measure the fighters and watch the aftermath.

Editorial Notes

Form Classification

Form family: Control, Automation & Runtime

Rationale: Tracks the damage the contest is inflicting on third parties and fires a mandatory escalation to a neutral authority once that harm crosses a preset line — so bystanders' losses can't be ignored indefinitely, making its operative form a live operational control that automatically routes, enforces, adapts, or responds during execution.

Independent corroboration: The frozen evidence defines Collateral-Harm Escalation Trigger as 'Tracks the damage the contest is inflicting on third parties and fires a mandatory escalation to a neutral authority once that harm crosses a preset line — so bystanders' losses can't be ignored indefinitely', so its operative form is Control, Automation & Runtime.

Nearest alternative: Monitoring, Sensing & Alerting — The mechanism not only senses harm but automatically transfers control to a neutral authority when the bright line is crossed.

Review outcome: Independent reviewer agreement; medium confidence.

Origin Attribution

Primary origin: Law & Governance

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Legal governance established mandatory escalation when third-party harm or externalities exceed a predeclared protective threshold.

Related originating lineages:

Review resolution: Both reviewers agree on law_governance as primary. Reading the source mechanism confirms that its defining operation belongs to that lineage; the final record retains military_strategic_studies only where it materially formed the mechanism and keeps present-day application breadth separate from provenance.

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

Both this trigger and Mediated Off-Ramp Protocol route the contest to a neutral, but the routing differs in agency: mediation is a channel the parties choose to invoke, whereas this trigger is an automatic handoff that removes control from them once bystander harm crosses the line. The escalation target must be pre-agreed and genuinely neutral, or the trigger merely relocates the fight to new ground.

[n1] An externality is a cost imposed on parties who are not part of a transaction or contest. A war of attrition is a machine for producing them; this trigger is a device for forcing those costs back into the decision by capping how large they may grow before control is taken away.