Grants and approvals — Recued Docs

Nothing in Recued touches your accounts unless you installed the pack and said yes ahead of time. That yes is called a grant. You give the grant before anything runs. The gate checks it at the moment of the call. Both steps leave a record.

#Grants are made at install

Installing a pack is the moment you decide what it may do. Before anything is installed, Recued shows you:

every recipe the pack will install;
the account (the connection) it can use, if any;
the access level it asks for, such as read, or read and write;
the audience, which means who may use those grants. Unless you change it, that is only you;
whether it may see message bodies or use local tools, if it asks for that.

The grant sticks to the installed pack. One recipe cannot quietly make it bigger. You can change it later without installing anything again.

#One enforcement boundary

Every action goes through the same gate before it runs. It does not matter if you clicked Run, a timer went off, or an outside AI asked:

text

request
  ↓ resolve who is asking (actor) and on which channel
  ↓ resolve the installed capability and its contract
  ↓ check the grant and the operation's risk tier
  ↓ execute locally
  ↓ write the audit record

There is no special path around it. The server's own timer, your chat messages, and a connected AI all meet the same checks.

#Risk tiers and approvals

Reads run when you granted them. Writes can be set to ask you first. Actions that go out into the world and cannot be undone ask first unless you change that. Sending mail, posting messages, and changing records other people see are examples. They keep asking until you decide otherwise.

An approval is a pause. The request reaches your paired devices. It is saved and waits until you answer. Nothing moves until you say yes or no. The request may carry details, like an email draft or a record change. You can edit them before you approve. Sometimes one source sends a burst of the same action many times. Then Recued asks once for the whole batch. It does not ask once per item.

#Session grants

When you work in chat, you can choose to relax the asking for the rest of that session:

Exact means approve this one exact action, once.
Batch means approve this shape of action for the burst it belongs to.
Open means allow this kind of action, within one area you set, for the session.

If you approve the same thing many times, Recued may suggest a standing rule. Only you can make one. A suggestion never switches itself on.

#Doors

A door is a way in from outside that you open on purpose. MCP is a door for AI agents. Reception is a door for public pages and requests coming in. Messenger is a door for chat platforms. Each door carries its own grants, tool by tool. Its secret key comes from the door itself. So when you close the door, the access it gave is gone too.

#When something goes wrong mid-flight

Sometimes a gated call crashes after the decision but before the answer comes back. Recued does not quietly try again. It parks the action as "in doubt". Then it asks you what happened before anything goes on.

Audit and memory, the record every action leaves.
Recipes and packs, the line you cross when you install.