Policy Pilot Reintegration Review¶
Procedure — instantiates Branching and Merging
Reviews locally piloted rules or practices and decides which elements should be merged into the general policy baseline.
A policy pilot is a branch made of rules rather than code: one site, cohort, or jurisdiction is authorized to depart from the standard policy, try a variant under real conditions, and generate evidence — and the reintegration review is the governed act of folding what worked back into the baseline. Its defining idea is that it treats a pilot as a time-boxed, scoped divergence that must earn its way into the general rule on evidence, not as a permanent local exception nor an automatic promotion. The procedure sets, up front, exactly what may vary, where, for how long, and what result would justify making the variant standard for everyone. It is the branch-and-merge archetype rendered in the language of governance: scope the departure, bound its duration, define the evidence bar, then decide what merges.
Example¶
A national parks agency wants to reduce trailhead congestion. Rather than change the reservation rule for all 400 sites at once, it authorizes a pilot at eight high-traffic parks: those sites may replace first-come parking with a timed-entry reservation — the scope is fixed at eight named parks and the reservation rule alone, so rangers know precisely what they may and may not alter. The pilot runs one season; that lifetime is set in advance so it cannot quietly become the permanent local arrangement.
At season's end the reintegration review convenes. The merge criterion was declared beforehand: adopt system-wide only if congestion drops materially without cutting total visitation. Six pilot sites cleared the bar; two did not, and the review finds both were low-traffic parks where the rule added friction for no gain. So the general policy is amended to make timed entry the standard for high-traffic trailheads only — a partial merge — and the low-traffic finding is fed back as a scoping refinement rather than discarded.
How it works¶
- Scope the departure explicitly. Name which units diverge and which rule may change, so the pilot is a bounded branch, not an open license to improvise.
- Constrain the divergence. Specify what pilots may and may not vary (and what must stay fixed for comparability), keeping results interpretable against the baseline.
- Pre-declare the merge bar. Fix the evidence that would justify generalizing before anyone is invested, so reintegration turns on results rather than advocacy.
- Time-box and then decide. A set pilot lifetime forces a merge / amend / retire decision, preventing indefinite parallel policy regimes.
Tuning parameters¶
- Pilot breadth — how many and how varied the pilot sites are. Wider pilots generalize more safely but cost more and expose more people to an unproven rule.
- Divergence latitude — how much local variation is permitted. More latitude surfaces creative adaptations but muddies comparison to the baseline.
- Evidence bar height — how strong the result must be to merge. A high bar guards the general policy from noise but may reject genuinely good local rules.
- Pilot lifetime — long enough for real effects, short enough to avoid a de facto permanent split. The central branch-lifetime tradeoff, in policy form.
- Merge granularity — all-or-nothing adoption vs. conditional merge (as with "high-traffic sites only"). Finer granularity fits reality better but complicates the rulebook.
When it helps, and when it misleads¶
Its strength is that it lets a large system adapt locally without fragmenting into a patchwork of permanent exceptions: divergence is deliberate, bounded, and reversible, and only evidence — not the loudest region — decides what becomes standard. Its failure mode is the pilot that succeeds because it is a pilot. Extra attention, hand-picked staff, and the mere fact of being watched inflate results — the Hawthorne effect[n1] — so a variant shines under pilot conditions and disappoints once it is the boring default everywhere. A classic misuse is policy-based evidence: running a pilot to ratify a decision already made, with a bar quietly set where the favored variant will clear it. The guarding discipline is to fix the merge criterion and comparison group before the pilot starts, and to treat generalization as a claim about external validity — will this hold at ordinary sites, on ordinary days, without the spotlight — rather than a reward for a good season.
How it implements the components¶
This procedure supplies the scoping, constraint, criterion, and time-box components; it leaves conflict resolution and validation machinery to others:
branch_scope— defines which units and which rule are allowed to diverge, bounding the pilot as a reviewable branch.divergence_rule— specifies what a pilot may and may not vary while separate, keeping results comparable to the baseline.merge_rule— the pre-declared evidence bar that determines which pilot elements are folded into the general policy.branch_lifetime_limit— a fixed pilot duration that forces a merge / amend / retire decision rather than an indefinite local regime.
It does not adjudicate incompatible obligations between drafts — conflict_resolution_rule belongs to Negotiation Redline Merge — nor does it run the coherence check (integration_test, from Integration Test Suite) or hold the approval record (provenance_trace, from Pull Request or Merge Request).
Related¶
- Instantiates: Branching and Merging — governed local divergence reintegrated into a shared policy baseline.
- Sibling mechanisms: Version-Control Branching Workflow · Pull Request or Merge Request · Integration Test Suite · Collaborative Draft Merge Workflow · Design Variant Merge Review · Negotiation Redline Merge · Merge Conflict Board
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Policy Pilot Reintegration Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it reviews locally piloted rules or practices and decides which elements should be merged into the general policy baseline.
Independent corroboration: The frozen evidence defines Policy Pilot Reintegration Review as 'Reviews locally piloted rules or practices and decides which elements should be merged into the general policy baseline', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Policy Pilot Reintegration Review includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Reintegrating locally tested rules into a general baseline is an adaptive public-administration practice.
Related originating lineages:
- Computer Science & Software Engineering — Its explicit branching-and-merging framing is borrowed from software version-control practice.
- Organizational & Management Science — The mechanism's review and institutionalization cadence draws on organizational learning.
Review resolution: Both blind reviewers agree that public administration policy is the primary origin. Reconciliation resolves alternate origin disagreement. Formative alternate lineages are retained as computer_science, organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The Hawthorne effect is the tendency of people to change their behavior — usually to perform better — because they know they are being observed, named for productivity studies at the Hawthorne Works. It is why a piloted policy can outperform under scrutiny and regress once it becomes the unremarked default, and why external validity, not pilot success, is the real merge question. ↩