📚 Series Navigation:
← Previous: Part 2 - The Performer
👉 You are here: Part 3 - The Gatekeeper
Next: Part 4 - The Borrower →
On the third species in our field guide: the technical expert who treats knowledge the way dragons treat gold — sitting on it, sleeping on it, and answering Slack messages about it at 23:40 on a Sunday.
🧬 Human Code — A field guide to the corporate predator. Seven episodes. One habitat. No clean hands.
- 🔥 The Arsonist — Ignis salvator
- 🎭 The Performer — Architectus theatralis
- 🔐 The Gatekeeper — Draco runbookensis ← You are here!
- 🪤 The Borrower — Pica creditrix
- 🪞 The Collector — Fiducia disponibilis
- 👻 The Phantom — Praesentia vacua
- 🧫 The Habitat — the finale
📋 SPECIMEN PLATE №3
Species: Draco runbookensis — the Documentation Dragon
Habitat: legacy systems, deployment pipelines, the only chair that knows the password
Diet: dependency, midnight questions, unwritten context
Call: "Let me just handle it, it'll be faster."
Conservation status: endangered only by wikis, which it eats
✉️ A Note from the Field
A warning before we enter this territory: today's specimen is, by every conventional measure, the most valuable animal in the building. Its knowledge is vast. Its judgement is trusted. Its availability is heroic. That is the entire problem. The Arsonist's value is a performance and the Performer's value is a costume, but the Gatekeeper's value is real — it's the monopoly on that value that makes the species dangerous.
This is also the first specimen in the guide for which the field researcher feels genuine sympathy. Hold that thought until the end. It matters.
🎬 Cold Open: The Deploy
Andrei has been trying to deploy to staging for three hours.
The wiki sent him to a runbook. The runbook sent him to a config repo. The config repo's README sent him — with the cheerful confidence of a sign pointing off a cliff — back to the wiki. At 14:20 he gives up and asks in #platform-help, and the answer arrives from four desks away before the message has finished posting.
"Don't touch the env vars on staging-2. Let me just handle it, it'll be faster."
And it is faster. Four minutes later the deploy is green. Andrei has learned nothing, which means the next deploy will also go through the same four desks, which is — though no one in the room would phrase it this way — the business model.
Observe the specimen in its den: surrounded by three monitors, terminal sessions stacked like geological strata. It is patient. It is generous. It will explain anything — verbally, fluently, and at a speed precisely calibrated so that you retain 40% and return within the week. At 23:40 on a Sunday it answers a production question in four minutes, and the grateful emoji bloom like flowers around a watering hole.
FIELD LOG — J. (QA), entry 17: Specimen's median Slack response time: 4 minutes, including weekends. Median age of its documentation: 3 years. These two numbers are not unrelated. They are the same number, wearing different hats.
📓 Field Notes: The Monopoly
The sociologist Max Weber — a man who studied bureaucracy with the enthusiasm of someone who found misery intellectually fascinating — identified the pattern a century before the first standup meeting. He called it the monopolisation of knowledge: in any organisation, the people who control information control the organisation, regardless of what the org chart claims. The clerk who knows how the filing system works has more actual power than the director who signed it, not because the clerk is senior, but because the clerk is necessary.
Weber meant it as a description. Draco runbookensis uses it as a survival strategy.
The crucial field observation is that the dragon never refuses to share. Refusal would be visible, and visible is dangerous. Instead it shares in a format that cannot be stored. The verbal walkthrough. The screen-share that nobody recorded. The Slack thread that scrolls into the void. Ask it to write things down and it agrees warmly — "yeah, I should really write that up" — a vocalisation with the same sincerity as "we should get coffee sometime," technically true, functionally extinct.
That is not teaching. That is leasing. The knowledge never transfers; it is rented, per question, with the dragon as sole landlord. And every transaction compounds the dependency, until the team's entire operational memory lives in a single skull — an architecture decision nobody made, with a bus factor of exactly one.
🦴 Lifecycle: The Hoard
FIELD LOG, month 2: Reviewed specimen's code documentation. Technically present — parameters, return types, the works. Describes what in loving detail. Never why. The why is the hoard. The what is the decoy.
FIELD LOG, month 5: Production incident, payments adapter. On-call engineer attempted the obvious fix. The obvious fix broke invoicing, because there was a reason the code was non-obvious, and the reason lives in exactly one place, and that place was on holiday in Crete. Incident resolved by long-distance phone call. The hero, once again, was the dragon. The dependency, once again, got deeper. Every rescue feeds the moat.
And the team adapts, the way ecosystems adapt to any apex resource-holder. Why spend three days writing the runbook when the dragon answers in four minutes? Why insist in the retro — again — on the bus-factor item that gets moved to "ongoing" — again? The moat is invisible precisely because crossing it is so convenient. Nobody addresses it, because addressing it would require saying out loud: we are entirely dependent on one creature, that creature has done nothing to mitigate the risk, and we have rewarded it for years.
Then one day the dragon is gone. They always go — promotion, resignation, burnout. Mostly burnout, because being the single point of failure for an entire system is exactly as exhausting as it sounds, and nobody thinks to ask whether the animal that always has the answers might be drowning in the cost of always being asked.
Week one: the team discovers the deployment has six undocumented manual steps, three involving environment variables that existed on exactly one laptop — which IT, with impeccable timing, wiped on the specimen's last day.
Week two: an incident in the dragon's territory. The on-call engineer reads everything ever written down, understands all of the mechanics and none of the reasoning, and learns the difference the hard way.
Week three: someone finds the Confluence page. You already know what it says. We'll frame it in a moment, like the museum piece it is.
Week four: the engineering manager calls a meeting with one agenda item, the question that should have been asked two years earlier: how did we let this happen? The honest answer — nobody let it happen; it happened the way rust happens, one convenient four-minute answer at a time — does not make it into the minutes.
🗂️ Exhibit C
EXHIBIT C — Recovered from Confluence, fourteen months after the specimen's departure:
Deployment Process — Payments Platform
Owner: [REDACTED] · Last edited: 3 years ago
"This page documents the full deployment process for the payments platform.
TODO: add details"
Field annotation, J. (QA): this artifact is the most common spoor left by Draco runbookensis. Carbon-dating the TODO is the standard method for estimating how long a territory was occupied. This one is old enough to attend nursery school.
🔬 The Field Identification Guide
Late afternoon. Janet finds Andrei still at his desk, halfway through a diagram of the staging pipeline that he is reconstructing from memory, like a court artist. She pulls up a chair.
"You're doing archaeology," she says. "Good instinct, wrong order. First, learn to identify the species while it's still in the building. Run this test: could you deploy that system using only what's written down? No Slack. No four desks away. Paper and pipeline only."
"Honestly? No. I'd need to ask him."
"Then you've found your dragon. Second test — watch how knowledge moves around him. If the critical answers always travel by conversation and never by document, the channel is being kept narrow. Maybe by strategy, usually by convenient neglect, but narrow either way. A bottleneck with a friendly face is still a bottleneck."
"He did offer to just handle it for me."
"Of course he did." Janet taps the diagram. "Third test. When you ask to own something — not borrow, own — listen for the call of the species: it's more complicated than it looks. There's a lot of history here. Let me just handle it, it'll be faster. Complicated systems can be explained in writing, Andrei. History can be recorded. 'Faster' is how the moat stays full."
"So he's a villain who answers production questions on Sunday nights."
Janet is quiet for a moment, which Andrei has learned means the lesson is about to change shape.
"No. That's the part you need to get right, because if you get it wrong you'll make it worse. Watch him in the next reorg meeting. Watch his face when they announce the new platform team. That animal isn't guarding treasure because it loves gold. It's guarding the only proof it has that it can't be replaced. Punish the hoarding and you confirm the fear — and a frightened dragon digs deeper. There's exactly one thing that works, and I've seen it work twice in fifteen years: make the sharing worth more than the hoard. Praise the runbook louder than the rescue. Promote the engineer who made themselves replaceable. Dragons follow the gold, Andrei. Move the gold."
🧭 The Naturalist's Note
Of all the species in this guide, this is the one I have the most sympathy for, and I want to be honest about why: the Gatekeeper is afraid. Being wanted is conditional — you can be wanted today and unwanted after the next reorg. Being needed is structural. You can't be deprecated if the pipeline lives in your head. The hoard was never about power. It's a moat around a single, trembling belief: if anyone else could do what I do, I would stop mattering.
So if you manage a dragon, don't bring a sword. Bring a better incentive. Recognise the engineer who writes the runbook, not just the one who executes it. Make "I made myself replaceable" the highest-status sentence in your engineering culture. It is the hardest cultural shift in this industry — harder than Agile, harder than DevOps, harder than whatever the methodology is called this quarter — because it asks people to believe their value doesn't decrease when it's shared.
And if you are the dragon — if you read this with the quiet recognition of someone sitting on a very organised hoard — open the drawer. Show them the map. It won't make you less valuable. It'll make you the kind of valuable that doesn't require a hostage.
The Library of Alexandria burned, and nobody knows how much was lost, because the catalogue burned with it. The knowledge that survives from the ancient world isn't what was hoarded in one place. It's what was copied, shared, and scattered across libraries nobody thought important enough to burn.
Be the copy, not the original. Originals are fragile. Copies are how things survive. 🪨
Next in the series: 🪤 The Borrower — a magpie, a one-to-one, and the strange journey of an idea from your Slack DMs to someone else's slide deck.
