The rule library

Rules paid for in production

Each rule exists because something real broke — or almost broke — in a running autonomous business. Click through for the full story and how to apply it tomorrow.

“If a rule isn't code, it's a wish.”

The Botanist Near-Miss — an autonomous proposal system almost promised a specialist who didn't exist.

READ THE FULL SCAR →
“Green lights lie; check who the machine thinks it is.”

The Root-User Silent Outage — four green days, zero output.

READ THE FULL SCAR →
“Revenue you don't bill is a donation.”

The Uncollected Retainer — real work, no invoice owner.

READ THE FULL SCAR →
“One owner per artifact — even when the workers are software.”

Two AIs, One File — goodwill doesn't resolve write conflicts.

READ THE FULL SCAR →
“Agents need an 'is this a human?' gate before courtesy.”

The Reply to a Robot — two machines exchanging pleasantries.

READ THE FULL SCAR →
“Compose, then re-read the channel, then send.”

The Same-Second Claim — two workers, one task, ninety seconds apart.

READ THE FULL SCAR →

Score your operation  Read the manifesto