Info

Info

GridBot is the current user-facing operator workspace for bounded crypto-futures execution, account visibility, runtime history review, and product evolution.

What Users Can Do Today

• review active runtime status on the Dashboard
• use Grid Control as the formal control surface for the current minimal-runtime mainline
• inspect futures account state and symbol-level positions
• review runtime history and recent trade/fill records

Current Product Position

The current usable operational baseline is the `8000` mainline.

That baseline is:

• usable
• actively maintained
• still evolving
• intentionally bounded for safety and observability

Product Direction

GridBot is moving toward a broader AI-assisted account operations platform.

Near-term work remains focused on:

• stability
• observability
• recovery
• controlled evolution of the current mainline

Project Objectives

GridBot is a strategy execution and position-management platform for crypto futures.

In the long run, AI-grid bot is intended to evolve toward an AI-assisted account operating system: one platform where AI helps with multi-asset execution, records user behavior and preferences, and supports more consistent decisions across scenarios.

Current Usable Mainline

The current usable baseline is the `8000` mainline.

That means:

• the product has a real operational core today
• the current mainline is usable, but still being hardened
• short-term work is focused on stability, observability, recovery, and controlled evolution

Major Capability Blocks

Trading Execution And Grid Strategy

• current core execution surface
• centered on Grid Control and the minimal-runtime path
• current status: usable and actively maintained

Account And Position Management

• account visibility and symbol-level position handling
• centered on the Futures Account page
• current status: partly established, still expanding

Risk Control And Exception Handling

• runtime safety, supervision, and bounded stop/recovery behavior
• current status: active priority

Monitoring, Logs, And Recovery

• runtime history, journals, restart visibility, and operational recovery evidence
• current status: strong foundation, still improving

Data, Statistics, And Reporting

• grid profit, cycle counts, pending metrics, and runtime history summaries
• current status: early-to-mid stage

AI Assistance And Future Platform Direction

• AI-assisted interpretation, decision support, multi-agent coordination, and long-term user memory
• current status: future-facing, phased later

Development Order

The recommended order remains:

1. stabilize the current mainline

2. improve monitoring, recovery, and reporting

3. strengthen account-level management

4. expand AI-assisted decision layers later

Current Priority

The near-term priority is not broad feature expansion.

It is:

• protecting the current usable mainline
• improving transparency
• reducing operational uncertainty
• evolving in small, controlled steps

Related Pages

• Dashboard
• Grid Control
• Futures Account
• Runtime History
• Project Objectives section in this page