A diagram transfers. A record does not.
Six stages, and a competitor can have the drawing. Two of the things it runs on do not come with it.
The mechanism is a specification. These two are not.
What comes out the far end goes back in as data.
- Read from
- the trader's own Hyperliquid fills
- Reconciled
- continuously, not on request
- Kept
- close reasons and liquidations, as reported
- Sized from
- closed trades, not stated intentions
- Month four
- knows what month one did
- A copy gets
- the diagram, empty
One rate on the orders it places, and nothing on the ones it does not.
- Paid
- a builder fee, on orders Ernest places
- Rate today
- 0.05%, flat, one number
- Charged
- on top of Hyperliquid's own fees
- Gate fires
- the order is not placed
- Fee on it
- none
- Held by
- code, not a model each time
- Written by
- the trader, in a calmer hour
Code computes. The model only interprets.
- 01 Data the exchange, the trader
- 02 Processing code only, same number twice
- 03 Interpretation the model, and nowhere else
- 04 Validation the trader's rules, checked first
- 05 Execution on instruction, after approval
- 06 Observation what happened, into the record
Stage three is the only one a model touches. That is the whole reason a figure here can be checked against an exchange twice and match.
What the six stages run on
- Exchange
- fills, funding, open interest, candles
- Market
- news, and the threads under it
- The trader
- written rules, limits, stated theses
- Computed
- trades rebuilt, 31 detectors, quarter-Kelly
- Checked
- readiness verdict, then a step-back check
- Returned
- weekly review, scheduled reports
All thirty-one, by name.
A detector is a rule code runs over closed fills. When one fires, that pattern is in the record — it is not a prediction, and not a verdict on a trader. Most read an address on their own; some need what you tell Ernest in the chat.
Emotional 11
- Tilt
- Revenge trading
- Revenge leverage
- Martingale
- Unplanned averaging down
- Euphoria sizing
- Overconfident leverage
- Restlessness
- Analytical paralysis
- Undertrading after drawdown
- Trading to exhaustion
Cognitive 8
- FOMO
- Confirmation bias
- Anchoring on entry price
- Overholding
- Self-sabotage at highs
- Superstitious thinking
- Trading unfamiliar assets
- Knowledge mistaken for skill
Operational 8
- No exit plan
- Flat sizing
- Risk concentration
- Hidden correlation
- Overnight losses
- Position overload
- Strategy drift
- Live account traded like a demo
Social 2
- Following someone else's calls
- Publicly committed position
Structural 2
- Frequent re-entry
- Leverage inversely related to result
A chat reads the link once. Ernest keeps reading it.
The source is named by the trader, and so is the instruction that stands on it: which hours, how often, and what is worth a message at four in the morning.
Sources, added by the trader
- Feeds
- the pages and desks worth watching
- Assets
- tickers, or a whole class
- Wallets
- an address, watched and named
- Events
- the kinds worth waking for
The instruction that stands on them
- Cadence
- how often, and which hours
- Filter
- what counts, and what is noise
- Rules
- the lines, written in advance
- Theses
- what was claimed, and when
- Checkedevery 15 minutes
- Cycles, seven days672
- Met the condition1
- Messages sent1
Ernest · 04:12That wallet is now short the thing you wrote down as a long on 14 May. Price has not moved yet, which is the only reason this is worth waking you for rather than telling you at breakfast.
- 01Read, when you paste it
- 02Judged against nothing you wrote
- —Checked again at four in the morning
The difference is not the reading. It is who opened the page.
Three things a general chat is missing, and one property.
- A link, when it is pasted
- Read once, then gone
- A standing instruction on it
- Sources registered by the trader
- Reread on the cadence set
- Under the instruction you wrote
- Whatever got pasted in
- A screenshot, at one moment
- March, when you need it
- Every fill, reconciled continuously
- Close reasons kept as reported
- Liquidations kept as reported
- Opens when you open it
- The expensive minute has no question
- Speaking first
- Checks on its own schedule
- Most cycles it sends nothing
- Wakes on a condition you wrote
- Computed inside the model
- Plausible, and different next time
- Checkable against the exchange
- Computed by code, before the model
- Same input, same number twice
- Reproducible from your own history
A number a model computes is a number it recomputes. That is why interpretation sits at stage three and not stage two.
Two ways in. Neither can move funds out.
Mode two involves a key, so it is named here rather than discovered later.
- Mode one
- a wallet address, watched read-only
- Mode two
- a Hyperliquid API wallet, on instruction
- It signs
- orders and cancels, nothing else
- It cannot
- withdraw, or send anywhere else
- Approval
- required, on every order
- Custody
- the trader's own account, throughout
- Funds
- never held, at any point
- Revoke
- the key, on-chain, without us
Hyperliquid's own docs carry exactly one asset transfer an API wallet may sign, and its destination has to equal its source. That is the protocol's rule rather than ours.
Access opens in waves. The list is the only way in.
- Today
- an email address, and nothing else
- The only mail
- the one saying the wave is open
- Not required
- an account, a key, a trade