Secured NAV
A high-level health check used during Heliox cycle completion
Secured NAVis Heliox's internal confirmation metric for deciding whether a cycle can complete cleanly. The public product promise is simple: Heliox checks more than one balance condition before finalizing state.
Why It Exists
Heliox uses an internal portfolio-health check so cycle completion is not triggered by a single surface-level condition alone. That helps the product avoid declaring a cycle complete when the broader vault state still looks unhealthy.
What Public Docs Do Not Expose
Exact formulas, thresholds, and intermediate debug values are intentionally omitted from public docs. Those details belong in internal engineering references and operator tooling.
What Users Should Take AwayHeliox does not promise profit or guaranteed outcomes. It does promise that cycle completion is governed by product rules that look beyond a single trigger and that users retain vault-level control outside the Heliox app.