Operations
From local loop to production runbook.
Operations deserves its own lane: deployment shape, configuration, production readiness, Kubernetes rollout, and incident recovery should not be hidden inside architecture or roadmap pages.
Start the daemon, WebUI, and TUI, then validate the full workspace loop.
Track Deployment shapeChoose embedded workers first, then split API, controller, queue, and worker planes when scale needs it.
Track Production readinessReview storage, credentials, observability, backups, rollout, and failure-mode requirements.
Track Kubernetes rolloutUse the checklist and runbook as the deployable operational contract.
Runbook shelf
Keep deploy-time facts close to failure recovery.
These pages form the practical operating surface: configuration, split deployment, queue reliability, and the Kubernetes runbook.
Operational context
Tie runbooks back to product ownership.
Operational docs should stay practical, but they need clear links back to the architecture, API, and roadmap decisions that shape them.
Use architecture docs to understand what should run in clients, control plane, workers, and storage.
API Check operational endpointsUse API docs when deployment behavior affects workspace, session, run, storage, model, or stream contracts.
Roadmap Decide what is ready nextUse roadmap docs to connect operational gaps to worker scale, reliability, and product maturity work.