ADR-0005: k3s Stays Stable Across Modes in V1

Status: accepted

Context

k3s provides platform/control-node duties. Starting and stopping it during every mode transition would add operational churn before there is evidence that it is needed.

Decision

Keep k3s.service stable across desktop, studio-local, and compute in v1.

Express mode differences through platform.slice budgets first. Defer labels, taints, workload intensity policies, and service lifecycle changes until a real platform workload requires them.

Consequences

• Mode switching has fewer moving parts.
• k3s remains available during desktop and compute operation.
• Platform pressure must be bounded through slice policy until richer k3s mode behavior is justified.