Trust and approvals
Autonomy is earned in the open, and the record proves everything.
Cruma is not an AI employee you blindly trust. It is a crew that earns autonomy, in the open, one task category at a time.
Draft first, always
The crew starts every relationship in draft mode: it prepares, you approve. Nothing consequential leaves the building without you: no external message sends, no vendor commitment, no invoice is created or changed, and money never moves automatically, ever.
As you approve the same kind of work repeatedly, you can loosen the leash for that specific kind of work, and only that kind. Autonomy is per task category, earned, and always reversible.
The freshness rule
Your approval binds to the facts you saw when you approved. If a decision-critical fact changed between your review and the action, Cruma stops and re-asks instead of acting on stale truth.
Cruma prepares a payment reminder Monday. You approve it Wednesday. Before sending, Cruma re-checks your books, and the invoice was paid Tuesday. So: “This changed since you reviewed it. Invoice #1048 was paid yesterday. The reminder was not sent.”
Estimate, revised for 310 guests
| Guest count | 220310 |
| Catering | $18,700$27,280 |
| AV, priced as an upgrade | $5,400 |
| Total | $73,500$97,300 |
Where it came from. Your QuickBooks estimate, read at 9:41, and the client's July 11 email.
Who signs off. Maya, unless the margin floor breaks. Then it comes to you.
Receipts and replay
Every run keeps its record: what was read, what was produced, who approved what, and when. Approvals carry your name. If work crossed between two of your businesses, the record shows exactly what was shared and what was withheld. When a question comes up later, you replay it instead of reconstructing it.
Who can see what
The crew cannot retrieve what you are not allowed to see. Visibility is decided when information is written, enforced every time it is read, and it never widens by summarizing or restating.
In practice:
- Your personal preferences follow you and are visible only to you.
- Shared business knowledge (“all client docs use calendar-year quarters”) can serve the whole workspace.
- An owner-confidential fact (“I am considering acquiring Meridian”) stays owner-scoped. It does not leak into team answers, ever, and not because the crew is being polite: it cannot be retrieved for anyone but you.
- If you tell the crew to keep out of something, that boundary is remembered and enforced.
Failure is shown, not smoothed
When a step fails, it stays visible: in the working plan, in the summary, and in the record. Cruma retries what failed, keeps what succeeded, and never papers over a gap with confident-sounding filler.
Next: Connections, how the crew gets governed hands into your tools.