Connections
Governed hands into the tools you already run on.
Cruma does not replace your tools, and it does not copy your world into itself. Connecting a tool gives the crew governed hands: scoped, permissioned, and revocable at any time.
Your tools stay in charge
Gmail owns the email thread. QuickBooks owns the invoice and the books. Drive owns the document. Stripe owns the payment. Your calendar owns the events. Cruma stores its own work: the drafts, plans, decisions, approvals, and the relationships between records, and points at the originals rather than hoarding copies.
Referenced record: Invoice #1048, source: QuickBooks. The original, where it lives.
Cruma artifact: a deposit reminder draft, created by Cruma, based on Invoice #1048 plus the client email thread plus your payment policy.
Read, draft, and act are separate permissions
A connection is not all-or-nothing. Each one splits into what the crew may read, what it may prepare, and what requires your ok:
Gmail: read email, draft replies. Ask before sending.
QuickBooks: read invoices, prepare drafts. Ask before creating or changing anything. Never move money automatically.
Calendar: read availability. Ask before creating external events.
Before acting on anything approved earlier, the crew re-checks the source first; the freshness rule applies to every connected system.
Connecting pays off immediately
Cruma recommends a connection only when it can tell you why it is worth it, and the first thing you see after connecting is what it learned, not a settings page. If a connection is not earning its place, disconnect it; the crew keeps working with what it still has.
Boundaries are honored
Tell the crew to keep out of a folder, a thread, a client, or an account, and that is a standing rule: remembered, enforced on every future run, and visible in your Playbook.
Next: Memory and the Playbook, what Cruma keeps and how it gets sharper.