Monitoring Requirement¶

Compliance monitor — instantiates Moral Hazard Mitigation

Obliges the protected actor to expose their behavior through reporting, telemetry, inspection, or audit, so hidden action that shifts risk becomes visible enough to govern.

Every other lever in this archetype needs to know what the protected actor actually did. A Monitoring Requirement is the mechanism that produces that knowledge. It obliges the actor to expose the risk-relevant behavior — through reporting, telemetry, inspection, sampled audit, or verified self-report — turning hidden action into a visible signal measured against a defined standard. Its distinctive role is that it imposes no consequence and holds no stake: it manufactures observability, and the sanctions, repricings, and recoveries that other mechanisms apply all depend on the signal it creates. Because it is the sensor rather than the penalty, its design questions are different from its siblings' — how intense, how proportionate, how gameable — and its most valuable side effect is that watching often surfaces a developing problem early enough to fix before it becomes a loss.

Example¶

A factory operates under an air-emissions permit. It is protected in the sense that it is licensed to run and to discharge within limits, and the environmental cost of any exceedance falls on the public and downstream neighbors, not the plant's own balance sheet. With no visibility, an operator could quietly exceed limits whenever compliance is inconvenient. The permit therefore carries a monitoring requirement: a Continuous Emissions Monitoring System reports stack concentrations, periodic third-party stack tests verify the instruments, and inspectors have access.^[1] That makes exceedances observable, so a penalty, a permit action, or a repricing can attach to them — and, just as important, a drifting scrubber shows up in the trend data before it becomes a violation, letting the plant fix it first. The requirement produces the visibility; what to do about a breach belongs to other mechanisms.

How it works¶

Name the observable. Define the behavior or metric that matters and the standard it is judged against, so monitoring measures the real risk rather than a convenient proxy.
Establish the channel. Require a means of visibility — telemetry, reporting, inspection, or audit — proportionate to the stakes and to privacy.
Verify self-reports. Where the actor reports on themselves, add sampling or third-party checks so the signal can be trusted.
Feed the signal downstream. Deliver the observations to the mechanisms that attach consequences, and use early trends to prevent loss at the source.

Tuning parameters¶

Intensity — continuous telemetry versus periodic audit versus verified self-report. More intensity sees more but costs more and intrudes more.
Monitor identity — self-monitoring, third-party, or regulator. Independence raises trust and cost; self-monitoring is cheap but needs verification.
Proportionality — how far surveillance is scaled to the stakes and to privacy and dignity concerns; over-monitoring is its own harm.
Metric choice — what exactly is measured; the difference between the true risk and an easy proxy decides whether the actor can game it.
Cadence and retention — how often behavior is observed and how long records are kept, shaping both timeliness and the evidence base for later consequences.

When it helps, and when it misleads¶

Its strength is foundational: without observability, none of the archetype's other levers can attach — a clawback has nothing to trigger on, an experience rating has no record, a behavior-conditioned warranty cannot tell whether the condition was met. Monitoring also earns its keep by catching problems early enough to prevent the loss entirely.

Its weaknesses are cost, gaming, and intrusion. Monitoring is expensive, it can be defeated by teaching to the metric — reporting the observed proxy while the real risky action moves elsewhere — and it can become disproportionate surveillance that harms the people it watches. The classic misuse is measuring what is easy rather than what matters, so the actor optimizes the proxy and the real risk is untouched. The discipline is proportionate monitoring tied to the actual risk metric, with verification of self-reports and a metric chosen to resist gaming.

How it implements the components¶

Monitoring Requirement realizes the observability side of the archetype:

observability_or_monitoring_channel — its core output: the channel that makes hidden action visible.
behavior_standard — the standard the observed behavior is measured against, so the signal means something.
loss_prevention_support — early visibility surfaces developing problems in time to correct them before they become losses.

It does not impose the consequence when a breach is seen — that is Clawback Clause and Experience Rating — nor require a stake, which is Collateral Requirement and Performance Bond, nor allocate the resulting loss, which is Shared Liability Clause.

Instantiates: Moral Hazard Mitigation — it converts hidden action into a governable signal that the archetype's other mechanisms depend on.
Sibling mechanisms: Clawback Clause · Experience Rating · Behavior-Conditioned Warranty · Collateral Requirement · Copay · Deductible · Malpractice or Professional Liability · Performance Bond · Risk-Adjusted Contract · Shared Liability Clause · Usage Cap or Throttle

Notes¶

Monitoring is upstream of most of the set. Clawback needs its evidence, experience rating needs its records, a behavior-conditioned warranty needs its proof of compliance, and a performance bond needs its confirmation that obligations were met. On its own it changes nothing — it only makes the actor's behavior knowable — which is why it is almost always paired with a consequence mechanism rather than deployed alone.

References¶

[1] A Continuous Emissions Monitoring System (CEMS) directly measures a facility's stack emissions on an ongoing basis and is required under U.S. Clean Air Act permitting for many sources. It is a real, standardized observability channel: it produces the compliance signal, while enforcement and penalties are handled separately. ↩