Go/No-Go Condition Review¶
Ritual — instantiates Necessary-Condition Closure Design
Reviews each hard condition independently before proceeding with a high-consequence action.
A Go/No-Go Condition Review is a convened decision ritual in which each hard condition is called and adjudicated independently — one owner at a time attests to their condition, and a single "no-go" holds the action regardless of how strong every other condition is. Its identity is the non-averaging poll: it deliberately refuses any composite verdict, treating success as a strict conjunction so that no amount of readiness elsewhere can outvote one owner's "not ready." It is a judgment event — people decide, out loud, on the record — not a document or a dashboard.
Example¶
Minutes before a rocket launch, the flight director runs the go/no-go poll. Each console is called by name — propulsion, guidance, range safety, weather, flight dynamics, recovery — and each gives a crisp "go" or "no-go" for its own condition only. Everything is "go" except weather, which reports a violated upper-level wind constraint: "no-go." No tally is taken; there is no "seven of eight, launch." The single no-go holds the count. The director's options are exactly the archetype's blocker moves — hold and wait for the condition to clear, or scrub. The launch waits. This poll structure is the essence of launch-commit criteria[1] — pre-agreed conditions, each owned, each carrying a veto.
How it works¶
Pre-declare the hard conditions and assign each to a single accountable owner. Convene at the decision point and poll owners one by one, requiring an explicit go or no-go per condition with no averaging or trading between them. Any no-go blocks and routes to a decision — hold, repair, scrub, or accept the risk under a named authority. The ritual's power lives in two features the archetype prizes: the independent veto, and the on-the-record ownership of each call.
Tuning parameters¶
- Veto strength — a hard single-veto versus a senior authority who may override a no-go with explicit, recorded risk-acceptance. Absolute veto is safest; override preserves agility at the cost of gate integrity.
- Poll independence — owners calling in sequence blind to each other versus calling after open discussion. Blind calls fight conformity pressure; discussion catches condition interactions.
- Quorum — which conditions must be personally attested versus delegated. Broader personal attestation raises accountability but slows the poll.
- Re-poll trigger — whether a late change forces a fresh poll of all conditions or only the affected one.
When it helps, and when it misleads¶
Its strength is that it makes ownership and veto explicit at the exact moment of commitment, and its independent poll is the strongest social defense against aggregate-readiness masking. Its failure mode is that it can curdle into theater if owners feel pressure to call "go" to avoid being the one who scrubs — a launch-fever conformity — or if no-go authority is quietly undermined by routine override. It is also episodic, so it only protects the moment it is run. The guarding discipline is to protect the cost-free "no-go," to poll independently before any group discussion, and to log every override as a risk-acceptance that gets reviewed afterward rather than forgotten.
How it implements the components¶
non_substitutability_test— the refuse-to-average, single-veto structure operationally enforces that each condition is non-substitutable: strength elsewhere cannot buy out a no-go.condition_owner_map— the poll is by owner; every hard condition has a named person who alone may call it.blocker_decision_rule— a no-go routes to the archetype's closure moves (hold / repair / scrub / explicit risk-acceptance) at the moment of decision.
It does not re-verify the freshness of each condition's evidence (condition_evidence_record) or run a last-minute probe (rehearsal_or_probe) against the full list (necessary_condition_set) — that time-sensitive final sweep is its ritual twin Preflight Review; this review instead adjudicates each condition's veto independently through its named owner.
Related¶
- Instantiates: Necessary-Condition Closure Design — it is the moment-of-commitment decision form of the gate.
- Consumes: Readiness Gate Scorecard without Averaging supplies the per-condition status the poll is run against.
- Sibling mechanisms: All-Conditions Checklist · Blocker Register · Condition Coverage Test Suite · Dependency Closure Map · Limiting-Factor Board · Preflight Review · Readiness Gate Scorecard without Averaging · Red-Team Precondition Challenge · Weakest-Link Postmortem
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: The review makes a bounded proceed-or-stop disposition for a high-consequence action after each hard condition is considered independently.
Nearest alternative: Assessment, Review & Assurance — Condition checks supply findings, but the operative output is the go-or-no-go authorization.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Launch commit criteria require independent clearance of every hard condition before commitment.
Related originating lineages:
- Engineering & Design — Safety engineering generalizes independent mandatory-condition review across hazardous operations.
Review outcome: Independent reviewer agreement; high confidence.
References¶
[1] National Aeronautics and Space Administration. Launch Services Program Pre-Launch Readiness Reviews. NPD 8610.24C (effective 2005; revalidated 2025). Identifies the final commit-to-launch poll as the launch-commit criteria structure. registry ↩