trade.clab.one
Operational overview
This console tracks public edge readiness for market data, feature computation, and strategy services, then lays out the operational surfaces the desk will use once portfolio, proposal, and execution adapters are connected. Missing systems are shown plainly instead of simulated.
Waiting for readiness checks from the public edge.
Service health
Market data
Ingress and normalization
Waiting for service response.
Feature pipeline
Transform and enrich
Waiting for service response.
Strategy engine
Signal generation
Waiting for service response.
Portfolio management
Portfolio balances, position inventory, and risk limits are not yet exposed on this edge.
Trading management
Order routing remains disabled until rotated credentials and bounded execution controls are published.
Proposals and signals
Proposal review remains unavailable until strategy output is published into a reviewable feed.
Fills and execution
No execution endpoint is currently published from the edge, so live orders, fills, and reject messages are unavailable.
System monitoring
Public edge checks update on a fixed polling cadence. Additional telemetry can be surfaced here once log, queue, and deployment signals are published.
Readiness is measured from the same static site your operators will use.
Service checks keep the dashboard current without inventing unsupported APIs.
Static assets mirror cleanly into the existing delivery path at rollout time.
Operational guardrails
Replace compromised venue credentials and inject them through managed secrets only.
Publish a dedicated execution service with explicit trade-count, notional, and venue allowlist controls.
Expose portfolio and fill data before any routing path is opened so operators can verify state transitions.
Keep the desk on manual approval until proposal review, kill switch visibility, and audit logging are wired end to end.