Development7 min read2026-06-30

Hyperhelm: A Governed Trading Cockpit for Hyperliquid, Built on the RiskState Stack

Hyperhelm is an application for Hyperliquid built on top of the RiskState Stack. It turns three engines — structure, playbook, and risk — into a single governed verdict you execute non-custodially.

Hyperliquid gives you the venue. Hyperhelm gives you the verdict.

Hyperliquid is one of the best places to trade perps on-chain: fast, deep, and non-custodial. But a venue only answers one question — where to execute. It does not tell you whether a setup is worth taking, which direction the structure favors, or the question that actually blows up accounts: how much risk is allowed right now.

Hyperhelm is an application for Hyperliquid built on top of the RiskState Stack. It is not another chart or another signal feed. It produces a single governed verdict for BTC and ETH — a direction, a size, a leverage cap, and entry/stop/target levels — that you execute non-custodially on Hyperliquid (perps) and CoW (spot).

The word that matters is governed. Every verdict is the output of three independent engines that have to agree before any exposure is permitted.

Three engines, one decision loop

Hyperhelm doesn't compute anything itself. It orchestrates the three engines of the RiskState Stack, each answering exactly one question:

• Navigator — the Market Structure Engine. 'Are we near an inflection?' It maps breakout and breakdown triggers, the nearest top and support, the 180-day range, and the current regime.

• Strategist — the Trading Playbook Engine. 'Is there a setup to trade?' It runs a registry of rule-based playbooks and surfaces which ones are firing now, each annotated with the navigator's structural vote (ALIGN / NEUTRAL / CONFLICT).

• Governor — the Risk Engine. 'How much is allowed?' It turns live market state into a pre-trade gate: max position size, leverage cap, allowed actions, and a policy hash for the audit trail.

A setup only becomes a verdict when the structure, the playbook, and the risk gate line up. If the governor's gate is closed, the verdict is STAND ASIDE — no matter how good the setup looks.

What a governed verdict actually contains

A Hyperhelm verdict is not a tip. It is a fully specified, sized intent:

• Direction — long or short, for the selected asset.

• Size — the position size the Risk Engine permits, as a fraction of your account. The governor sizes the trade; that is the entire point.

• Leverage cap — the maximum leverage allowed under the current regime and volatility.

• Entry, stop, and target — the levels from the firing playbook, with the risk-reward shown.

• Gate status — OPEN or CLOSED, with the reason, plus a SHA-256 policy hash so the decision is reproducible and auditable.

Because the governor decides the size, a strong-looking setup in a fragile regime is allocated small — or zero — automatically. You are never sized by your conviction; you are sized by the engine.

Non-custodial execution, both venues

A verdict is only useful if you can act on it. Hyperhelm closes the loop without ever holding your keys or your funds:

• Perps execute on Hyperliquid. You approve a no-withdraw agent wallet once; it signs your orders locally. The entry goes in as a limit, with take-profit and stop-loss as native reduce-only triggers (OCO). Your master key never leaves your wallet, and the agent can trade but cannot withdraw.

• Spot executes on CoW Protocol, on the chain you select, with you signing the swap.

Hyperhelm is non-custodial end to end — it sizes and routes the trade, it never takes custody. And because Hyperliquid fills land on-chain, the resulting track record is independently verifiable.

Built on the stack — and you can build on it too

Hyperhelm is the reference application for the RiskState Stack, but the stack is not locked to it. The same three engines are public:

• The Risk Engine (the governor) is the /v1/risk-state API plus a free, read-only view.

• The Market Structure Engine and the Trading Playbook Engine each have their own endpoints and live surfaces.

That means any trading system, bot, or AI agent can call the same governor Hyperhelm uses — to get a pre-trade verdict before placing an order on any venue, not just Hyperliquid. Hyperhelm shows what a governed cockpit looks like; the stack lets you build your own.

The pattern is always the same: form a candidate action, ask the engines, and only proceed if the verdict permits — recording the hashed decision either way.

One verdict. Three engines. Your call.

Hyperhelm is the governed cockpit for Hyperliquid, built on the RiskState Stack. Use it — or build your own application on the same three engines.