Docs
Agentic OS
Gabi works as an agent dispatch: she prepares, the human approves. Live tools, a repair loop, and a human approval gate.
The loop. Draft, approval, delivery
Every action starts as a draft the agent prepares, passes a human approval gate, and reaches its destination only after explicit approval. The decision and the send stay with the human.
Three permission levels
Draft only: the agent prepares, nothing leaves without approval. Draft plus reminder: the agent prepares and nudges for approval, delivery is manual. Quiet path: actions with no personal content (scheduling, internal summaries) may run on their own and are logged. Client-facing content always passes a gate.
Human approval gates
Live gates: Holding Queue in the practitioner office, draft approval before a client message, a soft cap on partner seats, and a source stamp on artifacts that go out. The closer the action is to a person or to money, the stricter the gate.
Tools the agent holds
Grow and Stripe for payments, Supabase for data, email and the client portal, notebook cinema render, the media bank, and the alchemy lab for assembling flows. The agent cannot delete data, take payment, or publish outside its permission.
What this model does not do
The agent does not decide clinically, does not send to a client without approval, and does not act outside the cap that was set. The human remains the owner of the decision.