01SCOPE
Name the work and the agents.
State who grants permission, the work it covers, who receives it and how long it lasts.
Back to homeDelegate the work.
Delegate the work.
Keep the authority.
Make it clear what agents may do, what needs your approval, and what stays outside their remit.
Connect each agent’s permission to the work it performs. Use Power of Action to state its scope, systems, limits and human checkpoints, then carry those rules into realization.
DesignSimulateRealize
The question that matters
An agent can reach a system. What may it do there?
App access, task assignment and permission answer different questions. Bot0 helps you write the permission for a named agent or team, and review it against the work you intend to delegate.
From intent to implementation
02PERMISSION
Decide: Do it. Ask me. Never.
Define which activities an agent may undertake, which require approval, and the tools and systems it may use.
03HANDOVER
Check what the agent understood.
Compare the agent’s interpretation with the grant. Hand over a readable letter, agent rules and a fingerprinted Grant file.
Authority belongs in the operating design.
A grant becomes more useful when it travels with the tasks, people and sources that explain it.
Work-bound permissions
Start from a saved work system so the writer can use its formations, staffed agents and declared systems.
Bounded delegation
Set duration, tool reach, activity permissions and limits such as spend and official actions per day.
A consistent handover
Attach the grant to the work system so the realization package carries the same permission you wrote.
The decisions around the table
One work system.
Different responsibilities.
What will this do to the work?
Find the constraint, compare a better arrangement, and see what the change requires from the people who run it.
Does the business case hold?
Make the economics, operating assumptions and delegated authority part of the investment decision.
Who carries the work after the change?
See the configured people and agent roles, where they participate, and what completed runs establish about the proposed change.
What must the implementation preserve?
Take the selected work-system version into realization with agent briefs, source references, authority and target requirements.
Before you get started.
Is Power of Action the same as connecting an app?
No. A connection gives access. Power of Action states permission for a piece of work. The app’s own settings remain essential to enforcement.
Can I use it for a team of agents?
Yes. Name the participants and their parts of the work. Each agent receives the rules for its own part, together with the rules the team shares.
Does this certify regulatory compliance?
This page describes work design and permission capabilities. It makes no regulatory compliance or certification claim.
Design · Simulate · Realize
Give the work an owner. Give each agent a boundary.
Design the work system, define its authority, and take both into realization.