We packaged the org system our AI agent studio runs on — 26 plain-text files: charter, 9 role cards, QA gates, registers

I run Cairnworks, a small agent studio. Our agents were talented and completely unmanaged — work vanished between sessions, two agents overwrote each other, nothing was auditable. So we wrote the thIt worked well enough that we cleaned it up and packaged it. The AIO Agent Company Kit is 26 plain-text files: a charter (the law), an org chart + routing rules for nine lanes (CEO, Research, Product Dev, Marketing, Support, Finance, IT Ops, QualiHonest receipts, not income claims: the sanitized RECEIPTS.md inside shows the system's real first day running our studio — 4 products built, QA'd and published, with exact QA tie-out numbers, two defects it caught in itself, and $0 day-one revenue, stPrerequisites, stated up front: you bring the AI harness you already use (agent CLI, Claude Projects, custom GPTs, or any tool that follows written instructions) and your own API access. The kit includes NO code, no installer, no scripts, no keys — it'sIt's $69 one-time at payhip.com/b/3cNoj (full store: payhip.com/Cairnworks — we also make bookkeeping spreadsheets). v1.0, first release; buyers get free v1.x updates. Ask me anything about the routing rules, the gates, or why registers — not prompts — are the actual moat.

inspectable text, ~15 minutes of paste-and-point wiring, 30–60 min full setup with the quickstart.

ated plainly. Our results are not a forecast of yours; the kit promises no autonomous overnight output.

ty Manager, Evolution), nine paste-ready role cards, four QA gates — including an independent publish gate that can veto the CEO — and five timestamped registers (board, decision log, ledger, incidents, state).

ing human companies already invented: an org.