Synchronized Campaign Calendar¶
Scheduling artifact — instantiates Sanctuary-Aware Source Control
Schedules source and sink interventions to land together and inside the target's vulnerable window, so no actor clears early and leaves a gap the surviving source can reseed.
Acting on the source and the sinks is not enough if they are acted on at different times. Synchronized Campaign Calendar is the artifact that sequences every intervention across every actor onto a common timeline, locked to the target's intervention window — the phase of its life-cycle or operation when action actually bites — so that suppression and source-control land together rather than piecemeal. Its defining move is to treat timing and simultaneity as the deliverable: a zone cleared a month before its neighbor, or an actor who treats late, opens exactly the gap a surviving source needs to reseed the rest. The calendar coordinates when and in what order; it does not itself carry out the intervention, and it confers no authority to act — it is the shared clock the whole campaign is run against.
Example¶
An apple-growing valley is fighting codling moth, and every grower spraying on their own schedule has produced a stalemate: someone always treats late or skips a block, and the untreated trees reseed the moth back across the valley within a generation. The Synchronized Campaign Calendar replaces the private schedules with one regional plan. It is built around the moth's biology — degree-day models and pheromone-trap counts fix the ~2-week window when eggs are being laid and the sprays and mating-disruption releases actually work — and it locks every orchard, plus the community-managed source blocks along the creek, to the same window. It also routes deliberately around the valley's organic and pollinator refuges, timing and placing treatments so sparing those blocks doesn't reopen a reseeding corridor.
The output is a dated, valley-wide schedule: this window, these blocks, in this order, with the source blocks hit no later than the sinks. Its whole value is denying the gap — if even ~10% of blocks fall off the calendar or drift a week late, that fraction becomes a source and the synchronization is worth little. So the calendar tracks participation as a first-class number and ties its windows to live trap counts rather than fixed dates, re-issuing when the season runs early. What it does not do is spray anything or give anyone the right to enter a block — it says when, and leaves the doing and the access to others.
How it works¶
- Anchor to the intervention window. Set each action's timing from the target's vulnerable phase — phenology, degree-days, monitoring thresholds — rather than from operational or calendar convenience.
- Synchronize source and sink. Lock every actor's treatments to a common window and order them so the source is hit no later than the sinks it feeds, denying any reseeding gap.
- Route around the sanctuaries in time and space. Schedule and place interventions so that sparing a protected refuge does not leave an opening the source can exploit.
- Track participation and re-issue. Treat coverage as a first-class metric and re-cut the calendar as the season shifts, since a stale window or a few defectors reopens the reseeding path.
Tuning parameters¶
- Window definition — how the intervention window is fixed (fixed dates, degree-day phenology, or live trap thresholds). Tighter, biology-driven windows raise efficacy but shrink scheduling slack.
- Synchronization tightness — simultaneous action versus staggered-with-overlap. Tighter denies reseeding gaps but is harder for many actors to hit at once.
- Participation target — what fraction of actors must be on-calendar for it to work. A low bar tolerates defectors who then reseed the whole area.
- Sanctuary carve-outs — how refuges are timed and routed around. Careless carve-outs spare the refuge but open a reseeding corridor beside it.
- Buffer and slack — how much weather and readiness contingency each window carries. Too little and one bad-weather day collapses the synchronization; too much and the window drifts out of the vulnerable phase.
When it helps, and when it misleads¶
Its strength is that it closes the timing gap that quietly defeats source control — the cleared-then-reseeded cycle that comes from actors treating at different times. Area-wide synchronization is what turns dozens of local suppressions into a single, durable shift in the source–sink balance instead of a rolling stalemate.
Its failure mode is that a calendar is only paper: it assumes participation it cannot compel and window-accuracy it does not verify, so a wrong phenology window or a handful of defectors silently reopens the reseeding path, and a static schedule drifts as the season runs early or late.[n1] The classic misuse is a synchronized-looking schedule assembled to signal coordination while the key actors never actually commit — coordination theater. The discipline that keeps it honest is to tie windows to live monitoring rather than fixed dates, to track participation as a first-class metric rather than assume it, and to re-issue the calendar as the season and the trap counts move.
How it implements the components¶
Synchronized Campaign Calendar realizes the timing-and-coordination side of the archetype — the components that decide when and in what order the campaign acts:
synchronized_source_and_sink_control_plan— it is the time-sequenced, cross-actor plan that lands source and sink interventions together rather than piecemeal.intervention_window— it anchors every scheduled action to the target's vulnerable phase, so effort falls when it actually bites.
It does not carry out the suppression or conversion it schedules — that is the Source Reduction Program — nor does it decide which nodes are sources and sinks (the Source–Sink Network Mapping) or secure the access and authority to be present in a zone at the scheduled time (the Coordinated Access Protocol and Sanctuary Reachability Audit).
Related¶
- Instantiates: Sanctuary-Aware Source Control — the calendar is the shared clock that makes "act on source and sinks together" real rather than aspirational.
- Consumes: Source–Sink Network Mapping supplies which nodes must be scheduled, in what order.
- Sibling mechanisms: Source Reduction Program · Coordinated Access Protocol · Source–Sink Network Mapping · Sanctuary Reachability Audit · Sentinel Surveillance Dashboard · Rebound and Reseeding Stress Test · Containment Barrier · Below-Replacement Confirmation Test · Cross-Boundary After-Action Review · Protected-Zone Exception Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Synchronized Campaign Calendar is defined in the frozen evidence as: Schedules source and sink interventions to land together and inside the target's vulnerable window, so no actor clears early and leaves a gap the surviving source can reseed. Its operative deployed or enacted form is therefore Representation, Specification & Plan.
Nearest alternative: Control, Automation & Runtime — Control, Automation & Runtime can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Coordinating timed campaigns across actors is a program-administration scheduling practice.
Related originating lineages:
- Law & Governance — Legal doctrine, regulatory governance, and procedural accountability supplies a parallel or contributing lineage for the mechanism's defining operation: schedules source and sink interventions to land together and inside the target's vulnerable window, so no actor clears early and leaves a gap the surviving source can reseed.
- Military & Strategic Studies — Military planning, readiness, and strategic operations supplies a parallel or contributing lineage for the mechanism's defining operation: schedules source and sink interventions to land together and inside the target's vulnerable window, so no actor clears early and leaves a gap the surviving source can reseed.
- Organizational & Management Science — Shared calendars align dependencies and ownership.
Review resolution: The blind reviewers agree that public_administration_policy is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
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.
Notes¶
The calendar coordinates timing but grants no authority: a slot on the schedule for a hard-to-reach or protected zone is inert until the Coordinated Access Protocol or the Sanctuary Reachability Audit establishes that the controller may be there. In other words, it consumes reach and legitimacy; it does not create them. A calendar that schedules actions no one is authorized to take is the paper form of the archetype's failure.
[n1] Area-wide integrated pest management treats an entire pest population across a whole area and season as the management unit — rather than field-by-field — precisely because untreated neighbors reseed treated fields. Synchronization across independent actors is its defining requirement and its most common point of failure, since a few defectors or a mistimed window restore the source–sink cycle the approach exists to break. ↩