PROJECTS · CONTROL PLANE1/4
Projects as the enterprise control plane
- Every operating environment is represented as a Project — its environments, missions, workflows, discoveries, compliance posture, runtime health, topology, learning state, audit history and connected capabilities in one place.
- Operators approve meaningful changes instead of watching dashboards.
- Sidekick is the conversational interface into the control plane — it proposes and follows missions, and never mutates production silently or bypasses the policy path.
PROJECTS · CONTROL PLANE2/4
The Project Manifest — desired state
- Configuration is a signed, declarative, versioned Project Manifest, not a Terraform state file or a kubeconfig.
- It describes deployment identity, tenants, capabilities, runtime versions, policy bundles, model providers, infrastructure endpoints, approval policies and execution budgets.
- It carries references, never secrets — secrets stay in Vault, a cloud secret store or a local encrypted keychain.
- Synced to a lightweight Project Registry (
~/.sidekick/projects/ locally; Git / object storage / a database in the enterprise), so cloning a project recreates the whole operating environment while Mission Runtime reconciles desired and actual state.
PROJECTS · CONTROL PLANE3/4
Three records, one principle
- Project Manifest — desired state: declarative, signed, versioned, portable, no plaintext secrets.
- Provider state — implementation state: Terraform/OpenTofu, Kubernetes, Helm, migrations and cloud resources stay authoritative in their own controllers.
- Mission ledger — execution evidence: an append-only, hash-chained record of the compiled plan, approvals, diffs, tool calls, artifact digests, verification results and rollback/compensation — tamper-evident, so you can prove it wasn't rewritten after the fact.
- The governing principle: the manifest anchors intent, provider tools own implementation state, and Mission Runtime owns the evidence of execution.
PROJECTS · CONTROL PLANE4/4
Software delivery — one governed use case of the workspace
- The same Missions, Attention and Discovery, applied to infrastructure — delivery is one enterprise use case of Projects, not the definition of it.
- CI: a manifest change opens a planning mission — schema + policy validation, ExecutionPlan compilation, native previews (
terraform plan, Helm diff, server-side dry-run), and a PR plan report for human approval. - CD: an approved, signed commit becomes a deployment mission — acquire an environment lease, re-plan against actual state, gate, deploy progressively, verify, then release, roll back, or compensate.
- Drift + compliance: Discovery Runtime continuously compares intent with observed state; drift and missing controls become governed discoveries — observe, reconcile automatically, or request approval.