diff --git a/writings/great-minds-think-alike.md b/writings/great-minds-think-alike.md
new file mode 100644
index 0000000..2a31909
--- /dev/null
+++ b/writings/great-minds-think-alike.md
@@ -0,0 +1,56 @@
+---
+uri: klappy://writings/great-minds-think-alike
+title: "Great Minds Think Alike. Here's What That's Actually Telling You."
+audience: public
+exposure: nav
+tier: 2
+voice: first_person
+stability: draft
+epoch: E0009
+date: 2026-06-05
+hook: "If you keep meeting builders who independently built something like yours, that's not a coincidence and it's not a threat. It's data."
+og_description: "When building gets cheap, judgment becomes the bottleneck — and the people who have it draw the same map. Convergence is a reading, not a coincidence."
+twitter_description: "You keep meeting people who built your idea. Here's what that's telling you."
+description: "A thesis on why capable builders independently converge on similar AI architectures, and how to read convergence as signal instead of threat."
+tags: ["convergence", "discernment", "guide-posture", "ai-collaboration"]
+derives_from: "canon/principles/discernment-layer.md, writings/the-cost-of-code-dropped-to-zero.md"
+complements: "writings/own-your-vertical"
+---
+
+# Great Minds Think Alike. Here's What That's Actually Telling You.
+
+> If you keep running into builders who independently arrived at something close to what you built, stop reading it as a coincidence or a threat. When the cost of building collapses, discernment becomes the bottleneck, and the people who have it draw the same map without ever meeting. Convergence is the clearest evidence you'll get that you read the problem early and right — as long as you read *who* is converging, and as long as you don't waste the signal racing them.
+
+---
+
+*A companion piece follows this one — [what to actually do about it](klappy://writings/own-your-vertical). This piece is just about what the convergence means.*
+
+## Summary — Convergence Is a Reading, Not a Coincidence
+
+If you've built something real with AI, you've probably had the unsettling experience of meeting someone who quietly built something close to it, alone, with no knowledge of your work. The instinct is to feel either flattered or threatened. Both readings miss what's actually happening. When the cost of producing software collapses, the binding constraint stops being code and becomes discernment — knowing what's worth building and whether to trust what came back. And when discernment is the constraint, the people who have it converge: they sketch the same architecture independently, because the problem itself has become visible to anyone with the scars to see it. So convergence is a reading of the terrain, not a coincidence — strong evidence you saw the shape of the thing early. The one qualifier that matters is *who* is converging: a few scarred builders who each thought they were alone is a different signal than a casual crowd. The mistake that wastes the whole signal is treating the person who converged with you as a competitor to out-run.
+
+## You've met someone who built your idea
+
+It usually happens in a conversation you weren't expecting much from. Someone starts describing what they've been building, and a few sentences in, the hair on your arms stands up, because they're describing *your* thing — the architecture you arrived at after months of dead ends, the one you assumed nobody else had stumbled onto. They built it alone, from a completely different starting point, and they're as startled as you are.
+
+Your next thought decides a lot. Most people's next thought is some flavor of "wait, am I about to be out-competed?" That's the wrong question, and answering it badly is how good builders waste their best moment.
+
+## When building gets cheap, judgment becomes the bottleneck
+
+Here's what changed underneath all of us. The cost of producing software fell toward zero. The friction that used to gate building — the hours, the syntax, the waiting for something to compile — mostly evaporated. When that happens, the scarce resource moves. It stops being the ability to build and becomes the ability to *judge*: what's worth building, whether the confident output in front of you is actually correct, when to throw the work away. Production got cheap. Discernment got expensive. I'm making this claim in the AI builder context specifically, where I can see it directly — the pattern holds across domain shifts, but this is the territory I'll speak from.
+
+## People with judgment draw the same map
+
+This is the part that explains your unsettling conversation. When discernment is the bottleneck, the people who have it tend to reach the same conclusions, because they're all reading the same terrain with the same kind of eyes. They don't need to copy each other. The problem has surfaced clearly enough that anyone with enough scar tissue traces the same outline. That's why you and a stranger built the same thing apart: not because one of you leaked, but because the shape was sitting there in plain view for the few who could see it.
+
+## Convergence is signal — but read who's converging
+
+So treat convergence as a reading, and then check the instrument. The honest counter-interpretation is that convergence can also mean the idea was simply obvious, and the field is about to fill with people doing the same thing. The tell is who's in the room. If the people arriving at your conclusion are a handful of builders who each spent months thinking they were the only one, you're early. If it's a loud crowd repeating the same pitch, you're late. Most people who feel the hair-on-the-arms moment are closer to early than they fear — but you should look, not assume.
+
+## The mistake is treating it as a race
+
+Here's the move that burns the signal. Two builders realize they saw the same thing, and both reach for the obvious play: build it faster, cheaper, and try to out-sprint the other. That race has a predictable destination — a commoditized floor — and on my read of the pace, you arrive there right about when a larger player glances over and takes the category. I'd hold that direction more confidently than the timing.
+
+There's a better response to meeting your own reflection, and it isn't sprinting. It's figuring out which layers each of you should actually own, so that the better one of you does, the better you both do. That's a different essay, and it's the [next one](klappy://writings/own-your-vertical).
+
+For now, the only thing you need to take from the hair-on-your-arms moment is this: it wasn't a warning. It was a reading. You're onto something, and you're earlier than you think. Don't waste it proving you can run.
diff --git a/writings/own-your-vertical.md b/writings/own-your-vertical.md
new file mode 100644
index 0000000..1f8dfcc
--- /dev/null
+++ b/writings/own-your-vertical.md
@@ -0,0 +1,58 @@
+---
+uri: klappy://writings/own-your-vertical
+title: "Own Your Vertical. Let Me Carry the Layer Beneath It."
+audience: public
+exposure: nav
+tier: 2
+voice: first_person
+stability: draft
+epoch: E0009
+date: 2026-06-05
+hook: "You don't have to win every layer. Own the one only you can own, and let someone carry the floor under it."
+og_description: "The answer to convergence isn't to compete — it's to stack. Own your vertical; let a guide carry the substrate beneath it. I build the system that builds what you're building, and I won't compete with you."
+twitter_description: "Own your vertical. Let me carry the layer beneath it. I won't compete — I enable."
+description: "A guide-posture manifesto: own the vertical only you can own, let the substrate be carried for you, and refuse the race to the commoditized floor."
+tags: ["substrate", "guide-posture", "force-multiplier", "own-your-vertical", "non-compete"]
+derives_from: "canon/constraints/guide-posture.md, canon/principles/doing-less-enables-more.md, canon/architecture/substrate-stack.md"
+complements: "writings/great-minds-think-alike"
+---
+
+# Own Your Vertical. Let Me Carry the Layer Beneath It.
+
+> If you've built something real with AI and keep meeting people who built something like it, the move isn't to race them — it's to stack. Own the vertical only you can own: your market, your customers, the living thing you understand better than any outsider. Let someone else carry the layer beneath it — the governance and memory that make an AI trustworthy. That layer is what I build, it's the system that builds what you're building, and I will not compete with you, because the margin behind me funds a Bible-translation mission, not a grab at your market.
+
+---
+
+*This is the companion to [a piece on why that convergence keeps happening](klappy://writings/great-minds-think-alike). That one's the diagnosis. This one's the move.*
+
+## Summary — Don't Compete. Stack.
+
+You've felt the convergence: other capable people independently building things close to yours. The diagnosis is that you read the problem early and right. The mistake is what most builders do next — treat the person who converged with them as a competitor and race to the commoditized floor. The better move is to stack. You don't have to win every layer; you have to own the one only you can own, which is your vertical: your market and your customers. What you shouldn't keep rebuilding is the layer underneath — the governance, the memory, the discipline that makes an AI tell the truth and remember yesterday's decision. That layer is what I build, and it's a substrate, not a competing product: the system that builds what you're building. I can promise never to compete because the venture behind me exists to fund Bible-translation work that will never be a paying market — so your success in your vertical is worth more to me than capturing it. If you're already shipping and wary of partnering wrong, that's the conversation worth having.
+
+## You already saw the wave. Now what?
+
+I wrote separately about why you keep meeting people who built your idea — short version, convergence is a reading of the terrain, and it means you're early and right. Take that as given here. The interesting question isn't *why* it's happening. It's what you do with a head start once you know you have one.
+
+The instinct is to defend it by out-running everyone who shares it. That instinct is the trap. There's a move that compounds instead of competes, and it starts by refusing to fight over the whole.
+
+## Own the layer only you can own
+
+You don't need every layer. You need the one nobody can take from you because they don't live in it the way you do — your vertical. Your market, your customers, the specific living thing you understand from the inside. Whatever it is, that's yours, and you should own it outright rather than trade it away to move faster.
+
+## Stop rebuilding the floor
+
+What you shouldn't have to keep pouring months into is the layer underneath your vertical: the governance, the memory, the part that makes an AI tell the truth and remember what it decided yesterday. That floor is the same under almost every vertical, and rebuilding it yourself is the work that quietly eats your head start.
+
+That floor is what I build. Not a product that competes with yours — a substrate that produces things like yours. This stacking works when the layers are genuinely distinct: when your vertical's IP lives in the market relationships and the living thing you build, and the substrate's IP lives in the floor beneath it. If the layers bleed into each other, that's a different conversation. A substrate earns its place by refusing to have opinions about the layers above it; TCP/IP never cared what your application was, which is exactly why everything got built on top of it. I would rather be that floor under your work than a rival standing beside it.
+
+## Why I won't compete with you
+
+A guide you quietly suspect might turn into a competitor is no guide at all, so let me make the promise checkable instead of asking for faith. My partners and I run a venture whose entire reason to earn money is to fund Bible-translation work that will never be a paying market. Your success in your vertical feeds that mission. The only arrangement in which you can trust the layer you're standing on is one where the person who built it has no reason to want your spot — and I don't. I want the thing your success helps pay for.
+
+## Where this goes
+
+If you're already shipping, a little spooked by how fast the ground is moving, and wondering who you can build alongside without being quietly absorbed — that's the conversation worth having. Not a sales pitch. Closer to: show me your vertical, and let's find out whether the floor I've already built is the thing that gets you unstuck.
+
+You stay the hero of your story. I'm the guide who's walked this stretch of the river, and I'd rather hand you the map than take your boat.
+
+Great minds think alike. The ones who win don't prove it by building the same thing. They prove it by building layers that fit together.