This is the artifact Closos hands you after every action it takes — annotated. Click each layer to see what the action was, why it was allowed, what evidence it used, how it's signed, and how to take it back. Hand it to legal. Hand it to your board. Archive it for seven years.
This isn't a screenshot tour. It's the same artifact your team gets in production — annotated so you can see what accountability looks like when it's built in, not bolted on.
Most autonomy comes with a kill switch. Ours comes with a contract. These two rails are compiled into the product. Your admin can't loosen them. Our support can't unlock them. They are how Closos can be trusted to run on a Friday at 4:47pm.
Closos can never auto-send an email, message, or notification to a person outside your org without an explicit human approval. Not in any plan. Not on any policy. Not for any role. This is the line.
A user can choose to be stricter than their org's autonomy policy. They cannot choose to be looser. Org policy is a ceiling, not a starting point — the math goes one direction only.
| Action | OFF | ASK | AUTO | Notes |
|---|---|---|---|---|
| outbound.email — to human | Locked | — | Rail 01 | |
| internal.note | ||||
| crm.update | ||||
| meeting.propose | ||||
| asset.send (templated) | ||||
| spend.approve (< $50) | ||||
| spend.approve (≥ $50) | — | |||
| user.override (loosen org) | Locked | — | — | Rail 02 |
Retention purges happen on schedule. DSRs get fulfilled. Erasures leave nothing behind. These numbers are aggregated across the platform — no PII, no per-customer detail, no inferred identifiers. The receipts behind them live inside each org's authenticated dashboard.
Operated by EthicalBrain Technologies · Dubai International Financial Centre (DIFC), Dubai, United Arab Emirates. Privacy and security questions: privacy@closos.com.
