feat: 'Artifacts Are Projections' (public essay) + bifurcation session journal

journal/2026-06-09-bifurcation-execution-and-boundary-canon.tsv

@@ -0,0 +1,10 @@
+type	typeName	facet	quality_score	quality_max	quality_level	title	content
+D	Decision		5	5	strong	Bifurcation executed: three repos live, one-KB-per-concern restored	142→160 docs to outcomes-driven-development (public), 74→67 manuals-only to oddkit, klappy.dev is the overlay. ODD repo public until private-repo auth lands; license deliberately open; no federation today — knowledge_base_url per repo.
+D	Decision		5	5	strong	All undecided markdown adjudicated live; AGENTS.md split is the only structural remainder	Overlay: identity, relationships, chosen styles (guide-posture), house genres, provisional Triangle. Core: vodka cluster, writing canon, dual-context, portable methods, boundary trio (envelope-time-fields, canon-integration-audit, frontmatter-validation-before-merge).
+D	Decision		5	5	strong	Four routing criteria canonized as odd://canon/constraints/core-boundary-criteria (tier 1)	Topic is not the routing criterion; provisional found-frameworks stay overlay; exposed tension is core, the ruling is overlay; tool repos are manuals only. Plus proof-vs-subject, operational genericization, derivation-chain cohesion. Challenge battery passed, canon-tier-1 mode, no tensions.
+O	Observation		5	5	strong	Body-grep routing shipped stowaways: the bifurcation DR traveled to both repos by quoting the enum	Mover selection string-matched target_repo values in document bodies. Frontmatter-only recompute: ODD 140, oddkit 74, undecided 19; zero missing. Fixed in outcomes-driven-development#2, oddkit#183. Canonized as a named failure mode.
+O	Observation		4	5	medium	First odd:// mint normalized to klappy:// by the worker	core-boundary-criteria minted as odd:// per D0002 item 7; get returned uri klappy://… — concrete evidence the authority-as-column work item (D0002 item 3) is unimplemented. Logged against the P2 backlog entry.
+O	Observation		4	5	medium	Standalone KB override verified end-to-end	catalog/search/get/resolve/orient all served from outcomes-driven-development via knowledge_base_url; grouped search showed zero baseline leakage; klappy-only content correctly invisible (triangle query: 1 hit vs 3+).
+L	Learning		5	5	strong	The maintainer's corrections are the calibration data — encode each as a worked example	Every criterion in core-boundary-criteria was minted from a live correction to an over- or under-eager routing call (triangle-pass pulled; vodka cluster kept core; manuals-only boundary). Smell-pass distinguished klappy-as-proof (stays) from klappy-as-subject (moves).
+L	Learning		5	5	strong	Knowledge base as the unit; artifacts are projections	The organizing principle the bifurcation converged on: KB is the durable asset (write model), artifacts are regenerable projections off the read model, the human holds the director's chair (adjudication + projection direction). Encoded as odd://canon/principles/knowledge-base-as-the-unit + public essay klappy://writings/artifacts-are-projections.
+H	Handoff		4	5	medium	Open: AGENTS.md split, stakes-calibration split, complement-vs-supersede ruling, PAT rotation	Class-3 detangling (mixed-scope docs) awaits maintainer ruling on overlay-extends-core mechanics (complement vs supersede). Queue unchanged: read defaults → removal pass, worker auth, license. Rotate the in-chat PAT.

writings/artifacts-are-projections.md

@@ -0,0 +1,41 @@
+---
+uri: "klappy://writings/artifacts-are-projections"
+title: "Artifacts Are Projections"
+audience: public
+exposure: public
+tier: 2
+voice: first_person
+stability: draft
+tags: ["knowledge-base", "projection", "artifacts", "directors-chair", "ai", "expertise"]
+public: true
+type: "essay"
+slug: "artifacts-are-projections"
+hook: "You shipped the thing. Six months later the thing is stale, and everything you knew while making it lives nowhere but your head."
+description: "The artifact was never the asset. Your knowledge base is — and every app, essay, video, or deck is a projection you can regenerate at will. Companion to the ODD principle 'Knowledge Base as the Unit.'"
+date: "2026-06-09"
+epoch: "E0009"
+og_description: "The artifact was never the asset. Your knowledge base is — everything else is a projection."
+companion: "odd://canon/principles/knowledge-base-as-the-unit"
+---
+
+# Artifacts Are Projections
+
+You shipped the thing. The deck, the app, the video, the course. It was good — 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*, because anything projected can be re-projected from the source that didn't go stale.
+
+I learned this the slow way. My own knowledge base spent months as a tangle — personal story, portable methodology, and a tool's manual all sharing one repository. Every artifact projected from it inherited the tangle. Untangling it meant deciding, document by document, which knowledge base owned which truth. The artifacts weren't the hard part. The artifacts were never the hard 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 projections get made, for which audience, on which surface. The model runs the camera. You own the screenplay.
+
+Which raises the question that matters more than any tooling: what do you know that nobody else has encoded? Not your outputs — your *judgment*. 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 a photograph of it.
+
+Start there. 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.