Hire it, brief it, set its limits
There is no bot to build and no workflow to draw. An employee arrives knowing its job. What it does not know yet is your business - and that is what you tell it.
From hiring to the record
Step 1 of 7
One screen: a name, a voice, and what it will know, filled in from your Brain. The rest is asked on its page later.
The screens are from a sample business.

- A name and a voice, from the role's card - yours to change.
- What it will know, filled in from your Brain, each fact saying where it came from.
You set the limits. The system enforces them.
Each skill an employee has sits at one of four levels, and you choose which. The limit is enforced by the platform on every action - it is not a request the AI may ignore - and each action records the level that applied and why.
- L0 · Suggests onlyPrepares the reply or the action, and leaves the doing to you.
- L1 · Drafts for approvalPrepares the work and places it in your approvals list. Nothing happens until you say yes. Refunds, invoices and messages to customers start here.
- L2 · Acts, then tells youDoes it, then lets you know what it did.
- L3 · Acts within a budgetGets on with it quietly, as long as it stays within the budget you set.

Approve from wherever you are
Everything that needs a person waits in one list: what the employee wants to do, the order and the amount, why it is asking instead of acting, and three choices - approve, edit and approve, or decline. The same card works on your phone, and on WhatsApp if you would rather not open anything.


Test it before customers meet it
Write down what a good conversation looks like - what a customer says, and what must be true afterwards - and run it. Each check passes or fails with the full conversation beside it. Change the employee after a passing run, and you are told the result is out of date.


Then see what it did
This is one row of the record, and it looks the same wherever the action appears - in a conversation, on a task, in the approvals list. One account of what happened, everywhere.


Changes stay in draft until you publish
Customers keep talking to the version you published while you edit. Every version is kept, with who published it, what changed and why - and you can restore an earlier one in a click.







