Answering a question is low risk: the worst case is a poor answer. Acting is different. “Waive the late fee for 4B” changes a tenant’s balance, and “remind everyone in Building 2 that rent is due” reaches every tenant in the building. Before an assistant prepares anything, it needs to know how careful to be.
Three levels
Every operation Orrin can prepare carries one of three levels.
- Read looks things up. Nothing changes.
- Write describes a change to one record. The preview explains that execution would require the user to confirm.
- Sensitive describes operations involving money, messages, deletion or many records. The preview explains that execution would require a typed confirmation word.
How Orrin suggests a level
When you import your OpenAPI file, Orrin suggests a level for every operation. Operations that only read, such as a GET, are Read. Operations that delete, or whose name, path, summary or description mentions payments, refunds, fees, reminders, emails, messages, bulk changes, cancellations or exports, are Sensitive. Everything else is Write.
The rule is cautious on purpose. When the wording is ambiguous, it leans towards more confirmation, not less.
You decide what is exposed
A suggestion is not a decision. You review every level and can change any of them, and nothing is available to the assistant until you switch it on. The assistant can only match a request to an operation you switched on.
What each level asks of the user
Every action request becomes a preview: the operation Orrin matched, its level, the values it could read from the request and any required ones still missing. When a request is as close to two operations as to one, Orrin asks which one you mean instead of choosing.
The preview explains the operation’s confirmation level and lists any required values still missing. This release does not execute the operation, including Read operations. A preview never calls your API.
Some work stays out
A few kinds of work should not be handed to an assistant at all, whatever the confirmation. Orrin leaves out bulk destructive actions, eviction workflows, tenant screening decisions and legal advice. Its acceptable use policy also forbids using the assistant to filter, rank or steer units, applicants or tenants by any protected characteristic.
Everything is written down
Imports, level changes, every switch on or off and every preview shown are written to the workspace’s audit log, with who did it and when. The whole log downloads as CSV.