The agent checks who is asking, where they are asking, and what they may use.
A name is not a key.
Example · not a live agent
Ana · approved staff · private chat
“Read my approved sales sheet.”
1Ana is on the approved list.
2Her record allows this sales range.
3She is asking to read it.
Allowed to ask Sheets.
Only that range is requested. The app still needs a working connection.
What else should I know?
Like checking a name at the school gate. A name in a message is not an ID.
Founders manage the agent from verified private chats.
Staff use only the data they are allowed to use.
Groups have their own approved people and data.
USER.md holds company language and time zone. Staff access is stored in control.json.
Staff
Approved app data, own private notes and own private reminders.
Cannot add staff, change company settings or read someone else’s private notes.
Founders
Either verified founder can manage people and groups from private chat.
Company and app changes need an open Setup window. Client owners are not automatically founder admins.
Installer
At the Mac: install, connect accounts, run checks and record evidence.
Being called “installer” in chat does not grant founder access. Local machine access is a separate responsibility.
Group
Approved members can use data explicitly allowed in this group.
No private notes. People in the real WhatsApp group can see messages; membership needs a human review.
Keep exploring
The parts, in plain language
Use this overview to understand the whole agent before exploring the interactive examples. It describes the public pilot kit; custom agents such as Emily have their own implementation and permissions.
Instructions
These seven files tell the AI its name, how to speak, and how to do its job.
Like a school handbook. It explains the way to do things.
Name and speaking style.
Language, time zone and work instructions.
How to ask for tools, notes and reminders.
Instructions guide the AI. The permission checker decides which actions are allowed.
Puestario checks the agent, keeps records, and can make an encrypted recovery copy.
Like a checkup and a spare copy of your important work.
Logs help explain what happened.
Real checks are needed before handover.
A restored agent starts paused, with jobs off.
The gateway must be stopped for a backup. The encrypted copy goes outside the company folder; its key stays separate. Backups are not automatically scheduled.
This guide documents a specific public pilot release. Installation and real-account testing are still required. Voice handling and all workflows from existing custom agents are not included in this release.
