Coordinated Access Protocol¶
Coordination protocol — instantiates Sanctuary-Aware Source Control
A standing agreement that lets one controller act on a source sitting inside another authority's domain, sequencing who may act where so source and sinks can be hit together.
A Coordinated Access Protocol is a standing, pre-negotiated agreement among the several authorities whose jurisdictions the source and its sinks straddle, granting a controller permission and a sequence to act across those boundaries — so the source is not left untouchable merely because it sits on someone else's land, network, or mandate. Its defining move is that it manufactures authority to reach, not the reach itself: where the source hides behind a jurisdictional seam, the protocol dissolves the seam by pre-arranging who may act where, in what order, with one accountable owner able to convene the parties. It is what makes a joint strike on source and sinks possible instead of an endless solo campaign at the one sink you already control.
Example¶
A city draws its drinking water from a river, but the nitrate and pesticide load originates on intensive farmland 80 km upstream, in a different county with its own environment agency, and the aquifer recharge zone between them is a protected sanctuary no one wants disturbed. Treating the water at the city's intake — the sink — is perpetual and expensive while the upstream source keeps loading. A Coordinated Access Protocol is negotiated ahead of any crisis: the upstream agency, the water utility, and the farm cooperative sign a standing agreement letting the utility's team enter and retrofit upstream drainage (buffer strips, controlled-drainage structures) under the county's authority, with sanctuary carve-outs around the recharge zone and a single named campaign owner empowered to convene all three. When a loading spike hits, the owner triggers a joint action that works the source upstream and the intake downstream in the same season — the strike the seam had previously made impossible.
How it works¶
The distinguishing logic is pre-authorized reach across a boundary, owned by one convener:
- Pre-negotiate, before the crisis. The permissions, the joint action set, and the sanctuary carve-outs are agreed in calm, not improvised when a window opens.
- Name one accountable owner with convening power. A single owner can compel the parties to the table and answers for the coordinated action; a protocol without one is inert paper.
- Encode who acts where, jointly. The agreement specifies the cross-boundary action on source and sinks together, and the order, so neither is left orphaned on the far side of a seam.
- Fence the sanctuaries explicitly. Protected zones are carved out of the access grant, with a separate exception route, so "coordination" cannot become a licence to overrun a refuge.
Tuning parameters¶
- Standing vs on-request — a permanent joint authority versus a case-by-case grant. Standing acts fast but concedes sovereignty; on-request preserves it but is slow when a window opens.
- Authority depth — observe-only, act-with-escort, or fully delegated action across the boundary.
- Convening power — how far the accountable owner can compel participation versus merely request it.
- Sanctuary carve-outs — which protected zones the grant explicitly excludes, and how exceptions to that are routed.
- Party breadth — the minimal coalition that actually closes the gap versus an inclusive one that is more legitimate but slower to move.
When it helps, and when it misleads¶
Its strength is that it turns an out-of-reach source into an actionable one and lets source and sinks be struck together, breaking the trap of forever mopping the sink you happen to own. Its failure modes are coordination overhead that can exceed the benefit, and a protocol that exists on paper but has no real accountable owner and so never converts into action. Its classic misuse is standing up an impressive multi-agency structure to appear to act on the source while the real work stays at the sink — or reaching into a legitimate sanctuary under colour of "coordination." The discipline that keeps it honest is a single accountable owner with a mandate and a clock, modelled on unified command,[n1] plus sanctuary carve-outs adjudicated separately rather than waved through in the name of cooperation.
How it implements the components¶
A protocol fills the cross-boundary coordination subset of the archetype's machinery, on the access side:
synchronized_source_and_sink_control_plan— its core output: the agreed set of who-acts-where-across-which-boundary, so source and sinks are addressed jointly rather than in isolation.accountable_campaign_owner— it names the single owner empowered to convene the authorities and answerable for the coordinated action.
It does not measure the authority gap it closes (reachability_and_authority_gap — Sanctuary Reachability Audit), schedule the actions in calendar time (intervention_window — Synchronized Campaign Calendar), or actually suppress the source once access exists (source_suppression_or_conversion_path — Source Reduction Program).
Related¶
- Instantiates: Sanctuary-Aware Source Control — it supplies the cross-boundary authority the campaign needs to reach an otherwise-untouchable source.
- Consumes: Sanctuary Reachability Audit — the audit's gap map tells the protocol exactly which authority seams it must bridge.
- Sibling mechanisms: Sanctuary Reachability Audit · Synchronized Campaign Calendar · Source Reduction Program · Containment Barrier · Below-Replacement Confirmation Test · Cross-Boundary After-Action Review · Protected-Zone Exception Review · Rebound and Reseeding Stress Test · Sentinel Surveillance Dashboard · Source–Sink Network Mapping
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Coordinated Access Protocol operates as a repeatable ordered procedure or handoff sequence that coordinates action because it a standing agreement that lets one controller act on a source sitting inside another authority's domain, sequencing who may act where so source and sinks can be hit together.
Independent corroboration: The frozen evidence defines Coordinated Access Protocol as 'A standing agreement that lets one controller act on a source sitting inside another authority's domain, sequencing who may act where so source and sinks can be hit together', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Incident Command System practice established Unified Command for coordinated action across separately held jurisdictions.
Related originating lineages:
- Law & Governance — Standing agreements and delegated authorities provide the enforceable basis for cross-jurisdiction access.
- Public Administration & Policy — Interagency public-administration practice supplies jurisdictional coordination and resource-request procedures.
Review resolution: The source-control, receiving-control, and unified coordination pattern is most directly recognizable in emergency and incident management. Law and public administration supply standing authority and interagency procedure; the generalized source/sink formulation is synthetic.
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¶
The protocol grants the right to act, not the act itself, and its most common failure is being mistaken for progress. Twin it with a calendar that schedules real source-side action and a clock on the accountable owner, or a coordinating body decays into a standing committee that meets while the source runs on.
[n1] Unified Command is a feature of the Incident Command System in which several agencies that each hold jurisdiction over an incident act under a single coordinated command structure with shared objectives, rather than issuing separate and possibly conflicting orders. It is the established model for precisely the problem this protocol addresses — multiple authorities needing to act together across a boundary under one accountable structure. ↩