Assumptions
- Case identity, owner, date, and revision are recorded.
- Units and source of each major assumption are visible.
- Known uncertainties and open questions are listed.
Review resource
Pressure-fed design review checklist.
A safe, workflow-oriented checklist for preparing review artifacts. It focuses on assumptions, documentation, exports, and follow-up review rather than construction instructions.
Checklist
Use this before a design review.
Propellant basis
- Propellant selection and thermochemistry basis are documented.
- Any comparison source or backend context is noted.
- Unsupported combinations are not presented as validated.
Chamber targets
- Primary sizing basis is clear.
- Warnings and margins are preserved with the case.
- Reviewers can see requested versus actual solved context where relevant.
Injector basis
- Pattern, pressure-drop basis, and O/F consistency notes are captured.
- Drill-chart or export context is tied to the solved case.
- Open manufacturing or test questions are listed separately.
Nozzle basis
- Contour type and geometry export basis are visible.
- DXF handoff is linked to the same solved case used in the report.
- Known limitations and review needs are listed.
Feed boundary assumptions
- Feed boundary notes are recorded for reviewer context.
- Any assumed operating boundary is clearly labeled as an assumption.
- Follow-up analysis ownership is assigned.
Warnings and margins
- Warnings are not removed from review artifacts.
- Out-of-scope or unsupported behavior is clearly labeled.
- Decision makers understand what remains unreviewed.
Export package
- Report, DXF, images, and supported media are named consistently.
- File dates and revision notes match the review package.
- Exports do not include secrets, private data, or export-sensitive notes.
Review notes
- Advisor, peer, customer, or internal reviewer questions are captured.
- Action items have owners and due dates outside the static report.
- Known gaps are carried into the next revision.
Validation/test follow-up
- Reference-case or comparison context is documented.
- Test planning and acceptance decisions are treated as separate qualified review work.
- Software output is not treated as validation by itself.
Compliance/safety review
- Export-control, sanctions, organizational, and safety review obligations are assigned to qualified reviewers.
- Distribution scope is clear.
- Legal and safety decisions are not delegated to the software.
Handoff package
- Next team or semester receives the case, report, export package, and open notes.
- Assumption drift risks are called out before work resumes.
- Reference case goals are listed for future review.
Use it with RPL
Turn the checklist into a repeatable review package.
RPL Engine Workbench helps keep solved cases, geometry, reports, warnings, and exports connected for Apple silicon Mac users.