T3 TradesSpec · prototype space
PROTOTYPE · MOCK DATA Hyperliquid TESTNET

§19.4 · Mission timeline prototype

One mission iteration, step by step

A T3-managed Claude harness ran an ETH momentum mission with $1,000 of allocated capital. This prototype steps through a single iteration of the §3 architectural loop — the path from a registered watch firing to a confirmed, protected fill — using the verbatim §19.4 timeline. Pick a loop phase to see where the mission sits, which node of the loop is current, and how the execution lifecycle reads. Static UI · mock data · no network calls.

Claude · model phase LOOP_WAITING

Static UI · mock data · no network calls. Switch the loop phase above to advance the narrative and update the highlighted loop node and lifecycle row.

§3 · The architectural loop

The loop the POC must prove

one mission · one bound harness · many turns
  1. 1 · User instruction“Execute a momentum strategy on ETH with $1,000.”
  2. 2 · T3 starts harnessProviderService starts the bound Claude session
  3. 3 · Harness publishes strategy + watchesStrategy v1, candle watches registered
  4. 4 · Turn ends · T3 activeMonitoring armed; no discretionary action
  5. 5 · Watch / timer fires5m candle closes above threshold
  6. 6 · T3 resumes harnessSame provider, fresh mission snapshot
  7. 7 · Harness decidesenter · decline · revise
  8. 8 · Typed execution$150 long IOC · stop defined
  9. 9 · T3 validates · signs · reconcilesauthority · nonce · execution wallet
  10. 10 · Persist + next watchesprotection confirmed · loop repeats

Nodes are coloured by the authority that owns that step: human (User), platform (T3), model (Harness), exchange (Hyperliquid), risk (Authority/execution). The highlighted step tracks the selected loop phase.

A watch firing does not itself authorize a new position. The harness decides; T3 validates and executes. See runtime §12.4 for the between-turns path and risk for the authority and loss-budget that gate every position increase.

15:27 entry · execution lifecycle

Accepted → Order → Fill → Reconciled

Claude
  1. 1 · Acceptedauthority + wallet approved
  2. 2 · Order$150 long IOC submitted, risk reserved

The lifecycle row reflects the selected loop phase. Fill is current while T3 is executing; Reconciled completes once exchange-native reduce-only protection is confirmed.

§19.4 · Full mission timeline

ETH momentum mission · 14:05 → 15:42

Mode · 5m breakout continuation Market · ETH perp

Verbatim from spec §19.4. Tag colour marks the owning authority: cyan = model/harness, green = Hyperliquid, red = authority/controls, amber = user. A watch firing never authorizes a position on its own.

Step-through narrative · §12.4 between turns

What each phase means

User stays in control between turns. At 15:41 the user disabled future short entries; at 15:42 T3 updated authority and reassessed the harness. Deterministic controls (pause, cancel entries, reduce, close, revoke) work the same way and never depend on the bound harness being online.