Controlled design basis
Requirement, geometry state, operating condition, assumptions and acceptance question.
Productised engineering engagements
The public delivery path is deliberately bounded: Project Fit Check → Architecture Screen → deeper Architecture & Evidence Package only when the first decision justifies it.
Operating envelope → options → governing risks → next proof.
Review Architecture Screen →Project Fit Check comes first and contains no numerical design work.Non-confidential structured intake, data gaps and go / no-go for a scoped Architecture Screen. No numerical design work.
Check project fit →Operating envelope, assumptions, first-order screen, sensitivity, governing risks, options and next-proof route.
Review Architecture Screen →Requirements dossier, model-tier route, supplier-independent logic, risk register and acceptance / evidence plan.
Review deeper package →CFD, FE or evidence review only for a question and state already defined by the decision chain.
Review verification routes →Secondary commercial route
OEM Architecture Screens remain the primary public offer. Separately, a spindle or gas-bearing manufacturer can use Breshev Engineering as an external specialist design source for qualified requests that exceed internal capacity or sit outside the normal product range.
Boundary: this is scoped as engineering capacity, not hidden referral influence over an OEM Architecture Screen.
Discuss supplier-side engineering capacity →What the handoff looks like
The deliverable is designed to support an engineering decision, not simply to export plots or a solver file.
Requirement, geometry state, operating condition, assumptions and acceptance question.
Physical result, rotor consequence, margins, rejected states and comparison basis.
What is established now, what remains open, and what CFD / FE / test must prove next.
Send the machine context and the decision you need. The first response should define whether a screen is worth doing.