declare your team. watch it run.
Your org chart is a file you commit.
PaperAgents is the room an entrepreneur walks into. You don't script your company — you declare it: a team of small specialist agents for sales, support, ops, and books, each written in plain TOML.
A long-running watcher keeps the live team matched to that file. Edit the manifest, apply it, and everything downstream — agents, routing, budgets, diagrams — moves with it. No team structure exists anywhere except as a consequence of what you declared. Same Sealed Super Skills underneath as the rest of the stack — a different surface, for a different operator.
Take Northfleet, a regional trucking company: declare the
team you want in one file, apply it, and the platform reconciles
the running agents to match — a watcher closing the gap forever after.
Press apply and watch the manifest become an org-chart.
Zoom into one agent. The dispatch SSM watches a load board over TCP, prices each lane against a live rates feed, and brokers only the loads that clear margin — the rest it skips.
A team is a TOML file, version-controlled. Idempotent apply, graceful drain, rollback.
The platform closes the gap between desired and observed — continuously, observably.
Each team carries its own RAG corpus. Dispatch, billing, safety — no cross-bleed.
A long-running daemon surfaces drift the moment observed ≠ desired.
Edit the file. The company reconciles. Your whole org, version-controlled.
Built on the open-source Paperclip AI platform (MIT). Any agent, any runtime, one org chart — and a watcher keeping it honest.
A team is a config file, not a script. Idempotent apply, graceful drain, and rollback are first-class. Git-commit your org chart.
A long-running process that watches desired vs observed state and surfaces drift the instant they diverge.
Each team has its own corpus. Isolation is a contract — sales context never bleeds into books.
Small purpose-built agents handle the volume; frontier models step in on demand; ARAIL runs original research when the answer doesn't exist yet.
Spend is attributed to the declared escalation path, so every dollar maps to a team and a task.
Org diagrams and audit trails are generated from the manifest — never hand-drawn, never stale.
If it isn't in the file, it isn't running.
One source of truth fans out into the running team, the cost report, the generated diagrams, and the audit trail. Change the file, and every downstream artifact moves with it — no manual sync, no drift.
A non-engineer can run a team. An operator can review a pull request against the org chart. That is what declarative does for a business.
declares the team, the routing, the budgets, and the diagrams. Apply it; the platform reconciles the rest.
What if your whole company was version-controlled?
Write the manifest, apply it, and watch a team of specialist agents come up to spec.