← redevops.io
Control plane · resource model · redevops.io

Projects — the Control Plane

The durable resource model that anchors every mission.
Projects is not merely the UI. It is the control-plane resource model: desired state you declare, observed state the runtime reconciles, and the ledger of everything that happened in between.

Projects is to rAIls what a control plane is to a cluster. You declare desired state in a Project Manifest; Discovery, the Execution Planner, Mission Runtime and Context Runtime reconcile toward it as governed missions; and Projects keeps the authoritative record — approvals, discoveries, learning state and an audit ledger. Sidekick is its conversational Mission Supervisor, and every mutation it makes still runs through Mission Runtime.

The Project Manifest — desired state

A project is anchored by a versioned manifest that expresses desired decision policy, not mutable execution state. It is the one place mandate, universe, objectives, constraints, approval policy and connected capabilities are declared — and it is signed and version-controlled like any other infrastructure artifact.

apiVersion: redevops.io/v1
kind: Project
metadata: { name, tenant }
spec:
  environments: [ dev, staging, prod ]        # promotion path
  universe / scope
  objectives
  constraints                                 # policy bundle bindings, budgets
  approval: { side_effecting: required }     # human gates
  capabilities: [ ... ]                       # granted, denied by default
  data: { connectors, residency }
  execution: { topologyPolicy: learned, verification: required }

Three records, one principle

The control plane keeps three separate records so that what you want, what is true, and what happened never blur together.

Project ManifestDesired mandate — universe, objectives, constraints, approval policy, capability grants. Declared, versioned, signed.
Provider / Portfolio stateObserved state — holdings, orders, deployments, NAV, environment topology, source timestamps. Written only by governed missions.
Mission ledgerWhat happened — evidence snapshot, ExecutionPlan, approvals, artifacts, decisions, verification and outcomes. Append-only and replayable.

What a project holds

Everything an operator or an auditor needs to run and account for the system lives as a first-class resource under the project — not scattered across dashboards.

ResourceWhat it is
Environmentsdev / staging / prod with a promotion path and per-environment policy
Tenant & deployment identitywho owns this project, which cluster/tenant it runs in, workload identity
Desired vs observed statethe manifest vs what the runtime actually reconciled — drift is a discovery
Mission historyevery mission run against the project, replayable from the ledger
Discoveriesthe Discovery Runtime's ranked proposals for this project
Policy bundlescapability eligibility, residency, budgets, approval rules — applied before selection
Connected capabilitiesthe models, retrievers, tools and humans this project is granted (denied by default)
Learning statethe shadow/promoted policy, offline gate and per-regime routing health
Approvalsthe human-decision inbox — every side-effecting node waits here
Audit ledgerthe append-only record of decisions, side effects and outcomes
Sidekick surfacethe conversational Mission Supervisor bound to this project
CI/CD integrationmanifest-anchored delivery — a deploy is itself a governed mission; drift re-opens one

Manifest-anchored delivery

Because the manifest is desired state and Mission Runtime is the only thing that changes observed state, delivery and compliance fall out of the same loop: a change to the manifest opens a governed deployment mission; the Discovery Runtime watches for drift between desired and observed state and re-opens a remediation mission when they diverge; every step lands in the audit ledger.

Declare desired state. Let governed missions reconcile it. Keep the ledger of everything in between. That is the whole job of the control plane.

See also: the canonical platform architecture · the Projects deck · the Quickstart.

redevops.io — Projects Control Plane · the control-plane resource model. © 2026 redevops.io