Agents

Execution

What the execution mandate is allowed to read, what it produces, and what proof exists for it today.

Miloexecution
Mandate
liquidity zones, entries and exits
Reads
the same asset on public venues, one quote each, and what each venue is really quoting
Produces
An annotated series: liquidity zones, levels, and the invalidation
Rejoins the desk
Milo annotates. It sends no order; the desk has no broker write access at all.
  1. reading Milo reads the same asset on three public venues at once.
  2. checking Milo catches one venue quoting a stablecoin, not dollars, and writes it on the card.
  3. reasoning Milo marks liquidity zones and the level that would invalidate the read.
  4. writing Milo annotates entries, exits, and where the idea stops being true.
  5. done Milo returns the annotated series. No order is sent; the desk has no broker write.
Declared capabilities
Ohlcv · Desk · Instruments
Tools it may call
ohlcv · vendor_bars · options_chain · crypto_quote · symbol_search · vol_surface · chart_open · chart_indicators · place · annotate · report_blocked
Ask it something like
“Mark where this would fill on public venues, and where the idea dies.”

Sealed capture on fileA sealed capture of the application exists for this mandate, taken from a named build and listed in a manifest. It is evidence on file, not a run you can watch here, the roster room used to replay it, and no longer does.

More in Agents