Everyone Steals - The Smart Ones Call It Learning.

August 5, 2026 SupportTrenches Systems, Processes & Resilience 5 minutes

What the AI distillation wars accidentally teach us about knowledge hoarders in your own org

24,000 fake accounts. 16 million conversations. That's what it allegedly took for a handful of ambitious AI labs to siphon the intelligence out of a rival's frontier model - a technique politely called "distillation," less politely called "photocopying someone else's brain."

The victim was outraged. Letters to the Senate. Talk of industrial-scale intellectual property theft.

The same victim had recently paid 1.5 billion dollars to settle a lawsuit over training its model on roughly seven million pirated books.

You can't write satire anymore. Reality keeps scooping you.

There's an old saying: "rob one person and you're a thief. Rob everyone and you're an institution." The frontier labs scraped the collective output of humanity - every blog post, every forum answer, every Stack Overflow rant written by an engineer who just wanted to help - declared it fair use, and built trillion-dollar valuations on top. Then someone scraped them, and suddenly the concept of intellectual property was rediscovered with the zeal of a fresh convert.

Here's the uncomfortable part: the distillers aren't doing anything humanity hasn't done since the first apprentice watched the first blacksmith.

Distillation IS civilization. Apprentices copying masters. Scientists building on prior papers - the entire citation system is just distillation with receipts. Engineers reverse-engineering competitors' products. Michelin-star chefs doing unpaid stages in other Michelin-star kitchens specifically to absorb and mimic. I learned to cook by watching an unreasonable amount of food television and later YouTube. I learned woodworking entirely from YouTube. Nobody sued me. Knowledge transferred, compounded, and the world got one more person who can produce both a decent braise and a dovetail joint.

Every "stolen" output becomes someone else's input. That's not a bug in the system. That's the only reason the system works.

Which brings me to your org. Because you have a distillation war running right now, and it's costing you more than you think.

Every support and engineering team I've ever worked in had at least one of him: the senior engineer with the private notes file. Years of fixes, workarounds, tribal knowledge - all in a personal document nobody else could see. Ask him why he doesn't put it in the knowledge base and you get a shrug and something about "not having time to write it up." The real answer, which he'll never say out loud, is job security. He thinks his knowledge is his moat.

I spent years as a KCS Ambassador fighting exactly this, and here's what I learned: the hoarder's strategy fails in both directions.

Direction one: the moment he leaves, gets sick, or burns out, the org discovers his moat was actually a single point of failure with a salary. I've watched a team lose six months of velocity because one man's encrypted brain walked out the door.

Direction two - and this is the part nobody tells the hoarder: you cannot be promoted out of a job only you can do. Management isn't stupid about this. If replacing you causes a crisis, you will never be moved, elevated, or given the interesting project. You've built a prison and called it leverage. Meanwhile the power horse 🐎 who documents everything, who deliberately makes him- or herself replaceable, keeps getting handed bigger problems - because s/he can be extracted from the current one without the building catching fire.

The AI labs and the knowledge hoarder are making the same mistake: they're defending the exhaust instead of the engine. A model checkpoint, a private notes file - both are snapshots of yesterday's learning. Anyone who copies them gets your past. If your rate of producing new knowledge is high, being distilled barely matters; the copy is stale on arrival. The panic only makes sense if you secretly suspect your lead is nothing but your last snapshot. That's the confession hiding inside every outraged press release.

👉 Knowledge that isn't transferred doesn't compound. It just depreciates in one person's head.

👉 Judge your moat honestly: is it the artifact (copyable, always) or the machine that produces artifacts (copyable, never)?

👉 If you run a team: reward the people who make themselves replaceable, loudly and visibly. The incentive structure most orgs run does the exact opposite, and then leadership wonders why nothing is documented.

👉 If you're the hoarder: your file isn't a moat, it's a ceiling. Publish it and go build the next thing nobody knows yet.

If someone can copy everything you know and replace you, you were never a source. You were a cache.

👇 Every org has one encrypted brain walking the hallways. What's your plan for the day it walks out?

This article is also available in German.

AICareerDocumentationKnowledge ManagementManagement