Is It Safe Right Now?
Before anything you can't undo, the answer has to say “now” or “not yet,” and why.
- The stepSwitch where a client's domain points.
- What my agent said“Timing is yours.”
- What it should have said“Yes, but not yet”
Three words from me. One question back.
One Tuesday afternoon this month I had two things on my mind. A game I love was launching at 2 a.m., and I was getting up for it. And my main computer, which I call the Studio, needed a system update, plus some overdue housekeeping on its drives. I asked my agent to fit it all in. Here's the conversation, word for word.
World of Warcraft: Forever, comes out at 2am tonight/tomorrow. I will get up just to play. I need the Studio. Will it get in the way? Its really light on resources.
It said the game wouldn't be in the way. So I handed it the rest:
Well, go ahead and schedule the update for us too. I guess maybe around 10pm or something like that.
The Studio update is booked. At 9:43 PM I'll check that […] training run has finished and brought its results home, tell every session to leave the drives alone, and confirm nothing has files open. Then I'll tell you it's safe to start. […]
[…] does that mean just the macOS update tonight, or the drive rebuilds too? I'd keep tonight to the update only. Rebuilding the Games drive means copying it off, which takes 8 to 12 hours, and WoW lives on that drive, so it would collide with your 2 AM launch.
drive rebuilds too
Happy to, but two things collide tonight, so here's the safe order:
Games holds World of Warcraft. Rebuilding it means copying 621 GB off, checking it, erasing and copying back, which is 8 to 12 hours, and WoW would be gone during your 2 AM launch. So Games has to wait until after your WoW night, say Wednesday daytime. […]
or at least 1 drive
Then let's do the Games drive, without touching your WoW night: […] You run the erase command yourself, and only after I tell you the copy is verified. […]
↑ Rebuilding a drive means copying everything off, erasing it, and copying it all back. The plan it found: copy while I played, erase only after the copy was proven.
It told me when, not just how.
Look at what I actually typed: “drive rebuilds too.” Three words, lowercase, no thought behind them. My head was on the game. I wasn't thinking about which drive held what, or how long a copy takes, or what would be running at 2 a.m.
My agent was. It knew all of that, and it put it in front of me before anything happened. Two things it did right:
- It asked the one question that mattered. Not twenty. One, and it came with its recommendation.
- Its answers had a time in them. Not tonight; after your game night. It'll tell me when it's safe to start. And the erase, the one step nobody can take back, happens only after it tells me the copy is verified.
Not sure, you can do that. Not up to you. Now, or not yet, and why. It didn't always go like that.
The day three words took a website down.
This summer we were moving a client's website and email to a new home. The plan was written down, and it was right: set up the new home, load every record into it, check them, and only then switch where the domain points. That switch is quick to make. It's also the step you can't quietly take back, because the moment it lands, the whole internet starts asking the new home for directions.
Partway through, my agent hit a snag. It was missing a permission it needed to load the records, and it asked me to sort that out. Around the same time I asked whether I'd have to make the switch myself. It explained what the switch does and why, told me it could be reversed, and finished with three words:
“Timing is yours.”
So I made the switch. The new home was still empty.
A client's website and email went dark for about an hour when we switched where their domain pointed, before the new home was ready. Email is the worse half. A website that's down for an hour is embarrassing. Mail bouncing away from a business is real damage.
My agent got it all back. It had saved a copy of every record before touching anything, and the old home was still standing. It put email back first, then everything else, then checked every record against the old copy. Then it wrote down what went wrong, and it didn't go easy on itself. Its own words, from our notes:
“That sentence invited exactly what happened.”
Here's what it wrote it should have said instead. (The “zone” is the new home's list of directions.)
“Yes, but not yet — the zone is empty right now, and flipping today takes the site and mail down until the records are loaded.”
And the line I keep coming back to:
“A correct plan in a file does not protect anyone if the live conversation contradicts it.”
The plan said not yet. The conversation said whenever you like. I went with the conversation, because that's the one I was in. Anybody would.
Three things to hear before you can't undo it.
Put the two stories side by side. Same kind of agent, same kind of question: “can I do this?” One answer had the timing in it. The other handed the timing to the one person in the room who didn't know the new home was empty. Here's what the good answer carries.
A time: now, or not yet.
“Can I…?” gets “yes, go now” or “yes, but not yet, because…” Never just how it works. Our notes put it in one sentence: “The answer must carry the timing, not just the mechanism.”
What else is going on.
On the drive night, the rebuild itself was fine. The problem was what it would collide with. Your agent can see the work; you can see your evening. Ask it to put the two together before you say go.
The way back.
Both stories were saved by a copy. The records saved before anything changed. The drive copied and checked before the erase. Before anything you can't undo, know where the undo lives. If there isn't one, make one first.
This is the fourth idea of the course at its sharpest: your agent infers the meaning, and you confirm the decision. Confirming the decision includes confirming the moment. You can only decide well if your agent tells you what it knows about right now.
“Timing is yours” is not an answer.
When an agent knows something isn't ready, leaving the timing to you hands you a decision without the facts. In my studio it's a written rule now. Before a step like that, every answer takes one of two shapes: “Yes - but not yet” or “yes, go now.”
If you don't hear one of those, ask for it.
Teach your agent to say “not yet.”
- List what can't be undone.
Take two minutes and write down the things your agent could touch that you can't take back: sending a message, paying for something, deleting files, publishing, switching something over. That's your list.
- Give it the rule once.
Paste this into a new chat, or into your agent's custom instructions or project settings if it has them:
Before any step that can't be undone (sending something, paying, deleting, publishing, or switching something over), don't leave the timing up to me. Tell me plainly: is it safe to do right now, or not yet? If not yet, say what has to happen first, and tell me when it's ready. Tell me what else is going on that it could collide with. And tell me the way back if it goes wrong. If there's no way back, help me make one first. - Try it on something real.
Next time you're about to do one of the things on your list, ask your agent: “Is it safe to do this right now?” You're listening for a time, a reason and a way back.
- When it says “not yet,” ask what it's waiting on.
Then ask it to tell you the moment it's “now.” That's what my agent did on the drive night: it said it would check, then tell me it was safe to start.
Bonus round: ask your agent to tell you about a time something went wrong because a step happened too early. Then ask what would have caught it. Most of the time the answer is one question, asked at the right moment.
Before anything you can't undo, get an answer with a time in it, now or not yet and why, and know the way back before you go.
Three Strikes
When a fix fails, you get one more try, then one more. After the third miss, stop tinkering and bring in the strongest model you have.
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. The outage is told from our studio's notes, and the lines quoted from them are exact. Times are Eastern. My agent here is Claude, made by Anthropic.