Your Agents Need an Org Chart
Operates one abstraction layer above joelclaw's Inngest loop infrastructure — adds budget enforcement, hierarchical delegation, and org-chart coordination that system-bus doesn't have
The framing is unusually sharp: if OpenClaw is an employee, Paperclip is the company. Not a framework, not an SDK — a full company runtime, complete with org charts, reporting lines, monthly budgets, governance controls, and a ticket system that threads every agent conversation from task to goal to company mission.
Most multi-agent tooling attacks the individual agent problem: make the agent smarter, faster, more reliable. Paperclip attacks the coordination problem. What happens when you have 20 Claude Code terminals open and can’t track which one is doing what — and then your machine reboots and you lose all of it? The answer isn’t a smarter agent. It’s company infrastructure. Org charts with actual hierarchies. Monthly budgets per agent that cut off runaway spend when the limit hits. Heartbeats that wake agents on a schedule and push delegation up and down the hierarchy automatically. The architecture is provider-agnostic at the contract level: if it can receive a heartbeat, it’s hired. OpenClaw, Claude Code, Codex, Cursor, Bash scripts, HTTP endpoints — all valid.
Task checkout and budget enforcement are atomic — no double-work, no runaway cost, agents throttle automatically at their limit. Agent state persists across reboots so machine restarts don’t wipe context. Every tool call is traced; every decision is logged. You’re the board: approve hires, override strategy, pause or terminate any agent at any time. It’s a Node.js server with a React dashboard and a CLI — the usual stack for something trying to get real adoption fast.
The piece worth watching is Clipmart — a coming-soon marketplace for downloadable company templates. Full org structures, agent configs, and skills bundled into an importable artifact. The pitch is effectively npm for autonomous business units: browse pre-built companies, fork one, run it. If a company’s structure can be a reproducible, versionable artifact, you can share entire organizations the way you share libraries. That’s the interesting bet embedded in this project.
For joelclaw, the heartbeat model maps directly to cron-triggered Inngest functions, and the ticket/audit trail parallels the OTEL telemetry pipeline in system-bus. What Paperclip adds is the budget enforcement layer — per-agent spending limits with automatic throttling — and hierarchical delegation between agents. The 110+ durable functions in system-bus handle individual tasks well; Paperclip is what the layer above that looks like when it’s built out.
Key Ideas
- Employee vs. company abstraction — individual agents are employees; Paperclip is the company that coordinates them, not just another agent wrapper
- Heartbeat as the hiring interface — any process that can receive a heartbeat ping can join the org chart; completely provider-agnostic
- Atomic budget enforcement — task checkout and spend tracking happen together, preventing both duplicate work and runaway token costs
- Hierarchical delegation — goals flow down the org chart from company mission through management to individual agents; context flows up automatically
- Persistent state across reboots — agent context survives machine restarts, solving the “20 tabs lost on reboot” problem
- Clipmart — coming-soon marketplace for downloadable company templates as reproducible artifacts (versionable org structures + agent configs)
- Multi-company isolation — one deployment, many companies, complete data separation; useful for running a portfolio of autonomous operations
- Mobile-ready — designed to monitor and manage autonomous operations from a phone