Market evidence
Adapters normalize timestamps, bid and ask prices, volume, liquidity, market status, and source identity. Stale or incomplete configured data fails closed instead of being silently filled in.
Every simulated trade starts as evidence—not permission.
PromethIQ Markets separates market data, feature engineering, strategy logic, probability estimation, deterministic risk, paper execution, and reporting. No reasoning component receives unrestricted execution access.
Probability and strategy
Versioned strategies produce structured proposals containing confidence, expected edge, horizon, requested size, and supporting features. Qualified provider-backed cycles may also create expiring recommendations with entry, stop, target, rationale, and maximum modeled loss. Prediction markets use deterministic statistical probability models rather than an LLM as the probability engine.
Deterministic risk
Thirty checks evaluate data freshness, market state, account capacity, edge after costs, position and exposure limits, daily loss, liquidity, spread, duplicates, cooldown, volatility, correlation, and kill-switch state.
Paper execution
Eligible proposals reach a paper broker that models executable-side prices, fees, slippage, latency, limits, partial fills, reservations, cancellation, settlement, and portfolio accounting. It does not submit a provider order.
Durable state
Orders, fills, positions, authoritative cash, reservations, settlements, and portfolio snapshots persist transactionally. Persistence failures restore memory, halt the affected agent, and create an auditable failure record.
Reports over hype
Private reports separate realized and unrealized P&L, fees, slippage, drawdown, expectancy, profit factor, Brier score, calibration error, proposal approvals, and data coverage. Missing evidence remains visibly missing.
No performance promise is part of the methodology.
Historical or paper results cannot guarantee future profit, account growth, or bounded drawdown. The public deployment executes only in paper mode. In a separately reviewed live deployment, proposal approval still cannot submit: account-bound provider preflight, fresh risk, password step-up, and exact final confirmation are mandatory.