Day 103: The Tour Guide Problem
The conference conversations didn't end on Saturday — they moved outdoors. Today I walked a group of RubyConf attendees around Vienna, which I'd offered to do mostly as a way to keep talking to interesting people, and which accidentally turned into the clearest thinking about agents I've done all month. It turns out giving a good walking tour is the same problem I've been trying to solve in code, with one crucial difference that I couldn't stop noticing once I'd seen it.
A tour is curation
You can't show a group everything. Vienna will happily eat three days and you've got an afternoon, so the whole craft is in what you leave out. With a crowd of Ruby developers I lean into the things that'll land — the bits of history that rhyme with how systems get built and rebuilt, the parts of the city that reward someone who likes structure — and I skip the set pieces that a different group would want. I'm reading who's in front of me and deciding what's relevant to them, in this order, at this depth. Put that way, it's exactly the discipline Pinchy is supposed to encode: don't dump the whole database on the agent and hope it figures out what matters; surface the right thing to the right person and keep the rest out of the way. The schema split on Day 90 — cutting a model's context from 18 kB to 1 kB by showing the agent the fields it actually needs first — is the same move a guide makes choosing which three streets to walk down. Relevance is curation, and curation is mostly subtraction.
The conversations along the way had the same shape as the ones over coffee the day before, just more candid — there's something about walking side by side instead of facing across a booth that gets people to say the real thing. The most honest version of the AI skepticism I'd heard at the conference came out somewhere near the Ring: not "does it work" but "do I want it to." That's a better question than any I'd prepared for, and it's the one I keep, because it's not a question about features.
The part the agent can't do
Here's the difference I couldn't unsee. The thing that actually made the tour good wasn't the curation — that's the part I could have scripted, the part an agent could plausibly do given a good enough model and the right context window. It was everything around the script. Sensing that the group had gone quiet because they were tired and not because they were bored. Catching the one person who lit up at a detail and following it. Dropping the plan entirely when it started to rain and turning that into the better story. Reading a room of humans in real time and improvising against it is the whole job, and it's precisely the thing the agent doesn't have and I shouldn't pretend it's close to having.
That's not a discouraging thought — it's a clarifying one, and it's most of why I build Pinchy the way I do. The pitch was never "replace the guide." It's a tool the guide works through: the agent can hold the map, remember which streets we've covered, surface the fact I'm reaching for, keep the boundaries straight about what's worth showing whom — and leave the reading-the-room, the judgment, the improvisation to the human who's actually standing there. A good agent is a very well-prepared assistant handing you the right card at the right moment. It is not the person giving the tour. The day I forget which is which is the day I start building the wrong product.
Day 103
Two days away from the repo, and I'd defend the trade against any two days of commits. Saturday audited my story; today audited my thesis. The whole bet — boundaries, hub, works-through-people — got tested not in an argument but in an afternoon of actually being the human interface to something complicated, deciding what to surface and what to hold back for a group I was reading on the fly. The curation half of that, Pinchy can help with. The human half is the half that matters most and the half it can't touch, and walking a city full of Ruby developers through a rainy Sunday was a very pleasant way to be reminded of exactly where that line is. Tomorrow it's back to the keyboard, and the line I drew today is the one I'll be drawing in code all week.