Signal
Your bot, alert, or REST client creates order intent.
Product
Pre-trade guardrails before broker submission.
Titan gives signal operators a pre-flight layer for order intent: safety checks, gate-level reasons, receipt records, and a clear execution boundary.
How it works
Evaluate
Titan checks the signal against configured pre-trade gates before broker submission.
Return
Titan returns allow or block output with a reason, trace id, and decision trail.
Execute
Your own execution path decides what to do next. Hosted Titan does not place orders.
Pre-trade checks
Titan evaluates proposed orders before they reach the broker. Gates can inspect symbol scope, side, market hours, cooldowns, drawdown, daily loss, exposure, sizing, and bracket validity.
The first failed gate stops the signal and returns a structured reason your bot can handle.
Decision receipts
Every recorded eval creates a traceable decision receipt. The receipt is an inspection record for what Titan checked and decided, not proof that an order was placed or filled.
When proof artifacts are available, the verifier can recompute the receipt path against the committed evidence.
Broker rejection diagnosis
Titan helps separate strategy decisions from downstream broker friction: duplicate alerts, unsupported symbols, market-hour misses, bracket issues, and account-state limits are easier to inspect when they appear as gate reasons.
Execution boundary
Hosted Titan evaluates and records proposed order intent. It does not generate signals, hold funds, require broker credentials for public evals, or independently place broker orders.