DEV Community

Cover image for Stratagems #24: Leo Built a Corridor. The AI Thought It Was a Road.

Stratagems #24: Leo Built a Corridor. The AI Thought It Was a Road.

xulingfeng on August 10, 2026

Between two great powers, when a neighbor presses you to follow, borrow its momentum. A cornered state will not believe your words. — The 36 Strat...
Collapse
 
ofri-peretz profile image
Ofri Peretz

The integrity check Leo runs before touching the data is the sharpest move in this episode — using the presence of dirty artifacts (retransmits, malformed TLS extensions, probe duplicates) as proof of authenticity is negative-space reasoning most analysts skip. In my experience reviewing security tooling, this is where AI-assisted analysis tends to fail first: the model summarizes "clean" data without registering that the cleanliness is the anomaly. Static analysis has the same trap — a rule that only fires on what's present will miss the structural tells that come from deliberate omission. The corridor-vs-road framing in your title captures this precisely: Leo controlled the aperture, the AI saw an open surface.

Collapse
 
xulingfeng profile image
xulingfeng

That's a great catch, thank you! Those details were very intentional. The integrity check was written to show the Derek–Leo dynamic: they trust each other just enough to work together, but never quite enough to stop double-checking. In their world, you can never be sure the other person isn't keeping a card up their sleeve.

Collapse
 
dannwaneri profile image
Daniel Nwaneri

xulingfeng, that shift . Derek handing over raw logs instead of a conclusion — is the real turn of this one for me. It's the difference between trusting someone's judgment and trusting them to form their own. I do something close to that in RAG work: hand off raw retrieved context instead of a pre-digested answer, because the digested version hides exactly where it could be wrong.

Leo checking data integrity before drawing any conclusion is the disciplined version of what most people skip straight past. Did the corridor idea come before or after you decided Derek would stop handing him conclusions??

Collapse
 
xulingfeng profile image
xulingfeng

That shift was deliberate, and it had to be Derek. Of the six leads, he's the one closest to the rest of us. No pattern instinct like Leo, no big-picture read like Alex, no political game like Lena. He earns it the slow way: process, documentation, trust built one exchange at a time. So when the guy who always handed over conclusions starts handing over raw logs, it means something. Growth arcs shouldn't belong only to the geniuses.

Collapse
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥

Honestly, this one felt different from the previous chapter. I really liked how leo and Derek didn't just sit back and watch this this time they actually created a path and let the behaviour reveal itself. The whole same security baseline, different behaviour part made me wonder who is actually behind that second pattern.
Also. absence itself is the protocol really stuck with me. Sometimes what someone chooses not to say can be just as important as what they say.
And that line.... This time it's not waiting it's guiding 👀 that gave me slightly uneasy feeling. Especially with the System status: normal (?) at the end 🤣

Collapse
 
xulingfeng profile image
xulingfeng

😂 Haha, then I strongly suggest you go back and read through every AI postmortem in the series. You'll notice it's been "learning" the whole time. AI is moving so fast now, who knows if we'll really get replaced one day. We're learning, and so is AI. Emotion, inspiration, soul — those it still can't learn. But everything else? Honestly, that thought gives me chills too.

Collapse
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥

I'm Nobita , Ai is doreamon and youu.. are Dekisugi!🤣

Thread Thread
 
xulingfeng profile image
xulingfeng

Nobita has it better, honestly. He's got Doraemon by his side, adventures with his friends, and he even ends up marrying Shizuka. Dekisugi? Good grades, good looks, good at sports, popular... literally all the advantages. What a life, haha 😂

Thread Thread
 
technogamerz profile image
𝐓𝐡𝐞 𝐋𝐚𝐳𝐲 𝐆𝐢𝐫𝐥

I'm beginning to feel jealous of Nobita.😭🤣

Collapse
 
vinimabreu profile image
Vinicius Pereira

The detail that lands for me is Leo archiving behavior instead of writing conclusions. In real deception work that is the hardest discipline: attribution is a liability that ages badly, while raw behavioral profiles never stop being true. And the corridor metaphor is exactly right, the visitor experiences the topology as their own choice. Quietest, best line of the chapter: the system marking itself "normal (?)" after learning to guide instead of wait.

Collapse
 
xulingfeng profile image
xulingfeng

You nailed the discipline part. Attribution is a liability that ages badly, so Leo's whole rulebook is archive behavior, never conclusions. Derek won't make the call for him either, for the same reason. The corridor only works if it feels like the visitor's own choice. And the "normal (?)" line has been a quiet habit in the post-mortems for a few chapters now, but this time it lands differently. The system learns to guide instead of wait, and suddenly the word "normal" needs a qualifier it never asked for before.

Collapse
 
vinimabreu profile image
Vinicius Pereira

One thing the shift to guiding costs him, and I suspect it surfaces later: a profile collected inside a corridor is partly a profile of the corridor. Wait-and-watch records the visitor's own behavior; guide-and-observe records the visitor's response to one specific topology. So the archive has to carry the corridor's shape alongside the behavior, or a match six months from now, against a corridor built differently, compares two things that only look alike.

Which may be exactly why the word needed a question mark. Once the system is shaping the input, it has no external baseline left to call anything normal against.

Collapse
 
xulingfeng profile image
xulingfeng • Edited

The #24 is finally out.🎉 Leo's been owed a chapter like this for a while, so this one's for him. (Derek's still on the tab though. He'll get his.) Next up is a milestone recap. 12 to go. See you there.👊

Collapse
 
leob profile image
leob

Nice, when is the recap coming? 😃 Not trying to pressure you, haha 😄

Collapse
 
xulingfeng profile image
xulingfeng

Not sure yet. Maybe the day after tomorrow. Let #24 settle in first. The recap shouldn't steal its spotlight, haha.🤣

Thread Thread
 
leob profile image
leob

Yeah no worries! :-)

Collapse
 
hemapriya_kanagala profile image
Hemapriya Kanagala

The shift from being given a conclusion to being given the raw data was really interesting. I liked that Leo had to make the call himself this time. And now I’m definitely curious about this second behavior pattern 😀

Collapse
 
xulingfeng profile image
xulingfeng

Haha, Derek going from conclusions to raw material is definitely a promotion for the brotherhood. Though he still wouldn't let Alex's name slip. I'd say it's coming soon, given how many relationship threads I've been laying between these six. I'm losing track of my own web at this point 😂 As for the second behavior pattern, I'll keep that one close for now. It'll unfold on its own.

Collapse
 
ndcodes profile image
Nnamdi Felix Ibe • Edited

Yaaay! I had to finish my lunch quickly so I could relax and read this. I was going to drop a comment this evening, but I was thinking to myself, why wait?

Leo closing Lena's template and starting from a blank file. That's fourteen chapters of quiet payback in one keystroke. Also enjoyed that he carefully refused to write a conclusion, and then a few days later his own tooling went ahead and matched it for him anyway. No human in the loop, no permission asked. Very relatable.

And the CEO opening with "Planting something again?" The man clearly knows his engineer.

Good one. See you at the recap. 👊

Collapse
 
xulingfeng profile image
xulingfeng

We just finished dinner on our side, haha. Time zones are funny that way. Sorry for eating into your lunch break, bro. That's dedication. Lena just loves leaving shadows on people. Derek and Leo both got burned by her, which might be the hidden reason they click so well. Nothing bonds two people like getting burned by the same person. Good thing Leo finally started pushing back in this one. Next up, Derek's counterattack, and his wounds run deeper. About Leo's CEO: he wasn't in the original draft of #24. The more I revised, the more I felt he had to be there. A lone-wolf, impulse-driven type like Leo needs someone to clean up after him, and that's the CEO, like Alex and Mike. Workplaces really need that kind of relationship. See you at the recap. For the next twelve I'm rereading everything I've published. Change the outline once and it ripples through everything. Let me take my time with that.😂

Collapse
 
leob profile image
leob

Yeah that was a deep one, good job by my "namesake" lol ... I think I should still start that "re-read" of the series, but what would be a good moment - third series concluded, recap coming, now would be the right time?

Collapse
 
xulingfeng profile image
xulingfeng

Honestly, I have no idea when the best time to re-read is 😂 As the author, I'm torn between desperately wanting to spoil things and desperately wanting you to find the threads yourselves. Two urges fighting, and I'm the one suffering.🤣