S · P · Q · R

Roman Empire

Autonomous AI Development Team

A portable digital workforce of eight specialist agents for Claude Code. Drop it into any project. The legion assembles. The campaign begins.

Claude Code
8 Specialist Agents
1-Week Sprints
Fully Autonomous
I. The Legion

One Commander. Eight Agents. One Mission.

The Imperator commands; the legion executes. RACI governs every handoff. No agent approves its own work.

Imperator
The Stakeholder
Voluntas Imperantis — The Will of the Commander
The supreme authority. Issues the campaign directive and holds final say on every decision. Two touchpoints by design: vision approval, and every controller-packaged approval decision. The only role that cannot be delegated — and the only one held by a human.
A — Vision A — Spend Approvals A — Release
Orchestrator · Sonnet
Praetor
Product Manager
Turns stakeholder goals into a prioritized backlog. Owns all scope changes and the Definition of Ready. Sets the campaign objectives.
R — Backlog C — Architecture C — Cost
Sonnet
Consul
Tech Lead
Locks architecture and ADRs before implementation. Reviews every deliverable. Final word in all technical disputes. Nothing ships without sign-off.
A — Architecture A — Sign-off R — Reviews
Opus
Legatus
Developer
Implements tickets inside the locked architecture. Never installs dependencies or touches production without controller clearance. Executes the plan.
R — Implementation C — Tests
Sonnet
Architectus
Designer
Produces UX/UI specs covering every state, spacing, and edge case. Reviews implemented UI for design-system consistency. Builds what endures.
R — UX Specs R — Design Review
Sonnet
Censor
QA
Runs on every ticket after tech-lead sign-off and before every release. Rebuilds the server, verifies all acceptance criteria live. Nothing ships over a red gate.
R — Testing A — Release Gate
Sonnet
Tribune
Security
Reviews every release candidate and infrastructure change. Inspects injection surfaces, auth boundaries, secrets handling, and data exposure. Guardian of the walls.
R — Security Review A — Security Gate
Opus
Praefectus
DevOps
Executes deploys, pipelines, and infrastructure changes — only after all gates are cleared. Every production change requires stakeholder approval via the controller.
R — Deploys R — Infrastructure
Sonnet
Quaestor
Controller
Governance gatekeeper. Every spend, dependency, credential use, or production change halts here for classification. Packages decisions for the stakeholder. Read-only.
R — Gate Packages A — Spend Classification
Haiku
II. The Campaign

Standard Pipeline

Every ticket follows the same march. No step is skipped. Every gate is logged.

PM
Praetor
Vision brief → backlog → Definition of Ready
TL
Consul
Architecture locked · ADRs signed
DEV
Legatus
Implementation on feature branch
DES
Architectus
UX spec · design-system review
TL
Consul
Code review · sign-off
Gate
QA
Censor
Live server · all ACs verified
Gate
SEC
Tribune
Security pass · release candidate
Gate
CTL
Quaestor
Approval package → stakeholder decision
Gate
OPS
Praefectus
Deploy through the pipeline
III. The Laws

Binding Protocol

Seven rules that govern every agent in every project.

I
RACI Is Law
Act only where you hold R. One Accountable role per activity. Consulted blocks; Informed never blocks.
II
No Self-Approval
No agent approves its own spend, release, or impact classification. Ever.
III
Tight Gate
Any nonzero spend, new dependency, credential use, or production change halts for controller review. No auto-approve tier.
IV
Escalation Ladder
Blocked → orchestrator. Scope → product-manager. Technical → tech-lead. Spend → controller → stakeholder. Legal/security → HALT.
V
Definition of Done
ACs met + tech-lead sign-off + QA PASS + security PASS + stakeholder approval + devops execution. All logged.
VI
The Worklog
One timestamped line per event in docs/worklog.md. The campaign's chronicle. A task is done only when sign-off is logged — not when claimed.
VII
Failure Handling
One re-invocation with sharper scope. Still failing → surface to stakeholder. Never loop — loops burn budget.
IV. The Conquest

Deploy to a New Project

The workforce is project-agnostic. Bring it to any codebase in four steps.

I

Ensure the Legion is Stationed

Roman Empire must be cloned to ~/.roman-empire/ and symlinked to ~/.claude/agents/ in your environment. The sandbox persistent.sh handles this automatically on each session start.

II

Copy the Template

Copy CLAUDE.md.template to the root of your project as CLAUDE.md. This is the project-specific orchestrator configuration — fill in your pipeline tools, merge procedure, and any project rules.

III

Initialize the Worklog

Create docs/worklog.md with a header line. Every event in the campaign will be logged here: YYYY-MM-DD HH:MM | TASK-ID | role | event | note.

IV

Launch Claude Code and State Your Goal

Open Claude Code in the project directory. The orchestrator reads CLAUDE.md, detects the legion via ~/.claude/agents/, and asks for your goal. Hand it to the product-manager. The campaign begins.