Skip to content

Time-Locked Exposure Protocol

Timing protocol — instantiates Critical-Window Intervention Timing

Phase-locks delivery of the intervention to the open window — starting only after the window opens and completing before it closes — so exposure lands when the system can actually use it.

A receptivity signal is worthless if the intervention arrives before or after it. Time-Locked Exposure Protocol is the delivery timetable that binds the intervention's schedule to the shape and edges of the window itself rather than to an ordinary calendar: it defines the intervention window, then enforces a timing rule that holds delivery until the window is open and drives it to completion before the window closes. Its defining move is phase-locking — the exposure is not merely "soon" or "on time," it is aligned to a biological, developmental, or situational clock that the intervention does not control. It presupposes that the near edge has already been detected and says nothing about how much to deliver; it governs only when, mapping the intervention onto the window's own tempo.

Example

A vineyard needs its cover crop and certain perennials to flower on schedule, which for many temperate plants requires a sustained cold spell before spring — the process of vernalization.[1] The grower cannot induce flowering by adding warmth, fertilizer, or light out of season; the cold exposure only "counts" if it is delivered during the plant's competent developmental phase and sustained across a defined interval.

The protocol time-locks accordingly: it marks the intervention window as the plant's cold-competent phase, sets a timing rule — begin chilling once the plant reaches that phase, maintain it for the required duration, and end before the phase lapses into spring growth — and phases the exposure across that interval instead of on a fixed date. Applied a week too early, before competence, the cold does nothing; delivered too late, after the phase passes, the plants bolt without flowering. Locked to the window, the same cold produces the intended flowering. The protocol's whole contribution is that alignment of delivery to the receiving system's clock.

How it works

The protocol first fixes the intervention window — the concrete open/close boundaries within which delivery must fall — and then enforces a timing rule that maps the exposure onto that interval: a start gate (no delivery before open), a completion target (finish before close), and, where the effect depends on sustained or repeated input, a phasing across the interval. Because it locks to an external clock the intervention cannot move, it treats the window's tempo as a hard constraint and schedules everything else around it, rather than the reverse.

Tuning parameters

  • Lead / preposition margin — how early resources are staged so delivery can begin the instant the window opens. A larger margin avoids a slow start but commits resources before they are certainly needed.
  • Phase alignment — front-load, spread evenly, or back-load the exposure within the interval. The right profile depends on whether the effect needs early establishment or sustained presence.
  • Completion buffer — how much slack to leave before the close edge. A wide buffer protects against an early closure but shortens usable delivery time.
  • Clock source — which external signal the schedule locks to (developmental stage, ecological season, injury timeline). Locking to the true driver rather than a proxy calendar is what keeps the exposure phased correctly.

When it helps, and when it misleads

It earns its place when the effect is genuinely phase-dependent — when the same input helps inside the window and does nothing (or harms) outside it, so alignment, not amount, is the binding variable. Its failure mode is locking to the wrong clock: a fixed calendar treated as if it were the receiving system's real tempo, so delivery drifts off the true window even while the schedule looks perfect on paper. The classic misuse is rigidity — holding to the locked schedule after evidence shows this individual's window has shifted, defending the timetable instead of the outcome. The discipline that guards against it is to lock to the real receptivity driver, keep a completion buffer, and let a re-estimated window move the schedule rather than forcing the system to the schedule.

How it implements the components

  • intervention_window — it establishes the concrete open/close interval within which all delivery must occur, translating a detected opening into scheduled boundaries.
  • timing_rule — it holds the start-gate / completion / phasing logic that binds the exposure to those boundaries.

It does not decide the dose, cadence, or safety ceiling of what is delivered (bounded_exposure_and_support_plan, safety_bound — see Within-Window Dose and Cadence Titration), does not detect the opening it waits on (readiness_signal, window_opening_criterion — see Window-Opening Readiness Assessment), and does not judge closure (window_closure_criterion — see Window-Closure Review).

Notes

Timing and dose are deliberately split. This protocol fixes when the exposure runs; Within-Window Dose and Cadence Titration fixes how much runs at each point inside it. The two are consumed together during the window, but separating them lets a team re-time delivery after a window re-estimate without re-deriving the whole dose plan, and vice versa.

References

[1] Vernalization is the acquisition of the competence to flower only after a plant experiences a prolonged cold period during a specific developmental phase. It is a clean instance of phase-locked exposure: the cold is effective only when delivered inside the window, which is why the protocol locks to the plant's developmental clock rather than to the calendar date of winter. ↩