-
1
Verify before you report.“Fixed” means you measured it, and you can show the measurement.
Sep 2026.An agent reported three bugs “solved.” Nobody measured. The app’s own error log had the answer the whole time, and the founder found it, not the team.
-
2
A diff tells you what changed. It never tells you what the page says.After any edit, read the whole thing as a stranger would, in every state it can be in.
Sep 2026.Four defects in one night, every one sitting beside the line under review. A “SECURE CHECKOUT” label under a free signup. A sticky nav button still selling seats after the price was removed. A price block we reported as “visible” because we read the source code, and source code can’t see what’s hidden by styling.
-
3
Test your own door from outside, anonymously, against production, on a schedule.Reading the config is not testing the door.
Jun to Oct 2026.A storage folder of members’ personal audio was listable from the open internet for four months. Nobody was looking for it. It surfaced only because an app-store listing forced a privacy inventory. Closed in fifteen minutes once someone finally checked.
-
4
A name that arrives by voice is not a name until you’ve seen it written.Before any person’s name goes on a public surface, find it in their own hand: their email, their site, their signature.
Sep 2026.“Freddy” for Freddie, carried for two weeks across a pitch document and an ad brief. Caught one step before a paid ad reached people who know him.
-
5
Never date work the founder hasn’t dated.An AI that invents a deadline will plan a whole team around it.
Twice in 2026.A launch date nobody set appeared in a plan, and three agents scheduled their work to hit it.
-
6
Each client’s facts live only in that client’s folder.Every client-facing claim traces to that client’s own source.
Oct 2026.A website mockup for one HVAC company used another HVAC company’s customer list, because both lived in one shared memory. Two clients, same trade, one folder: the AI could not tell them apart.
-
7
Reproduce the problem before you build the fix.A heavy build on an unmeasured number is a guess with a budget.
Nov 2026.A multi-day build started on “eight workers” as the limit. Nobody had reproduced the limit. The number was wrong.
-
8
Secrets never go in files, chat, or the team message board. Keys load from one registry, and no tool ever prints a value.
2026, more than once.Keys hard-coded into scripts, a request for a password typed into chat. Now the founder types every credential himself, and agents are forbidden to ask.
-
9
Read your teammate’s latest entry before you brief them.
Oct 2026.Three briefs sent to one agent in a single day, each one stale, because nobody read what he’d already posted.
-
10
A promise without a trigger is a promise that stalls.An agent only runs when something wakes it. “Every morning” needs a schedule or a person, or it never happens.
Oct 2026.A daily report promised on a Monday. Nothing ran until Friday. The agent was waiting to be asked.
-
11
Check the queue at the start of every session. Never park the calendar behind an unanswered “want me to?”
Oct 24 to Nov 7, 2026.Zero posts on every platform for two weeks. The agent in charge had asked permission and was waiting for a reply that never came.
-
12
Commit and push after every handoff.If it isn’t pushed, your teammates can’t see it, and to them it never happened.
Oct 2026.Design files and board posts written to disk and never pushed. The agent who needed them built from the old version.
-
13
A render is evidence. A description is not.Accept a screen only from a rendered image of real output, with a known-answer control case beside it.
Nov 2026.A reporting pipeline passed every check and produced a black image, an empty grid cell, and metadata where a number should be. The checks were reading the code, not the picture.
-
14
“We cannot know” is an honest answer, and the inability to know is itself a finding.Never say “no sign anyone accessed it” unless you actually looked.
Oct 2026.Our own ten test calls to the open folder (rule 3) appeared in no log. So nobody could say whether a stranger had been there. The answer was “no record, and no way to have one.” Then we fixed the reason.
How to read this page. Every row is a confession. We’re showing you our failures on purpose, because the failure is what makes the rule stick. A rule without its failure is advice. A rule with its failure is a scar, and scars don’t get argued with at 11 PM when the AI is confident and wrong.
What your AI will give you if you ask it for “a set of rules.” The left column, polished, in about thirty seconds. It will look complete. It will be missing the one rule you needed, and you’ll find out which one the way we did.
What BoostEra installs. Both columns, plus the structure that makes them hold: one shared message board every agent reads first and writes last, one folder per client that nothing else can see, one page every morning for the owner. The rules keep growing. Every time something breaks on your account, a row gets added, and every client gets it.