A bookshelf holds particular books. A metabookshelf holds the structure that produces the right bookshelf for a given context — a meta-function for knowledge and venture building. Publish the function, not the output.
First web edition, distilled from working notes 2022–2026.
A bookshelf holds this specific title, in this order, for this reader, right now. A metabookshelf holds something else: the structure that generates the right bookshelf for whoever meets it, in whatever context they bring. An early working document first sketched it as a framework of modular components: a structure of interlocking parts rather than a single finished list.
Instead of publishing a fixed, finished artifact, you publish the generating structure itself, and let each reader, team, or venture instantiate it for their own situation. The shelf that results looks different for every context it meets — the function that produces it stays the same.
The Schmachtenberger Connection
The word “function” here borrows deliberately from Daniel Schmachtenberger (co-founder of the Civilization Research Institute, formerly the Consilience Project), who popularized the idea of generator functions: rather than engaging each surface-level problem one at a time, identify the underlying dynamics that generate whole categories of problems at once. In his work on existential risk, a small set of generator functions — for example, rivalrous, win-lose dynamics multiplied by exponential technology — produce a wide range of catastrophic outcomes on their own. Working at the level of the generator function means one intervention addresses the whole class of problems it produces, not one instance of it.
The metabookshelf takes the same move constructively instead of diagnostically. Where Schmachtenberger asks, “what function generates these catastrophic outcomes?”, the metabookshelf asks, “what function generates the right set of resources, practices, and solutions for this context?” Define and publish the generating function; the concrete bookshelf — the curated set that actually shows up — falls out of applying it.
Schmachtenberger diagnoses the functions that generate risk. The metabookshelf tries the same move the other way — designing a function that generates what a context actually needs.
Concept: Daniel Schmachtenberger / Civilization Research Institute — from his talks and essays on the generator functions of existential risk, c. 2019. The constructive reading above belongs to these working notes, not to him.
How It Behaves
None of these came from designing a system top-down — they surfaced from actually trying to live the practice across 2022–2026, one working note at a time.
A metabookshelf lives as linked, modular blocks, not as a linear document. The links are not decoration on top of the content — they carry the structure itself.
Every block gets updated individually, carries its own history, and carries its own links — so the whole can keep growing without forcing a rewrite of everything around it.
The notes trace a publishing path from public Tana/Notion pages embedded in a blog, toward SilkNotes (the EvoBioSys sovereign-notes holon) once it’s ready — with visible backlink counts from anywhere on the web standing as a long-term wish.
The notes speak of a metabookshelf of solutions, of practices, of deliverables — and even one that “could also run as a holding company” across all nine purpose pillars (9pp — the nine purpose pillars structuring the EvoBioSys venture architecture).
The proto-EvoBioSys whitepaper and the “Onion of Truth” template both describe themselves as metabookshelves with multiple dependencies — including tricks like marking sections for selective disclosure: hide certain aspects, export a version without what’s marked private.
The “default bookshelf — one book to rule them all”: for any topic, the single best entry point the function selects when the context stays unspecified.
A finished list freezes yesterday’s values in place. A metabookshelf keeps re-evaluating them.
2026 Upgrade
Recent working notes (April 2026) admit that “bookshelf” served the idea well as a metaphor but never became fully intuitive, and reach for a more precise frame: a workflow function or meta-function (a function whose job is to keep producing the right values for a workflow, rather than to describe one fixed outcome).
The insight worth carrying forward: as the variables change, what counts as a good value for each variable changes too. The best AI model this year will not be the best model next year; the best book, tool, or practice for a context shifts as the context shifts. A finished list freezes yesterday’s values in place. A meta-function stays true to the moving target.
Publish the function — the criteria, the slots, the update rule — and re-evaluate the values whenever the variables move.
“Publish the function, not the output.”
This page distills working notes gathered between 2022 and 2026, not a finished argument. The properties, the instantiations, and the meta-function framing will keep sharpening as they meet more contexts — and, eventually, a real implementation in SilkNotes. Publishing it now — early and visibly unfinished — belongs to the same practice the rest of the Publications holon follows: built in the open, thought along rather than delivered whole.
Working notes 2022–2026 · First web edition