# ADR 0001 — Control Plane and Three-Plane Topology

**Status:** Accepted  
**Decision:** AWP is an Agentic Software Delivery Control Plane deployed as distinct Edge/Gateway, Control and Execution planes.

## Context

AWP must expose a web/API product, own durable software-delivery state and safely execute untrusted agents/CI. The Overdeck model mixed local workstation authority and execution too freely.

## Decision

```text
Internet
  -> Edge/Gateway: public ingress, auth/session ingress, webhooks, realtime fan-out
  -> Control plane: final authorization, domain/application, DBOS, PostgreSQL, providers, audit/events
  -> Execution plane: K3s AgentRuns, Workspaces, Fabro, ARC/CI jobs
```

Logical/code/trust boundaries exist from day one even when all planes share one physical cluster.

## Consequences

Positive: clear trust boundary, portable gateway/control, Kubernetes-specific execution, no normal workstation dependency. Cost: more explicit internal contracts and deployment units than a single web process.

## Rejected Alternatives

- single privileged monolith hosting agent processes directly;
- workstation-centric execution;
- fully serverless architecture that weakens durable control/execution needs.

## Increment Realization

I0 establishes all three logical planes; I1 proves live execution; later increments deepen them without changing authority.

## Supersession Rule

Any merge of public gateway and privileged control authority, or normal return to workstation execution, requires a superseding Decision and threat-model update.