Progressive Threshold Raise¶
Incremental ramp — instantiates Latent Capacity Release Design
Turns a single quantitative limit upward in small, feedback-gated increments — each step held until the system settles and cleared of overshoot before the next raise.
When the suppressing constraint is a number — a rate cap, a dose, a speed limit, a concurrency ceiling — you can release it by turning the dial up a little at a time. Progressive Threshold Raise raises one quantitative limit in small increments, holds after each raise until the system settles into a new steady state, checks for overshoot, and only then clears the next increment. Its defining move is that the step size and hold time are a controller: the release is a feedback loop on a continuous quantity, not a plan of distinct stages. The dial goes up only as fast as the system proves it can absorb, and each raise is gated on the last one having stabilized.
Example¶
A patient with severe hypertension needs a potent vasodilator, but the drug's latent effect could overshoot — dropping blood pressure so fast it causes fainting. The clinician does not prescribe the target dose on day one. She starts at 10 mg, holds for three days, and checks for orthostatic drop when the patient stands. Only when blood pressure has settled at a safe new level and no dizziness appears does she clear the raise to 20 mg, then repeats. "Start low, go slow."[1]
Over six weeks the dose climbs to the effective 60 mg without a single hypotensive episode, because every increment was gated on the previous one stabilizing and screened for overshoot. The latent blood-pressure response was released, but metered out slowly enough that the body's own regulation kept pace. The threshold moved; the patient never fell.
How it works¶
- Set the increment and the hold window. A small step and a settle period longer than the system's response lag are the two dials that make the loop safe.
- Raise, then hold. After each raise, freeze the dial and let the system reach a new steady state before touching it again — the stabilization step, not an afterthought.
- Screen each step for overshoot. Watch the monitored response for a swing past the safe band; overshoot at a small step is a warning the next step would be worse.
- Gate the next raise on stability. The readiness gate for increment n+1 is "increment n has settled and shown no overshoot"; if it hasn't, hold or step back down rather than pressing on.
Tuning parameters¶
- Increment size — small steps are safe but slow to reach the target; large steps reach it fast but risk overshoot the loop can't catch in time.
- Hold / settle window — longer holds let slow responses fully express before the next raise; shorter holds reach target faster but can stack unsettled effects.
- Overshoot trip threshold — how far past the safe band counts as overshoot; a tight threshold halts early and safely, a loose one tolerates noise but risks a real excursion.
- Back-off rule — on overshoot, whether to halt, step down one increment, or return to the last stable level; a decisive back-off protects safety at the cost of progress.
When it helps, and when it misleads¶
Its strength is on continuous, monotonic, observable responses: it extracts the full latent range while never letting the system move faster than it can stabilize, and the small steps make any excursion small and recoverable.
It misleads when the response is not smooth — a delayed or threshold response hides a cliff that the gentle steps march you right off, because each individual raise looked safe until the accumulated effect tipped over.[n1] Hysteresis is the other trap: a system that stabilizes on the way up at one level may not on the way down, so a back-off to a "previously safe" level isn't safe. The classic misuse is raising again before the previous step has fully settled, so unresolved overshoot compounds across steps. The guarding discipline is a settle window comfortably longer than the system's lag, and treating overshoot at any step as a stop signal rather than noise.
How it implements the components¶
release_readiness_gate— each increment is gated on the prior one having settled without overshoot; the gate is re-evaluated at every step, not once.rebound_and_overshoot_monitor— the loop continuously watches the response for excursions past the safe band and uses them to halt or reverse.post_release_stabilization_plan— the mandatory hold-and-settle after each raise is the stabilization plan, applied incrementally rather than once at the end.
It does not implement suppressing_constraint_map, bounded_release_plan, or rollback_or_reconstraint_path in the discrete sense — those belong to its nearest twin, Staged Rule Relaxation, which decomposes a categorical rule into separable clauses and lifts them one at a time; a threshold has no clauses to map, only a dial to turn, so the substance here is the control loop rather than a sequenced plan.
Related¶
- Instantiates: Latent Capacity Release Design — the incremental control loop that extracts a numeric constraint's latent range without overshoot.
- Consumes: Release Timing Gate can decide when the first increment is allowed to begin.
- Sibling mechanisms: Pilot Constraint Lift · Sandbox Release Trial · Staged Rule Relaxation · Release Timing Gate · Temporary Safeguard Net · Adaptive Reconstraint Protocol · Post-Release After-Action Review
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Progressive Threshold Raise operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it turns a single quantitative limit upward in small, feedback-gated increments — each step held until the system settles and cleared of overshoot before the next raise.
Independent corroboration: The frozen evidence defines Progressive Threshold Raise as 'Turns a single quantitative limit upward in small, feedback-gated increments — each step held until the system settles and cleared of overshoot before the next raise', so its operative form is Control, Automation & Runtime.
Nearest alternative: Rule, Policy & Commitment — Progressive Threshold Raise includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a live operational control that automatically routes, enforces, adapts, or responds during execution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Ramping a quantitative limit in feedback-gated increments is canonical commissioning and control-engineering practice.
Related originating lineages:
- Systems Thinking & Cybernetics — Progressive Threshold Raise is most plausibly rooted in the systems_cybernetics tradition because its characteristic form depends on feedback, thresholds, dynamic regulation, and whole-system intervention. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of engineering design. NIST: Overshoot Mitigation Using the Reference Governor Framework documents the defining practice, history, or theory described in the selected origin rationale. Other domains are retained only where the blind reviews identify material co-development or translation; broad later application is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among formative lineages.
Attribution caveat: The blind-review boundary with systems cybernetics is substantive: those traditions materially developed, translated, or operationalized part of the mechanism. The cited provenance places its defining lineage in engineering design.
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:
Notes¶
[n1] Titration — the clinical practice of adjusting a dose in small steps toward a target effect while watching the patient's response, captured in the adage "start low, go slow." It is the medical name for exactly this feedback-gated ramp, and its known danger is the non-linear response: a dose that is safe at each step can still cross a threshold the small steps conceal. ↩
References¶
[1] Catterson, M. L., Preskorn, S. H., & Martin, R. L. “Pharmacodynamic and Pharmacokinetic Considerations in Geriatric Psychopharmacology”. Psychiatric Clinics of North America 20(1), 205–218 (1997). Advises geriatric psychopharmacology prescribers to “start low and go slow.” registry ↩