Cross-Boundary After-Action Review¶
Retrospective ritual — instantiates Sanctuary-Aware Source Control
A structured retrospective over a campaign that spanned several authorities, deciding what to restore, when to exit, and how to respond if the source rebounds.
A Cross-Boundary After-Action Review is a facilitated retrospective, held after a control campaign that crossed jurisdictional or organizational boundaries, that reconstructs what actually happened across all the parties and converts it into two forward artifacts: a plan to restore the treated ground and exit responsibly, and a contingency plan for if the source comes back. Its defining move is that it treats the whole cross-boundary campaign as one story — surfacing the seams where hand-offs failed and the source slipped between authorities — rather than letting each party review only its own patch. It is where a campaign decides it is done enough to leave, and what leaving responsibly requires.
Example¶
An 18-month campaign has cut elephant poaching across a national park and the adjacent community land — two authorities, park rangers and community rangers, with a jurisdictional seam between them. At the closing Cross-Boundary After-Action Review, both parties reconstruct a single shared timeline and find the decisive failures all sat at the seam: poachers staged on community land, outside park-ranger authority, in the gaps between park patrols. Out of that come two artifacts. A restoration-and-exit plan draws down the surge patrols, hands routine monitoring back to community rangers, and restores the snare-damaged corridors. A relapse plan names the specific trigger — a cluster of fresh snare finds at the seam — that re-activates a joint surge, and says who is authorized to call it. The review's value was seeing the seam at all, which neither party could from inside its own boundary.
How it works¶
The distinguishing logic is one shared cross-boundary reconstruction, aimed at the seams:
- Convene every party that touched the campaign. The point is the boundaries, so a review missing an authority misses exactly the hand-offs that matter.
- Reconstruct one timeline from records. A single shared sequence built from logs, not from each party's memory, is what exposes where the source slipped between mandates.
- Locate the seam failures specifically. Attention goes to the inter-authority gaps rather than to any one party's internal performance.
- Produce two forward plans. The review's output is not a report but an exit-and-restoration plan and a rebound contingency plan, each with named owners.
Tuning parameters¶
- Party inclusion — every authority that touched the campaign versus a core few. Broader surfaces more seam failures but is harder to convene honestly.
- Blame posture — blameless learning versus attribution. A punitive tone buys silence and kills exactly the candid seam findings the review exists for.
- Exit aggressiveness — how fast to draw down. A fast exit frees resources but risks rebound before the source is truly below replacement.
- Trigger sensitivity — how twitchy the relapse plan's re-activation signals are. Sensitive triggers catch rebound early but at the cost of false surges.
- Cadence — one closing review versus periodic reviews staged through a phased exit.
When it helps, and when it misleads¶
Its strength is that it captures the cross-boundary lessons no single party can see, and it turns exit into a deliberate, planned act with a rebound safety net rather than a drift into neglect. Its failure modes are that memory is reconstructive and self-serving — especially across parties with divergent incentives — and that a review with no owner produces a document nobody executes. Its classic misuse is running it as blame-assignment, each authority pinning the seam failures on the others, which buys silence and destroys the very cross-boundary honesty the review depends on; a close cousin is convening it only to ratify an exit already decided. The discipline that keeps it honest is a blameless posture,[n1] a timeline built from records rather than recollection, and a named owner on every action in both plans.
How it implements the components¶
A retrospective ritual fills the learning-and-close-out subset of the archetype's machinery:
restoration_and_exit_plan— its primary product: the sequenced draw-down, hand-back, and restoration that lets the campaign leave the ground in good order.relapse_or_rebound_plan— the contingency it writes from the failure modes it just observed: the trigger signals, the re-activation steps, and who owns the call if the source returns.
It does not proactively stress-test rebound scenarios before the fact (source_sink_reseeding_model — Rebound and Reseeding Stress Test), confirm the source is actually below replacement (Below-Replacement Confirmation Test), or monitor for the return signals it defines (recurrence_monitor — Sentinel Surveillance Dashboard).
Related¶
- Instantiates: Sanctuary-Aware Source Control — it closes the loop, turning a finished campaign into a safe exit and a rebound safeguard.
- Consumes: Sentinel Surveillance Dashboard — the recurrence record and campaign data it reconstructs the shared timeline from.
- Sibling mechanisms: Rebound and Reseeding Stress Test · Below-Replacement Confirmation Test · Source Reduction Program · Containment Barrier · Coordinated Access Protocol · Protected-Zone Exception Review · Sanctuary Reachability Audit · Sentinel Surveillance Dashboard · Source–Sink Network Mapping · Synchronized Campaign Calendar
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Cross-Boundary After-Action Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a structured retrospective over a campaign that spanned several authorities, deciding what to restore, when to exit, and how to respond if the source rebounds.
Independent corroboration: The frozen evidence defines Cross-Boundary After-Action Review as 'A structured retrospective over a campaign that spanned several authorities, deciding what to restore, when to exit, and how to respond if the source rebounds', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: The facilitated reconstruction of intent, events, results, and lessons originates in military after-action review, with material adaptations in emergency management, public administration, and computing.
Related originating lineages:
- Computer Science & Software Engineering — Site-reliability and software postmortems independently adapted blameless incident learning.
- Disaster Management & Risk Reduction — Emergency-management doctrine adapted after-action reviews for multiagency incidents.
- Public Administration & Policy — Public-sector continuous-improvement programs formalize findings, owners, and corrective actions.
Review resolution: The facilitated reconstruction of intent, events, results, and lessons originates in military after-action review, with material adaptations in emergency management, public administration, and computing.
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 review's two plans are only as good as their owners: a restoration-and-exit plan without a funded owner becomes abandonment, and a relapse plan no one monitors is a document rather than a safeguard. The review should end by assigning both to standing owners with live triggers, not by filing a report.
[n1] A blameless postmortem is a retrospective run on the premise that people acted reasonably given what they knew at the time, so the review can surface systemic and process failures without participants concealing them to avoid blame. Popularized in site-reliability and incident-response practice, it is the standard corrective to the after-action review's classic failure mode — degenerating into attribution, which suppresses exactly the candid, cross-party detail the review exists to capture. ↩