In development Community beta target Q1 2027 View roadmap
ANDIPDistributed infrastructureJoin Beta
Home/Docs/Development Roadmap
Architecture specification · not released product behavior

Development Roadmap

The architecture source roadmap from repository verification through single-server, multi-VPS, recovery, mixed workloads and beta readiness.

Architecture baseline · subject to change

Engineering phases

The sequence below reflects the architecture baseline. Only upstream repository evidence is marked verified; that is not evidence that the ANDIP implementation is complete.

  1. Phase 0 — Repository Verification and Architecture Baseline: Pin upstream source and licenses, run the supported checks, agree adapter contracts and record architecture decisions. Gate: Verified upstream repository source does not mean ANDIP implementation is complete. VERIFIED SOURCE
  2. Phase 1 — Single-Server MVP: Create a local control API, durable state, one worker, a deterministic mock agent, artifact capture and cleanup. Gate: A restart-safe vertical slice; planned, not reported as delivered. PLANNED
  3. Phase 2 — Multi-Agent Execution on One Server: Add resource reservation, concurrency caps, cancellation, and isolated workspaces for parallel tasks. Gate: No overcommit and per-attempt workspace separation must be demonstrated. PLANNED
  4. Phase 3 — Distributed Execution Across Multiple VPS: Add worker enrollment, heartbeat, capacity placement, cordon/drain, durable leases and fencing. Gate: Multi-VPS behavior and safe worker-loss reassignment require tests. PLANNED
  5. Phase 4 — Security, Reliability, Recovery, and Budget Controls: Add scoped secrets, checkpoints, approval/audit, cost metering and failure-recovery scenarios. Gate: Isolation, recovery and hard budget controls require reproducible validation. PLANNED
  6. Phase 5 — Browser Integration and Mixed Workloads: Integrate an optional browser adapter, isolated profiles, policy hooks, verification and multiple resource classes. Gate: Approved-site scenarios and browser profile isolation require validation. PLANNED
  7. Phase 6 — 100-Agent Concurrency Validation: Run repeatable load scenarios, separate mock concurrency from real model/browser workloads, inject failures and publish raw evidence. Gate: 100 Concurrent Agents — Engineering Validation Target. No pass is claimed. TARGET
  8. Phase 7 — Community Beta and Commercial Readiness: Prepare installation, upgrade, backup/restore, security and license review, runbooks and beta readiness. Gate: Community Beta Planned for Q1 2027; commercial readiness remains conditional. TARGET

Beta target

Community Beta Planned for Q1 2027. Development milestones and beta availability are targets and may change as engineering validation progresses. No fixed day is announced.

Concurrency validation

100 Concurrent Agents — Engineering Validation Target. Validation distinguishes simulated processes from model requests and browser sessions, checks actual RUNNING work, and measures the stated workload, queued work and failure conditions.

Important: Do not mark any ANDIP implementation phase complete merely because an upstream repository contains related local functionality.

All documentation · Full architecture page · Roadmap