What is release evidence for a gas-bearing rotor system?

Release evidence is the traceable basis that determines what a calculated result is allowed to prove. It connects a bearing coefficient to the geometry and clearance state it belongs to, the thermal envelope, the balancing process, rotor-dynamic screening, validation scope, and explicit decision limits. A clean calculation answers the model; release evidence answers the manufactured system.

How is release evidence different from a normal bearing calculation?

A calculation produces a number. Release evidence records what that number depends on and where its authority ends. The same stiffness value can be valid in one clearance, thermal, and balance state and misleading in another, so release evidence separates the physical calculation from the permission to use it in a release decision.

Is residual imbalance enough to release a high-speed rotor?

No. Two rotors can meet the same residual-imbalance grade and still run differently, because the correction path, the manufacturing baseline before balancing, the difference between component-level and assembly-level balance, and the high-speed vibration and orbit response are all part of the evidence. The grade alone is one input, not the decision.

Does AURA expose its solver or calculation engine?

No. AURA exposes the evidence surface — registry, residuals, benchmark anchors, applicability boundaries, and claim limits — while the engineering engine, including the Breshev perturbation-method core and coefficient engine, stays closed. The principle is an open evidence surface with a closed engineering engine.

AURA Technology

Release evidence for gas-bearing rotor systems.

AURA does not treat a bearing coefficient as a free-standing answer. It asks what that number is allowed to prove after geometry, clearance, thermal state, balance process, rotor dynamics, validation scope, and decision limits are considered.

Most tools give coefficients. AURA tells you what those coefficients are allowed to prove.

That is the difference between a calculation result and release evidence. The goal is not to expose the full solver. The goal is to make the evidence surface inspectable: provenance, residuals, applicability boundaries, and explicit claim limits.

Request a scoped review Read Technical Note 03

What release evidence means

RequirementsMachine loads, speed range, precision target, environment.

GeometryBearing family, clearance state, cone/journal/thrust layout.

CoefficientsK/C matrices with method provenance and scope.

DynamicsCritical speed, whirl margin, orbit/runout, vibration risk.

ValidationRegistry anchors, residuals, leakage audit, applicability limits.

DecisionPASS / REVIEW / SCREENING ONLY / freeze boundary.

A clean number can still have weak decision authority. AURA separates physical calculation from release permission.

Why coefficients alone are not enough

Geometry and clearance: a stiffness value belongs to a manufactured and adjusted clearance state.

Thermal envelope: material growth, distortion, and clearance shift can invalidate a coefficient outside its operating state.

Balance process: the path to a residual imbalance target can matter as much as the final number.

Rotor response: vibration, orbit, critical-speed separation, damping, and whirl margin are release-facing evidence.

Balancing / assembly evidence: the chosen balance grade needs a rationale; the residual must be mapped to the correct tolerance planes; capability and vector repeatability must support the requested limit; and component-level balance does not automatically reproduce at assembly level.

Operating envelope: customer-site loads, process conditions, thermal state, duty cycle, and overload events can invalidate evidence that was valid inside the design envelope.

What AURA records

For a scoped case, the decision package can preserve the evidence path: what was assumed, what was computed, what was compared, what residuals remain, what operating envelope applies, and what the result is not allowed to claim.

Static PASS is not freeze Application fit

Roadmap evidence gate

Balancing / assembly evidence

A residual-imbalance grade is not release evidence by itself. For high-speed precision rotors, the release question is broader: which rotor regime applies, why the grade was selected, where acceptance is judged, how correction and measurement planes map to the tolerance planes, whether the machine-process-rotor combination can demonstrate the requested residual, whether the vector repeats, whether component-level balance survives assembly, and what the complete speed-path response shows.

Tolerance basisRequirement edition, basis speed, permissible total, plane coordinates, centre of mass, and allocation.

Plane mappingCorrection and measurement coordinates, radii, angular reference, and transformation.

CapabilityMinimum achievable residual, reduction ratio, angle and correction capability, and guard band.

RepeatabilityVector runs across starts, settling, thermal states, and reassembly.

Assembly transferFingerprint, clocking, before/after vectors, fixtures, interfaces, and revision.

Modal speed pathModes, damping provenance, participation, acceleration, deceleration, crossings, and dwell.

Boundary: the evidence model and locked preview are a specified product direction, not yet a shipped production module. They expose the proposed evidence surface without claiming that the live AURA platform already enforces these fields.

Open Gate 4 Preview Field Guide v1.1 Read TN04 methodology

Why evidence gates are not a software idea

An evidence gate — a rule that a result may not authorise an irreversible step until independent confirmation exists — is not new. The same principle governs how the most consequential decisions are made across unrelated fields. AURA applies it to rotor systems, where it is still largely absent.

Biology

Cell-cycle checkpoints

A dividing cell does not proceed on a single signal. Checkpoints hold the transition until every chromosome is confirmed correctly attached. Evidence-gated release predates engineering by a billion years.

Aerospace

Design assurance

Since 1980, flight-software standards have required evidence — traceability, verification, applicability scope — to be generated and presented, not asserted. Rigour scales with the consequence of failure.

Rotor systems

The missing layer

Bearing and rotor-dynamic tools compute results, but the decision evidence usually lives in an expert's head. AURA makes that evidence layer explicit for gas-bearing rotor systems.

Open evidence surface. Closed engineering engine.

AURA is not built around full transparency of the solver. It is built around inspectable evidence without exposing the proprietary engineering core.

Exposed

Evidence surface

Registry, residuals, benchmark anchors, applicability boundaries, technical notes, DOI records, claim boundaries, and decision limitations.

Protected

Engineering engine

Solver implementation, Breshev perturbation-method core, coefficient engine, damping logic, and decision heuristics.

Current fit

Aerostatic / gas-static systems

Precision spindles, gas-bearing rotor decisions, conical/journal/thrust support screening, semiconductor positioning, cryogenic turboexpanders, and adjacent high-speed precision rotor applications.

Near-axis research

Oil-free turbomachinery / foil bearings

The same release-evidence problem appears in broader oil-free rotor systems: coefficient credibility, thermal envelope, damping, whirl screening, vibration, orbit, and process control. This is tracked as an expansion research line, not a current solver claim.

Practical rule

A result should not be allowed to support a release decision beyond the evidence envelope that produced it.

This is the category AURA is built around: release evidence for gas-bearing rotor systems.

Discuss a scoped case View technical notes Back to home