Documentation / Working with Genie
What Genie will never do
Eight actions are refused at every tier, with any confidence, after any amount of good behaviour.
The eight
| He will never | Because |
|---|---|
| Approve billable time | You are charging a client for it |
| Commit to a client | A promise is made by a person |
| Attest compliance | A legal representation |
| Act unsupervised on a domain controller or identity system | The blast radius is everyone |
| Send anything to a client | He drafts; you send |
| Delete or destroy client data | Irreversible |
| Declare a security incident | It starts a legal clock |
| Resolve his own pending item | An agent that closes its own request for help has no boundary |
Enforced where it cannot be talked around
These are checked at the single write path every action passes through, before the tier is consulted — so a permanent refusal is never reported behind an appealable one.
Several are database constraints rather than code. The wrong state is unspellable, not merely rejected. Prompting a model not to do something is a request; removing its ability to is a contract.
One line the other way
Nothing stops Genie protecting an estate. Not a lapsed licence, not a failed payment, not a billing dispute, not an expired trial.
Administration degrades. Monitoring does not. Your clients are not party to a commercial disagreement.
Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.
Thirty days · read-only · no card
Run it beside what you already have, against your real clients. It tells you what your tools are reporting that is not true.