# The Graveyard

> A record of discarded directions and the judgment they preserve.

**Type:** Essay

Behind every mature practice there are dead projects. Whether you talk about them or not, they're there — the versions that didn't survive, the products that were abandoned, the approaches that were tried with full conviction and turned out to be wrong.

The instinct is shame, and shame's instinct is deletion. Clear the repos, drop the folders, stop mentioning them. Present the practice as if it walked a straight line to what it knows now.

This is the single most expensive mistake available to you, because it discards the only asset the failures produced.

**The graveyard is not failure. It is the research program that found the answer.**

## The Most Expensive Documentation You Own

A dead project that taught you why it died is documentation — the costliest kind, paid for in months and sometimes in love. Every other document in your practice cost you hours to write. The graveyard's lessons cost you entire projects to learn. They are, per word, the most valuable text you will ever possess.

They are waste only if they go unread.

So the practice is this: **write the failure home.** When a project dies — or when a living project pays for a hard lesson — the lesson doesn't belong in the dead repo, where no one will return. It belongs in the nucleus, where the pattern lives, written as a rule that carries its tombstone. Not "don't build the character" — a bare rule, which will collapse at the first clever argument — but "don't build the character; here is the corpse that taught us; here is what it cost." Rules with graves under them survive edge cases. Rules without reasons are just fences, and fences get climbed by anyone with a good enough reason of their own.

## What Only Failure Can Teach

The curriculum teaches you to lock in discovered truths — patterns that worked, decisions that mattered. The graveyard locks in something success can't provide: _cost_.

Success teaches what works. Only failure teaches what it costs when it doesn't — and cost is the half of judgment that optimism can't supply. A practice that ossifies only its wins builds a map with all roads and no cliffs. The graveyard is the cliffs. This is why the strongest prohibitions in any long practice aren't derived from principle. They're derived from autopsy. Principle can be argued with. A grave is just there.

## The Grief Is Real

One thing should be said honestly: abandoning a project you loved is a loss, and it behaves like one. There was a version of the future in which that thing worked, and you lived in it for a while, and it's gone.

Walk through that, not around it. Because grief metabolized becomes exactly the clarity the graveyard runs on: when the house falls, you finally see its shape. You see what the dead project was actually for — which is sometimes different from what you were building. You take what serves. You release what doesn't. Carrying the lesson forward while leaving the corpse buried isn't betrayal of the work you loved. It's the only form of honoring it that produces anything. The dead project's last act is to make the next one possible.

## Visit Before You Build

The graveyard's daily use is simple. When you're tempted to build something — especially something exciting, especially something _obvious_ — check whether it's shaped like an old grave.

Often it is. The compelling idea you had this morning is frequently the compelling idea you had two years ago wearing new clothes, and there's a stone with its name on it and a date and a cause of death. Sometimes conditions have genuinely changed, and the idea deserves resurrection — graves are records, not laws. But read the stone first. Know what killed it last time. Make the new attempt an answer to the autopsy, not a repetition of it.

---

> **Every mature practice is built on top of its own graveyard. The difference between practices that compound and practices that circle is whether anyone reads the stones.**