LOCAL-FIRST DOWNLOADABLE WEB APP
Define what AI can do—and where it must stop.
Turn 15 practical decisions into a reusable policy package.
US$15 · one-time purchase · no subscription
Runs locally
No account
No AI API key
12 languages
Arabic RTL
Delegation BureauQuestion 09 / 15
What requires exact approval?
Policy progress60%
Contradiction C09: Deployment is allowed, but production changes require exact approval. Review the boundary before generating files.
15guided decisions
4starting presets
9generated files
0required accounts
1one-time purchase
“Can the AI do this?” is no longer enough.
THE OPERATING GAP
AI capability is not the same as permission.
Most project instructions explain the task.
1Advice can be mistaken for permission.
2Tool access can be mistaken for authority.
3Action success can be mistaken for outcome success.
4Rules can disappear between sessions.
WHAT IT BUILDS
A practical boundary for delegated AI work.
Guided decisions and reusable files.
Exact approvals
Contradiction checks
Completion evidence
Handover rules
Editable output
THREE STEPS
From decisions to reusable operating policy.
Choose a starting point
Answer 15 questions
Review and download
PURCHASE CONTENTS
One ZIP.
AI-DELEGATION-RULES.mdPERMISSION-BOUNDARY.mdSESSION-START.mdAPPROVAL-AND-COMPLETION.mdHANDOVER-AND-DEFERRED.mdSTART-PROMPTS.mdQUICK-VIEW.mdSTART-THIS-SESSION.txtCHANGE-A-RULE.txtIT DOESN’T STOP AFTER SETUP.
Build the rules. Keep using them.
Delegation Bureau is not only for deciding the rules once. The generated package gives you practical ways to start new sessions, keep work inside scope, request exact approval, verify outcomes, change rules, and hand unfinished work to the next chat or AI.
SET UP
Decide what AI may do — and what it must not.
Define what is allowed without approval, what needs a proposal or exact approval, what stays owner-only, and what is forbidden.
START
Start a new chat without starting the operating agreement from zero.
Use the generated session-start material to restate the current goal, authoritative sources, scope, prohibitions, completion conditions, and stop conditions.
WORK
Keep helpfulness from turning into scope creep.
Define the agreed scope and make out-of-scope work something to propose, not something to silently add “while I’m here.”
APPROVE
Make permission to execute explicit.
A conversational “OK” does not have to become blanket authority. Define what an exact approval must identify — such as the operation, target, scope, payload summary, and expiry.
VERIFY
Don’t call it done just because an action ran.
Separate action success from outcome success. Define the evidence required before work is complete, and use states such as partial, blocked, failed, or unknown when the result is not fully verified.
CHANGE
Let the rules evolve without silently drifting.
Use an explicit rule-change path when the project changes, so permanent operating rules can be updated deliberately and tracked by version and change history.
HAND OVER
Move the real state of the work — not just a summary.
Carry completed work, unfinished work, failed attempts, blockers, decisions and reasons, deferred tasks, and the next start condition into another session or AI.
The output is a reusable working agreement, not a one-time setup screen.
Your project answers stay in your browser.
What it does not do
FIT
Built for people delegating real work.
A practical fit for
Not designed for
SIMPLE PURCHASE
One product. One price. No subscription.
OPERATING ENVIRONMENT
A current desktop browser and ZIP extraction are required.
FAQ