1
1. State Management (we are here)
- Units CRUD + locking
- HTTP backend proxy and S3-compatible endpoint
- CLI and Terraform provider to manage OpenTaco itself
- Storage in S3 (bucket-only; drop-in with existing S3 backend bucket)
- Cross-unit dependencies + status API
2
2. Remote Runs (Next)
- CLI‑driven remote runs; server schedules on external compute
- CLI watch/logs; runs respect locks; artifacts/logs retrieval
- See: Remote Runs (How it would work)
3
3. VCS Integration & UI
- Connect repos; PR events → plan preview; minimal UI to manage repo connections and view runs
- See: VCS Integration & UI (How it would work)
4
4. Drift Detection
- Read‑only checks; drift status surfaced in CLI/UI; non-blocking
- See: Drift Detection (How it would work)
5
5. Policies
- Policy packs; evaluation gates before apply; audit trail
- See: Policies (How it would work)