The Human Context Protocol knows you’re a morning thinker
Pawel Halicki

The transit doors open, spilling commuters onto the platform. Central Station swallows them fast, funnelling the crowd toward exits before the next train rolls in. He takes the right escalator to their coffee kiosk. As he approaches, his lab colleague hands him his order, and they head for their last transfer.
- You look like you had a good ride.
- The seven was almost empty. Upper deck, window side. The window glass shaded before I even sat down.
- The Human Context Protocol knows you’re a morning thinker.
- It saw the Gigagram task in my queue and suggested a focus block timed around my caffeine hit.
- You work on Gigagram while commuting?
- Best place for it. No pings, no meetings, no drama. Just the route and whatever my brain does with it. Subvoc’d most of a concept map from South to Central.
- Glasses overlay?
He lifts the cup to chest height, the heat warning glowing along the rim.
- Layout floats about here, and the city moves behind it. Something about movement loosens the problem for me.
- I had something similar. My HCP slotted me into one of those anonymous, flash mentoring sessions on the tram.
- The transit-only ones?
- That’s the point. They launched it to get more people to use public transport. Fifteen minutes with someone from a different industry. No names, no companies. Just the problem. Protocols broker the match, transit AI scrambles the voices, and the session key expires when you step off. You can’t get it in a car.
- What was yours like?
- I described our problem: how to keep an image convincing on skin that curves, stretches, and ages differently on every person. First thing out of her mouth? We’re solving the wrong problem. Any projection from a curved surface to a flat plane loses something. So the problem isn’t to remove distortion, but to pick an acceptable one.
- What does she do, cartography?
- Something in spatial data.
- For skin?
- For skin, for maps, for anything that bends. She’d never heard of e-ink tattoos, but she understood the geometry in ten seconds. I’ve been turning that over since the bridge.
- And we haven’t even badged in.
- That’s the thing. I used to resent the commute. Forty-five minutes of dead time. Now my protocol has shaped it into this, I don’t know, intro? By the time I’m at my workspace, the hard thinking is already done. The office is for talking about it.
- My VP asked us to stop checking email in transit.
- Ours too.
- She said mornings are too valuable for comms or admin. If my protocol catches me opening emails before nine, it nudges me into a creative prompt instead.
- Does that annoy you?
- It did for a few weeks. Then I had the best idea I’ve had in two years, watching the river from a tram window. The protocol queued up a design challenge I’d bookmarked. It dimmed everything else, and then it just let me think.
- What was the idea?
- Our haptic dashboard. Whole interaction model. I sketched it in the air between North and the bridge.
- Wait, that was a commute idea?
- Twelve minutes of looking at water. Makes you wonder if we even need offices.
- We’ll need them for this.
- For what?
- For this. Right now. You told me about acceptable distortion from a stranger on a train, and I’m rethinking the whole Gigagram approach. Transit is for thinking alone. The office is for thinking together.
The temperature warning fades, so he savours a sip, then adds casually.
- By the way, my protocol suggested we sync our routes.
- It did what?
- We overlap for the last eight stops, and we’re both on Gigagram. We could flag this as collaborative transit.
- You want to turn our train ride into a meeting?
- A good meeting. No screen, no agenda. Just us and whatever we’ve been thinking about all morning.
- Did you accept?
- I wanted to ask you first.
- Accept it. But only for the last four stops. I’m keeping my river window time.
- Deal.

Memories to build from this future:
Try to recall a journey where you were watching the world slide past a window and a thought arrived that wouldn't have come at your desk. You weren't trying to think. You were just moving, and somewhere between two stops, something loosened and the shape of an idea was just there.
Now, stay in that motion:
Try to recall a regular morning when your context protocol dimmed everything except a problem you'd been sitting with, and the commute became the most focused part of your day.
What shifted about how you approach difficult problems once movement and quiet replaced your desk as the place for deep thinking?
How did you learn which tasks your protocol should protect your mornings for and which ones can wait until you arrive?
What changed about your resistance to being nudged once an idea you'd never have had at your desk arrived while you were watching the city pass?
Think back to a transit mentoring session where a voice-scrambled stranger from a different field reframed your problem before either of you stepped off.
What did the anonymity free up that a conversation with a colleague never would?
How did it change the way you describe a challenge once you had to explain it to someone with no context in your domain?
How did you start weighing ideas differently once the voice-scrambled session stripped away credentials and left only the thinking?
Go back to the quarter your team synced commute routes for unstructured conversation, and the office quietly became the place you share what you've already thought.
What changed about how collaboration feels once everyone arrives having done their hard thinking in transit?
How did your team negotiate which segments of the commute stay solo and which ones become shared?
Where did you first notice that an idea born on someone's train ride had shaped a decision before they'd even reached their workspace?
To close out this one. If the quietest, least structured parts of your day turned out to be where your best thinking already happens, what would you stop filling? What small experiment would you be curious to try?
And does anything here connect to patterns you've noticed across other sessions?