Public language for gas-bearing rotor release evidence.
Short engineering notes that explain AURA decision logic without exposing the closed engineering engine.
Static PASS Is Not Engineering Freeze
A calculation can pass static checks while still remaining screening-only once damping provenance, coupling maturity, and validation scope are considered.
Read noteFrom Application Fit to Support Architecture
Before geometry is selected, the decision is whether gas-static support is justified by the application and what architecture can carry the requirements.
Read noteGeometry, Clearance, and Balance Are the First Validation Gates
A coefficient is not release evidence unless the geometry, clearance state, balance process, and vibration/orbit criteria behind it are known.
Read noteResidual Imbalance Is Not Release Evidence
High-speed precision rotors need a balancing evidence trail: rotor regime, grade rationale, correction path, assembly state, balance-error sources, and vibration response.
Read noteRelease Evidence Has an Operating Envelope
A factory release decision remains valid only inside the operating envelope that produced its evidence. Site conditions and duty cycle are part of the evidence basis.
Read noteRelease Evidence Field Guide v1.1
The flagship AURA framework joins all five gates into one review method and adds a reusable evidence-object template, freeze-readiness checklist, worked balancing case, plane mapping, process capability, vector repeatability, assembly transfer, and modal speed-path evidence.
Get the next AURA technical note by email
Notes are published as a connected series. Current series: freeze, application fit, geometry / clearance / balance gates, residual imbalance evidence, and operating-envelope evidence.