Command the Machines
0 / 5
10
BAND III · ADVANTAGE
Week 10 of 12 · GOTTHARD · 2,100 m

Protect Everything Before You Scale Anything

The Go Rogue month checks its locks first. The Roll grows by zero this week — on purpose.

Next week you build. The week after, you hand over power. Which is exactly why this week exists. The one-page policy that closes the door today, contracts read before signatures, your regulatory exposure on one honest page, every worker's keys audited against the law that governs them all — and one bad day, rehearsed on purpose, so the real one is boring. Nothing new joins The Roll this week. Everything already on it gets checked.

Not your desk? This week's moves work on any desk: a one-page policy tonight · read the clause in four minutes · know what every machine may touch.

Today · one task

Run the prompt above, spend ten minutes editing it as the owner — then send the one page to the whole team tonight, amnesty paragraph included.

Right now, someone on your team is pasting something into a public AI tool — enthusiastically, helpfully, and completely unprotected. Not malice. Enthusiasm without a door. Today the door goes up: one page, live by tonight.

You'll have: THE BARN DOOR — a one-page AI usage policy: what's encouraged, what's allowed with care, what never leaves the building. Written tonight, sent tonight. A door, not a ban.

  1. Run the policy press below. It drafts the page from your world — the shelf, the charter from week six, the tools your company actually uses. Three sections, plain words: GREEN (use freely, here's how), AMBER (allowed with these rules), RED (never pastes anywhere, ever — client data, contracts, credentials, that spreadsheet).
  2. Edit for ten minutes as the owner. The tone matters more than the clauses: this is permission with boundaries, because bans just move the behaviour somewhere you can't see it.
  3. Send it to the whole team tonight — with the amnesty line the press includes: by Friday, everyone declares what's already been pasted where. No blame, no names in lights. You can't close a door you won't look at.

Draft my one-page AI usage policy in MY VOICE. Read the shelf first — the Approval Charter, the policy pack, what we actually use. Three sections, plain words: (1) GREEN — what everyone should use AI for freely, with our two rules for doing it well; (2) AMBER — allowed with care, and exactly what care means; (3) RED — what never gets pasted into any public tool under any circumstances: client data, contracts, credentials, financials, anything about our people. Close with THE AMNESTY PARAGRAPH: everyone replies by Friday with what's already out there — no blame attached, because we can only protect what we can see. One page. A door, not a ban.

COPY

Rescue — Team pushback on the amnesty? Lead it yourself — reply-all first with your own list. The owner going first is what turns an audit into a culture.

Did you get this done?

The page exists, one page long — and the whole team has it tonight.

Want more — The Friday amnesty returns your real inventory — the uncomfortable hour, made survivable. File every declaration on the shelf; week twelve's twin inherits this policy as one of its standing laws.

The door is up by bedtime. Tomorrow: the contract you signed without reading — read at last.

Today · one task

Paste in the contract you signed without reading. Four minutes later: risks ranked, three clauses quoted, counter-wording ready. Then set the rule for good — nothing gets signed before its four minutes.

The most expensive sentences in your business are the ones nobody read — and they live deep in clause fourteen, placed exactly where your attention was scheduled to die. From today, every contract gets read properly. Four minutes.

You'll have: THE CONTRACT PRESS saved — and the last contract you signed unread, finally read: risks ranked, the three clauses that hurt, and the exact counter-wording to request.

  1. Feed it the one you signed without reading. You know the one. Paste the whole contract into the press below — this first run is on a signed deal deliberately, because the lesson lands harder when the clause it finds is already yours.
  2. Read the four-minute output: risks ranked worst-first, the three clauses most likely to hurt you in plain words, and for each — the exact counter-wording you'd request across the table.
  3. Save it as THE CONTRACT PRESS — and set the standing rule: nothing gets signed before its four minutes. One line on this page and it stays there: this press prepares you FOR your lawyer; it never replaces your lawyer. You arrive prepared instead of billed.

Read this contract the way the other side's lawyer hopes I won't. Give me: (1) the risks, ranked worst first, each in one plain sentence; (2) THE THREE CLAUSES most likely to hurt me — quote each one, say what it means in plain words, and say when it would bite; (3) for each of the three, the exact counter-wording I should request, written out ready to paste into an email; (4) anything unusual for a contract of this type — silence where protection normally lives counts as unusual. Plain English throughout. This prepares me for my attorney's review — flag anything that must go to a qualified lawyer before signature.

COPY

Rescue — Output feels alarmist? Ask the calibrating question: "Which of these three would you actually negotiate, and which are standard for this contract type?" Ranked risk without proportion is just anxiety with numbering.

Did you get this done?

It found something in a signed contract your lawyer would have billed to find.

Want more — Four minutes before every signature, forever — supplier terms, the lease renewal, the platform terms nobody on earth has ever read. The unread sentences stop existing this week.

The expensive sentences get found before the signature now. Tomorrow: the regulations — what actually applies to you, on one honest page.

Today · one task

Tell the prompt above three things — where your customers are, what personal data you hold, what your machines touch — and run it with web research on. Mark the three exposures it names.

POPIA, GDPR, the AI Act — three names that produce the same fog in every boardroom: something applies, nobody's sure what, and the not-knowing is itself the exposure. Today the fog becomes one page with sources on it.

You'll have: THE EXPOSURE PAGE — what applies to you, what you must be able to prove, and where you're exposed right now. Every claim carrying its source and date.

  1. Tell it three things about your business: where your customers are, what personal data you hold, and what the machines on The Roll actually touch. Two minutes — The Roll is your inventory.
  2. Run the press below with web research on. It answers three questions on one page — what applies to you, what you must be able to prove, where you're exposed today — and every line carries a source and a date, or it doesn't go on the page.
  3. Mark the three exposures it names, and read the standing line: this page prepares you for your advisor. For anything with legal consequence it is the start of the conversation, never the end. Save as THE EXPOSURE PAGE.

My situation: customers in {where}; personal data held: {what}; my AI workers touch: {from The Roll}. Research current requirements and answer three questions on one page: (1) WHAT APPLIES TO ME — which regulations bind a company like mine, with a one-line reason each; (2) WHAT I MUST BE ABLE TO PROVE — the records and measures each expects; (3) WHERE I'M EXPOSED NOW — the gaps, ranked. Every line carries its source and the date you verified it, or it doesn't go on the page. Plain English. Close with: verify with a qualified advisor before acting on legal specifics.

COPY

Rescue — The page came back generic? It only knows the company you described. Add the two facts that change everything — where your customers sit and what personal data you actually hold — and run it again.

Did you get this done?

One page, three answers — and a source and a date on every line.

Want more — Diarise a quarterly rerun: regulation moves, and your machines multiply. The page that was true in August is a rumour by March — the date column is there so you never mistake one for the other.

Compliance is a page now, not a mood. Tomorrow the audit turns inward — on every machine you've built.

Today · one task

Read every "allowed to touch" line on The Roll out loud. Run the audit — powers, violations, blast radius, trim list. Then sign every trim, dated, in writing.

Since day four you've written a line on The Roll every time you built something: name, job, what it may touch. Today you find out why. Every name gets audited. Nobody keeps all the keys.

You'll have: The Roll, audited — every press and worker's powers read back against the one law that governs them all, anything over-powered trimmed today, in writing.

The Three-Powers Law — formally

THE THREE-POWERS LAW. There are three powers a machine can hold: SPEND money, SEND to the outside world, DELETE what can't be recovered. Any one, granted deliberately, is a tool. Any two demand supervision. All three in one pair of hands is how a bad day becomes a headline — so no worker of yours ever holds all three, and most hold none. This is the law every commission on The Roll has been written under since day four. Today it gets enforced in writing.

  1. Open The Roll and read every entry's "may touch" line aloud. All of them — the three workers, every saved press, the chain from week four. The lines exist because week ten was always coming.
  2. Run the audit press below. It reads the Roll against the law: powers per name, violations flagged, blast radius written for each — what's the worst thing this one could do on its worst day?
  3. Trim anything over-powered today, in writing, on the Roll. A demotion on the Roll is a sentence: "may draft, may no longer send to queue without review." Every trim is dated. The audit is only real when the ink is.

Audit The Roll against the Three-Powers Law. For every name — workers, presses, chains — read its commission line and produce: (1) POWERS HELD — spend / send / delete / none, as actually written; (2) VIOLATIONS — any name holding powers its job doesn't need, and any name anywhere near holding all three; (3) BLAST RADIUS — for each name, one line: the worst thing it could do on its worst day with the powers it holds; (4) THE TRIM LIST — the demotions you recommend, written as Roll amendments ready for my signature. You audit and recommend only. I sign every trim myself — an unsigned trim never happened.

COPY

Rescue — Every name passed clean? Read the blast-radius column anyway, slowly. The audit's value on a clean Roll is that you now know — in writing — what your worst day actually looks like. That knowledge is next week's licence.

Did you get this done?

Every name on The Roll audited — powers listed, blast radius written, and no name holds spend, send and delete together.

Want more — The audit becomes quarterly the day The Roll passes twenty names — diarise it. And notice what just happened: the course audited itself. Every line you've written since day four was for this hour.

The keys are counted and the locks are checked. Tomorrow you rehearse the one day all of this exists for.

Today · one task

Fill in the three columns — who gets called, what gets paused, what gets said. Then break one worker on purpose, and walk the page out loud while it's broken.

Somewhere ahead is the bad day — a worker misfires, something lands where it shouldn't, a client sees it. Companies aren't judged by whether that day comes. They're judged by the first hour after it does. Today you rehearse that hour — badly, on purpose.

You'll have: THE INCIDENT PLAN — one page: who's called, what's paused, what's said. And one rehearsal completed, two broken things found and fixed while breaking them was free.

  1. Fill the plan press below. One page, three columns: WHO'S CALLED (first call, second call, who speaks to the client), WHAT'S PAUSED (which workers stop, who may stop them — yesterday's audit is the map), WHAT'S SAID (the first sentence to the affected client, drafted calm, today, not during the fire).
  2. Now break something on purpose. Pick one worker from The Roll and declare it: "The Collector just chased a client who paid in full — they're furious, and it's public." Walk the page. Out loud. Who's called? What pauses? What's the sentence?
  3. Fix the two things that broke. Something always breaks in the first walk — a number that isn't saved, a pause nobody has the power to trigger, a sentence that reads like a lawyer wrote it. Fixing them now is the entire point. Save as THE INCIDENT PLAN.

Build my one-page incident plan for the day an AI worker misfires. Read The Roll and yesterday's audit first — the blast-radius column is the scenario list. Three columns: (1) WHO'S CALLED — first call, second call, and who speaks to any affected client, by name; (2) WHAT'S PAUSED — which workers stop in each scenario and exactly who has the power to stop them; (3) WHAT'S SAID — the first sentence to an affected client for each scenario: calm, honest, human, no lawyer-speak, drafted now while nothing is on fire. One page. Then give me one rehearsal scenario to run today, chosen from the blast-radius list — the one that would hurt most.

COPY

Rescue — The rehearsal felt silly? Good — silly is what cheap costs. The version of this that doesn't feel silly is called an actual incident, and it charges by the hour.

Did you get this done?

Rehearsed once, badly, on purpose — and two broken things fixed while fixing was free.

Want more — Rerun the drill each time The Roll gains a worker with real powers — next week qualifies. The plan that isn't re-rehearsed quietly expires; the date at the top tells you when it did.

Week ten is in. The door closed by bedtime Monday, the expensive sentences get found before signatures, your exposure fits on one sourced page, every key on The Roll is counted — and the bad day has been rehearsed into boredom. The Roll grew by zero, on purpose. Now you're armoured — and next week, you build.

Week 10

Armoured. Now you can go rogue.

Five for five. A one-page policy live by Monday bedtime, a signed contract that finally gave up its secrets, your regulatory exposure on one sourced page, every worker's keys audited against the Three-Powers Law with every trim signed and dated — and one bad day rehearsed, badly, on purpose, until it was boring. Nothing new was built this week. Everything you've built was checked. That ordering — armour before autonomy — is the entire discipline, and it's why next week you get to build without fear.

0 of 5 done

The week's quiz · seven questionsNO PASS MARK · IT TEACHES
Continue → Week 11