Topic · Critical design review

What is a critical design review, and how do I keep it true in CI?

Gist

A critical design review is a NASA lifecycle gate: is the detailed design ready to build. Proof assesses that gate from the current graph with proof gate cdr, then fails the merge when a criterion is not ready.

proof gate cdr

Keep Jama if you author the programme. Keep the review board if a human has to accept the drawings. Proof is not that meeting, and last month's CDR pack is not this push.

Request demo Last pack vs this graph

01 · The dated pack

A procedure PDF is not a CDR. Last review's pack is not this push.

The review board looks at the build-to baseline, the drawings, and remaining risk. A person can sign that once. The next commit does not reopen the room.

The architecture gate lives on preliminary design review. The test gate lives on test readiness review. The SAS pack lives on software accomplishment summary. This page is the detailed-design gate: code annotated, autolink clean, annotations valid, the build, orphan code.

CDR does not invent a drawing you did not write. It does not sit in the review. It does not fabricate hardware. Keep go build.

go build ./...
proof gate cdr
proof audit --fail-level warn

The first command is still the compile. The second assesses the CDR criteria and exits 0 (ready), 1 (not ready), or 2 (ready with observations). The third is the standing merge gate. Printing last review's pack after the gate is how the minutes got stale.

02 · The exhibit

Same agenda. A date, or this graph.

The pack still has annotation headings. The graph moved. Click the tabs.

Word / Confluence

Opened annotations from last CDR
rate_limiter still linked in the pack

Agenda present

This push

A function lost its SYS-REQ comment. The pack did not.

No re-assess

Word / Confluence

Still last CDR. Still a date.

Keep the review minutes

Proof

Ask does cdr still pass
Exit 1 if a criterion fails

Merge blocked if the gate is not ready

Same agenda. A date, or this graph. Click the tabs.

Criterion	What the graph asks	What a green cell is not
Code annotated	`lint_clean`	Not a drawing review. Keep the board.
Autolink clean	`autolink_clean`	Not a rewrite of the authored YAML.
Annotations valid	`annotation_validity`	Not a frozen ID list in Jama.
Build passes	`build_passes`	Not fabrication readiness. Keep `go build`.
Orphan code clean	`orphan_code_clean`	Not compiler dead-code analysis. Not overlay_audit.

Formats for the assessment itself:

proof gate cdr
proof gate cdr --format json
proof gate cdr --format markdown

Table is the default. JSON is for CI. Markdown is for a comment. CDR does not write a SAS. That pack is only proof gate sar --output sas.html on software accomplishment summary.

We have not run these gates against a frozen NASA review-board corpus, and we have not scored them against a DER pack on the same branch. The loss is named, not scored.

03 · The honest loss

A green Proof gate is not a critical design review.

The command reports criteria on the authored model. Proof will not pretend that exit 0 is a board signature.

NPR 7150.2D still wants a human to judge whether the detailed design is ready to proceed into fabrication, demonstration, and test. The gate lists what you declared: annotations, autolink, annotation validity, the build, orphan code. It does not independently prove those declarations are the right drawings. Keep the CDR. Keep the minutes.

Proof is not NASA. It is not OSMA IV&V. It is not DO-330 qualified. It is not a mechanical CDR. It is not a physical configuration audit. The build is not executed by proof gate cdr. Keep go build. Jama still authors the shall. VectorCAST or LDRA still win at a qualified C toolchain.

The architecture gate still lives on preliminary design review. The test gate still lives on test readiness review. The NASA SRS still lives on NPR 7150.2D. The four jobs still live on DO-178C-style verification.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a preliminary design review? PDR is architecture and interfaces before detailed design. That H1 lives on preliminary design review as proof gate pdr.

What is a system requirements review? SRR is the first gate. proof gate srr. Lives with PDR until it earns its own H1.

What is a test readiness review? TRR is the test gate. That H1 lives on test readiness review as proof gate trr.

What is a software accomplishment summary? The SAR pack. That H1 lives on software accomplishment summary as proof gate sar --output sas.html.

Is Proof an alternative to a CDR board? No. The board still signs. Proof re-assesses the graph you already keep. Jama still authors.

What is NPR 7150.2D? NASA's software engineering procedure. The SRS artefact lives on that URL. This page is the detailed-design gate, not a twin.