Projects

13 slides · the Runtime Workspace + Control Plane

Projects is the human workspace over the Runtime stack.

Missions are where work executes. Workflows define repeatable operating intent. Discovery shows what changed or was learned. Attention shows what needs a human. Sidekick lets you work across all of it conversationally.

PROJECTS · WORKSPACE1/9

Projects is the Runtime Workspace

  • The human-facing workspace across rAIls.
  • Missions are the core execution surface, but Projects also shows workflows, discoveries, attention, connected capabilities, activity and project-level state.
  • Sidekick is the conversational interface across the workspace.
  • Projects renders Runtime truth; it does not maintain a parallel operational reality.
PROJECTS · WORKSPACE2/9

Built around governed work

  • We evaluated generic project-management tools and automation UIs.
  • None naturally model durable Missions, approval gates, evidence, replay, Discovery, or Runtime state.
  • Projects is therefore the native workspace for governed autonomous work.
  • It is not Jira, Zapier or a chat wrapper.
PROJECTS · WORKSPACE3/9

A Project contains many kinds of Runtime state

  • A Mission is one concrete execution.
  • A Workflow is reusable operating intent.
  • A Discovery is something the system has found that may affect current or future work.
  • Attention is everything the system needs a human to resolve.
ProjectMissionsWorkflowsAttentionDiscoveriesConnected capabilitiesPolicies + authorityActivityRuntime configuration
PROJECTS · WORKSPACE4/9

Missions remain the execution core

  • Missions are still the primary unit of governed work.
  • Create, inspect, approve, retry, replay and verify from Projects.
  • Mission state streams directly from Mission Runtime.
  • No mirror database that can drift.
scandoneplandoneprovisionhuman approvalconfigurequeuedverifyqueuedthe Graph view — one node holds for sign-off
PROJECTS · WORKSPACE5/9

Workflows and Missions are different

  • Workflows describe reusable operating patterns.
  • Missions instantiate those patterns against current state.
  • The logical workflow can stay stable while physical providers change.
  • Projects shows the workflow; Mission EXPLAIN shows the resolved execution.
Customer Refund WorkflowMission #4821HubSpotStripeSlackStripeWhatsAppthe workflow stays stable while the Mission resolves providers
PROJECTS · WORKSPACE6/9

Discovery belongs in the same workspace

  • Discovery surfaces findings, evidence changes, contradictions and drift.
  • Findings can link directly to affected Missions and Workflows.
  • Users do not need a separate product to understand what the system has learned.
  • Projects becomes the common place where execution and discovery meet.
PROJECTS · WORKSPACE7/9

One Attention queue across Runtimes

  • Approvals, failed verification, missing credentials, ambiguous discoveries and policy exceptions all surface in one place.
  • Users should not need to know which Runtime produced the issue.
  • Attention answers one question: what needs me?
  • Every action still resolves through the owning Runtime.
PROJECTS · WORKSPACE8/9

Mission detail stays deep and inspectable

  • Summary · Tasks · Timeline · Evidence.
  • Graph · World State · EXPLAIN · Replay.
  • Every node shows why it was chosen: capability, cost, policy, evidence.
  • Human-readable operational view first; Runtime-native inspection one click deeper.
PROJECTS · WORKSPACE9/9

Why Projects

  • One workspace for Missions, workflows, discoveries, approvals, capabilities and Runtime state.
  • Sidekick lets you ask, configure, explain and act conversationally.
  • Projects makes autonomous work visible, inspectable and steerable.
  • The same workspace works for deploys, customer operations, finance, research, audits and other governed processes.
The enterprise control plane
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.