Skip to content
Breshev EngineeringAURA Engineering Platform

Decision asset · evidence boundary

Where an Architecture Screen must stop.

A screening result becomes unsafe when it is asked to support a decision outside the evidence it controls. Use this boundary map to separate what can be screened now, what must be proved next and where release authority must remain downstream.

8 stop conditionsEvidence authoritysupplier-independent2-page PDF
The ruleStop when the next conclusion depends on evidence the screen does not control.

Eight stop conditions

Do not let the model outrun the decision basis.

Each condition marks a boundary where the answer may still be useful for direction, but more evidence is required before authority can increase.

01 · Stop when

The decision or acceptance boundary is not explicit.

If the team cannot state what must be selected, rejected, frozen or proved next, the screen has no defensible authority target.

02 · Stop when

The operating envelope is not bounded.

Speed, duty, radial/axial load, gas state, temperature or packaging remain too open to identify the governing state.

03 · Stop when

The candidate identity is no longer controlled.

Geometry revision, clearance, supply state, shaft-line context or coordinate basis changed without being carried into the result.

04 · Stop when

The support model is assumption-dominant.

Stiffness, damping, state dependence or another decision-critical support behaviour lacks sufficient provenance for the requested conclusion.

05 · Stop when

Rotor consequence remains unresolved.

Mode-family separation, response, stability or operating-state consequence is uncertain enough to change the architecture decision.

06 · Stop when

Detailed CFD / FE cannot be reconciled to the same state.

High-fidelity evidence uses a different geometry, boundary condition, state identity or extraction basis and cannot be re-coupled cleanly.

07 · Stop when

Manufacturing and tolerance basis can change the answer.

Clearance, thermal state, tolerances, material or interface definition is not controlled tightly enough for the next irreversible step.

08 · Stop when

Test / acceptance / release authority is undefined.

The evidence does not define what test or acceptance proof is required before prototype release, freeze or production transfer.

Evidence authority

A result is useful only inside its authority.

The objective is not to maximise the status of every result. It is to state what the present evidence may support and keep the next proof explicit.

01

Project Fit Check

Can support

Whether a scoped Architecture Screen is justified.

Cannot support

Numerical design conclusions.

02

Architecture Screen

Can support

Candidate ranking, early rejection, governing operating state and the next proof.

Cannot support

Production release, certification or a final supplier mandate.

03

Architecture & Evidence Package

Can support

Deeper coupled evidence and a controlled verification route.

Cannot support

Claims not covered by the defined model, state or evidence boundary.

04

Detailed CAE / test / client release

Can support

Higher-authority evidence for the specific release question.

Cannot support

Anything outside its validated configuration and acceptance basis.

Do not promote the claim

Six evidence jumps that should trigger a stop.

These are not wording preferences. Each jump changes the engineering authority of the statement.

Screening resultProduction release
One CFD fieldValidated architecture
Component PASSSystem freeze
Assumed dampingStability evidence
One operating stateFull duty envelope
Historical case deviationUniversal error bound

Use this before the next irreversible step

Bring one decision. State what the current evidence can support - and what must be proved next.

An Architecture Screen should reduce uncertainty without pretending to own release authority it has not earned.