Red-Team Scoping Review¶
Challenge review — instantiates Boundary Reframing
Adversarially attacks a proposed scope to see whether the boundary survives challenge or was quietly drawn to fit someone's convenience.
A proposed boundary always comes wrapped in a justification, and the justification is usually written by the people who benefit from where the line was drawn. The Red-Team Scoping Review exists to attack that line before it hardens. It takes a proposed or provisional boundary and subjects it to deliberate adversarial pressure: it constructs rival framings, tests whether the proposed scope survives them, and probes whether the boundary tracks the real system or was gerrymandered to dodge cost, blame, or an inconvenient stakeholder. Its defining move is the counterframe test — the review does not merely question the boundary, it manufactures the strongest competing boundaries and forces the proposal to beat them. A special weapon is checking the boundary against authority: a scope drawn exactly to the edge of one team's mandate is often a scope drawn to make an externality someone else's problem.
Example¶
A city announces a "reduce downtown crime" initiative whose proposed scope is more police patrols in the central district, and it is about to be funded on that basis. A red-team scoping review is convened to attack the scope before the money moves. The team first states the proposed boundary plainly — the problem is defined as under-policing of downtown — then builds counterframes designed to break it. Counterframe one: the same data reframed as a lighting and vacant-storefront problem, where the causes are environmental. Counterframe two: a displacement frame, in which patrols simply push activity into adjacent neighborhoods, so the metric improves while the city gets worse. Counterframe three: a jobs and youth-hours frame locating causes months upstream of any patrol.
Then comes the authority probe, and it is the sharpest cut. The proposed boundary maps suspiciously neatly onto the police department's budget and mandate — which is exactly the scope that lets the initiative claim a win it can own while exporting the displaced activity to neighborhoods and the root causes to agencies with no seat. The review's finding is not a redesign; it is a verdict: the patrol boundary does not survive the displacement and authority challenges, and any funded version must at minimum measure adjacent-neighborhood effects and name who owns the causes that sit outside the police mandate. The proposal goes back with its convenient boundary exposed.
How it works¶
- State the proposed boundary as the thing under attack. The review pins down the scope being defended, along with the justification offered for it, so the challenge has a fixed target.
- Manufacture counterframes. Rather than raising objections, the team constructs the strongest rival boundaries — different causes, different scale, different beneficiaries — and argues them in earnest.
- Test survival against each. The proposed scope is judged on whether it still holds once each counterframe is taken seriously; a boundary that only wins by ignoring its rivals fails.
- Run the authority probe. The team checks whether the boundary coincides with an actor's mandate or budget in a way that conveniently exports cost or blame, treating a too-neat fit as a red flag rather than a coincidence.
Tuning parameters¶
- Adversarial intensity — how hard the team is licensed to attack. High intensity finds gerrymandered boundaries but can bruise the proposers and slide into obstruction.
- Counterframe count — how many rival boundaries are built. More is a sterner test but risks a review that generates frames faster than it can adjudicate them.
- Independence of the red team — how separated the reviewers are from the proposers. Full independence challenges freely; embedded reviewers know the context but pull punches.
- Authority-probe depth — how aggressively the boundary-versus-mandate fit is interrogated. Deep exposes blame-shifting but surfaces political conflict the sponsors may resent.
- Verdict bindingness — whether the review can block funding or only advise. Binding gives the challenge teeth but invites capture and appeals; advisory is safer but easier to ignore.
When it helps, and when it misleads¶
Its strength is catching strategic boundary manipulation — a scope drawn to shift blame, defer action, or exclude an inconvenient stakeholder — before it is funded and frozen. The authority probe in particular exposes the very common move of drawing the problem to the exact edge of one's own mandate. Its lineage is the red team and the older office of the devil's advocate[1], the advocatus diaboli once charged with arguing against a proposed canonization precisely so the case had to survive its strongest opposition.
Its failure mode is the review that becomes pure obstruction — a team that can defeat any boundary if pushed hard enough, so nothing is ever scoped well enough to proceed, and the challenge turns into an indefinite veto. The classic misuse is the captured red team: a review staged for legitimacy whose counterframes are strawmen the proposal was always going to beat. The guarding discipline is to require the red team to state, for each counterframe, what evidence would settle it, and to end in a bounded verdict — survives, fails, or survives-if — rather than an open-ended pile of doubts.
How it implements the components¶
current_boundary_description— it fixes the proposed boundary and its justification as the target of challenge.boundary_critique— it interrogates what the proposed scope conveniently excludes and exports.counterframe_test— its defining act: building rival boundaries and testing whether the proposal survives them.authority_constraint_statement— it probes whether the boundary was drawn to fit an actor's mandate or budget, exposing blame- and cost-shifting.
It does not redraw the boundary or produce a reframed_system_map — Problem Scope Reframing Workshop does — and it does not perform the constructive stakeholder_analysis of who is affected-but-absent the way Boundary Critique Workshop does.
Related¶
- Instantiates: Boundary Reframing — this is the adversarial diagnostic that tests whether a proposed boundary is defensible.
- Consumes: Problem Scope Reframing Workshop — the review typically attacks the boundary a workshop has just proposed, before it is committed.
- Sibling mechanisms: Problem Scope Reframing Workshop · Stakeholder-Inclusive Redesign · Environmental Impact Scoping · Lifecycle Assessment · Total Cost of Ownership Framing · Whole-System Problem Definition · Boundary Critique Workshop
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Red-Team Scoping Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it adversarially attacks a proposed scope to see whether the boundary survives challenge or was quietly drawn to fit someone's convenience.
Independent corroboration: The frozen evidence defines Red-Team Scoping Review as 'Adversarially attacks a proposed scope to see whether the boundary survives challenge or was quietly drawn to fit someone's convenience', 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: Multi-domain
Rationale: Adversarially attacking a convenient boundary follows red-team challenge practice, specialized through program-scope governance.
Related originating lineages:
- Organizational & Management Science — Project and decision governance materially shape authorized scope and stakeholder convenience risks.
- Security Studies & Intelligence Analysis — Red-team practice contributes protected attack on convenient assumptions.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of military_strategic_studies: Adversarially attacking a convenient boundary follows red-team challenge practice, specialized through program-scope governance. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
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:
References¶
[1] Burtsell, R. L. "Advocatus Diaboli". In The Catholic Encyclopedia, vol. 1. Robert Appleton Company (1907). Describes the Devil’s Advocate as an officer charged with advancing objections against beatification or canonization. registry ↩