Reset Period Protocol¶
Orchestration protocol — instantiates Resensitization Reset
Sequences the full reset — trigger, protected pause, and scheduled follow-up — so tolerance detection, recovery, and controlled return happen in order rather than ad hoc.
Every other reset mechanism does one job — rotate, ramp, retest, pause. Reset Period Protocol is the conductor that puts those jobs in the right order and holds the interval open long enough for them to work. Its defining move is not any single reset action but the sequencing and governance of the whole loop: it names the condition that starts a reset, protects a bounded window during which exposure is genuinely reduced, and schedules the follow-up checks that turn a one-time pause into a repeatable cycle. A team can rotate stimuli or ramp them back on their own, but without a protocol wrapping those actions, nothing decides when to start, how long to hold, or whether the reset stuck — and the pause quietly collapses back into the old pattern the moment pressure returns.
Example¶
A manufacturing plant runs a behavior-based safety program: supervisors log peer safety observations each shift. After two years, observation quality has cratered — people file identical "PPE OK" cards to hit their quota, and the cards no longer surface real hazards. Escalating the quota only produces more empty cards. The safety lead installs a Reset Period Protocol. The trigger is explicit: when the share of cards flagging an actual corrective action falls below a set floor for three straight weeks, a reset is warranted rather than a quota increase. The protected interval suspends the daily card requirement for six weeks — observations continue only for genuinely noticed hazards, so the program isn't abandoned, just relieved of its rote volume. The lead sets a follow-up cadence: check hazard-flag rate at week three, week six, and monthly for a quarter after observations resume.
The protocol itself doesn't decide the new observation format or run the recovery test — it hands those to other mechanisms. What it guarantees is that the pause is bounded, that someone is watching for the response to return, and that the reintroduction happens on a schedule rather than whenever a manager gets nervous about "not tracking safety." Six weeks later the flag rate has tripled, and the monthly cadence catches an early slide back toward rote filing before it becomes another two-year plateau.
How it works¶
The protocol is a state machine over the reset, not a reset technique:
- Arm the trigger. Define, in advance, the observable condition that distinguishes tolerance-driven decline from noise or a broken signal — and commits the team to reset rather than escalate when it fires.
- Open a bounded window. Declare the abstention interval with a fixed floor and ceiling on duration, so the pause can't drift into abandonment or be cut short by the first anxious stakeholder.
- Delegate the interior. The recovery signal, the retest, and the reintroduction shape are called by the protocol but owned by specialized siblings; the protocol only enforces that they happen in order.
- Schedule relapse checks. Fix the follow-up cadence before reintroduction, so returning desensitization is caught on a calendar rather than by luck.
The whole value is temporal discipline: a start condition, a held interval, and a follow-up rhythm that no single-step mechanism supplies.
Tuning parameters¶
- Trigger strictness — how much sustained decline is required before a reset fires. Loose triggers reset too often and thrash the system; strict triggers let tolerance entrench before relief arrives.
- Interval floor and ceiling — the minimum hold that protects recovery versus the maximum before skills or coverage decay. Wider bands give recovery room; narrower bands limit disruption.
- Delegation boundary — how much the protocol prescribes versus hands to siblings. A thin conductor stays reusable across domains; a thick one bakes in assumptions that may not travel.
- Relapse cadence density — frequent early checks catch fast rebounds but cost attention; sparse checks are cheap but let relapse run.
When it helps, and when it misleads¶
Its strength is that it converts a vague intention ("we should give this a rest") into a governed, auditable cycle with a defined beginning, middle, and end — and its relapse cadence is what keeps a reset from being a one-off that decays back to baseline. It also protects the interval politically: because the floor was agreed up front, a nervous stakeholder can't quietly reinstate the old exposure on day three.
Its failure mode is reset-as-avoidance — the protocol's ceremony can be used to look like the system is being fixed while the underlying input is actually invalid and should be redesigned, not merely rested. Because the protocol delegates the retest, it is only as honest as the recovery evidence fed back into it; a team can run the full sequence and declare victory on elapsed time alone, mistaking habituation's natural rest-driven recovery[n1] for a real fix. The guarding discipline is a stop rule: if response does not recover after a bounded, well-run interval, the protocol must escalate to redesign rather than schedule another pause.
How it implements the components¶
Reset Period Protocol realizes the governance-and-timing backbone of the archetype — the components that order the loop, not the ones that perform each step:
reset_trigger_condition— its opening move: the pre-committed condition that starts a reset instead of an escalation.abstention_period— it declares and protects the bounded window of reduced exposure, with an enforced floor and ceiling.relapse_monitoring_cadence— it fixes the follow-up schedule that turns a single reset into a sustainable cycle.
It does not implement response_retest (that belongs to Response Retest Assessment), reintroduction_rule (owned by Reintroduction Ramp), or variation_rule (owned by Exposure Rotation); the protocol calls those steps but does not perform them.
Related¶
- Instantiates: Resensitization Reset — this protocol is the sequencing spine the archetype's loop hangs on.
- Consumes: Response Retest Assessment supplies the recovery verdict; Reintroduction Ramp supplies the return shape.
- Sibling mechanisms: Exposure Rotation · Alert Suppression and Rotation Workflow · Reward Schedule Refresh · Message Refresh Campaign · Drug Holiday · Reintroduction Ramp · Novelty Reintroduction · Deload Week
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Reset Period Protocol operates as a repeatable ordered procedure or handoff sequence that coordinates action because it sequences the full reset — trigger, protected pause, and scheduled follow-up — so tolerance detection, recovery, and controlled return happen in order rather than ad hoc.
Independent corroboration: The frozen evidence defines Reset Period Protocol as 'Sequences the full reset — trigger, protected pause, and scheduled follow-up — so tolerance detection, recovery, and controlled return happen in order rather than ad hoc', so its operative form is Protocol, Workflow & Routine.
Nearest alternative: Control, Automation & Runtime — Reset Period Protocol includes features of a live operational control that automatically routes, enforces, adapts, or responds during execution, but its defining operation is a repeatable ordered procedure or handoff sequence that coordinates action.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Protected pauses followed by assessed recovery and controlled return are rooted in clinical management of tolerance and fatigue.
Related originating lineages:
- Pharmacology & Toxicology — Drug holidays and tolerance management independently developed medically supervised pause-and-return protocols.
- Psychology — Behavioral reset and relapse-prevention practice materially shaped trigger and follow-up sequencing.
Review resolution: Both blind reviewers agree that medicine_healthcare is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement adopts reviewer_a's evidence: Protected pauses followed by assessed recovery and controlled return are rooted in clinical management of tolerance and fatigue. The selected record uses alternates=pharmacology_toxicology, psychology, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; the other review proposed alternates=psychology, origin_mode=single_lineage, and domain_reach=multi_domain. The selected combination better preserves the mechanism-specific formative lineages and calibrated scope; broader present-day use is not treated as proof of additional historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
Keep the protocol thin. Its reusability comes from not prescribing a reset technique — the same trigger/interval/cadence skeleton governs an alert reset, a training deload, and an incentive refresh precisely because it delegates the interior. A protocol that hard-codes "suppress the alert" or "lower the load" stops being a conductor and becomes just another single-step mechanism.
[n1] Habituation — the well-established decrease in response to a stimulus repeated without consequence, and its partial recovery after a rest interval — is why a protected pause can restore responsiveness at all. It is also the trap: rest-driven recovery of a habituated response can be mistaken for a genuine fix to an input that was actually invalid. ↩