Agent System
The jjk-workspace uses a multi-agent Claude Code architecture (ADR 0009). Each agent has a clearly scoped role with explicit boundaries — “Not X; that’s Y’s job” prevents overlap.
Agent definitions live in .claude/agents/ and are assembled here at build time.
Agents
| Agent | Role |
|---|---|
| ash | Content trimming — proposes cuts, never rewrites |
| bastion | Security hardening and threat modeling |
| beacon | Frontend error surfacing strategy |
| bryce-fontaine | Creative direction for blog post design |
| canary | Backend error observability audit |
| cartographer | Spec + shared/ alignment checks |
| curator | Content pipeline audit (frontmatter, links, headings) |
| dispatch | Security audit of Cloud Functions |
| ernest | Satirical style guardian — deadpan voice gate |
| foundry | Firebase setup and configuration |
| garrison | Dependency and supply chain review |
| herald | CI/CD pipeline (Cloud Build) |
| hex | CSS and styling specialist |
| inspector | Project-wide compliance sweep |
| ledger | Data modeling and Firestore schema |
| lyle | Scheduling and publication logistics |
| oracle | Analytics and GDPR compliance |
| prospector | Terraform drift detection |
| research-gemini | Research offloading to Gemini |
| scout | In-file code hygiene |
| sentry | Frontend/backend boundary audit |
| usher | Onboarding and context assembly |
| vera-redline | Technical editing and copy review |