10.1 Product Roadmap

10.1.1 Current Phase (T0 – Last 24–48 Hours)

$Capture token

• $Capture launched on Pump.fun over 24 hours ago.

• Utility: powers access to Capture Bot and the broader Capture OS stack.

• 3% of total supply is locked in LP to back early liquidity and reduce rug fears.

Capture Engine (open-source)

• Live and open-source:

  • Continuously scans Solana DEXes and routing aggregators for price inefficiencies.

  • Surfaces real arbitrage opportunities (net spreads, not just raw price gaps).

• Designed for transparency from day one:

  • Anyone can review, fork, and run the engine locally.

Screener & Terminal (public UI)

• Web screener + live terminal available on the official site.

• Shows:

  • Real-time ranked arbitrage opportunities.

  • Key stats (count, average profit, best spread, etc.).

• This makes Capture OS already usable today for manual arbitrage monitoring.

---

10.1.2 Next ~24 Hours – Capture Bot Demo

Capture Bot Demo (Simulation Mode)

• Launching in ~24 hours.

• A full simulation of:

  • Market scanning (using live/realistic data).

  • Scoring and opportunity selection.

  • Execution and trading logic (no real funds).

• Purpose:

  • First full preview of how Capture Bot:

    • Reads spreads from the engine.

    • Scores and filters them.

    • Decides when and how to “trade” in real time.

  • Let users see the decision process before any live capital is involved.

This is the bridge between “read-only engine” and “live execution bot”.

---

10.1.3 Next 2–7 Days – Whale Beta Access & Support Layer

Whale Beta – Limited-Capital Capture Bot Access

• Beta access to Capture Bot (with limited operating capital) is already available for:

  • $Capture holders owning more than 1.5% of total supply.

• Current access flow:

  • Request via the Capture Bot section on the website → https://capture-os.com/#capturebot

  • Or directly via email: [e-mail].

  • The team:

    • Verifies on-chain holdings.

    • Onboards user into the beta.

    • Assigns a dedicated account manager per whale.

• Constraints during beta:

  • Operating capital per account is capped to control systemic and technical risk while the bot is validated under real market conditions.

  • Strategy set and risk parameters are monitored closely by the team.

Support & Community Layer

Over the coming days, the support layer will expand:

• Telegram support goes live

  • Direct line to the team for:

    • Access requests.

    • Incident reports.

    • Configuration questions.

• Private whale chat opens

  • Gated group for >1.5% $Capture holders and beta users.

  • Used for:

    • Faster coordination during beta.

    • Sharing performance snapshots and updates.

    • Gathering high-signal feedback.

• Telegram-based access requests

  • Whales will be able to:

    • Verify holdings.

    • Request / manage bot access.

    • Coordinate with their account manager directly from Telegram, without relying only on email/web forms.

Support layer and product layer evolve in parallel: as more execution risk comes online, the human and comms layer gets tighter.

---

10.1.4 ~14 Days – Capture Bot v1 (Live Execution)

Capture Bot v1 – Full Roll-Out

Target: ~2 weeks from now.

• First production version of Capture Bot capable of:

  • Live execution on Solana DEXes.

  • Operating with unlimited capital at the protocol level (within per-user risk caps and constraints).

  • Hosted on our proprietary platform (not just scripts/CLI).

• What v1 includes:

  • Stable integration with the Capture Engine and screener/terminal.

  • Core strategy set:

    • Cross-DEX arbitrage on key pairs.

    • Initial simple loops (where safe and measurable).

  • Risk / control layer:

    • Per-user risk caps (per-trade and daily).

    • Circuit-breakers and kill-switches.

    • Monitoring of PnL, error rates, execution latency.

• What changes at v1:

  • Capture OS becomes fully operational end-to-end:

    • Scan → Score → Execute

      • Engine scans.

      • Scoring layer ranks spreads.

      • Bot executes within risk limits.

  • Token utility becomes tangible:

    • $Capture holdings define who can access the automated execution stack, not just the read-only engine.

---

10.1.5 Beyond v1 – Medium-Term Direction

(Not all of this is timeboxed, but it’s the direction of travel.)

• Broader DEX / aggregator coverage

  • More venues integrated into the engine and bot routing logic.

• MEV-aware & private execution improvements

  • More sophisticated routing / fee strategies.

  • Better defenses vs front-running / sandwiching.

• API & integrations

  • Structured API for funds/quants to consume:

    • Capture Engine signals.

    • Aggregated stats and historical data.

• Analytics & dashboards

  • Historical PnL breakdown per:

    • Strategy.

    • Pair.

    • Venue.

  • Alerting and reporting for institutional users.