Nexus
The shared semantic layer for orchestrating decisions across agents, governance, and execution.
Eight primitives.
One shared language.
Nexus is the semantic layer under Harbor. It defines the objects, relations, and shared context contracts that make the six-agent chain inspectable instead of opaque. Architecture shows the motion of the system; Nexus explains the meaning that motion depends on.
DecisionContext at the center.
This is the part that belongs here rather than on the broader architecture page: the shared semantic bus and the typed primitives orbiting around it.
Shared bus for typed Harbor context.
Typed. Linked. Versioned.
Each primitive owns a different slice of the domain and tells the agents what kind of thing they are reasoning about.
| Primitive | Type | Owns | Produced By |
|---|---|---|---|
| Signal | Score | Composite score, vote category, timeframe alignment | Signal Agent |
| Asset | Entity | Ticker, sector, market cap, price, fundamentals | Data Layer |
| Sleeve | Group | Ticker list, thematic label, exposure cap | Configuration |
| Constraint | Rule | Threshold, scope, enforcement mode, version | Risk Agent |
| Position | State | Ticker, size, cost basis, sleeve, entry context | Execution Agent |
| Trade | Event | Order ID, fill price, slippage, chain context | Execution Agent |
| Risk | Assessment | Verdict, violations, sizing, stress result | Risk Agent |
| Regime | State | Classification, confidence, module scores | Macro Agent |
How primitives become decisions.
Nexus is not just a dictionary. It is the set of composable patterns that let Harbor move from market facts to portfolio action without losing semantic clarity.
An Asset becomes actionable only once Harbor knows where it belongs. Sleeve gives the entity a portfolio context, constraint envelope, and thematic home.
Regime describes the market state. Signal describes the setup inside that state. Nexus keeps those two ideas separate so the same tape can be read differently under different conditions.
Constraint defines the rule. Risk applies the rule to a proposed action and emits a governable assessment instead of leaving the boundary implicit.
Trade is the event. Position is the lasting state that event creates. Harbor keeps both primitives so it can reason about live exposure and historical action at the same time.
What lives on this page.
The ontology views, communication protocol, and graph tooling all belong to Nexus because they describe how Harbor names, links, and inspects decisions once those primitives are in motion.
Use Fabric on public and product surfaces. Reserve Ontology for deeper technical references and implementation details.
Typed objects, relationships, and governed actions interpreted from raw pipeline tables through Harbor Nexus views and graph edges.
Layered coordination model spanning shared objects, advisories, and training/knowledge transfer.
Product-system perspective
The isometric frame expresses the same Nexus layer from a product and systems-design angle: language, tooling, governance, agents, and applications.
Browse the graph.
This is the live graph surface backing Harbor’s system canvas. Architecture keeps the system story and the orbit view; Nexus keeps the semantic graph, the typed objects, and the closer reading tools.
Live Harbor graph
System nodes, cluster groupings, and cross-layer connections rendered from Harbor's live canvas payload.
Back to the full system.
Use Nexus when you want the language and graph. Use Architecture when you want the full system story.