Without a clear rule
The app pays. No one is asked.
Before you build
Describe your project. Decide who can do what, which limits apply, and what happens when something fails. Get a clear brief to give your coding agent.
versioned Control Packs: reusable safeguard rules, currently in review.
Try an example
Start with one click.Each example starts a browser-local review. Nothing is compiled until you choose to create the files.
What you get
Ready for your agent.agentdirective/agent-directive.jsonStructured rules your coding agent can follow..agentdirective/AGENTDIRECTIVE.mdA plain-language version for people and agents..agentdirective/control-status.jsonWhat your agent reports as built, incomplete, or still open.Your agent gets the boundaries to implement, available validation scenarios, and a structured way to report progress.
One small decision. A big difference.
A refund app can work perfectly and still send more money than you intended.
The app pays. No one is asked.
The app holds. You decide.
Illustration · AUT-001 v1.1.0 · $500 is fictional, not a recommended limit.
The film · under a minute
One build idea, from a plain sentence to a brief your coding agent follows and reports back against.
What one sentence gives you
This is the real map for the example below, drawn by the same rules your own review uses. Open any step to see its safeguards and the questions only you can answer.
Example descriptionAn AI support agent reads customer emails and automatically issues refunds through Stripe, using customer records.
Why it helps
A coding agent may make assumptions when a prompt leaves something out. Review the choices that affect authority, data, and failure handling before implementation.
Where to start
No account, no repository access, no source code. Pick whichever matches where you are.
What this is not
AgentDirective prepares instructions and checks reported metadata. You still need code review and testing to find out whether the implementation follows those instructions.
Your review
Restored from earlier in this tab. It is kept only in this browser tab and cleared when you close it.
Your journey
Step 2 of 5 · Confirm01 / Check the result
No safeguard matched yet
This is not a safety conclusion. It means the local review did not find a known trait that connects to a safeguard.
This sends only the description above to Cloudflare AI. We do not store it or the response. Suggestions cannot affect the review until you confirm them.
Help improve recognition (optional)
Send only the missing term and a short explanation. We will check whether it fits an existing trait. Nothing changes until you confirm a proposed match.
Why this may matter here
A short orientation based on the optional context you selected. It does not change the review.
See it in an app
Example screens drawn from your description and each safeguard. They show where a check belongs and what you will decide. They are not your app.
Why these safeguards matched
We show how your confirmed traits connect to each safeguard before you decide.
Public records illustrate similar failures. They do not show what happened in your project.
How much should we review?
Quick Review starts with the most important open decisions.
02 / Resolve what matters
Answer what you know. “Not decided yet” keeps a decision open.
Updating your directive
03 / Review before compiling
Review your answers before generating the files. You can go back and change anything.
Creating your directive sends your description, confirmed traits, and answers to our Cloudflare-hosted compiler, together with any prior directive or optional context you supplied. They are processed for this request, not stored. No AI is used for compilation.
04 / Ready to use
Give these files to your coding agent as its design boundaries and reporting rules.
Next: give your coding agent the instructions
Copy the prompt and paste it into your coding agent. It includes your requirements, open decisions, and reporting instructions. Copying sends no data to AgentDirective.
The same design drawn as components and the data that moves between them. Suggested from your description, not a code scan; an unmarked connection is not proof of safety. Select a connection or a warning for its safeguards and tests.
Generated in this browser. The map opens in a new tab through a one-time hand-off that is deleted when read, and your results stay on this page.
Did this review change your design?
Optional. We store only one aggregate category count—never your description, directive, identity, project, or free text.
Ask your agent for a report when it finishes
The prompt above already asks for a report. Copy this instruction separately if your agent has started. It generates an implementation report from the status file, showing requirements, reported work, and decisions still open.
Applied safeguards
Each pack shows the requirement, your decision, and the evidence your agent should record.
Still open
Answer any of these now and update your directive, or leave them open for your coding agent to ask you about.
05 / Improve · Optional follow-up
Once your coding agent writes its status file, submit it with your directive to check the reported evidence for missing or inconsistent claims. This does not verify the source code or runtime behavior.