ANDIP Documentation
A public technical guide to the proposed distributed infrastructure platform. Specifications describe design intent; they do not imply that the product or an API is released.
Document status: Derived from the architecture baseline audited 2026-10-08. Interfaces and implementation details are subject to engineering validation and change.
Start with the system model
ANDIP aims to coordinate projects, tasks, adapters and already-provisioned VPS workers through a durable control plane. Explore the component map first, then open the execution, scheduling, isolation and recovery documents.
System architectureComponents, data ownership, worker boundaries and deployment direction.Control planeRequest, identity, workflow, policy, scheduling and durable state responsibilities.Worker architectureEnrollment, health reporting, execution, networking and cleanup.Agent lifecycleTask and attempt states, adapters, verification and terminal conditions.Task schedulingCompatibility, resource fit, reservation, leases and backpressure.Execution isolationWorkspace, container, browser profile, secret and egress boundaries.Failure recoveryLease reconciliation, checkpoints, side effects, fencing and review.Monitoring & costHealth signals, usage accounting, budgets and concurrency test evidence.Development roadmapThe phased engineering gates and the Q1 2027 beta target.Architecture FAQConcise answers on project status, Kubernetes, recovery, licensing and beta.
Status vocabulary
“Verified source” refers only to an audit of upstream repository material. “Planned” describes proposed ANDIP work. “Under validation” identifies an engineering question still requiring evidence. None of these terms imply that the public website is an operational control plane.
Related links
Architecture overview · Open-source integration · Development roadmap