Place the order.
Close the loop.
Execution is Harbor’s last mile. It takes only risk-approved ideas, translates them into broker-ready tickets, manages the bridge to market, and leaves behind the audit trail that proves the full chain of custody.
Every order that leaves Harbor carries its upstream signal, risk, and sleeve context with it.
Local-only positions reconciled against IBKR paper state.
The end of the chain.
Execution only fires on approved trades. This is where Harbor stops being a scoring system and becomes an operating system that can place, reconcile, and explain real orders.
From verdict to fill.
The lifecycle view makes the last mile tangible for buyers. Harbor receives the PASS packet, validates it, submits it, monitors the working state, and only then archives the result.
PASS packet arrives with chain context already attached.
Broker, ticket, and routing checks pass pre-flight.
Order is transmitted and broker id is assigned.
Live in market, waiting for fill or cancellation outcome.
Fill confirmed and written back into Harbor’s ledger.
Harbor to market.
This bridge diagram stays close to your mockup on purpose. It makes the architecture legible: Harbor constructs intent, IBKR carries it, and the order reaches a real venue only after the chain has finished its work.
RECONCILE MISMATCH · Local-only positions reconciled against IBKR paper state.
What an order looks like.
The ticket below is intentionally close to your mockup, but it is grounded in a real MRVL trade Harbor already carried. Where live valuation fields are not exposed by the execution API, the page shows the chain attachment instead of inventing numbers.
A buyer can see that Harbor does not just say yes to an idea. It turns the idea into a broker-ready object with custody, routing, and auditability built in.
Execution is where thesis quality meets market microstructure. Good ideas still need sane tickets, venue routing, and ledger discipline to become real positions.
Every action. Timestamped.
The append-only execution log is how Harbor proves that a trade was not a black box. Even in a buyer-facing page, the trail needs to feel like an operating record, not a decorative timeline.
What Execution handles.
Execution is not just “send order”. It is the surface where Harbor turns approved intent into a tracked market action, then writes the result back into the system.
Translates RiskContext into a live ticket: symbol, side, quantity, routing rules, and limit instructions. No manual re-entry between decision and broker.
Checks broker availability, order identifiers, and live routing readiness before Harbor lets a ticket leave the system.
Maintains the IBKR bridge Harbor uses to turn approved intent into market instructions, with reconnect and reconciliation awareness built in.
Tracks live order state and records whether the idea is still working, has filled, or was cancelled before it became a position.
Writes the resulting position back into Harbor’s sleeve ledger so downstream monitoring, exits, and performance all share the same source of truth.
Preserves the full reasoning chain with each order so operators and buyers can see the exact custody from signal to broker acknowledgement.
From PASS to position.
This is the most latency-sensitive stage in Harbor. The page keeps that feel without losing the buyer-readable explanation of what happens between approval and a live position.
Read PASS verdicts from Risk together with the already-assembled reasoning trail from upstream agents.
Build the live ticket with side, size, limit price, sleeve attribution, and routing instructions that the broker bridge can understand.
Run pre-flight checks on routing readiness, broker handshake, and order completeness before Harbor attempts market access.
Transmit through the IBKR bridge, attach the broker order id, and monitor whether the order is working, filled, or cancelled.
Append the result to the audit log, update the sleeve ledger, and emit final execution context for the operating record.
What Execution emits.
ExecutionContext is the chain’s closing artifact. It confirms what was sent, what filled, and what context traveled with the order all the way to the broker layer.
Control the last mile.
Execution settings shape how Harbor meets the market. This is where routing, timeout, and connection behavior become part of the product story.
Choose how Harbor prefers to express intent at the broker layer, whether that means conservative limits, adaptive logic, or tighter timeout behavior.
Tune exchange and venue preferences so the execution layer reflects the mandate’s priorities around price improvement and certainty.
Inspect how Harbor watches the broker handshake, reconciliation notes, and fallback behavior when the execution bridge needs attention.
Ask Harbor to explain how an order was placed, filled, or cancelled and get the full chain context back in one readable answer.
Six agents. One governed surface.
From macro posture to broker fill, Harbor keeps every decision structured, every constraint visible, and every action auditable.