Product roadmap
What BattleGrid is building next — owned by Product (content and priority). Process and status cadence live with PM. Architecture and tech maps live under
docs/architecture/(System Architect).
This page is the public product plan for AI trade agents and the strategies that power them. It is organized by theme, then now / next / later. Dates are directional, not contracts.
How we prioritize
| Lens | Question |
|---|---|
| Activation | Can a new player reach an armed Radar (or a clear Arena / terminal win) without getting stuck? |
| Playbook truth | Does the strategy the player authored match what the agent reads, trades, and reviews? |
| Control plane | Can the same intent run from Commander, MCP, and the app without fighting over drafts? |
| Reliability | Is market data, settlement, and money movement trustworthy at the scale we already run? |
Cuts and sequencing changes are facilitated by PM; Product owns the final call on what moves between buckets.
Themes
| Theme | Outcome |
|---|---|
| Commander & MCP | Plain-language (and tool) control of the whole product — onboarding through co-edit to deploy |
| Strategies & agents | Authorable playbooks bound to runners with clear budget, risk, and levels ownership |
| Radar | Autopilot per coin that stays correct as coverage and policy complexity grow |
| Arena | Fair, fast prediction competition with settlement and live state players can trust |
| Trade & signals | Terminal + automation share one decision trail a reviewer can actually audit |
| Platform foundations | Market data provenance, capacity, and ops that keep the product honest |
Now
Actively shipping or mid-flight. Highest product attention.
Commander-led onboarding
Owner: Product · Delivery: Engineering · Process: PM
Get a newly registered account to an armed Radar through Commander: readiness ladder in chat, welcome path before deposit ask, docks only where a wallet signature is required.
Commander co-editing
Owner: Product · Delivery: Engineering · Process: PM
One working copy across web forms, Commander, docks, and MCP — background sync, presence, and a single committer — so strategy, agent, and Radar policy edits stop colliding.
Playbook → trade truth
Owner: Product · Delivery: Engineering · Process: PM
Close the gaps where authored levels, entry discipline, and review surfaces disagree with what ran: coin scan → proposed entry → reviewable decision trail.
Strategy Builder quality
Owner: Product · Delivery: Engineering · Process: PM
Keep authoring fast and honest — preview and vocabulary ownership, less idle polling, reports that match the live grammar.
Reliability that players feel
Owner: Product · Delivery: Engineering · Architect: tech map
Settlement correctness (e.g. Arena paths), market-data holes, and provenance so “what we showed” matches “what we used.”
Next
Queued after Now. Ready to pull when capacity frees or a Now item lands.
| Item | Why it matters |
|---|---|
| MCP contract maturity | External agents and Commander stay on one discoverable, versioned surface |
| One owner per knob | Agent owns money; strategy owns trade levels — end dual writers for good |
| Radar at scale | Push-driven qualification / policy updates; timer only as fallback |
| Arena hot-path health | Less discovery chatter on the live path; Redis / caching where the product already needs it |
| Entry discipline loop | Measurement and analytics so authors see whether levels behaved as written |
| Trade review completeness | Everything the system knew about a decision is visible to a reviewer — nothing silent |
Later
Important, not next. Revisit when Now/Next clear or a strategic bet changes.
| Item | Notes |
|---|---|
| Cross-exchange market data | Broader tape / books as first-class column-grammar reads |
| Deeper Commander skill waves | Richer ops, diagnostics, and model/prompt hardening beyond the current co-edit + onboarding tracks |
| Ecosystem depth | Progression, rewards, and social loops beyond core agent → deploy → trade |
| Multi-venue trading expansion | Only after playbook truth and Radar/terminal reliability hold on the current venue |
Ownership
| Role | Owns |
|---|---|
| Product Owner | Roadmap content and priority (this page) |
| Product Manager | Cadence, cuts facilitation, status communication |
| System Architect | Architecture / tech map (docs/architecture/) linking roadmap items to system design |
| Engineering | Delivery against the ordered backlog |
Change log
| Date | Change |
|---|---|
| 2026-09-22 | Initial public roadmap structure (themes, now / next / later, owners) |