Review-Remand-not-Replace Protocol¶
Procedure — instantiates Final Override Prevention
Lets a reviewer affirm a decision or send it back for reconsideration, but never swap in its own outcome — remand, not replace.
A Review-Remand-not-Replace Protocol is the workflow that lets an outside reviewer scrutinize a decision without becoming its author. Its defining constraint is the menu of permitted dispositions: the reviewer may affirm or remand — send the decision back to the original holder with instructions to reconsider — but "reverse and enter our own outcome" is simply not an available move. This is what lets genuine accountability coexist with sovereignty: the reviewer can catch a real error of process, legality, or standard, yet the last word always returns to the holder, who re-decides and keeps control of implementation. It is the operating counterpart to a written non-substitution rule — the rule declares the review/replace line, this protocol runs it as a live procedure.
Example¶
A trial court holds final authority over fact-finding in a case; a losing party appeals. Under a remand-not-replace protocol the appellate panel reviews the record deferentially — for legal error and abuse of discretion, not to re-weigh the facts to its own taste. The panel concludes the trial judge applied the wrong legal standard to a discretionary ruling. Instead of substituting its own verdict, it vacates and remands: "reconsider under the correct standard." Back below, the trial judge — now applying the right test — re-decides, and reaches a defensible result that stands. Review happened; a real error was corrected; yet no outside body ever imposed its own answer inside the domain. Had this been de novo review, the panel could have simply entered the outcome it preferred — which is replacement, exactly what this protocol forbids.
How it works¶
- Define reviewable grounds narrowly. Process, legality, boundary, and standard-of-review questions are in scope; the merits and the reviewer's own preference are not.
- Set the two permitted dispositions. Affirm, or remand-with-instructions. There is no third exit that lets the reviewer author the outcome.
- Route remands back to the holder. The original holder re-decides and retains the implementation pathway; the reviewer never seizes execution.
- Cap the loops. Bound how many remands may occur before finality attaches, so review cannot be used as attrition against a holder who won't yield the "right" answer.
The distinguishing feature is that the reviewer's power stops at reconsider, never reaching here is the new decision.
Tuning parameters¶
- Standard of review — deferential (abuse-of-discretion) vs. searching. More deference protects sovereignty; too much rubber-stamps.
- Reviewable grounds — narrow (legality, process) vs. broad (reasonableness). Broader catches more error but drifts toward reviewing the merits.
- Remand specificity — open ("reconsider") vs. directive ("reconsider, and you must weigh X and reach Y"). Directive remands verge on covert substitution.
- Loop cap — how many remands before finality attaches. Fewer means faster finality but a risk of leaving genuine error unresolved.
- Who re-decides — the same holder vs. a fresh panel inside the domain. A fresh panel guards against entrenchment but dilutes the original holder's authority.
When it helps, and when it misleads¶
Its strength is that it squares accountability with sovereignty: a reviewer can correct real error without becoming the decider, which is the direct antidote to "appeal used as disguised override." Its failure mode is the directive remand that is substitution in disguise[n1] — "reconsider, but the only acceptable answer is ours" leaves the holder no genuine choice. The classic misuse is the endless remand loop, weaponized to grind a holder into compliance by making them re-decide until they surrender. The guarding discipline is to keep remand instructions about the standard or process, never the outcome, and to cap the loops so finality eventually attaches.
How it implements the components¶
review_without_substitution_interface— its essence: a channel for outside scrutiny whose only outputs are affirm or remand, never a substituted outcome.implementation_control_pathway— after re-decision the holder carries out the result; the reviewer cannot take over execution.final_decision_holder— remands return to the original holder, protecting its last word.
It does NOT adjudicate whether an extraordinary exception may lift the bar entirely — that evidentiary judgment is the Exception Justification Hearing, its nearest twin; this protocol governs ordinary review (remand, never replace), while the hearing decides whether an override is legitimately permitted at all.
Related¶
- Instantiates: Final Override Prevention — the protocol operationalizes the review-versus-replacement line at the heart of the archetype.
- Consumes: Non-Substitution Clause supplies the declared review/replace boundary this procedure enforces in practice.
- Sibling mechanisms: Non-Substitution Clause · Finality and Scope Register · Consent or Supermajority Exception Gate · Hard Access Partition · Override Attempt Log · Anti-Retaliation and Remedy Pathway · Exception Justification Hearing
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Review-Remand-not-Replace Protocol operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it lets a reviewer affirm a decision or send it back for reconsideration, but never swap in its own outcome — remand, not replace.
Independent corroboration: The frozen evidence defines Review-Remand-not-Replace Protocol as 'Lets a reviewer affirm a decision or send it back for reconsideration, but never swap in its own outcome — remand, not replace', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Protocol, Workflow & Routine — Review-Remand-not-Replace Protocol includes features of a repeatable ordered procedure or handoff sequence that coordinates action, 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: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Appellate remand that preserves the original decision-maker's role is a canonical legal review doctrine.
Related originating lineages:
- Public Administration & Policy — Administrative review materially applies remand boundaries to agency decisions.
Review resolution: Both blind reviewers agree that law_governance is the primary historical origin. Explicit reconciliation of domain reach disagreement starts from reviewer_a’s mechanism-specific evidence: Appellate remand that preserves the original decision-maker's role is a canonical legal review doctrine. Reviewer A proposed alternates=public_administration_policy, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=public_administration_policy, origin_mode=single_lineage, domain_reach=specialized, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (public_administration_policy) without an arbitrary cap, selects origin_mode=single_lineage to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=false from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Standard of review and remand — deferential appellate practice returns a flawed decision to the original decider for reconsideration rather than substituting the reviewer's own judgment. A remand that dictates the outcome collapses the very distinction the protocol exists to preserve. ↩