Proportional Response Design¶
Match response intensity proportionally to input magnitude so intervention is predictable, explainable, and resistant to overreaction or underreaction.
The Diagnostic Story¶
Symptom: Small cases receive the same heavy response as serious ones — causing resentment, waste, and avoidable harm — while serious cases sometimes receive only ordinary response because the system has no scaling rule. People cannot predict what will follow from a given magnitude, and decision makers argue about whether a response was too much or too little without shared anchors.
Pivot: Define a calibrated mapping from input magnitude to response intensity, then bound and review that mapping with minimum obligations, maximum tolerances, and exception review. The rule must be predictable and explainable, and must remain valid for the input measure being used.
Resolution: Similar inputs receive similar responses; larger inputs receive proportionally more intensive responses. Response magnitude can be explained and compared across cases, reducing both arbitrary overreaction and neglect of high-severity cases while preserving a clear handoff to emergency or nonlinear response when thresholds are crossed.
Reach for this when you hear…¶
[platform trust and safety] “A first-time minor policy violation triggering the same permanent ban as repeat fraud is not protecting anyone — it is just destroying the appearance of fairness in a way that makes users stop trusting the whole system.”
[emergency dispatch] “We can't send three engine companies every time someone smells smoke in a kitchen — we need a severity scale so we match the resource to the actual signal.”
[tax enforcement] “If a small arithmetic error triggers the same audit intensity as suspected large-scale fraud, we will exhaust our enforcement budget on paperwork and have nothing left for the real cases.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
A system receives inputs of differing magnitude—severity, demand, use, risk, need, harm, exposure, workload, or error—but responds with inconsistent, arbitrary, flat, excessive, or underpowered action.
What this problem means
The structural problem is a mismatch between graded inputs and uncalibrated responses. The system sees cases of different size, seriousness, demand, or need, but it responds through blunt uniformity, improvised discretion, symbolic escalation, or arbitrary tables.
This mismatch shows up in two opposite ways. In one direction, the system overreacts: a small mistake receives a severe sanction, a small load increase receives a large process change, or a minor support request consumes scarce expert attention. In the other direction, the system underreacts: major incidents are handled like routine issues, severe needs receive generic support, or large users consume far more capacity than the rule accounts for.
A second problem is legitimacy. When there is no visible scaling rule, people cannot tell whether a response is fair, biased, accidental, or politically driven. Operators also cannot learn from experience because each case looks like an exception rather than evidence for recalibration.
Show the applicability expression
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Degree-varying input · open
Input varies by degree and response intensity should track it.
The source archetype describes the situation as follows: The input varies by degree rather than by simple yes/no category, and response intensity should vary with it. The normalized requirement above isolates the load-bearing portion used in this condition set.
Unequal-case response mismatch · open
Equal response to unequal cases creates waste, unfairness, overload, underprotection, or illegitimacy.
The source archetype describes the situation as follows: Equal response to unequal cases creates waste, unfairness, overload, insufficient protection, or loss of legitimacy. The normalized requirement above isolates the load-bearing portion used in this condition set.
Biased ad hoc burden · open
Ad hoc discretion creates inconsistent or biased response burdens.
The source archetype describes the situation as follows: Ad hoc discretion produces case-to-case inconsistency, escalation bias, favoritism, or unpredictable burden. The normalized requirement above isolates the load-bearing portion used in this condition set.
Proportional operating relation · open
The input-output relation should remain approximately proportional across the operating range.
The source archetype describes the situation as follows: The input-output relation is expected to remain mostly proportional within the relevant operating range. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (3)
Why these sit outside the expression
Goal — a goal states an intended outcome or evaluation criterion, not a pre-existing situation that independently summons the archetype.
Deployment constraint — it constrains how the intervention must be deployed, not the situation that calls for it.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
GoalThe system needs a stable rule that operators, affected parties, or downstream systems can understand and anticipate.
Deployment constraintThe response can be bounded by minimum guarantees, maximum caps, rights constraints, safety limits, or exception review.
Do not use it when a baseline obligation, dignity standard, safety rule, or rights constraint requires the same minimum treatment regardless of magnitude. In this archetype, the relevant deployment constraint is: The response can be bounded by minimum guarantees, maximum caps, rights constraints, safety limits, or exception review. It identifies a boundary that responsible implementation must respect.
Solution feasibilityMeasurement is good enough to support calibration, or uncertainty can be represented explicitly.
Coverage
0 of 4 conditions grounded · 4 open.
Mechanisms / Implementations¶
- Proportional Penalty Schedule: A proportional penalty schedule maps severity, recurrence, duration, or harm to sanction or remedy.
- Usage-Based Pricing Table: Usage-based pricing maps consumption or service use to cost.
- Dose Scaling Protocol: Dose scaling adjusts treatment, training, support, or intervention intensity by measured size, need, tolerance, or response.
- Load-Scaled Staffing Rule: A load-scaled staffing rule links staffing or coverage to demand.
- Resource Allocation Formula: Distribute budget, time, capacity, or attention by weighted need, demand, population, or use.
- Risk-Based Response Matrix: A risk-based matrix scales scrutiny, controls, inspection, or intervention by estimated likelihood, impact, confidence, and exposure.
- Sliding-Scale Fee Policy: Sliding-scale fees scale cost or contribution by income, need, or ability to pay.
- Graduated Enforcement Ladder: A pre-defined, escalating schedule of responses to rule-breaking — from a quiet word up to expulsion — so enforcement is proportionate, predictable, and not left to mood.
- Service Credit Formula: A service credit formula calculates compensation or remedy by outage duration, missed service level, affected scope, or contractual impact.
- Calibration Review Meeting: A calibration review meeting compares recent cases with anchors and outcomes.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Linearity: Proportional output.
- Proportion and Scale: Relative size relationships.
- Proportionality: Match response to scale.
Also references 10 related abstractions
- Constraint: Limits possibilities to guide outcomes.
- Invariance: Properties unchanged under transformation.
- Marginal Analysis: Incremental effects.
- Nonlinearity: Disproportionate output.
- Optimization: Finds best solution under constraints.
- Procedural Fairness (Due Process): Due process.
- Resource Management: Allocation of finite assets.
- Risk Aversion: Preference for certainty.
- Scale: Properties change with size.
- Threshold: Safe vs harmful levels.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Severity-Scaled Response · governance variant · recognized
Scale sanction, remedy, scrutiny, or support to the assessed severity of a case while preserving review for context and error.
Usage-Based Scaling · implementation variant · recognized
Scale price, quota, service level, capacity, or contribution by measured use or load.
Dose-Scaled Response · domain variant · recognized
Adjust treatment, support, training, or intervention dose according to measured size, need, exposure, or tolerance.
Load-Scaled Capacity Response · scale variant · recognized
Scale staffing, capacity, throughput, inspection, or support level according to measured load.
Risk-Weighted Response · risk or failure variant · candidate
Scale scrutiny, controls, reserves, or support according to measured risk while preserving false-positive and false-negative safeguards.
Passive Demand Proportional Correction · implementation variant · recognized
Couple a nuisance-producing operating variable mechanically to a corrective force so mitigation grows automatically with the condition that makes it necessary.
Editorial Notes¶
Problem Classification¶
Classification: Decision, Search & Optimization Failure → Intervention Intensity & Placement Calibration
Problem kernel: response magnitude is mismatched to input severity or need
Rationale: Earliest causal condition: A system receives inputs of differing magnitude—severity, demand, use, risk, need, harm, exposure, workload, or error—but responds with inconsistent, arbitrary, flat, excessive, or underpowered action.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system receives inputs of differing magnitude—severity, demand, use, risk, need, harm, exposure, workload, or error—but responds with inconsistent, arbitrary, flat, excessive, or underpowered action. That is a intervention intensity and placement calibration problem because A selected response is applied at the wrong magnitude, proportionality, inspection point, or exposure level relative to benefit, harm, feedback, and operational burden.
Review outcome: Independent reviewer agreement; high confidence.