Static PASS is not engineering freeze.

In requirement-driven design, you start from the application: speed, load, rotor-dynamic targets, clearance limits, allowable flow, and architecture constraints. You synthesize a bearing candidate. You run the static checks.

Everything looks acceptable on paper. Then the same support coefficients move into rotor-dynamic screening. Critical-speed separation may be acceptable. Forced response may stay within limits. Stability may look favourable. But damping provenance may still be screening-level, cross-coupling evidence may be partial, and rotor-bearing coupling may be one-way.

Nothing has failed. Yet the result is not strong enough for engineering freeze.

Calculation completion is not decision authority

A calculation that converges numerically is not the same as a result that can carry a release decision. In gas-bearing rotor systems the two are often treated as identical. That is where silent decision risk enters.

What a defensible verdict looks like

In an evidence-gated workflow, the verdict separates calculation result from freeze authority:

Reason: damping provenance / coupling maturity / validation trace insufficient for release.

That is not a flaw in the calculation. It is honesty about what the evidence supports. A candidate can be physically plausible, pass static checks, and still remain screening-only until damping provenance, coupling maturity, benchmark trace, tolerance basis, and validation scope are strong enough for release.

Synthesis gets you to a candidate. Evidence decides the freeze.

Requirement-driven synthesis gets from an application to a feasible bearing candidate quickly. But synthesis alone does not earn a freeze decision — evidence does. The discipline is keeping the chain from requirement to decision traceable, and keeping the boundary of what the evidence can support visible before anyone trusts the result.