Encode the state of the market.
Assets, sleeves, regimes, signals, and positions become typed objects with explicit ownership and relationships. Feeds can change without changing the contract consumers read.
The typed decision graph connecting market evidence, portfolio state, governance, and execution.
Assets, sleeves, regimes, signals, and positions become typed objects with explicit ownership and relationships. Feeds can change without changing the contract consumers read.
Strategy rules and constraints are versioned, sealed in signed bundles, and evaluated with purged walk-forward tests before activation.
Orders, fills, and resulting position changes remain distinct but linked, so execution can be reconciled against the decision that authorized it.
Each proposal from the configured council enters the same PASS, BLOCK, REVIEW gate. The evaluated constraint version and verdict stay attached to the decision record.
DecisionContext gives every authorized component the same versioned view of assets, signals, regimes, constraints, positions, and trades. Select a primitive to inspect what it publishes and consumes.
Each primitive owns a distinct contract: what fields it carries, which component writes it, and which decisions may consume it.
Nexus defines how domain objects combine: a Signal is interpreted inside a Regime, a Constraint becomes a Risk verdict, and a confirmed Trade becomes Position state.
A typed read model, explicit graph relationships, and a layered communication protocol keep storage, reasoning, governance, and execution connected without collapsing them into one system.
Nexus is Harbor's decision fabric: the typed layer that lets data services, agents, risk controls, and execution tools exchange context without sharing implementation details.
Follow one path from source records to application action. Isolate a layer to see where data, governance, Nexus, agents, and operator tools enter the decision lifecycle.