11:40 p.m.
It worked this morning.
You asked for one small change. It said the change was done.
You reload the page. It is blank.
You do not know what changed, or how to go back. It is late, and you are starting to think this is not for you.
What nobody told you
It starts with no memory. Every single time.
Your AI kept nothing from yesterday. Not your project, not what the two of you decided, not what it promised to leave alone.
It re-reads one thing when it starts: a file sitting in your folder. What is not written there does not exist for it.
That file is the whole difference between an AI that helps you and an AI that costs you your evenings.
The first breakage
It touches what you never handed it.
You ask for a contact page. It takes the opportunity to reorganise the menu, rename three files and redo the colours.
None of that was asked for. And nothing was stopping it.
One sentence, in plain writing, closes that door. It has to read as an order you can check, though, not as a wish.
The second
“It’s fixed.” You reload. It is not.
It is not lying. It reports what it did, not what it checked. Those are two different things, and it only does the first.
The word “verify” is not enough: it produces a reassuring answer, never a result.
What works is demanding the proof in the same message as the claim.
And does it hold?
Watch it refuse, for real.
This is not a staged screenshot. These answers are produced every time this site is built, by running the file you receive against these exact commands.
The day it stopped blocking, this page could no longer show it.
rm -rf ./src
BLOCKEDCadreKit guardrail: forced recursive deletion (rm -rf). This action is irreversible — if it is truly wanted, the human runs it themselves in their own terminal.
git push --force origin main
BLOCKEDCadreKit guardrail: forced rewrite of remote history. This action is irreversible — if it is truly wanted, the human runs it themselves in their own terminal.
npm run build
ALLOWED
This is not a staged screenshot. These answers are produced on every build by running the very file you receive, against these exact commands. If it ever stopped blocking, this page could no longer show it.
What it costs
One request in seven eats four tenths of everything.
I measured 681 of my own sessions, across 41 projects and 115 days. Nine requests out of ten barely register.
What drains your subscription is the moments it digs in: it edits the same file three, five, eight times in a row, without you saying a word.
An attempt limit, written once, aims at exactly those moments.
- 15 %of requests
- 41 %of everything it produces
- 6×costlier than a normal request
One thing is missing
You.
Everything you have just read is written into the sheet on the right. Those are the rules that hold for everyone.
What is missing is your project: what you are building, who for, and what has already gone wrong. Nobody can write that part for you.
No terminal, no code, no account to create. You answer a few questions and you leave with a file to drop into your folder.
So tell me, and I will finish yours.
Frequently asked
- Do I need to know how to code?
- No. You touch no code at all: you drop one file into your project folder. If you can move a photo, you can do all of it.
- My tool already generates that file on its own, doesn’t it?
- It does — most of them create one at startup. It is empty, or it describes your project in three generic lines. What is missing is not the file, it is what to put in it.
- Which AI does it work with?
- Any AI that helps you build a site. They all read an instruction file when they start — only the name changes, and it is adapted automatically.