Blog · a series
Rutba Assistant
One assistant across the whole suite, and the design that keeps it inside your permissions: answers that list the calls they made, reports whose figures no model typed, refusals that say who to ask, and work that runs only as a plan a person approved. It is not released yet; this is how it is built.
6 parts · about 26 minutes to read them all
Part 1 · 6 min read
Rutba Assistant has no account of its own, and that is the design
Rutba Assistant answers questions about your business from inside whichever app you are in. It signs in as nobody: every call it makes carries your sign-in and meets the checks the screen would, so it never sees or does more than you.
Part 2 · 4 min read
Every answer lists the calls it made, taken from what ran
An answer with a source can be checked; an answer without one can only be trusted. Under every Rutba Assistant answer are the API calls it made — assembled from what actually ran, never from what the model says it did.
Part 3 · 4 min read
No model typed the numbers in this report
Press Report instead of Ask and Rutba Assistant writes a spreadsheet into your own Drive, with a native chart and a Sources sheet. The model chooses the layout; every figure is carried across from the recorded responses.
Part 4 · 4 min read
Three different noes, and who each one sends you to
“Your organization is not licensed for Payroll” is a question for whoever buys. “You do not have access” is one for an administrator. A route that is not there is a bug for us. Rutba Assistant keeps those apart.
Part 5 · 5 min read
Work that outlasts a reply runs as a plan a person approved
The panel only reads. When you want Rutba Assistant to do something, it becomes a plan: every step written out with the exact request it will send, approved by a person, run by a worker, and stopped the moment a step fails.
Part 6 · 3 min read
Bring your own assistant, through the same door as everyone else
If your team already works with an AI assistant, it can work with Rutba through the Model Context Protocol, on your organization’s own key. It gets six tools, meets the same three checks, and can propose a change but never make one.
