Record the architecture for moving code implementation AFK, decided in a
design/grilling session. The owner wants the human-in-the-loop boundary to
stop at design + spec: once an issue is triaged ready-for-agent, an agent
should implement it test-first, push it, and see it to a healthy deploy on
its own, escalating only when it can't proceed.
Decisions captured:
- claude-agent-service is the control plane (poller + watcher + safety);
a dedicated in-cluster T3 Code instance is the executor + cockpit, because
T3 can only show sessions it launched itself -> we dispatch into it
(ADR 0003).
- AFK code pushes straight to master; on a broken deploy it fix-forwards
then freezes the broken state for forensics rather than reverting
(ADR 0002).
- Implementation agents use persistent per-repo checkouts + git worktrees on
SSD-NFS for warm caches, reversing the throwaway-clone rule for this path
because concurrency is serial-within-repo (ADR 0004).
Pilot-gated: five integration unknowns must be validated against a dedicated
T3 instance before the poller is wired. No code yet.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
