Local agents · Claude Code, Codex, Doc D, R2D2
David's local agents do hands-on laptop work, dispatched through the Rack (https://www.dvo88.com/rack).
Agent roles
Who does what, in one line each.
WebCTO · cloud CTO surface
Cloud/operator CTO surface where it applies.
Codex
Coding and implementation helper; a lightweight second set of eyes when useful.
Claude
Coding, synthesis, and a lightweight second set of eyes when useful.
Gemini
Specialist helper, especially for GCP and the Google ecosystem when useful.
CIA · Chief Information Agent
Institutional knowledge layer for provider docs, prompting best practices, model specs/costs, agent-memory paradigms, and high-level routing architecture.
Parliamentarian
Institutional documentation alignment: agent .md files, drift detection, organization, publication, and currentness.
How work moves
The short loop for most work, and the optional heavier pattern for larger work only when warranted.
Normal work
- David
- The Rack
- lead agent / local agents / WebCTO
- implementation
- quick proof
- The Rack
- David
A short, direct loop for most work. Current work is filed on The Rack.
Important or larger work · only when warranted
- original implementation plan
- quick Codex or Claude plan challenge
- at most 1–2 iterations
- final implementation plan
- implementation
- quick Codex or Claude result check: was the intended thing built, and does it work?
Optional and proportional. This is a quality check, not enterprise process.
Capability targets
Tracked on the live capability board. Names only — current verdicts live at /api/infra/state.
- Capability board
- CTO operator workspace
- WebCTO cloud door
- WebCTO Telegram door
- Single CTO memory authority
- Approved cloud tool parity
- Backup and restore rehearsal
Proof sources
Reachable without a site session. Dashboards and other status APIs are gated (see the note below).
- getCapabilityStatus Cloud Function that returns checker-computed capability verdicts.
- /api/infra/status Current infrastructure and provider signal.