Artifacts Are Projections

A map projection takes one Earth and renders it a hundred ways. Nobody confuses the projection for the planet, and nobody panics when a projection ages, because the planet is still there. Your expertise works the same way once you encode it: the knowledge base is the planet, every artifact is a map printed from it, and staleness stops being a crisis because regeneration is cheap. The hard work moves upstream, into deciding what you actually know and stating it carefully enough to project from. That is director's work. The rest of this essay is the walk from the pain to the chair.

You shipped the thing. The deck, the app, the video, the course. It was good enough that people asked for another one, a different shape, a newer version. And six months later the thing is stale, the rework feels like starting over, and everything you actually knew while making it lives nowhere but your head.

What if the thing was never the asset?

Here's a question worth sitting with: when your artifact went stale, did your knowledge go stale, or just the surface it was printed on?

A map projection takes one Earth and renders it a hundred ways. Mercator for sailing, polar for flying, equal-area for honesty about Greenland. Nobody confuses the projection for the planet. Nobody panics when a projection ages, because the Earth is still there and you can always project again.

Your expertise works the same way, if you let it. Encode what you know (the decisions, the constraints, the hard-won "never again" rules, the vocabulary) into a knowledge base: a living, versioned, reviewable body of your own canon. That becomes the planet. Then every artifact is a projection: the website is a projection, the essay is a projection, the audio overview is a projection, the app scaffold is a projection. Some projections are deterministic builds. Some are generated: a model reading your knowledge base and rendering it as a video script, a slide deck, an interactive tool. Either way, the projection is disposable on purpose. Anything projected can be re-projected from the source that didn't go stale.

My own knowledge base spent months as a tangle. Personal story, portable methodology, and a tool's manual all shared one repository, and every artifact projected from it inherited the tangle. Untangling it meant deciding, document by document, which knowledge base owned which truth. The artifacts, it turned out, were the easy part.

So the work changes shape. You stop being the person who makes the things. You take the director's chair: you decide what enters the canon (what you actually know, stated carefully enough to be projected from) and you direct which maps get drawn, for which traveler, on which surface. The model does the drawing. You own the planet.

That question matters more than any tooling. I mean your judgment, not your outputs: the tensions you've learned to navigate, the failure modes you can smell, the rules you'd give an apprentice. That's the planet. Everything you've ever shipped was one map of it, drawn on one particular afternoon.

Fair warnings before you reorganize your life around a metaphor. This is a working rule, not a law of nature: I'll hold it until an artifact-first workflow beats it for knowledge work, and I'd genuinely like to see one try. It holds where the artifact is derivable from what you know. It does not hold where the artifact is the asset — a painting, a live performance, a codebase whose value lives in years of accumulated runtime behavior no document captures. And encoding costs real work up front; encode the wrong things carefully and you've built a beautiful planet nobody needs maps of.

The evidence isn't just my one tangle. The same substrate already serves a second expert's corpus — a theology scholar's dissertations — through identical machinery, and for twenty years colleagues have asked to "clone" me, which I eventually understood as demand for the methodology, not the person. The knowledge base is what cloning actually looks like.

One decision you'd defend, one constraint you've paid for, one definition you'd fight over. Written down, owned by you, licensed if you choose and never assigned. The projections will come faster than you expect. They always do, once there's something real to project.

The governance-side companion to this essay (the formal principle, the projection contract, the failure modes) lives in the ODD canon as Knowledge Base as the Unit. This is the view from the artifact looking back at its source. That one is the view from the source, looking out.