Go/No-Go Review Gate¶
Decision gate — instantiates Operational Context Validation Testing
A pre-declared decision forum that weighs accumulated field evidence against stop/go criteria and authorizes, scopes, or halts the rollout.
A Go/No-Go Review Gate is the governance checkpoint where all the validation evidence gathered so far is brought together and a bounded decision is made: proceed, hold, contain, or stop. Its defining idea is aggregation and authority — it produces no new field evidence of its own; it consumes the outputs of every other mechanism (acceptance results, shadow deltas, canary metrics, observation logs) and applies criteria fixed in advance to a single, accountable decision. Crucially, it decides not just whether to proceed but how far — it declares the scope the decision covers, so a "go" for one site, load level, or population is never silently read as a go for all of them. The gate is where evidence stops accumulating and a person or board owns the call.
Example¶
A national tax agency is about to switch on a new online-filing system for the whole country. Every upstream mechanism has run: the acceptance tests passed, a shadow trial processed a season of real returns silently, a canary opened filing to one region, and observers logged how agents actually used the new case tool. On the eve of national launch, a Go/No-Go Review Gate convenes — the program owner, operations, security, and an independent reviewer — against criteria agreed months earlier: defect severity ceilings, a maximum acceptable canary error rate, a signed security review, and a rollback confirmed ready. The board reviews the consolidated delta log and finds most criteria green, but the canary's peak-hour latency sat just over threshold and a data-migration edge case is unresolved. The decision is not a binary launch: it is go for the six regions already piloted, no-go for the two highest-volume regions until the latency fix ships — an authorized, explicitly scoped rollout rather than an all-or-nothing gamble.
How it works¶
- Fix the criteria before the evidence. Go, no-go, contain, and stop conditions are agreed in advance, so the decision is a comparison against a standard rather than a negotiation under launch pressure.
- Consolidate the evidence. The gate pulls together the results of the upstream mechanisms into one reviewable picture — the running delta log of where field behavior met or missed expectations.
- Decide with accountable authority. A named person or board owns the call, including the option to stop or contain, insulated from the momentum of the people who built the thing.
- Scope the decision. The output declares where the go applies — which sites, loads, and populations — and where it explicitly does not, so approval never over-generalizes.
Tuning parameters¶
- Criteria strictness — how demanding the go conditions are. Strict criteria catch more risk but delay or block launches on marginal evidence; lenient ones ship faster and let weak evidence through.
- Reviewer independence — decided by the delivery team or by an independent board. Independence resists optimism bias but adds cost and can slow decisions.
- Evidence completeness bar — how much of the validation suite must report before the gate convenes. A high bar is thorough but slow; a low bar decides on partial information.
- Decision granularity — a single binary launch, or a scoped, staged authorization. Finer granularity matches exposure to evidence but is more complex to govern.
- Re-review cadence — one-shot gate, or a recurring gate as staged rollout proceeds. Recurring gates catch late-emerging problems but demand sustained governance attention.
When it helps, and when it misleads¶
Its strength is that it forces the launch decision to be explicit, accountable, and scoped — converting a diffuse sense that "we're probably ready" into a criteria-checked call with a named owner and a stated boundary, which is what makes stopping or containing socially possible. Its most dangerous failure mode is the normalization of deviance: when evidence repeatedly falls just short and is repeatedly waved through, the out-of-spec becomes the accepted baseline, and the gate hardens into a rubber stamp that launders schedule pressure as approval.[n1] The classic misuse is a gate convened only to bless a decision already made. The guarding discipline is to treat every criterion breach as requiring an explicit, recorded waiver by an accountable authority — never a silent pass — and to keep an independent voice with real standing to say no.
How it implements the components¶
A Go/No-Go Review Gate fills the aggregate-and-authorize slice of the archetype:
acceptance_stop_and_escalation_criteria— it applies the pre-declared go / hold / contain / stop conditions that turn evidence into a decision.context_transfer_boundary— its output explicitly scopes where the decision applies, so a go for the tested conditions is not read as a go beyond them.lab_to_field_delta_log— it reviews the consolidated record of where field behavior met or diverged from expectations as the basis for the call.
It does not implement requirement_behavior_trace — the gate generates no per-requirement field evidence of its own; it weighs evidence others produced. That contractual, per-requirement sign-off in the real environment is the Field Acceptance Test's job.
Related¶
- Instantiates: Operational Context Validation Testing — the decision node where accumulated context evidence becomes an accountable, scoped rollout choice.
- Consumes: Field Acceptance Test, Shadow-Mode Trial, Canary or Limited Rollout, and Workflow Observation Log — their results are the evidence the gate weighs.
- Sibling mechanisms: Field Acceptance Test · Shadow-Mode Trial · Canary or Limited Rollout · Production-Like Testbed · Operational Scenario Rehearsal · Environmental Stress Run · Workflow Observation Log
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Go/No-Go Review Gate operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a pre-declared decision forum that weighs accumulated field evidence against stop/go criteria and authorizes, scopes, or halts the rollout.
Independent corroboration: The frozen evidence defines Go/No-Go Review Gate as 'A pre-declared decision forum that weighs accumulated field evidence against stop/go criteria and authorizes, scopes, or halts the rollout', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Stage-gate and deployment-readiness reviews in systems engineering weigh accumulated evidence against declared criteria.
Related originating lineages:
- Aviation & Aeronautics — Flight-review practice supplies the go, hold, and no-go vocabulary.
Review resolution: Both reviewers agree that engineering_design is primary: Stage-gate and deployment-readiness reviews in systems engineering weigh accumulated evidence against declared criteria. I retain aviation_aeronautics only as formative lineage, not as a list of later applications. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
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] Normalization of deviance, a term from Diane Vaughan's analysis of the Challenger launch decision, describes how repeated acceptance of out-of-specification results gradually redefines them as normal, eroding a decision gate's protective function until the once-unacceptable is routinely approved. ↩