Sanctuary Reachability Audit¶
Diagnostic audit — instantiates Sanctuary-Aware Source Control
Checks, source by source, whether the controller can actually reach and lawfully act there — and separates a genuine refuge that must be spared from a blind spot the target is exploiting as cover.
Knowing where the source is doesn't mean you can touch it. Sanctuary Reachability Audit examines, node by node, whether the controller actually has the reach and the authority to act on each source — physical access, legal right, seasonal window, political permission — and it forces a decision the campaign cannot skip: for every zone it cannot act in, is this a legitimate sanctuary that must be spared, or an authority gap the target is exploiting as cover? Its defining move is to keep "we can't reach it" and "we must not touch it" as two separate findings, because collapsing them is the archetype's central trap — either poisoning a genuine refuge in the name of thoroughness, or letting a source hide behind borrowed protection. The audit turns a vague sense of "the source is untouchable" into a mapped register of exactly why, so the campaign can route around what it must protect and find another way into what it may not.
Example¶
A regional program is trying to knock down feral cats that are eating out a native-bird population, across a patchwork of grazing leases, private smallholdings, and a national park. Where the source-mapping said the cats are breeding, the Sanctuary Reachability Audit asks whether anyone can act there. Parcel by parcel it scores access and authority: on the grazing leases, control is permitted; on several smallholdings, owners have refused entry (an authority gap); the national park is a protected sanctuary whose native wildlife the campaign exists to defend, so broad baiting there is off the table. Then comes the harder finding — cats are denning just inside the park boundary, using the protected zone as a refuge from the control happening all around it.
The audit's output is two ledgers, deliberately kept apart. A sanctuary map marks the park as legitimately spared, with the reason recorded. A reach-and-authority-gap register lists the refusing smallholdings and the park-edge denning as places the source persists for reasons of access, not biology — each tagged with what would close the gap (a negotiated entry agreement; a sanctuary-safe, targeted method at the boundary rather than area baiting). What the audit refuses to do is quietly turn "we can't get in" into "so it's fair game" — or let "it's protected" become an excuse to stop asking how the source there could be reached without harming what the park is for.
How it works¶
- Audit access and authority, not biology. For each source node, score the dimensions of reach — physical access, legal right, seasonal availability, jurisdiction, political consent — rather than the target's abundance.
- Force the spare-or-reach question. For every zone the controller cannot act in, classify it as a legitimate sanctuary to be spared and routed around, or an authority gap to be closed by other means.
- Demand evidence for each classification. A "sanctuary" claim needs independent grounds that the zone is a genuine refuge, not a target's cover story; a "gap" finding names what would close it.
- Keep two separate ledgers. Maintain the sanctuary map and the authority-gap register as distinct artifacts so unreachability is never silently upgraded into permission.
Tuning parameters¶
- Authority dimensions scored — how many facets of reach you assess (legal, physical, seasonal, jurisdictional, political). More dimensions catch subtler gaps but cost survey effort.
- Sparing strictness — how strong the evidence must be to grant protected-sanctuary status. Loose strictness rubber-stamps cover; over-strict strips protection from real refuges.
- Resolution — parcel-level versus zone-level. Finer resolution catches boundary-cover exploitation but multiplies the work.
- Refresh cadence — one-off versus re-audited as access agreements, ownership, or law change. A stale audit blesses reach that no longer exists.
- Escalation routing — whether a flagged authority gap is handed to a negotiation or access process, or merely logged. Logging without routing lets gaps sit open.
When it helps, and when it misleads¶
Its strength is that it names the true reason a source survives — usually reach, not biology — so effort stops being spent where the controller has no standing, and so the graver error of harming a legitimate refuge is caught before it happens. It is what lets a campaign be sanctuary-aware rather than either timid or indiscriminate.
Its failure mode is capture from both directions. A party that wants no control can dress an ordinary blind spot as a "sanctuary," and the audit becomes the instrument that legitimizes the target's refuge; conversely, an over-zealous campaign can reclassify a genuine refuge as mere "cover" to license a breach it had already decided on — the audit run backwards to justify entering a protected zone.[n1] The discipline that keeps it honest is to require independent evidence for every spare-or-breach call and to keep the sanctuary map and the authority-gap register as separate ledgers, so "we cannot reach it" can never quietly become "therefore we may."
How it implements the components¶
Sanctuary Reachability Audit realizes the reach-and-legitimacy side of the archetype — the components that decide where the controller may act and what it must protect:
reachability_and_authority_gap— its core deliverable: the per-node register of where physical reach or lawful authority is missing.sanctuary_zone_map— it produces and validates the demarcation of zones that must be spared, each with its recorded reason.legitimate_sanctuary_safeguard— it supplies the legitimacy judgment (genuine refuge versus exploited cover) on which any sparing rests.
It does not model which nodes are sources in the first place — that is the Source–Sink Network Mapping — nor does it build the operating procedure to obtain access and act across a boundary (the Coordinated Access Protocol), or run the recurring governance that adjudicates specific requests to enter a protected zone (the Protected-Zone Exception Review).
Related¶
- Instantiates: Sanctuary-Aware Source Control — the audit tells the campaign where it may act and what it must spare.
- Consumes: Source–Sink Network Mapping supplies the source nodes whose reachability this audit assesses.
- Sibling mechanisms: Source–Sink Network Mapping · Coordinated Access Protocol · Protected-Zone Exception Review · Sentinel Surveillance Dashboard · Synchronized Campaign Calendar · Rebound and Reseeding Stress Test · Source Reduction Program · Containment Barrier · Below-Replacement Confirmation Test · Cross-Boundary After-Action Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Sanctuary Reachability Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it checks, source by source, whether the controller can actually reach and lawfully act there — and separates a genuine refuge that must be spared from a blind spot the target is exploiting as cover.
Independent corroboration: The frozen evidence defines Sanctuary Reachability Audit as 'Checks, source by source, whether the controller can actually reach and lawfully act there — and separates a genuine refuge that must be spared from a blind spot the target is exploiting as cover', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Separating an unreachable target, a lawful military objective, and a protected refuge is an operational targeting audit constrained by humanitarian law. ICRC doctrine requires commanders to know protected-zone locations and loss-of-protection conditions, while Additional Protocol I limits attack to military objectives; law is therefore co-constitutive, not merely present-day applicability.
Related originating lineages:
- Law & Governance — Sanctuary Reachability Audit's terminology and operating form—checks, source by source, whether the controller can actually reach and lawfully act there — and separates a genuine refuge that must be spared from a blind spot the target is…—are rooted most directly in legal doctrine, regulatory governance, and procedural accountability.
- Political Science — political_science contributes a parallel disciplinary practice to the mechanism's formative or independently convergent form; that contribution does not displace the primary military_strategic_studies lineage.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: checks, source by source, whether the controller can actually reach and lawfully act there — and separates a genuine refuge that must be spared from a blind spot the target is….
- Security Studies & Intelligence Analysis — Intelligence analysis independently tests access, jurisdiction, and cover.
Review resolution: The blind reviewers disagreed on primary lineage (military_strategic_studies versus law_governance); authoritative or primary research supports military_strategic_studies as the best historical origin. Separating an unreachable target, a lawful military objective, and a protected refuge is an operational targeting audit constrained by humanitarian law. ICRC doctrine requires commanders to know protected-zone locations and loss-of-protection conditions, while Additional Protocol I limits attack to military objectives; law is therefore co-constitutive, not merely present-day applicability. The cited ICRC, Additional Protocol I Article 52; ICRC, Handbook on International Rules Governing Military Operations directly supports the defining operation used in that choice. All independently supported contributing domains are retained without an arbitrary cap, while domain_reach=specialized records later applicability separately from provenance.
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:
- ICRC, Additional Protocol I Article 52
- ICRC, Handbook on International Rules Governing Military Operations
Notes¶
The audit's whole value is in not merging its two findings. "Unreachable" is an operational fact to be worked around or closed; "protected" is a commitment to be honored. The archetype fails when a campaign treats an authority gap as though it were a sanctuary (and stops trying to reach a source it could have reached) or treats a sanctuary as though it were mere unreachability (and breaches a refuge it should have defended). This audit produces the evidence and the demarcation; it deliberately leaves the granting of any exception to the Protected-Zone Exception Review.
[n1] A refugium is a locality where a population persists through adverse conditions and from which it later recolonizes. In pest and resistance management a deliberately spared refuge preserves a wanted population — but an unmanaged or wrongly granted one becomes the reservoir that undoes control, which is why distinguishing a legitimate refuge from an exploited blind spot is a decision, not a formality. ↩