Rename every one of them, delete the ones your business does not have, add the ones it does.
The chart is not an illustration — it is the configuration, and it is what the agents actually obey.
01
Work moves as typed hand-offs
An agent does not "mention" another agent. It passes a baton — who it goes to, the title, the input, the reason, the priority, and whether it must wait for the answer. The system turns that into a real task and a ledger row.
Two agents asking the same worker for the same thing attach to one task instead of creating two. An agent may only hand off to the receivers its role actually lists. Nothing gets lost in a thread.
02
One gate. Everything goes through it
Every action in the product — from a dashboard click, a scheduled cadence, an incoming customer message, the AI brain, or an outside system — enters through a single function. It decides one of three things: run it now, hold it for you, or run it under a permission you already signed.
There is no second path. That one property is what makes the rest of this page a specification rather than an aspiration.
03
Three risk classes — and one that can never be automated
Reversible — drafts, notes, CRM edits, updating a number. Runs on its own once the agent has earned it.
Irreversible — sending a message, placing a call, ordering stock, turning on ad spend. Needs you to type EXECUTE, or an active mandate.
Affects a person — flagging a customer, blacklisting an account, advancing or declining a candidate. A named human decides every single time. No autonomy level and no mandate can ever cover it.
An agent may raise its own risk class. It can never lower one.
04
Autonomy is earned, not switched on
No agent starts trusted. It climbs a staircase, and only for reversible work.
Stage 1Asks you first. Every time.
Stage 2Acts, you review. Earned after three reviews.
Stage 3Runs itself. Earned after eight.
A rejection counts exactly as much as an approval: what the staircase measures is how often a human actually looked, not how often the agent turned out to be right. Trust is earned by being checked — which is the only way trust is ever actually built.
05
Mandates — a signed permission with a hard edge
When you do want an agent acting alone on something irreversible, you sign a mandate rather than flipping a switch: one action, one agent, one scope (this segment, these stages, these tags, this intent), one script, a daily cap, and an expiry date.
Signing takes a typed EXECUTE. Every use is counted against the cap and linked back to the mandate. One step outside the scope, or one over the cap, and it queues for you like anything else.
06
A record that cannot be quietly edited
Every consequential event is written into a hash chain — each entry sealed over the one before it. Re-verifying the whole chain is one request: it either passes, or it names the row where it stops.
Stated precisely: this is tamper-evident, not tamper-proof. An alteration is detectable, not impossible. We would rather tell you the true property than the impressive one.
07
Loops — your business cycles, running themselves
Attention → lead → conversation → offer → order → cash → repeat. A loop is that chain written down as an ordered set of agents, started on a schedule or on demand, with the baton's position visible at every step.
A loop is not a way around the gate. A stage that needs your decision pauses the whole loop, and it resumes at exactly that point when you decide — never by skipping you.
08
Graphs — because real work branches
A lead scoring 80 goes to the closer; one scoring 30 goes back to nurture and comes round again next week; five hundred leads have to fan out and rejoin; a campaign that underperforms loops back to creative instead of marching on to reporting.
Graphs put that in the open: branches, fan-out, cycles, sub-graphs, and a hard human interrupt as a node type. Every step checkpoints, so a run can be resumed, forked or replayed.
The alternative is hiding the branch inside a prompt, where nobody can see it, audit it, or change it.
09
One warehouse. Every number carrying its source
Your CRM knows the leads, your accounts know the invoices, your counter knows the cash, your service desk knows the open jobs. None of them knows the business, because those facts have never sat at the same grain in the same place.
Boardroom pulls one row per source, per metric, per day — and holds three rules: nothing is invented, a day's fact is immutable, and every figure carries where it came from.
A system that is down produces a gap, and a gap is drawn as a gap — never as a zero, because a zero is a claim that the number was zero.
10
Your industry as configuration — not as a rewrite
A pack is your company written down: identity, the rules you must not break, the revenue staircase, your funnel with one metric and one owner per stage, the org chart, the playbooks, the call scripts, the follow-up cadence.
That is how one product serves a manufacturer, a pharmacy, a clinic, a distributor and a software company without any of them inheriting somebody else's workflow.
A regulated pack carries law, not just tone: our pharmacy pack refuses dosage advice, blocks reminders to anyone who has not opted in, keeps calls inside legal hours, and lints prescription-drug words out of marketing — enforced in what the agents do, not printed in a prompt and hoped for.
11
It reaches customers where customers already are
WhatsApp, with the messaging-window rules respected. Outbound phone calls with a real dialogue, an outcome classified at the end, and a hand-off to the right human or agent. Email. Slack and push, for you.
If a channel is not connected, the reply is held with the exact reason. It is never faked, and you are never told something went out that did not.
12
It runs your existing systems, not just its own
Boardroom discovers the software your business already runs, probes what each one can answer, and turns those capabilities into actions the agents may take — through the same gate as everything else.
Your billing system, your CRM, your accounts, your service desk. The agents work your stack; you do not re-key your business into ours.
13
Seven rooms. Four nouns. One verb
Mission · Agent · Task · Decision — and "ask the company". Today, Decisions, Work, Company, Market, Integrity, Medic. Every screen answers three questions in the same order: what is happening, does it need me, what do I do about it.
Needs-you is the first block on the screen, always — even on the mornings when the numbers are more interesting.
14
Integrity — it audits your own books, and argues with itself
A room whose only question is "is anything wrong with my money". It sweeps the business against a catalogue of detectors — round-number payments, a supplier and an employee sharing a bank account, a refund with no sale behind it, a record quietly edited after the fact.
Every finding arrives with a probability, the evidence, and the most likely innocent explanation stated beside the guilty one. You answer; the arithmetic re-calibrates against your answers rather than against our opinion of your trade.
A finding nobody can check is noise wearing a lab coat, so each one names the exact record to open. It reads the other systems and writes to none of them.
15
Medic — it watches its own health, and asks before it fixes
Every app in the fleet answers a deep health check that says what is wrong, not just that something is. Medic reads them all in one screen and can propose the repair.
A repair runs by itself only when it is reversible, idempotent and touches no data. Everything else is a proposal you approve — through the same gate as every other action, on the same record.
16
It works without an AI key, and it works offline
Every role ships with a deterministic playbook, so the company runs, briefs and escalates on day one with no AI subscription at all. Connect a model and the same roles get sharper — governed identically, never more freely.
It runs on your own machine, and its licence is verified by signature on the spot. Nothing phones home to ask whether you are allowed to open your own business.