Repository navigation
[Roadmap] Deliver the Veer alpha control plane #1
Description
Outcome
Deliver an independently operable alpha that manages application intent across Kubernetes and AWS with explicit security, recovery, cost, and release evidence.
Scope
- Coordinate the foundation, API, security, reconciliation, provider, automation, and operations workstreams.
- Use native sub-issues for scope and native dependency edges for sequencing.
Acceptance criteria
- Every epic exit criterion is satisfied with linked evidence.
- A clean installation completes CLI and GitOps lifecycles across both initial providers.
- Security, recovery, cost, upgrade, and teardown gates pass from signed release artifacts.
Test and evidence
- All child epics are closed with their native sub-issues complete.
- The final qualification report links CI runs, artifacts, recovery exercises, and residual risks.
Dependencies
- None.
Activity
gnanirahulnutakki commentedon Sep 9, 2026
Gap review against DuploCloud (read-only inventory of a live portal, its docs, Terraform provider, and duploctl) is tracked in the parity roadmap #98. The alpha plan here is a control-plane kernel; parity work is grouped into epics #99, #100, #101, #102, #103, #104, #105, #106, #107, #108, #109, #110, #111, #112, #113, #114 and needs the decisions listed on #98 (hierarchy mapping, imperative actions, browser UI, provider breadth).