Roadmap · Phase 0–7 · Phase-gated · Not a release schedule

Roadmap discipline: prove the system before expanding the system.

The IntelliBot roadmap is intentionally gated from Phase 0 through Phase 7. Each phase must satisfy its own engineering, risk, security, QA, and governance checks before the project can move toward broader access, live-capital workflows, beta enrollment, commercialization, or funding-pathway activity.

Current roadmap authority

Eight public roadmap phases, with clear gating.

This restores the detailed Phase 0–7 structure while keeping the cleaner visual presentation. The roadmap is directional and phase-gated; it is not a promise of product availability, trading performance, beta access, or investment opportunity.

0
Current · TT-169 V2.8 authority

Phase 0 · Governance, architecture, and clean foundation

Establish the authoritative TPMS baseline, product boundaries, schema-readiness requirements, and disciplined implementation controls before runtime work expands.

Key workstreams
  • STATUS.md ticket authority
  • TT-169 V2.8 schema-readiness baseline
  • UI authority and retired page cleanup
  • Codex Plan-mode discipline
Authorization gates
  • No superseded package may control scope
  • No implementation outside approved phase
  • No live-capital, beta, or commercialization activity
Not yet allowed
  • Runtime implementation without gate approval
  • Provider integration or API-key acquisition
  • Public beta or investor workflow activation
1
Next only after Phase 0 gates

Phase 1 · Local foundation, credentials, persistence, and diagnostics

Build the controlled local application foundation: configuration, database persistence, exchange-account setup, credential handling posture, diagnostics, and readiness checks.

Key workstreams
  • Local app shell and settings workflow
  • SQLite persistence and migration readiness
  • Coinbase portfolio/account selection
  • API permission verification and diagnostics
Authorization gates
  • View + trade permission only
  • No withdrawal scope
  • Sandbox-first environment default
  • Readiness checks before unlock
Not yet allowed
  • Live trading automation
  • Public user onboarding
  • Analytics, beta forms, or production deployment
2
Signal spine and strategy contracts

Phase 2 · Market data, indicators, screener, strategy contracts, and watchdogs

Develop the internal market-data and strategy-evaluation spine while keeping AI/news/sentiment advisory only and preserving deterministic risk authority.

Key workstreams
  • Coinbase Spot market data ingestion
  • Indicator pipeline and candidate screener
  • Strategy contract definitions
  • AccountSafetyWatchdog and system-state monitoring
Authorization gates
  • Data integrity checks
  • Strategy eligibility placeholders
  • Watchdog status visibility
  • Advisory context remains non-executing
Not yet allowed
  • AI-triggered trades
  • News/sentiment bypass of RiskManager
  • External framework live-eligibility grants
3
Risk and proof engine

Phase 3 · Risk engine, sandbox broker, order lifecycle, and canonical backtester

Implement and validate the core proof systems: deterministic backtesting, sandbox order lifecycle, risk budget, drawdown persistence, cooldowns, and one-active-trade enforcement.

Key workstreams
  • Internal canonical backtester
  • Sandbox broker/order lifecycle
  • Daily/weekly drawdown persistence
  • One-active-trade enforcement and partial index
Authorization gates
  • Backtesting before trust
  • Sandbox before live capital
  • Proof status before eligibility
  • Guardrail audit logging
Not yet allowed
  • Production live-capital automation
  • Commercial beta access
  • Performance claims based on mockups or tests
4
Live-hardening review

Phase 4 · Live execution hardening after deterministic simulation

Prepare live execution only after deterministic simulation, sandbox behavior, risk controls, and operator intervention paths are hardened and reviewed.

Key workstreams
  • Live broker boundary review
  • Emergency stop and kill-switch workflow
  • Order reconciliation and failure handling
  • Production-floor safety rules
Authorization gates
  • Minimum equity and readiness conditions
  • RiskManager and watchdog pass state
  • Live eligibility cannot be created by AI/news
  • Operator acknowledgement of risk
Not yet allowed
  • Unreviewed live-capital use
  • Multi-position expansion
  • Custody or withdrawal capability
5
Operator cockpit

Phase 5 · Operator cockpit UI and progressive unlock workflow

Build the user-facing cockpit around the approved UI authority: Dashboard, Live Trading, Strategies, Backtesting, Risk Center, Reporting, and Settings.

Key workstreams
  • Dashboard risk/readiness view
  • Live Trading embedded screener and chart
  • Strategy proof and Backtesting surfaces
  • Risk Center, Reporting, and Settings workflows
Authorization gates
  • Progressive unlock requirements
  • Decision logs and audit trail visibility
  • Emergency controls remain prominent
  • No retired standalone Screener/Charts/AI pages
Not yet allowed
  • UI shortcuts around guardrails
  • Hidden live-trading enablement
  • Public product-download workflow
6
Advisory context and support layer

Phase 6 · Advisory context, alerts, deployment packaging, and operator support

Add non-executing advisory context, alerting, exportable evidence, deployment packaging, and operator-support readiness without weakening trading authority boundaries.

Key workstreams
  • AI/news/sentiment advisory panels
  • Alerts and operator notification flow
  • Export/reporting packages
  • Installer/deployment readiness and support materials
Authorization gates
  • Advisory-only enforcement
  • No provider can open trades
  • Support docs and risk disclosures ready
  • Security and privacy review before public intake
Not yet allowed
  • Provider-driven execution
  • Unapproved analytics activation
  • Public beta signup or account onboarding
7
Later · commercial and compliance review

Phase 7 · Commercialization, beta, compliance, and funding-pathway review

Evaluate whether the project is ready for controlled beta, public communications, commercialization planning, compliance review, and any funding pathway after product and safety gates mature.

Key workstreams
  • Controlled beta readiness review
  • Legal/compliance review and public communications policy
  • Commercial packaging and support model
  • Funding-pathway review only if separately authorized
Authorization gates
  • No beta without security and onboarding readiness
  • No financing language without legal process
  • No performance claims or implied results
  • Separate approval for any public intake workflow
Not yet allowed
  • Public investment solicitation
  • Public beta enrollment on this interim site
  • Claims that concept imagery is released software
Roadmap boundary: This roadmap is directional and phase-gated. Dates, phase sequencing, scope, features, beta timing, commercial plans, and funding-pathway decisions remain subject to engineering progress, security review, legal review, testing evidence, and explicit approval. Nothing on this page is product availability, investment advice, a securities offering, beta enrollment, trading advice, or a performance claim.