Proviso
04 / EXECUTION

A signal is not
an order. Yet.

Between a condition and a trade sits a series of checks: data quality, market depth, account permissions, and the exact limits you approved.

THESIS TRADING / PROVISO
01CONFIRMED IDEA
02VALID INPUTS
03PERMISSION
04SIGNER POLICY
ORDER ATTEMPT
01 / SIGNALS MOVE AT DIFFERENT SPEEDS

Freshness belongs
to the source.

INPUTINPUT SOURCEREFRESH TARGET
Price / funding / OIHyperliquid WebSocket + info APIStream, debounced to 5s
Robinhood Chain pricesUniswap v4 StateView + Chainlink5 seconds
Sessions / corporate actionsRobinhood assets and market APIs60 seconds
Fear & GreedPublic index API15 minutes
EarningsCalendar vendor, not yet selectedDaily
Selected X accountsCost-dependent API polling30–60 seconds, later stage

Source freshness is part of the decision. Stale inputs, unavailable references, or market halts prevent an input from becoming a valid trigger.

02 / DECISION PATHS

The checks
change the outcome.

DECISION PATH

Valid inputs

01Confirmed rule02valid data03approved limits04attempt order

A valid path reaches the signer. It does not guarantee a fill or a profitable result.

03 / THE SIGNER BOUNDARY

Permission is narrow.
Enforcement is specific.

Only the confirmed idea.

The Hyperliquid signer policy requires an order to belong to a live thesis, stay within idea and global limits, and sit within 2% of mark. Stops and exits are reduce-only. Unrecognized order shapes must be refused.

One leg, one reference check.

Hyperliquid mark is compared with its oracle; a Robinhood pool is compared with Chainlink or another pool. A cross-venue gap may exist precisely because two independently valid prices differ.

Stop is a workflow.

The stop workflow closes idea positions with reduce-only orders and stops future operation. Order acknowledgements and fill status must remain visible; a click cannot promise an instantaneous market exit.

Closed sessions stay visible.

Stock Token prices carry a closed-session flag when the US market is shut. Thin pools, halted markets, and third-party oracle failures remain meaningful sources of risk.

Make the boundaries concrete.

Inspect and save allocation, leverage, daily-loss, and slippage preferences.

Open risk controls