Who writes what
HoBo splits cleanly along the lines most teams already have. Each role owns a clear artifact or surface.
| Role | You write / own | The artifact answers |
|---|---|---|
| Developers | Bindles, Trails | What is this app, and what does it need? |
| Platform Engineers | Camps, Yards, Junctions, Matching | Where may apps live, and how are those places run? |
| DevSecOps | Policy packs, guardrails | What is allowed — and what may cross a border? |
| SREs | Runbooks, SLOs | How do we detect, diagnose, and safely fix? |
| FinOps | Budgets, showback expectations | What does it cost, and is the move worth it? |
| Agents | Scoped tasks via SDK/CLI/MCP | What can an autonomous principal do under policy? |
Credentials and audit trails are not role docs — see Security → Agent credentials and Observability → Agent audit.