Risk disclosure.

Nothing on this site, in the dashboard, in MCP responses, or in operator chats constitutes investment, tax, or legal advice. Strategy outputs are signals, not recommendations.

Target CAGR, max drawdown, Sharpe and win-rate ranges are model expectations derived from backtests and forward live runs. Future returns are not predictable and can fall outside any stated range, including to total loss.

Historical performance is calculated with constant slippage and fee assumptions, survivorship in the chosen universe (BTC / SPY / GLD / SHY for long sleeves; a curated crypto pair set for intraday), and the data quality of the underlying feeds. Real conditions vary.

Forward-tested numbers may have been collected in paper mode (an internal simulation venue). Live behaviour on a real venue differs because of partial fills, queue position, funding flips, market-maker reactions to order flow, and exchange-side throttling.

Positions can move against the operator faster than guardrails can act. In illiquid sessions, fast moves, or venue outages, intended exits may not execute at the modelled price. Stops are not guarantees — they are instructions.

Spot, perp, or fiat balances live at the operator's chosen venue. Venue insolvency, withdrawal halts, hacks, geographic restrictions, or unilateral policy changes are venue risks the operator carries — inite.fund cannot insulate against them.

Venue keys are stored encrypted on the inite.fund infrastructure but remain the operator's bearer credential. Venue-side permission scoping — trade-only access, IP allow-lists — is the operator's responsibility. We recommend both.

Intraday strategies can run on margin venues. Drawdown on a leveraged position multiplies. Liquidation cascades during volatility spikes can close positions below the modelled stop.

The control plane, the simulation venue, the data feeds, and Claude or other MCP clients can fail or behave unexpectedly. The audit log reconstructs what happened; it does not undo it. The kill switch is for situations where the operator wants the engine to stop trading immediately.

Guardrail breaches surface as approval requests. The operator is expected to read and decide them — auto-approving everything erases the protection. Conversely, an unattended HIL queue can stall risk-reducing rebalances.

Operating systematic strategies on venue keys may be restricted, regulated, or licensed in the operator's jurisdiction. The operator is responsible for confirming eligibility before connecting funds.