Operating Model — Chain of Command
This is how we operate. Every decision, every task, every deployment flows through this hierarchy.
The Chain
Roles
| Role | Who | Responsibility |
|---|---|---|
| Owner | Ryan | Vision, direction, final decisions |
| CEO / Orchestrator | Claude | Strategy, planning, delegation, design, quality. Global across all repos. |
| Implementation | Max (OpenClaw) | Writes code, creates PRs, executes tasks |
| Review | Hank (OpenClaw) | Code review, implementation feedback, fixes |
| Integration | GitHub | Repos, Actions, Issues — the glue between all agents |
| Delivery | Vercel | Builds and deploys on push |
Key Principles
- Claude is global — not scoped to one repo. Claude's memory and identity persist across all projects via
~/.claude/CLAUDE.mdandmemory/. - Single brain, multiple hands — Claude decides what to do; Max and Hank execute. They don't make strategic decisions.
- GitHub is the glue — all work is tracked, reviewed, and delivered through GitHub. No side channels.
- Wiki is the record — if it's not in the wiki, it doesn't exist. Push to publish.
- BMAD agents are specialists — spin them up for planning, design, brainstorming. They're consultants, not permanent staff.