Screen wake lock: requesting… Uptime: 0m Frame health: normal Bridge: demo
Cortex Orb · Ambient Intelligence

The market, as a living system — not a chart

One engine, fed by every Cortex product, rendered as a single ambient organism instead of numbers. PC app and Android tablet share this same display — Orb living system plus Orbit desk drill-down.

DESK FEED Retail depth normal · Copy crowd balanced · Orchestrator regime Risk-On · CRM exposure flat · Glasses · Watch: ALL CLEAR
CLAWBOT
Clawbot armed via Bridge — commands fill the HOUSE hedge book
✦ CORTEX BOT & INTELLIGENCE SUITE Client Q&A · Neural Docs · Dealing Ticket Orbit · Weekly Macro Story
SOURCESlive
CORTEX ORB
DESKlive
Calm Market
Slow, even drift — nothing material happening
No single product is driving this state right now
Core platforms — feed the Orb AI & wearable surfaces — display the Orb
CORTEX ORB (concept) · particle field driven by market-state parameters, not live data in this prototype · nine Cortex products shown as either data sources (Retail, Pro, Copy Trading, CRM, Bridge, Orchestrator) or display surfaces (Mobile, Watch, AI Glasses) for the same underlying intelligence · this is a screen-based proof of concept — no physical hardware decision has been made
Orbit — What This Means For The Desk

Drilled down from the Orb's current state

Eight categories orbit the desk. Nothing material pulls in and grows; everything else drifts to the edge. The same assessment below reaches AI Glasses and Watch at the right level of detail for each.

0 items need attention
DEALING DESK
RegimeRisk-On
LiquidityNormal
ExecutionHealthy
Attention: 0

Dealing Desk — Full Detail

Orbit

AI Glasses — HUD Overlay

Reduced

Watch — Ambient Glance

Minimal
CORTEX ORBIT (concept) · category positions driven by attention score · the same underlying assessment renders at three levels of detail — full case on the desk, a headline on AI Glasses, a single status word on Watch
Under The Hood — How This Actually Connects

Orb isn't wired to nine products. It's wired to one contract, nine times.

Everything above — the living sphere, the Orbit drill-down, the Sources and Desk panels — is only possible because every connected product speaks one shared event language into Orchestrator.

SENSE — events flowing up ACT — approved commands flowing down
Layer 4 — The Brain
CORTEX ORB
Waiting for live feed…
Living Market Model
The ambient state visualisation — calm, volatile, risk, liquidity, event, regime
Digital Twin / What-If
Simulates the brokerage's own book under hypothetical shocks
Orbit Attention Engine
Dynamically re-prioritises what deserves a human's attention right now
Ask & Act Interface
Natural-language Q&A and action-triggering, grounded only in real connected data
synthesised state up · approved intent down
Layer 3 — Coordination
ORCHESTRATOR
Checking orchestrator…
Synthesis
Correlates raw events from many products into a small number of prioritised, sourced items
—
⚠ Human Approval Gate
No action reaches a product without an authorised human decision
—
Action Router
Once approved, calls the specific product's own Action API
—
publish · subscribe
Layer 2 — The Contract
Cortex Event Bus
Checking event bus…
Every product speaks one schema: { source, timestamp, event_type, severity, entity_ids, payload } — new products plug in by adopting the contract, not custom integration work.
events out · commands in
Layer 1 — The Body
Ten Connected Products & AI Engines
Checking product heartbeats…
Retail Platform
—
OUT price, volatility, order flow
Cortex Pro
—
OUT institutional depth, big-ticket flow
Copy Trading
—
OUT follower flow, AUM changes
IN pause strategy, flag investor
CRM
—
OUT KYC, withdrawals, account events
IN approve, restrict, clear
Bridge
—
OUT execution telemetry, LP health, heartbeat
IN routing changes, restart
Cortex Bot
—
OUT client questions, natural language prompts
IN synthesized answers, doc graph, tickets
CortexONE Mobile
—
IN display surface — receives priorities
Cortex Watch
—
IN display surface — one word, one colour
AI Glasses
—
IN display surface — HUD headline only

Why "robust" means loose coupling

If Orb integrated with each product's internals directly, a schema change in any one of nine systems could break Orb. With a shared event contract, products can change behind their API as long as events stay the same shape.

Why every connection needs a heartbeat

Bridge's status dot isn't decoration — if a product's connection goes stale, Orb must show "data unavailable," never silently reuse the last known state as if it were current.

Why the approval gate sits in Orchestrator, not Orb

Orb reasons and recommends. It never calls a product's Action API directly. Every approved action passes through one auditable choke point.

Why client AI lives inside Cortex AI Engine, not a tenth product

Retail and Pro still publish events up to Orchestrator — unchanged. Their AI features (DEBATE, Insight, Ask Cortex) call into Cortex AI Engine's engine room: an invisible router that picks the right model and sourcing rules. No separate Fabric URL, icon, or product card — just one honest answer whether the trader or the executive asked first.

CORTEX ORB CONNECTIVITY · Clawbot commands route through Bridge; desk approvals route through Orchestrator · live state from /v1/orb/state when Bridge is connected