Cumulative Impact Budget¶
Budget model — instantiates Ratchet Control and Release Design
Tracks total accumulated displacement as a running budget against the original baseline, counts the compounding burden of interacting layers, and trips a mandatory review when the cap is breached.
A Cumulative Impact Budget treats accumulated displacement as a quantity to be accounted, not a feeling to be argued about. It fixes an explicit ceiling — a budget — on the total burden the system may carry (complexity points, control-count, cognitive load, scope units), measured against a protected baseline, and it counts not merely the linear sum of teeth but the super-linear burden that interacting teeth impose on each other. When the running total approaches the cap, the budget trips a mandatory review. Its defining move — and what separates it from a rule applied one increment at a time — is that it measures a stock: the whole accumulated pile at once, interaction effects included, rather than screening each new increment in isolation. It answers "how much have we accumulated, and is it still tolerable?", not "should we admit this next one?"
Example¶
A hospital's electronic health record has, over a decade of incidents and quality initiatives, accreted best-practice alerts — some 214 distinct pop-up warnings now fire during a routine admission. Each was added for a real reason. The patient-safety committee installs a Cumulative Impact Budget. It anchors a baseline (the alert load the workflow was designed around, roughly 40), sets a cap on alerts fired per encounter, and — critically — models interaction, because the twentieth alert does not cost one unit of attention: it costs far more, since clinicians begin dismissing all alerts reflexively. The budget's tally shows current load at 214 against a cap of 60, and the interaction curve estimates effective attention-cost has long passed the point where alerts are net-negative. Breaching the cap triggers a mandatory review that must consolidate or remove alerts back under budget before any new one is admitted. The numbers are illustrative, but the shape is real: the budget makes "too many alerts" a measured overage, not an opinion, and gives the aggregate a number that can be held accountable.
How it works¶
- Anchor the baseline. Peg to the original design load, not last quarter's already-inflated figure, so the total is judged against intent rather than against yesterday's drift.
- Choose a burden unit and a cap. Count in a unit that matters (alerts per encounter, active controls, scope-points) with an actionable ceiling.
- Model interaction, not just the sum. Estimate the super-linear cost of teeth acting together (attention collapse, combinatorial checks), so the budget reflects felt burden rather than a headcount.
- Trip review at the cap. Crossing the ceiling mandates a review that must bring the total back under budget; the cap is a trigger, not merely a readout.
Tuning parameters¶
- Cap rigidity — a hard limit (reject everything over) versus a review trigger (flag and require justification); harder is safer, softer preserves flexibility.
- Burden unit — a simple count versus a weighted, interaction-adjusted score; richer units capture felt load but are harder to compute and contest.
- Interaction curve — how steeply burden is assumed to compound; too flat understates the pile, too steep cries wolf.
- Baseline choice — original design intent versus a negotiated "acceptable current" baseline; the former is stricter and harder to game.
- Review consequence — whether a breach forces removal back under budget or merely records a note.
When it helps, and when it misleads¶
Its strength is that it makes the aggregate visible and gives the "no single decision is culpable" problem a number that is culpable — the total. Its interaction modeling captures what linear tallies miss: that burden from retained layers is often super-linear, the core of the intervention-stack failure and the mechanism behind alert fatigue.[1]
Its failure mode is that a budget is only as honest as its unit and its interaction curve; a tidy score invites false precision over burdens (morale, legitimacy) that resist counting, and a cap set too loosely just ratifies the current pile as "within budget." The classic misuse is gaming the unit — reclassifying teeth so they no longer count against the cap. The discipline that keeps it honest is to keep the baseline pinned to original intent, re-derive the interaction curve from observed behavior rather than assumption, and self-check periodically for reclassification.
How it implements the components¶
displacement_cap_or_budget— the explicit ceiling on total accumulated burden, and the review it triggers, are exactly this component.aggregate_interaction_model— the super-linear model of how retained teeth compound each other's cost, so the total reflects interaction and not just headcount.baseline_anchor— the protected original-design reference the total is measured against, rather than the already-drifted current state.
It measures the pile but does not screen each new increment at the door (increment_admission_gate — that's One-In/One-Out or Cap Rule), and it computes the total rather than keeping the running event record (cumulative_displacement_ledger — that's Ratchet Event Log, which it reads).
Related¶
- Instantiates: Ratchet Control and Release Design — it supplies the cap and the aggregate-burden accounting the review structure hangs on.
- Consumes: Ratchet Event Log — the record of teeth the budget totals.
- Sibling mechanisms: Add/Remove Symmetry Audit · De-Escalation Gate · De-Ratcheting Sprint · One-In/One-Out or Cap Rule · Ratchet Event Log · Ratchet Threshold Dashboard · Stale Tooth Review · Sunset Clause Register · Rollback Runbook
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Cumulative Impact Budget operates as an ongoing sensing arrangement that repeatedly observes actual state and surfaces changes or alerts because it tracks total accumulated displacement as a running budget against the original baseline, counts the compounding burden of interacting layers, and trips a mandatory review when the cap is breached.
Independent corroboration: The frozen evidence defines Cumulative Impact Budget as 'Tracks total accumulated displacement as a running budget against the original baseline, counts the compounding burden of interacting layers, and trips a mandatory review when the cap is breached', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Regulatory-stock and cumulative-impact practice is primary because the artifact governs an accumulated burden against an accepted baseline and makes a cap breach trigger mandatory review. Accounting supplies the running budget ledger, while organizational risk practice supplies the broader operational burden inventory.
Related originating lineages:
- Accounting & Auditing — Budgetary control supplies the running stock, cap, interaction charge, and exception-ledger structure.
- Organizational & Management Science — Operational governance supplies inventories of accumulated controls, complexity, workload, and cognitive burden.
Review resolution: Regulatory-stock and cumulative-impact practice is primary because the artifact governs an accumulated burden against an accepted baseline and makes a cap breach trigger mandatory review. Accounting supplies the running budget ledger, while organizational risk practice supplies the broader operational burden inventory.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] Alert fatigue — the well-documented clinical phenomenon in which a high volume of alerts (many low-value) desensitizes practitioners, so they begin overriding or ignoring all alerts, including critical ones. It is a concrete case of super-linear interaction burden: the marginal cost of the next alert is not constant but rises as the population grows. withdrawn registry ↩