Reading all four execution routes.

EMI verifies paper and practice routing across stocks, options, futures, forex, spot crypto, and crypto perpetuals. A clean TRADE_READY episode must settle in both the internal book and its configured broker—or surface a visible defect.

Loading current route and settlement receipts from PostgreSQL.

Read-only Paper / practice only No order controls

ConnectivityCurrent broker receipts

Execution incidentsCurrently unresolved only

AuthorityPaperNo live-money route

Position lineageHistorical ADD/TRIM readiness

Execution routes

All configured routes are always visible. A real zero-position book is healthy; missing evidence is shown as unknown.

02 / Routes

Market-data venues are separate. Coinbase, Kraken, and CoinGecko can supply prices or intelligence, but they are not execution destinations and therefore do not appear as broker routes.

Did clean trades reach the broker?

Current settlement truth is separated from severe trading decisions and historical software defects.

03 / Dual execution

Window

Route

Asset

What needs attention now?

Only currently unresolved execution defects or route receipts appear here. Severe Holds are trading decisions and do not belong in this queue.

04 / Operator queue

Recent broker executions

Every row has a broker order identity. Internal logical trades without a broker receipt are excluded.

05 / Order flow

Time	Symbol	Asset	Direction	Broker	Action	Qty	Fill	Status	Protection

Loading broker orders…Paper / practice receipts only

Current broker positions

Normalized holdings across all four routes, compared with EMI's internal position lineage.

06 / Holdings

Unavailable position evidence is shown as —, never zero. A parity mismatch does not mean the broker is offline.

Broker	Symbol	Asset	Side	Qty	Avg cost	Mark	Value	Unrealized	Protection	Internal lineage

Loading portfolio-truth receipt…No account identities exposed

Historical portfolio reconciliation

Position-lineage agreement affects portfolio ADD/TRIM readiness, not basic trade routing.

07 / Lineage · secondary

Execution quality by route

Historical failures are reported separately from current route status. An old reject never reads as a current outage.

08 / Coverage

Historical execution auditForensic depth · not the operating view