Hyperliquid monitor

Reconstruct current exchange state and distinguish safe, triggered, and unavailable observations.

Workflow

1. Bind the network, user account address, account abstraction mode, DEX, markets, observation time, freshness bound, and requested condition.
2. Read authoritative state. Query the account or subaccount being monitored, never the API wallet address.
3. Reconcile positions, balances, open orders, trigger details, order status, fills, funding, ledger updates, fee tier, and action budget. Under unified or portfolio margin, include spot clearinghouse and borrow/lend state.
4. Check every open position against protection and incidents. Match stop side, reduce-only state, trigger, size, and position-tied status.
5. Normalize funding by its stated interval. Use node scripts/funding.mjs --help for arithmetic. Preserve funding signs from the account's perspective.
6. For continuous work, use stream discipline. Snapshot first, deduplicate, heartbeat, detect gaps, and reconcile after reconnect.
7. Evaluate the condition as exactly one of triggered, not-triggered, or unavailable. A failed, empty, stale, partial, or gapped read is unavailable.
8. Emit the monitor contract. Alerts state facts and open a plan; they never act.

Hard rules