DevelopmentAI Control Plane
Warp-era Workflow
Warp-era terminal workflows treat the terminal as an operations cockpit, not as
Purpose
Warp-era terminal workflows treat the terminal as an operations cockpit, not as a place to improvise irreversible changes.
Roles
| Surface | Role |
|---|---|
| Warp / terminal agents | Local command execution, logs, runbooks, previews, quality checks. |
| Codex / Cursor / Claude Code | Scoped coding workers. |
| CI | Independent feedback for type, lint, tests, architecture, and builds. |
| Storybook / UI Workshop | Visual feedback for component and shell UI work. |
| Architect AI | Planning, scope, task graph, worker prompt generation. |
| Integrator AI | Read-only merge and release-risk review. |
Rules
- Keep command output tied to a task graph or run log when the task is non-trivial.
- Prefer documented scripts over ad hoc command chains.
- Never write secrets, tokens, account IDs, or private environment values into the repo.
- Do not mutate production deployments, DNS, Access policies, or databases without explicit human approval.
- Promote repeated terminal workflows into docs or scripts only after they are stable and reviewed.
Future Runbook Areas
- Local dev startup.
- Preview deployment checks.
- Cloudflare deployment preflight.
- API docs exposure checks.
- Architecture report regeneration.
- Incident notes and recovery steps.