Cue Intensity Cap Protocol¶
Protocol — instantiates Supernormal Cue Guardrail Design
Sets a maximum allowed value for how strong a single cue may be — its salience, urgency class, sensory loading, or social-proof prominence — measured against a calibration range.
Supernormality often starts with one cue turned up too far. Cue Intensity Cap Protocol governs the strength of a single cue instance: it defines a scale for how intense a cue is, fixes a ceiling on that scale tied to a legitimate calibration range, and forbids any cue from exceeding it. Its defining idea is the per-instance strength ceiling — this protocol says nothing about how often a cue appears or how unpredictable its reward is; it caps how loud any one instance is allowed to be. A countdown may not spin faster than X, an alert may not claim a severity class higher than the underlying condition warrants, a "trending" badge may not exceed a set visual weight. The cap is a published limit, not a case-by-case judgment, so it survives staff turnover and optimization pressure.
Example¶
A hospital's clinical monitoring system has drifted into alarm chaos: over years, each vendor and each ward added louder tones, brighter flashes, and more insistent repeat patterns until nurses face a wall of maximum-urgency signals, most of them non-actionable. A Cue Intensity Cap Protocol re-establishes order by defining an urgency scale — say five classes from advisory to life-threatening — and mapping each physiological condition to the highest class it may legitimately claim. A low-battery notice is capped at the advisory class: it may not use the red-flashing, escalating tone reserved for asystole, no matter how the device ships.
The calibration range is clinical: the strongest cue is reserved for conditions where an immediate maximal response is genuinely warranted. Once the cap is enforced across devices, the top urgency class becomes rare again — and therefore meaningful again. Nurses regain the ability to distinguish a true emergency from a nuisance, because the loudest signal now tracks the highest stakes rather than the newest vendor's default. Crucially, the protocol has not reduced how frequently alarms fire; it has capped how loud each one may be.
How it works¶
- Define the intensity scale. Choose a measurable or rankable dimension of cue strength — decibels, urgency class, animation energy, metric prominence — comparable across design alternatives.
- Anchor the ceiling to a calibration range. The maximum is not arbitrary; it is set at the top of the range over which the response circuit stays proportional, so the strongest permitted cue still maps to the highest legitimate stakes.
- Publish and enforce per instance. Every cue instance is checked against the cap at design and release time; exceeding it is a defect, not a growth-experiment option.
- Reserve the top of the scale. The most intense class is held for the conditions that warrant maximal response, keeping strong signals trustworthy by keeping them scarce.
Tuning parameters¶
- Ceiling height — where the maximum sits on the intensity scale. Lower ceilings protect against hijack but risk dampening a genuinely important signal; higher ceilings preserve punch but invite arms races.
- Scale resolution — how many intensity classes the scale distinguishes. More classes allow finer proportionality; fewer are simpler to govern and audit.
- Calibration source — whether the range is clinical, historical, contractual, or validated by testing. A well-grounded source makes the cap defensible; a hand-waved one invites erosion.
- Enforcement point — design-time review, automated lint, or runtime clamp. Earlier enforcement prevents drift; runtime clamping catches escapes but can surprise.
When it helps, and when it misleads¶
Its strength is that it directly attacks the runaway-intensity condition and keeps strong cues meaningful by keeping them rare — the counter to alarm fatigue, where everything is maximal so nothing commands response.[1] Because the cap is a published number tied to a calibration range, it resists the silent escalation that happens when each team nudges its own cue up a notch.
Its failure mode is safety-signal dampening: a cap set too low, or applied without a genuine severity carve-out, can mute a cue that should be maximal — the real emergency throttled to look like the nuisances. It is also vulnerable to static-ceiling drift, where a cap set years ago no longer matches the cue environment. The classic misuse is capping intensity while ignoring repetition, so a cue that is individually within limits still overwhelms by sheer frequency — which is why this protocol must run alongside its frequency-governing sibling. The guarding discipline is to anchor the ceiling to a live calibration range, carve out verified high-severity conditions explicitly, and revisit the cap as the environment shifts.
How it implements the components¶
cue_intensity_metric— it defines the scale on which a single cue's strength is measured or ranked.response_ceiling— the cap is the ceiling, expressed as a maximum permitted intensity per cue instance.natural_calibration_range_reference— the ceiling is anchored to the range over which response stays proportional, not set arbitrarily.
It does NOT implement exposure_and_frequency_budget — limiting how often a cue repeats is Frequency Cap and Cooldown's role; nor harm_and_compulsion_signal or substitution_pathway, the reward-loop levers of Variable-Reward Schedule Limit. This protocol caps a single cue's strength, not its repetition or its reward schedule.
Related¶
- Instantiates: Supernormal Cue Guardrail Design — supplies the intensity ceiling that keeps individual cues within a proportional range.
- Consumes: Salience Normalization Test can supply evidence on where response stops being proportional, informing where the ceiling belongs.
- Sibling mechanisms: Frequency Cap and Cooldown · Variable-Reward Schedule Limit · High-Arousal Content Throttle · Supernormal Cue Audit
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Cue Intensity Cap Protocol operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it sets a maximum allowed value for how strong a single cue may be — its salience, urgency class, sensory loading, or social-proof prominence — measured against a calibration range.
Independent corroboration: The frozen evidence defines Cue Intensity Cap Protocol as 'Sets a maximum allowed value for how strong a single cue may be — its salience, urgency class, sensory loading, or social-proof prominence — measured against a calibration range', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction (HCI)
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Human-factors interface design established graded alert salience; clinical alarm safety and psychology shape the calibrated per-cue ceiling.
Related originating lineages:
- Medicine & Healthcare — Clinical alarm-safety practice supplies governed severity classes and alarm-fatigue constraints.
- Psychology & Behavioral Sciences — Psychophysics and attention research supply perceptual calibration and desensitization effects.
Review resolution: Human-factors interface design established graded alert salience; clinical alarm safety and psychology shape the calibrated per-cue ceiling.
Attribution caveat: The cap combines interface severity design, clinical alarm governance, and perceptual calibration.
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.
References¶
[1] The Joint Commission. Medical device alarm safety in hospitals. Sentinel Event Alert, Issue 50 (2013). Documents alarm fatigue as desensitization under an overwhelming volume of alarm signals, producing missed, silenced, or disabled responses. withdrawn registry ↩