The Runner and the Grid: A Field Note on Working with AI

On my desk, there’s a photo I can’t unsee: a handful of hand-drawn mazes, coffee nearby, pencils scattered like tiny witnesses.

Some of the mazes are polite and clean.
One is aggressively scribbled over.
One “cheats,” with an arrow pointing straight through the border.

It’s a simple image — but it sums up my last year perfectly.

Because that’s how “AI” has felt in practice: not a single tool, but a messy table full of mazes. And the word AI feels too abstract now — a foggy label we slap on everything from autocomplete to “culture-fixing” chatbots.

So, to keep my sanity, I’ve started using my own vocabulary for the workflow:

The Runner. The Grid. The Countermeasures. The Trace.

The Runner

I stopped viewing it as a genius. Or a replacement for thinking.

Instead, I treat it like a Runner.

You dispatch it into the mess because it has quick feet and fast hands. It’s a bit reckless — but very useful when the clock is ticking.

A Runner brings options, not outcomes.

It tries routes and comes back with possibilities, but you’re still responsible for the result.

And if you’ve done any real work lately — coding, product decisions, negotiations — you know the maze isn’t on paper.

It’s in the system.

---

The Grid

The Grid is where everything connects: legacy code, shifting priorities, compliance rules… and that one service nobody touches because “it just works.”

The Grid isn’t evil.
It’s just dense.

This is where the Runner shines — provided you give it a job that fits its nature:

• “Here’s the error; give me three likely causes and how to verify them.”
• “Draft a script to convert these files (with logging and a dry-run mode).”

Sometimes it feels like magic. Not because it’s always true — but because it unblocks me.

But other times, the Runner builds new corridors I didn’t ask for.

Ten refactors. Five shiny libraries. Three new patterns.

Suddenly I’m not shipping — I’m exploring.

The Runner didn’t trap me on purpose. It just did what Runners do.

---

Countermeasures → The Trace

You can move fast… until you hit something that moves back.

In the Grid, “countermeasures” aren’t just security rules. They’re anything that punishes sloppy speed: confident hallucinations, subtle bias, privacy mistakes — or that copied snippet that becomes a production incident next week.

So I’ve learned a rule:

No run without a Trace.

The Trace is the boring part.
Proof, not vibes.

Tests. Logs. Citations. Examples. Tiny checkpoints that prove the Runner didn’t just sound right — it actually holds up when reality touches it.

Looking back at the maze

Looking back at that photo on my desk, I realise the work has changed.

Sometimes the Runner solves the maze.
Sometimes it creates the maze.
Sometimes it is the maze.

And the real work is learning how to navigate it.

I’m curious: when you dispatch your Runner… do you get an exit strategy — or a new habitat? 🌈

---