TALOS OPS · EXECUTION & RISK CONTROL · STATUS: BUILT · HOLSTERED
Talos. The hands that follow the rules.
Talos is the execution agent of the Sovereign-Minds system: it takes signals that have already earned their place and turns them into controlled, observable, logged actions — while enforcing the rules a human breaks under pressure.
TALOS DOES NOT CREATE AN EDGE. IT OPERATIONALIZES RULES THAT HAVE ALREADY PASSED THE REQUIRED RESEARCH AND APPROVAL GATES. AUTOMATED TRADING CARRIES REAL RISK OF LOSS — READ THE TRADING RISK DISCLOSURE.
What Talos does
- Routes approved signals from their source to the broker through an automated pipeline.
- Executes orders inside human-defined risk limits: session windows, trade caps, loss limits.
- Logs every event — signal received, order sent, fill, rejection, halt — for audit.
- Alerts the operator when something fails, rather than failing silently.
What Talos does not do
- It does not invent strategies, predict markets, or generate an edge.
- It does not trade instruments, sizes, or hours outside its configured limits.
- It does not guarantee profit, and it cannot remove market risk. Backtested or simulated behavior of a strategy is not a promise about live results.
- It does not hide its state — if the pipeline is down, the operator knows.
Signal sources
Talos is signal-agnostic by design. The current production pipeline runs TradingView strategy alerts through TradersPost into TopstepX. Signals only reach Talos after passing the research gate — for the trading operation, that gate is Augur.
Risk controls — current production pipeline
These controls are implemented and active in the current Sovereign-Minds pipeline:
- Approved trading window: 9:30–12:00 ET session only.
- Maximum trades per day: 3.
- Daily-loss kill-switch: trading halts for the day when the loss limit is hit.
- Force-flat on session close: no positions held past the window.
- Single approved instrument per strategy configuration.
Additional controls — position-size limits, duplicate-order prevention, stale-signal rejection, connectivity monitoring, and fill reconciliation — are scoped per build to the client's broker and platform. We list a control on a delivered system only when it is actually implemented and demonstrated during handover.
Logging and observability
Every stage of the pipeline emits events: signal in, order out, fill, rejection, halt, and error. Logs are the client's — stored on client-controlled infrastructure and included in the handover documentation.
Failure handling
Failure states are designed to be loud: a broken webhook, a rejected order, or a platform outage triggers an operator alert. The documented kill procedure lets the operator flatten and halt the system manually at any time.
Human approval
Go-live is a human decision, made after watching the system run. Risk limits are set by the human, changed by the human, and enforced by the machine. Builds can include an approval step on every order where the client's risk posture requires it.
Supported environments
Current production experience: CME micro futures via TradingView → TradersPost → TopstepX. Other broker and platform combinations are scoped per engagement — honestly, including when we haven't built on a platform before.
Relationship with Augur
Augur is the gate; Talos is the hands. Strategies reach Talos only after surviving Augur's pre-registered validation — and Talos's live execution data flows back into Augur's evidence ledger. Zero orders until the forward gate passes. See the evidence ledger for how verdicts are reached.
Risk disclosure
Futures and derivatives trading involves substantial risk of loss, including total loss. Automated systems add failure modes of their own — slippage, latency, outages, data errors. Read the full Trading Risk Disclosure before considering any automated execution.