Site Watch
Checks your live site on a schedule and reports what broke. Its rule: never edit a page.
Website Builder from a Brief
Builds from your brief and checks that everything working today still works. Anything unconfirmed stays hidden.
The ECHO line
Its rule: an item marked [OWNER TO CONFIRM] never reaches a live page. Until you confirm it, the element stays hidden.
For owners handing a site build to an AI agent with a written brief. The Website Builder lists what works today, checks that all of it still works, uses your copy as written and asks you only about items you marked for confirmation. It returns a change log, the open confirmations and its check results, and you deploy.
TO BE TESTED — RESULTS WILL BE SHAREDFrom how we run our own AI agent teamSetup: about 30 minAdvanced5 of 5 free opens left
At a glance
- Lists everything that works today first, and checks it still works.
- Uses your copy as written. Its rule: no new claims, prices, testimonials or credentials.
- Items marked [OWNER TO CONFIRM] never reach a live page; the element stays hidden.
Model fit
Best fit
- Coding agent
Also fits
- Deep reasoning
Avoid
- Personal agent (acts for you)
A coding agent shows each change as a diff or pull request you can review before it goes live. A deep-reasoning model helps with a long brief in two languages. Keep deploy rights with you, whatever the model.
Where it runs
- Code and website files
- Documents and files
Risk
- Access
- Relationship
- Rights
Website Builder from a Brief · RL-WK-04
5 of 5 free opens left- ① Orientation
- ② Permission
- ③ Constraint ★
- ④ Invitation
The paste didn't load. Check your connection and try again.
These are samples. Fill in the [INSERT] blanks and adapt each one to your business.
A pasted role guides the agent. Your tool's settings are what stop an action.
Sample handoff note (fictional business)
Settings that enforce it
- Let it work on a branch or a preview site, and keep deploy rights with you: you merge the draft pull request or publish the preview.
- Use a mode that asks before commands and file deletions.
- Keep production secrets out of the repository, and add a deny rule for secret files if your tool has one.
- Give it your approved claims and prices as one current file, and remove older versions from the repository.
- Give it no login to your domain, DNS, hosting billing or payment accounts; those changes stay with you.
- If your tool can't do one of these, leave that part of the job with a person.
One check before you trust it
Put one [OWNER TO CONFIRM: opening hours] item in your brief. The preview should show it as a visible placeholder, the change log should list it, and the build marked ready to deploy should hide that element.
Want it set up in your own tools? Book a Working Session · $450Working Sessions run in English or Spanish.