HENSYNTH compliance matrix: PASS, FAIL, and margin

One table, one requirement set

The compliance matrix in HENSYNTH is the contract between what you typed on Requirements and what Run screening predicted. Rows appear on the Requirements run report after analysis, inside candidate zips as a compliance figure, and anywhere else the UI renders ComplianceTable with stored rows. If the analysis API returns no rows, the table shows an empty state — the UI does not fabricate PASS lines.

Column by column

• Requirement — the mission metric name tied to your saved caps (range, endurance, stall, field lengths, and the rest).
• Target — the number from the requirements form, with unit when the engine supplied one.
• Predicted — the screening value from the latest run for the current aircraft geometry and propulsion.
• Margin — headroom or shortfall in the engine’s margin convention. Read sign together with status; do not treat margin as a certified safety factor.
• Status — PASS or FAIL chip from the comparison logic. FAIL means the conceptual model says the cap is not met at this fidelity, not that flight test would necessarily agree.
• Confidence — optional metadata on the row. It is not a substitute for test data or a probability of certification.

How to use PASS and FAIL in reviews

Use PASS rows to show which caps the current geometry clears in screening. Use FAIL rows to prioritize the next geometry or requirement change — often span, battery mass, wing area, or tail volume when stability or field length fails. A candidate card’s passes count in the monospace summary is the number of compliance rows that passed for that synthesized sizing, not a score out of ten from an independent auditor.

Compliance in zip reports

Requirements run zips and candidate zips include a compliance PNG drawn from the same row list. Email share attaches that package so reviewers who do not have a HENDOI seat still see targets versus predictions. Remind them the footer context: conceptual analysis only.

Not certification language

Regulatory compliance for real aircraft involves parts, processes, and flight test far beyond this table. HENSYNTH’s matrix is an engineering screening aid for conceptual design. Do not map PASS directly to “approved for operation.”

In simple words: what this page is for

The compliance table compares each mission requirement to predicted screening values — target, predicted, margin, status chip, and confidence — on Requirements and in reports.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH compliance matrix: PASS, FAIL, and margin keeps the focus on conceptual screening you can explain in review.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands HENSYNTH compliance matrix: PASS, FAIL, and margin so you can answer three questions without jargon: what is the idea, when do you use it, and how do you check it in a HENDOI product.

Read the sections above for the core definitions. Use the steps below to move from reading into a real project trail you can share with a teammate.

How to apply this in HENDOI

In practice: open HENSYNTH after you sign in, set or confirm geometry, write mission targets on Requirements, Run screening, then read PASS / FAIL with margins. Use Mission, Performance, Trades, Optimize and Reports only after the screening snapshot exists. Numbers come from stored runs — the product does not invent missing values.

If you still need the wing section itself, finish that work in HENFOIL first, then continue the aircraft in HENSYNTH. One HENDOI account covers both. Plans stay Student USD 9, Professional USD 29 and Team USD 89.

What this page will not claim: HENSYNTH is conceptual and preliminary screening. It is not wind-tunnel data, not certification CFD, and not a compliance certificate for an authority. PASS / FAIL means requirement-versus-prediction inside the product.

Checklist before you leave this page

• Can you state the idea of HENSYNTH compliance matrix: PASS, FAIL, and margin in one sentence?
• Do you know which product owns the next action — HENSYNTH or HENFOIL?
• Will every number you keep carry a method label or a stored-run source?
• If you are new here, have you opened Register or Login?

Related reading on this site

• HENSYNTH candidate cards, Use this aircraft, and CAD
• HENSYNTH download and share technical reports
• HENSYNTH Geometry page: wing, fuselage, and tails
• HENSYNTH workflow: dashboard to technical report
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now