To Esthergen.
About the Author
Sean Devine is the Founder and CEO of XBE, a business operations platform for heavy materials, logistics, and construction. He founded XBE in 2016 with no construction-industry experience and no venture capital, and built it into a profitable software business with strong retention, serving tens of thousands of users across more than 100 customers, and growing to a global team of more than 100. In January 2024, he sold the majority of XBE to Banneker Partners and remained CEO and a significant shareholder. Since the transaction, he has continued to run the company while maintaining growth through a combination of organic product development and M&A, leading the acquisitions and integrations of BCMI, Gauge, and PriceBee.
His work has spanned entrepreneurship, operations, leadership, software development, and strategy, with a continuing interest in reducing the need for specialization.
Before founding XBE, he co-founded Partage in Chicago. Partage pioneered self-service spot freight brokerage by automating pricing and booking for partial- and full-truckload freight ahead of where the market would later move. In 2015, Partage’s software was acquired by TTS and its brokerage operation was acquired by MGN Logistics.
From 2006 to 2010, he held multiple roles at Con-way, including Vice President of Pricing and Engineering at Con-way Freight, where he was responsible for Strategy Management and led the rollout of Lean Six Sigma as the company’s continuous improvement operating system during the Great Recession. He also served as Chief Procurement Officer and Vice President of Engineering at Con-way Inc.
He attended Babson College from 1996 to 1999, where he studied Finance and Entrepreneurial Studies.
He also invests in businesses where his operating experience can contribute.
He grew up in Albany, New York, and lives in San Francisco, California, with his wife, Theresa, and their two youngest daughters.
He’s @barelyknown on X.
About the License
The transition from alchemy to chemistry was not a leap in human intelligence; it was a change in protocol. Alchemists hoarded knowledge, encoding their findings in metaphor to prevent theft. As a result, their discoveries often died with them. Chemistry became a science only when the Royal Society enforced a new standard: Nullius in verba (“take nobody’s word for it”). They demanded that methods be published, replicated, and critiqued in public. Knowledge was transformed from a private hoard into a public object.
The Dionysus Program is released under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License in the same spirit.
Making the text available also makes it easier to criticize and improve.
The program should be subject to the scrutiny it recommends. To that end:
- Quote and share freely. The text is designed to travel.
- Criticize in public. If you disagree, do so in the open. The program requires friction to remain honest.
- Patch the code. If you find errors—in logic, phrasing, or explanation—please submit a pull request on GitHub.
A Note on the Print Edition
A print edition is available for readers who prefer a physical book or want to give a copy to someone else.
The digital edition remains free.
Foreword
A good book can make you smile or make you think. But only great books change who you are and what you’re capable of.
The Dionysus Program can inject a new worldview. Not just at the surface level of your observations, but to transform you into a person who can thrive in an ever-changing world with grace.
A talent I seem to have is recognizing genius in others. Charlie Munger’s line “the best thing a human being can do is to help another human to know more” sat well with me. So I take particular pleasure in identifying brilliant people, important ideas, and promising companies—then shining a spotlight on them.
This has been the pattern throughout my hodgepodge career. Writing books to curate the genius of Naval Ravikant, Balaji Srinivasan, and Elon Musk. Investing in founders who start in obscurity and rise to command thousands of people and billions of dollars in capital. Just noticing genius, and supporting it.
There are no good people and bad people. There are simply people—some with good ideas installed, and some with bad ideas installed. There is virtue in knowledge, and evil in ignorance.
We can see humanity’s growth over thousands of generations, from animals to civilization, as an accumulation of more and more good ideas. The idea to use fire, to create a system of writing and numerals. The ideas of forgiveness, democracy, and computers. Recognizing a good idea and spreading it to others is the most fundamental human action. (Perhaps aside from some biological necessities and, of course, procreation.)
Sean Devine is full of good ideas. And he has been hiding from the spotlight for far too long. It is my pleasure now to shine my small light on his brilliance and his ideas in the hope that they might benefit you, spread, and benefit humanity.
Most people who engage with philosophy do so at a safe distance. They read, they discuss, they admire ideas, the way one admires a painting in a museum. They know the names, they can quote the famous lines, but they keep their hands in their pockets. The ideas remain fundamentally separate from daily life.
Many people read Deutsch, Taleb, Girard, Nietzsche. Only a few people really understand them. And even fewer people change how they live based on what they learn.
I’ve known Sean Devine long enough to know he is uncommonly fluent in counterintuitive ideas. He gets a flash of inspiration and then—quickly—tries something new. Then he observes, learns, and runs a new experiment. He plays with big ideas, testing them against reality. Always moving forward.
What has always impressed me about Sean is not just his intellectual range, but his insistence on integration. True inquiry is not a lighthearted hobby; it is a means of understanding reality. Practice is not thoughtless repetition; it is the proving ground of new ideas. Sean moves fluently between the ideation and application, closing the loop. Hard and fast.
What you’re reading will help you do the same.
You are about to learn the secret formula to Sean’s success. What he himself did not even know he was discovering, until after he discovered it. What took over a decade of building, collecting a brick at a time through intuition, until looking up and realizing he’d built a cathedral.
The Dionysus Program emerged suddenly (almost overnight in book-writing terms) after years of organic discovery.
Sean has crafted an incredible career across many domains and disciplines. He rose through the ranks of a large organization, becoming a young executive in strategy at a public company. Then, he went into the wild and reinvented himself, teaching himself to code and bootstrapping a software company. As that company grew, he built a team, brought on capital partners, and integrated acquisitions. He carefully, quietly, built a powerful and profitable company in his niche, stitching together people and teams from across cultures, companies, and continents.
His success is well-rounded, as I’ve gotten to know his family and friends as well. Sean is one of those people who seems to be “winning at life”. He’s a non-stop stream of positive energy, good ideas, and generosity.
He doesn’t seem to take himself too seriously. I expect this is because he deeply understands the need to continually destroy and rebuild your “self” (whatever that happens to be). And it’s much easier to destroy yourself if you can laugh about it.
The Dionysus Program is just that simple idea, of destruction and iteration, explained as thoroughly as possible, applied at all levels of society. In this book, Sean gives you every tool in his toolbox for understanding—and using—his guide to destroying bad ideas without destroying relationships, cultures, or companies.
There are robust explanations. There are new vocabulary words. There are myriad mythical references. There are equations, charts, and algorithms. There are archetypes. And, in a stroke of brilliant originality, there is even a “comment section” where we hear the simulated critiques of many great thinkers who are featured in this book.
This is a book to be engaged with and digested. That may take time. Readers learn new concepts and definitions, then apply them throughout the book. You just have to take the time to “install the software.” Sean recommends (and I found it extremely helpful) to read this with an AI companion open next to you, asking questions, expanding definitions, and getting reminders. The brain should stretch and strain as it takes on new ideas.
This is also a book to be applied, not simply observed. There are recipes in here. Instructions for meetings, for conversations, and for reflection. Use them! As David Senra is right to repeat, “Learning is changing your behavior.” Then bring back what you learn, and help improve this text. If you find errors, correct them. If you see omissions, add them. If you see something extraneous, cut it out.
The book is itself a living system, trying to teach you about a living system. It’s complicated, I know. But life is complex, and we must not look away from the truth of the universe.
As Sean shows us, this is the process of life: theory and experiment; mutation and selection; innovation and selection; conjecture and criticism. What determines our success as individuals, families, companies, countries, and a species relies on our ability to handle this process well. Destroying ourselves, humanely, so that we become ever better.
This is the promise of The Dionysus Program well-applied. That you become ever-better. And that is all any of us can dream of being.
— Eric Jorgenson
Preface
My early success did not scale. It relied too much on personal intensity—on being smart, working hard, and tolerating pain. Those are anti-social strategies in the long run. They ask too much of other humans. They burn trust. They create brittle organizations.
For the first half of my career, I lived inside the Apollo virtues. I learned to improve systems and processes the honest way: go to the floor, name the constraints, measure the flow, remove the waste, repeat. At Con-way, during the Great Recession, I helped build and roll out Lean Six Sigma as an operating system. When you’re standing in front of a messy operation and the numbers start to move in the right direction, it’s hard not to become a believer.
The improvements were real. But the same problem kept returning.
The tools still worked, but the incentives and relationships around them changed. Metrics became things to manage for appearances. Output improved while trust declined. People became more guarded and less willing to report problems while there was still time to act.
Common became normal. Normal became moral. And once something is moral, it is expensive to change—no matter how good your metrics are.
That experience raised the question behind this book: how can a system improve without making the people in it less able to work together?
Before XBE, I co-founded Partage, a freight business that evolved into a self-service wholesale brokerage. We built automated pricing and booking for spot movements. Partage was a modest success; we sold it in 2015. The experience taught me:
Seeing the technical trend is never enough; you have to think through the full implications—how new technology reshapes the work itself, the team that performs it, the organization that depends on it, and the industry that surrounds it.
In 2016 I started XBE with no construction-industry experience and no capital. We began with dump-truck logistics because it was painful, legible, and close enough to my prior life. We built visibility: dashboards, reporting, “truth.” Visibility felt like power.
Then a deeper constraint surfaced.
Our largest customer was running a major interstate paving job at night. Trucks backed up, idle time accumulated, and the customer paid for capacity it could not use.
By the time the trucks were backing up, the decision that caused the waste had already been made.
Adjustments during the shift could only do so much. Hours earlier, when uncertainty was still high, over-ordering trucks had been the safest way for the superintendent to protect production.
In messy systems, waste is often not an error. It is an insurance policy.
On that job, the superintendent became emotional about the visibility. He saw himself as the hero of the work. Our dashboards told a more complicated story. After talking with him for a few days, it became clear that I needed to do less convincing and more enabling. He didn’t need another lecture about efficiency. He needed planning tools that doubled as communication tools—a way to surface uncertainty before the fact, and make that uncertainty socially admissible.
So we built job production plans, supply–demand balancing, and shift schedule automation. Trucking surplus fell materially. Not because anyone became morally better, but because the system made a different kind of honesty possible.
We also built a ritual we called Game Tape Review: a recurring review of plan performance attended by people across construction, materials, and logistics. The point was not to assign blame. The point was to study error while it was still cheap.
Ritual time did something run time could not: it made it safe to be wrong in public.
—
I had believed artificial intelligence was “the future” in the vague way many people believe a thing without feeling it. I did not feel it until I started pushing GPT-3 hard in 2022. Then ChatGPT arrived. Then GPT-4 arrived.
I watched skills I had spent my adult life building become cheap in months. Not metaphorically cheap—functionally cheap. And then I watched something more revealing than any technical breakthrough: people didn’t struggle most with the technology. They struggled with what the technology made them feel about themselves.
That was the moment the problem clarified.
Technical progress was outpacing the ability of people and organizations to adapt. New capabilities required new roles, norms, and commitments. Making those changes without losing trust was becoming a constraint in its own right.
Later I saw the second side of the same transition. AI was not only melting expertise; it was multiplying agency. Work that once required a chain of specialists could be compressed into one person with tools, and then into one person directing many agents. The old question was whether the organization had enough competent hands. The new questions are whether their decisions remain consistent with a shared purpose and who has taken responsibility for the outcomes.
That is the lesson of factory electrification, replayed in a new domain. The first electric factories kept the old line shafts and merely changed the power source; the real productivity came later, when unit motors let the plant be redesigned around flow instead of power transmission. AGI inside the old org chart repeats the early mistake—it bolts the dynamo to the line shaft. The larger gains wait on a redesign around the new bottleneck, which is no longer labor capacity but coherent agency.
Earlier in my career I fell into a trap: stoicism plus optimization. I judged solutions by whether they eliminated waste and whether I could implement them myself in the short run. I undervalued social scale over time. I treated identities as liabilities to be reduced rather than assets to be cultivated. I treated redundancy as waste rather than as the buffer needed to live with uncertainty—and to make room for renewal.
This book exists as a response to that critique.
I entered college before the internet was widespread and the workforce before smartphones existed. I made a career before learning to code. Now I use coding agents to do work that once required much more of my time and skill.
Once you see knowledge being created—and therefore destroyed—at that speed, it becomes impossible to unsee how slowly organizations change, and how rarely the delay is technical. It is almost always about status, shame, loyalty, fear, and the quiet bargains people make with themselves to keep their identities intact.
I went looking for older practices that let people handle conflict without destroying their relationships. The connections are developed in the chapters that follow.
In the last few years we took institutional capital, integrated acquisitions, launched new products, and kept growing under real consequences. The hard work wasn’t the software. It was integration: cultures, rituals, and stories about what mattered—under stress.
The program grew out of that work.
—
I wrote this first for myself. I had a clear vision of what artificial intelligence could do, and I wanted to lean into it. I also saw how adoption would remake my identity and my role in the world. I needed a framework that could hold both facts at once: that automation of our existing capabilities is a given, and that what remains will be cultural, moral, and relational.
Second, I wrote it for my teammates, family, and friends. I wanted to give them practices they could use.
Third, I wrote it for people facing similar changes in their own work.
The risk is that we continue to manage for a world in which our skills were scarce and our roles were stable. We may preserve output for a while through longer hours, tighter control, and the trust accumulated in better conditions. That can conceal how little capacity remains for the next change.
This book could have been written ten years ago, or a hundred. The core human dynamics are old. What changed is urgency.
The book asks something of the reader.
You will need time to try the practices and a willingness to let other people challenge your explanations, including the ones you hold about yourself.
The program is indivisible. If you take one piece—“more candor,” or “better postmortems,” or “aesthetic rituals”—and staple it onto a culture that won’t metabolize error, you will get theater. The parts reinforce each other because the problem is whole.
Success would mean people can report an error, question a decision, and revise their work without needing a scapegoat. Leaders should be able to change direction without making each correction a crisis of loyalty.
This is a working proposal. Use it, criticize it, and discard what fails. The program should meet the standard it sets for other practices: it must help people correct errors without sacrificing each other.
Introduction
The first six short essays lay out why this program exists, what it protects, and how to read the rest of the book.
Between the acts sit two interludes that work as gates. The first checks whether your group has enough trust to run these practices at all; the second checks whether the people running them are turning into a permanent priesthood. Come back to both before you try the higher-heat rites.
Keep one distinction in mind as you read. AGI puts two pressures on an organization, not one. Ritual Time deals with epistemic melt: knowledge changing faster than people can rebuild their roles, norms, and commitments around it. Run Time faces a newer pressure: action is getting cheap, and cheap action still makes promises, creates obligations, and changes the world. The coherence chapters take up that second problem after The One-Man Job shows what happens when AI collapses the division of labor.
Why Was the Apollo Program Not Enough?
From 1961 to 1972, NASA’s Apollo Program designed, built, and launched the spacecraft that put people on the Moon and brought them home. It was a triumph of systems engineering and project management: specify requirements, break problems into parts, model trajectories, close feedback loops, and drive out variance.
NASA manager Abe Silverstein pulled the name from a mythology book in 1960; “Apollo riding his chariot across the Sun” matched the ambition of the project. In Greek myth, Apollo is the god of light, clarity, and measure.
Nietzsche turned that image into a sharper contrast. In The Birth of Tragedy, he uses “Apollonian” for the drive toward form, order, boundaries, and clear representation. “Dionysian” names the opposing drive: intoxication, dissolved boundaries, collective intensity, and the raw force of life in all its terror and excess. Greek tragedy, in Nietzsche’s reading, happens when Apollo and Dionysus have to work together. Neither wins; the form holds because both are there.
The historical Apollo Program shows what the Apollonian side does well. When the mission is clear (land a given payload at a specific place and time), prediction, checklists, redundancy, simulation, and control are indispensable.
Mechanistic thinking has a blind spot, though: the human meaning of the work. It tends to treat conflict as friction and hand questions of loyalty and identity off to HR. That works until new knowledge undercuts the roles and habits that gave people a reason to care about their jobs. Better technical control won’t help them through that transition.
As knowledge moves faster, progress depends more on how quickly a group can turn new knowledge into new norms, roles, and institutions. Precision and control still carry their weight, but they don’t solve that problem.
The Dionysus Program builds the complement to Apollo. Where Apollo sharpens an established system, Dionysus makes room to question and replace it. Ritual, beauty, and an honest accounting of loss let people make that change without treating one another as expendable.
Apollo governs what I’ll call Run Time: prediction, execution, scored forecasts, and safety margins. Dionysus governs Ritual Time: protected periods where criticism is invited, old meanings can break down, and new commitments are made in public. Together, the two modes let a group act on what it knows and revise that knowledge when it fails.
In a post-AGI organization, Apollo takes on a sharper job. Doctrine, evals, permissions, decision memory, and clear interfaces let abundant agency operate without contradicting itself. Dionysus handles the other half: when the doctrine turns out to be wrong, Ritual Time lets the group face the contradiction, repair Ren, and retire dead explanations without turning correction into a witch hunt.
Apollo makes action legible. Dionysus makes correction survivable.
Any organization that plans to keep learning needs both.
The Alchemy of Error
I. The Divorce
The Royal Society’s motto, Nullius in verba (“take nobody’s word for it”), changed the protocol for knowledge. Alchemists hoarded their findings in metaphor, so their discoveries often died with them. Chemistry became a science when publication, replication, and public critique turned private hoards into public objects.
This program keeps that commitment to public scrutiny.
In physical inquiry, the observer’s moral standing does not alter the material in the flask. Public methods and repeatable tests let anyone check a result, regardless of who produced it. That advance stays.
The trouble starts when we carry the same method into social systems without accounting for the relationships among the people involved.
In organizations, information is never “just data.” It is what Durkheim called a social fact: it carries status, threat, loyalty, and shame. The same sentence, “this project is failing,” produces opposite results depending on who says it, when, and under what protection. Said by a trusted peer inside a protected review, it starts repair. Said by a rival in an all-hands meeting, it starts a witch hunt. The words are identical; the relationships decide what happens next.
Rigor alone cannot account for that difference. The method must also consider who delivers the criticism and what protection the participants have.
In social systems, those conditions are part of the method itself.
II. The Lost Art
The standard story, superstition giving way to reason, misses something real. Alchemy was more than bad chemistry. It was a method of transformation that included the person doing the work.
Impurity affected the alchemist’s capacity to observe, interpret, and persist, not the reaction in the flask. Cracks in the vessel let in contamination that obscured what was actually happening, not demons. Timing and ritual disciplined the attention on which good observation depended; the stars did not govern chemistry.
None of that was mere mysticism. It recognized that in transformative work, you cannot fully separate the operator from the operation.
When chemists threw all of that out as superstition, they were right about chemistry and wrong about methodology. They kept what worked for dead matter and dropped what worked for living systems. For three centuries, that trade-off held up well enough.
Now the trade-off has flipped. The bottleneck is no longer epistemic—we know how to find better explanations. The bottleneck is metabolic—we do not know how to turn those explanations into new roles, new norms, and new commitments without burning the people who must live through the transition.
The core claim: Error correction in organizations requires both rigorous criticism and conditions in which people can give and receive it honestly.
The program combines public critique, falsification, and replication with clear protections for the people doing the work. Its goal is to turn error into greater explanatory reach without consuming the trust that makes truth-telling possible. People need to be able to face the evidence that killed an explanation, and then have a way to act on what replaces it.
AGI creates two kinds of error. Epistemic error means the map is wrong. Agentic error means action no longer follows the map. A model can be false; an agent can also follow a true model at the wrong boundary, with stale permissions, or toward a local win that hurts the whole. Ritual Time addresses epistemic error. Run Time keeps agentic error from compounding while the current map still holds.
A later chapter, “The Alchemist’s Assay,” uses this analogy to tell changes that build trust apart from changes that burn it.
Prerequisite: The Form and The Current
The practices in this program can surface serious disagreements. They work only when people trust one another enough to speak without fearing retaliation.
Confucius drew a useful distinction here between Li (ritual form) and Ren (humaneness, or “authoritative conduct”).
The One-Man Job explains why Ren is newly scarce, and how organizations can build it on purpose when daily work no longer produces it as a byproduct.
- Li: the form, including the meeting agenda, the rules, the calendar invite, and the “No-Blame Covenant.”
- Ren: the current, made up of the trust, goodwill, and shared history flowing between people.
Doctrine is a form of Li. It organizes action, bounds agents, and makes strategy executable. On its own, it cannot create Ren. A doctrine packet can tell a person or machine how to act; it cannot make people trust each other enough to revise that doctrine honestly when it fails.
Beauty helps on both sides of that revision. In Ritual Time, error comes in cold. Reading a failed project’s original proposal aloud reminds everyone of the good reasons they believed it would work. People can grieve what they hoped for and examine what went wrong without putting the author on trial. Call that catabolic heat: it helps a group take an old explanation apart.
New knowledge comes in cold, too. You can understand a replacement rule on Friday and still reach for the old habit on Monday. Think of cooking: heat unfolds proteins before the food reaches the gut. A story told in the language of the work, or a short phrase you can recall under pressure, does part of that digestion in advance. That is anabolic heat. It starts in reconstitution and pays off in Run Time, when someone has to make a hard call alone.
The Dionysus Program gives you the Li: structured ways to handle conflict and change. It cannot give you the Ren. You have to bring that yourself.
Put high-intensity rituals (Li) into a group that lacks basic trust (Ren), and you will get management theater or a struggle session. You will ask for candor from people who know they will pay for it later.
Without Ren, people repeat the official doctrine in public while hiding the disagreements it needs to resolve.
The Readiness Rule: Never build a ritual container (Li) larger than the shared humanity (Ren) you have to fill it. If your group is mostly transactional, start with lower-stakes practices before attempting a Great Dissolution.
The Wins That Break The Game
In James Carse’s terms, an infinite game is played so that play can continue. The goal is to stay in the game and keep it worth playing.
By that standard, several familiar ways of “winning” actually lose. They win a short round by breaking the game itself.
When old stories, roles, and norms stop working, most leaders reach for some mix of three moves:
Self-erasure (violence turned inward). Ask people to shrink themselves so the disruption barely registers: “Be more stoic.” “Leave who you are at the door and just do the job.” “Numb your feelings or stay distracted.”
This asks people to give up the commitments that make the work worth doing. It also hurts learning: people who suppress their judgment and disagreement stop helping the group catch errors.
Coercive order (violence pushed downward or sideways). Hold meaning together by threatening anyone who questions it: “Follow the process or you’re out.” “Align with the culture or be sidelined.” “Agree with leadership or lose your role.”
The more you rely on force, the less anyone believes in the game. Every punishment teaches people to choose safety over truth, killing the feedback loops adaptation requires.
Abdication (violence pushed forward through neglect). Refuse to face the disruption and leave the outcome to outside pressure: “Focus on short-term results.” “Stick to what we know.” “Pause new investment until things get back to normal.”
Letting things play out is not neutral; it hands your future to whichever outside pressure hits hardest. Every deferred decision turns into an uncontrolled experiment where outside shocks and rival agendas decide what happens next.
Leaders often combine these three. Each buys short-term calm by spending down the team’s ability to adapt. Output may even rise for a while as resentment builds, people hold back bad news, and decisions become harder to question.
All three fail an infinite game morally, by treating people and the future as things you can burn through to stay in control, and practically, by destroying the adaptability you need to survive. In the terms of this book, they are low-epimetabolic strategies: they trade the ability to turn error into better structure for the feel of control.
AI agency abundance is a fourth kind of win that can break the game. It is a real win: more capacity, more independence, fewer handoffs, more room to experiment. Yet it breaks the old game because coordination, apprenticeship, shared context, and trust used to arrive as byproducts of labor scarcity. When one person with agents can do what a small team once did, neither relationships nor clear ownership arrive automatically with the work.
Finite games aren’t bad; they’re how anything gets done. Inside an infinite game, every finite game has to serve the longer aim and be judged by it.
The Dionysus Program is for organizations that intend to keep learning. It lays out explicit practices for revising roles, norms, and commitments as knowledge changes, and judges those practices by whether they improve the group’s ability to correct error.
How to Read This Document
This book names the thinkers it draws on so you can tell their original arguments apart from how they are used here:
- Carse on finite and infinite games; Popper on error correction; Deutsch on explanations; Wittgenstein on foundational commitments.
- Confucius on Li and Ren; Durkheim on anomie and social facts; Mauss on the gift; Girard on mimesis and scapegoating; Ibn Khaldun on Asabiyyah.
- Turner on ritual; Nietzsche on Apollo and Dionysus; Hegel on tragedy; Eliade on sacred time and myth.
- Weber and Michels on bureaucracy and oligarchy; Cincinnatus and Athenian sortition on granting and limiting extraordinary authority.
- Prigogine and Ohsumi on dissipative structures and autophagy; Taleb and Mandelbrot on volatility, roughness, and fractals.
- Simon on bounded rationality; Galbraith on information processing; Thompson on interdependence; Ashby on requisite variety; Goldratt on constraints.
- Paul David, Gavin Wright, and Warren Devine on the organizational changes that follow general-purpose technologies.
Explaining every framework from scratch would double the length of the book. Instead, treat these names as entry points for further reading or for asking a language model while you read.
Give the model direct access to the text when you do: paste the passage you’re reading, let it see the page, or download the compressed “Context” export from the website. With the text in view, the model can explain a reference in plain terms, separate the original thinker’s argument from this book’s use of it, and apply it to your own work. For example:
“Given the text above, explain René Girard’s theory of mimetic desire and scapegoating, and then show how the Dionysus Program’s ‘anti-scapegoat’ modifies it. Assume I am a [software engineer / product lead / city official] with no philosophy background. Use concrete, contemporary examples.”
Or, early on:
“Using the essay above as context, summarize Nietzsche’s distinction between the Apollonian and the Dionysian as it applies to organizations, then explain how that distinction structures the ‘Run Time’ vs. ‘Ritual Time’ split in this text.”
For the coherence sequence, use the chapters as a map. Read The Dynamo and the Agent for the factory-electrification analogy: why dropping AGI into an old org chart repeats the mistake of bolting a dynamo to a line shaft. Read The Coherence Ceiling for the scaling limit: why extra agency turns harmful when intent breaks down across distributed work. Read Auteurs, Agents, Actors for the new organizational roles: doctrine as middleware, Agents for scalable execution, and Actors who answer for results. Then read the Ritual Time chapters for the harder problem: how doctrine changes when reality breaks the map.
Overture: The Melt and the Method
Karl Popper described knowledge as conjectures exposed to criticism. David Deutsch draws out the consequence: every explanation is provisional, and a better one can force us to rebuild much of what rested on the old one.
Knowledge changes whenever a better explanation replaces an earlier one. The pace varies by field, and in many areas the interval is getting shorter.
Myth runs on a different clock, what Mircea Eliade called sacred time. Not a slower clock: no clock at all. The Cincinnatus story has not aged in 2,500 years. It stays current every time someone takes extraordinary power in a crisis and then goes back to ordinary work. It doesn’t age because it isn’t making a claim about external facts. It makes a claim about how you should act.
Knowledge explains the world, so you can test it against reality and correct it when it fails. Myth explains your stance toward the world and your identity over time. You cannot disprove the Cincinnatus story by pointing to a CEO who refused to step down. That isn’t a counterexample; it’s someone who failed to live by the story. The myth stays intact.
Both do explanatory work, just at different levels. Knowledge shapes your model of the world; myth shapes the person doing the modeling. You need both, and neither can replace the other.
Doctrine sits apart from both. Knowledge explains the world. Myth explains who we are. Doctrine tells current agents how to act and names who owns the outcome. It is strategy made executable under the best map available right now. Coherence measures how much intent survives from doctrine into distributed action. Epimetabolism is how error updates that structure without burning Ren.
When professional skills lasted a career and industry assumptions held for a generation, knowledge stayed stable enough to carry identity on its own. You could anchor yourself to what you knew because what you knew lasted. Once expertise goes stale quickly, an identity built only on present skills is exposed. That is the case for building myth deliberately inside organizations: a shared story about how to meet change still holds when a product or strategy runs its course.
Apollo governs knowledge and doctrine in Run Time: predict, execute, score, and keep action faithful to the current map. Dionysus governs Ritual Time: process loss, rebuild identity, update the map, and keep your footing after it changes. Optimizing one won’t strengthen the other; they answer different questions on different clocks.
Replacing an explanation carries a social cost. Roles, routines, and reputations depend on it. When an explanation collapses, people can lose their sense of what counts and where they belong, what Durkheim called anomie. Girard adds a second risk: once shared goals lose authority, people compete for status through cynicism and blame instead of the work.
AI speeds this up. Skills can lose value faster than roles and habits adjust. Organizations that block the technology to protect old roles fall behind; organizations that adopt it without helping people adjust burn through trust.
This program connects criticism to repair in a four-step loop: critique → dissolution → reconstitution → renewal.
Call the speed at which a person, team, organization, or city turns error into better structure its epimetabolic rate. When that rate is high, disruption doesn’t stall into panic or politics; it rebinds cleanly.
Epimetabolic rate is the program’s central test. Revenue, valuation, headcount, and shipping speed can move for plenty of reasons. The question here is narrower: how fast can a group spot a wrong explanation, revise what depends on it, and act on the revision without damaging trust? Practices that fail that test should be changed or dropped.
Accountability splits by mode. In ordinary operations (Run Time), we use Apollonian accountability: answering to our best current knowledge, doctrine, and processes (forecast → act → score) to get coherent action out of the current map. In Ritual Time, we switch to Dionysian accountability: answering to the rules of the rite so the group can face loss without scapegoating (call the rite → keep the vows → publish what changed → exit on time). Ritual Time updates doctrine when reality breaks it, and it also restores people’s energy to give and receive criticism after heavy stretches of Run Time.
Rationality and personal responsibility never turn off. What switches is what everyone answers to. Ritual Time pauses performance scoring and output targets so people answer to honesty, reason-giving, and the rules of the room; Run Time turns performance scoring back on and holds decision owners accountable for the commitments they backed. We switch modes on purpose and say out loud which mode we are in.
The method pairs Popperian error correction with ritual, aesthetics, and tragedy: Turner for the structure of transition, Nietzsche for the role of beauty, Hegel for the recognition through which a group sees its own part in a failure. The same sequence works for a person, a team, a company, or a city. Criticism targets a shared object, people stay protected while assumptions are challenged, and the verdict turns into a commitment everyone can act on.
The One-Man Job
As knowledge compounds, work atomizes.
Tasks that once took a team (research, analysis, design, implementation, and review) increasingly fall to one person with the right tools. AI collapses the division of labor. A generalist can go deep without waiting on specialists, and a specialist can go wide without waiting on generalists. Work that once required coordination can now be done alone.
Call this the “one-man job”: a task carried from start to finish by a single person, with no need to negotiate, share context, or wait on anyone else.
Large language models put explicit knowledge on tap. A programmer can get legal guidance without a lawyer in the room; a strategist can check engineering constraints without an engineer in the meeting; a researcher can pull domain expertise without calling a domain expert. What once required a conversation now requires a prompt; what once required a meeting now requires a search. Fewer tasks require direct collaboration.
Durkheim hoped that a finer division of labor would create organic solidarity: cohesion built out of mutual dependence. The surgeon needs the anesthesiologist; the anesthesiologist needs the nurse; each role is incomplete on its own. AI independence cuts that dependence. People grow specialized and self-sufficient at the same time, leaving neither the old solidarity of sameness nor the newer solidarity of mutual need. What you get instead is atomization.
Distributed work compounds the shift. Remote and asynchronous schedules wipe out the unplanned contact physical proximity used to supply: hallway conversations, overheard problems, lunches that turn into projects, and a casual sense of what everyone else is fighting through. Jane Jacobs called this the “sidewalk ballet,” the unscheduled encounters that build trust and safety. Without shared space, the ballet stops.
Remote work also separates colleagues from a shared town or neighborhood. When people live and work in the same place, they run into each other at the grocery store, school pickup, or a restaurant. Their relationships stretch past the task list. Distributed colleagues rarely cross paths outside work.
These are two separate forces. AI independence removes the need to collaborate; distributed work removes chance proximity and local roots. Because both are hitting knowledge work at the same time, they drain Ren from every side: we no longer need to work together, we no longer happen to be together, and we no longer live near one another.
The appeal is obvious. Coordination is expensive: scheduling, miscommunication, politics, and waiting. The one-man job skips most of that friction. On any single task, working alone is often faster, cleaner, and more satisfying, and someone who works this way will outproduce someone who insists on collaborating for its own sake.
That is the real upside: fewer handoffs, lower coordination costs, and the ability to take on work the firm couldn’t afford to start before.
The risk sits right underneath it. Less coordination is not the same thing as a better organization. Coordination was slow, yet it forced context to move through the group. People heard each other’s premises, caught local optimizations that hurt the whole, and picked up a shared sense of what the company would and wouldn’t do. Guided only by private taste and local context, the one-man job turns into fast isolation; guided by doctrine, it becomes coherent autonomy.
Shared work also made ownership obvious. Scarce skills pointed to the person expected to handle a problem. As those skills spread, being able to finish a job alone no longer tells anyone which jobs are yours to finish.
Coherent autonomy needs both a shared map and clear ownership of the outcome.
For most of human history, work forced people together. Hunting took a band, farming took a village, building took a crew, and trade took a network. You couldn’t opt out of human contact and still get the job done.
Relationships formed out of that forced contact, messily, unevenly, and with plenty of friction. Still, time in the same room, shared problems, and shared outcomes gave trust room to grow. Work was the pretext; Ren was the byproduct.
Aristotle wrote that people who want to be friends have to eat a bushel of salt together, bit by bit, simply from spending time side by side. Nobody scheduled “relationship-building”; people worked, and relationships grew in the margins. Seneca made a similar point: “Associate with those who will make a better man of you. Welcome those whom you yourself can improve. The process is mutual; for men learn while they teach.” That kind of mutual sharpening assumes proximity and back-and-forth. The one-man job cuts both.
There is no reason to romanticize the old world. Plenty of historical collaboration was wasteful, political, and corrosive: pointless meetings, blown schedules, and years of quiet resentment among people stuck together. Working side by side never guaranteed trust and often wrecked it.
Even bad collaboration, though, left room for chance: the unexpected conversation that clicked, the shared crisis that showed who someone really was, the lunch that turned into a friendship. Moving from inefficient chance to zero chance is the shift we are living through.
Once AI independence and remote work take hold, what’s left of collaboration is scheduled meetings with agendas, delayed messages, and brief handoffs with thin context: the mechanics of working together without the substance. Li without Ren.
This program needs Ren to work. The rites in Act II assume enough trust to hold hard conversations, and the Readiness Gate in Interlude I warns against running high-heat sessions without it. If daily work no longer produces Ren on the side, organizations have to build it on purpose. Otherwise they end up with elaborate ritual machinery and no human goodwill to power it.
Ren comes from three sources. Each can partly cover for a shortage in the others, with diminishing returns, yet any organization aiming past short-term extraction needs some baseline of all three.
Collaboration: Joint work on hard problems still builds relationships when it happens. The channel hasn’t closed, just narrowed. Novel problems, high-stakes calls, and frontier creative work still demand real teamwork. As AI improves, fewer tasks will fall into that bucket, so collaboration alone won’t supply enough Ren.
Shared commitment to mission or quality: Working toward something worthwhile, or alongside people who care about doing the work right, builds Ren through shared standards and mutual respect. When you meet someone who holds themselves to the same bar you hold yourself to, something clicks. That bond doesn’t depend on sitting in the same office.
The trap here is Mission Theater.
Companies love inflating ordinary businesses into moral crusades. A logistics firm “connects communities.” A software vendor “empowers human potential.” A widget maker “builds the future.” Everyone can see the gap between the slogan and the work. When leaders talk about grand purpose while employees experience routine commerce, the gap corrodes trust. Each inflated claim makes the next one easier to mock. Mission Theater burns trust faster than silence.
The honest default is simpler: unless the mission carries real moral weight and the team actually believes in it, skip the speech. Ground the work in the dignity of quality: taking pride in a job done well, on your own and with your peers. Craftsmanship does not require saving the world. It requires caring about the work in front of you and respecting those who care alongside you. That holds up because it’s true.
Some missions do carry genuine moral weight, such as medicine, education, safety, justice, and environmental stewardship. When the work serves an end people truly believe in, and they can see how Tuesday’s tasks connect to it, that belief builds Ren. Saying it on a slide isn’t enough.
Play: When daily work no longer produces Ren by accident, and mission can’t honestly supply it, you need deliberate, non-instrumental time together: time that isn’t measured, optimized, or tied to output, where the contact itself is the point.
In Homo Ludens, Johan Huizinga argued that play isn’t a footnote to serious life; culture, law, war, and poetry all grow out of it. Play draws a “magic circle” with its own rules, pausing ordinary hierarchies. Georg Simmel made a related point: “Sociability is the play-form of association.” People need social time free of utility just as much as they need purposeful teamwork. When work stops forcing people together, sociability has to be provided on its own.
Play is not “mandatory fun,” which is just work in disguise, and it is not HR team-building exercises that nobody believes in. Real play has three marks:
- Nothing is scored against work output. No one tracks the ROI of a poker game.
- Everyone pays attention to the same thing. Working on laptops in the same room is co-working, not play.
- Status can flip or disappear. The CEO can lose at cards without drama; the intern can win at trivia without awkwardness. Hierarchies that keep Run Time moving drop away.
Play is not optional. Most companies treat it as a perk, the first line item cut when budgets tighten. In a world of one-man jobs, play is infrastructure. It needs protected calendar space, closer to Ritual Time than to PTO. Defend it when short-term deadlines push against it, or the Ren account drains and never refills.
Play and rest are also different things. Play rebuilds sociability through shared, unscored attention. Rest rebuilds energy by lowering demand. Companies built around one-man jobs often mix them up, scheduling happy hours when people need a break and calling it recovery. People need unscored time together, and they also need stretches where nothing is being asked of them at all.
Hiring: Some people naturally pull a group together. They bring colleagues into conversation, ease friction, and create the kind of warmth people want to work around. Their value rarely shows up in individual output metrics, yet you see it immediately in how freely teammates share information and ask for help.
A team needs enough of these people, even when hiring them costs some raw individual firepower. A roster of brilliant loners will fall behind a slightly less flashy team with strong internal ties, because those ties let the whole group learn from what any one person discovers.
This is not “culture fit” used as an excuse to hire clones. Connectors come in every personality type. The test is practical: does this person make the group more trusting and cohesive, or less? Watch how colleagues act around them and you’ll know.
Leadership: Individuals face a timing mismatch: working alone pays off today, while losing Ren hurts two quarters from now. The engineer who skips team lunch ships more code by five o’clock. The bill arrives later and spreads across the whole company, showing up in attrition, slower handoffs, and postmortems that turn into finger-pointing because the relationships weren’t strong enough to hold honest critique. People won’t automatically resist the pull toward solitude when the cost stays invisible in the moment.
Leaders have to price in those delayed, shared costs. Protecting relationships looks inefficient on a weekly spreadsheet even when the company’s survival depends on them over a year.
Leaders also have to show up for play, not just put it on the calendar for everyone else. If executives act too busy or too important to attend, everyone reads the signal immediately: play isn’t real. The gift dynamic collapses. What remains is assignment, and assignment does not generate Ren.
Competitive advantage: As AI tools become cheap and widely available, having the tools won’t set a company apart for long. The harder advantage to copy is collective learning: building better explanations together and fixing mistakes across a group.
Tocqueville judged the health of American democracy by its voluntary associations, the “art of association” practiced every day. That habit withers without use. When work no longer requires association, proximity no longer creates chance encounters, and colleagues don’t share a neighborhood, nothing replaces it by default.
Compounding knowledge across a group requires Ren, and Ren now requires deliberate investment: in play, in honest standards of quality or mission, and in people who bind teams together. The organizations that make that investment will beat the ones that optimize only for solo productivity. The organizations that play together will outlearn the organizations that only work.
The efficiency that makes collaboration unnecessary also makes relationships unlikely. The same tools that let one person do the work of ten also remove the reasons ten people had to share a room. That is a real production gain paired with a social loss you cannot ignore.
As more tasks become one-person jobs, keep the speed and replace what collaboration used to supply: shared time, trust, and shared context. Give solitary workers and their agents a living map and explicit responsibilities, with enough reality-contact and feedback that independence doesn’t turn into drift. Play, pride in craft, and hiring people who bring colleagues together are practical ways to start.
The Dynamo and the Agent
The first mistake with any general-purpose technology is dropping it into the old organization and calling the job done. Factories made that mistake with electricity, and organizations are repeating it with AGI. The first pressure in this book is epistemic: knowledge goes stale faster than people can reorganize around it. The second is agentic: action scales faster than organizations can keep it aligned with shared intent. Factory electrification makes that second pressure easy to see.
Before electrification, factory power came from one place and traveled mechanically. A water wheel or steam engine turned a central shaft; belts, pulleys, and gears carried force across the building. Machines had to sit where the shaft could reach them, not where the work naturally flowed. When power had to move through belts, the hidden layout of the energy system dictated the visible layout of the plant.
When electric motors arrived, factories made the obvious swap: they replaced the steam engine with an electric motor and kept the old shaft-and-belt layout. The power source changed while the factory stayed the same. They bolted the dynamo to the line shaft.
That is stage one of AGI adoption. A company keeps its job descriptions, approval chains, meeting schedules, and departmental walls, then hands everyone a model, adds a few copilots, pipes summaries into Slack, and calls itself transformed. The tools changed; the organization didn’t.
The real gains in manufacturing came later, when factories put a separate motor on each machine. Once power moved through wires instead of shafts, machines could be arranged around process flow. Material traveled in cleaner lines, backtracking dropped, single-story plants became practical, and a single breakdown stopped halting the whole floor. The jump in productivity came less from cheaper power than from the new layout it allowed.
Economic historians Paul David and Gavin Wright traced this lag: productivity did not jump when the dynamo arrived. Decades passed while factory layouts, accounting, and management habits caught up. Warren Devine’s history of the move from shafts to wires makes the same point. Electricity didn’t just make energy cheaper; it moved the bottleneck. Once power was abundant, the real limits became material flow, scheduling, downtime, and management design. The factory could finally be redesigned around the work.
AGI moves the bottleneck in knowledge work the same way. Pre-AGI organizations were built around scarce human labor, because people held the judgment, memory, skill, and execution. An org chart is really a power-transmission system for human attention: managers route effort, work clusters around scarce specialists, meetings carry context across teams, and approvals pass decisions down the line.
AGI breaks that setup. The hard question is no longer whether a firm has enough hands to do knowledge work. One person with agents can already research, draft, code, sell, and revise at a scale that used to take a whole team. The bottleneck shifts from capacity to coherence: can the organization preserve intent as action multiplies? Coherence is the post-AGI equivalent of factory flow. What limits scale now is whether human and machine agents can work from one living map without contradicting each other, outrunning correction, or making promises nobody owns.
The old org chart is the new line shaft. It will outlast the scarcity that justified it, because it holds status, habit, law, and memory in place. The first wave of productivity will come from using agents to make the old architecture cheaper; the real wave will come from redesigning the architecture around the new bottleneck.
There is one sharp difference from factory electrification. Keeping an old factory layout mostly delayed upside. Deploying autonomous agents without coordination creates active damage: conflicting customer promises, duplicated work, and errors that spread before anyone catches them. The longer you wait to redesign, the more mess you have to clean up.
An organization scales until its agency exceeds its coherence. Past that point, extra agency accelerates incoherence.
The Coherence Ceiling
An organization can have more power to act than it can coordinate. To see why, separate agency from coherence.
Epistemic melt is about whether your map is true. Agentic abundance is about whether action stays faithful to the map and whether someone owns the results. A coherent organization can still be wrong; a smart organization can still pull itself in six directions at once. AGI increases both risks.
Agency: the capacity to perceive, choose, act, and create commitments in the world.
Agency is different from output. Output is an artifact; agency changes the world. A sales agent emailing a customer, a coding agent opening a pull request, a support workflow issuing a credit, a manager changing a policy, or a founder making a public promise all exercise agency. It shows up in three states. Latent agency sits unused: the model can do the job, but nothing calls on it. Bounded agency works inside doctrine, permissions, evals, stop rules, and feedback paths. The organization knows what map it follows, what it may touch, who owns the outcome, and when it must stop. Unbounded agency moves faster than the organization can review or correct, looking productive locally while breeding contradiction across the firm.
Coherence: low-loss intent across distributed agency.
Coherence means intent survives every handoff: from vision to strategy, strategy to doctrine, doctrine to action, and real-world feedback back into doctrine. Coherence does not mean conformity. A coherent organization makes room for disagreement, rivalry, and local judgment. The opposite of coherence is drift: local action that stops serving the shared whole.
Coherence also means every obligation has a real owner. Shared doctrine can steer active workflows while an important duty sits untouched. Everyone needs to know who ensures execution, watches the results, and steps in when something breaks.
The Form and Function of Coherence
Imagine a dispatch office that used to promise delivery as soon as a slot opened on the board. After sending a crew to wait for a truck that never came, dispatch changes the rule. A slot is an estimate. Dispatch can promise a time once the carrier accepts the load.
On Monday the booking agent gets the revised specification. It can check for acceptance on the very next quote. It has no pride invested in last year’s habit of finding a truck after promising one. The dispatcher who saved a hundred loads that way has earned some pride. At two in the morning a foreman calls. “I’ve got eight people to call in. Are you coming at six?” The dispatcher sees an open slot and says yes.
The rule has doctrinal coherence. Its terms fit together, the tradeoff is explicit, and a reviewer can tell whether a given promise was allowed. Effective coherence is how much of that intent survives into decisions like the dispatcher’s. Sound instructions that people can explain in a meeting but cannot draw on under pressure are cold doctrine. Machine execution can switch to Monday’s rule across every account while the people handling exceptions still steer by the old one. That is the Agent–Actor prior split. The booking screen still says “estimated.” The foreman has called in the crew.
When a change traveled one shift at a time, the incoming dispatcher heard the story of the stranded crew at handoff. Now a fleet can update between shifts. Give the dispatcher six words to carry back to the phone. “The carrier confirms. Then we promise.” They recall the crew and the one thing to check before answering the foreman.
The Limit on Useful Agency
The Coherence Ceiling is the point where adding more agency stops increasing useful throughput, because shared intent, context, trust, and correction can no longer keep up with the actions being taken. Below the ceiling, agency produces throughput; above it, agency produces contradiction. Past the ceiling, every new agent is a faster way to be wrong. Output climbs (more docs, tickets, campaigns, code changes, and confident local answers) while promises collide and critical duties slip through the cracks. Every new automated channel also creates fresh work to review, supervise, clean up, and explain to customers. Call that sign flip agency inversion: the point past the ceiling where marginal agency turns harmful.
Five companion terms round out the vocabulary:
Dominant scaling constraint: the bottleneck that most limits useful scale once earlier bottlenecks have been relieved.
Incoherence tax: the drag created by excess agency: rework, contradictory promises, duplicated effort, uncovered duties, and trust repair.
Doctrine half-life: how long doctrine stays accurate, current, and understood before world-change or drift makes it stale.
Context debt: the gap between stated strategy, real incentives, operating reality, and the instructions people and agents actually follow.
Span of coherence: how much autonomous human and machine agency can act while staying one organization.
Herbert Simon explains why AGI doesn’t solve this by itself. Bounded rationality was never just about slow human brains; it is about deciding under real limits on attention, information, search, and shared premises. AGI expands local rationality (testing more options, summarizing faster, drafting more plans) without removing organizational limits. Someone still has to decide which premises hold, which tradeoffs win, which customer promises count, and what action counts as “us.” If every agent reasons sharply from a different premise set, the organization hasn’t become more rational. It has become many rationalities competing under one logo.
Doctrine bounds rationality without throttling intelligence. It is strategy made executable: the working set of premises that tells distributed agency what diagnosis applies right now, which tradeoffs are accepted, what local wins are globally wrong, when to escalate, and what evidence would change the plan. It is not a strategy deck or wall poster; it is what action actually runs on.
Jay Galbraith framed organization design as information processing under uncertainty: as uncertainty rises, a firm must lower its coordination needs, raise its processing capacity, or redesign the work. AGI boosts processing capacity, yet it can raise demand even faster. Agents spin up plans, objections, memos, code, and customer messages at a pace that swamps human review.
Direct doctrine-to-agent execution helps by cutting out unnecessary middle layers, provided the work is modular and the doctrine is fresh. When either fails, it simply spreads ambiguity faster.
James D. Thompson shows where to draw the line. Different kinds of interdependence call for different coordination: pooled work can be standardized; sequential work needs clear plans and handoffs; reciprocal work, where parts constantly affect each other, needs live mutual adjustment. In a post-AGI company, route modular work through doctrine-guided agents, and have Actors coordinate reciprocal, ambiguous, high-stakes work with agent help. Actors own execution and consequences either way, without having to approve every routine step.
Ross Ashby adds one more rule: only variety can absorb variety. As AGI multiplies the range of actions an organization can take, its regulatory tools (doctrine, evals, permissions, feedback loops, decision memory, and Ritual Time) have to grow to match. The answer is not less variety but regulated variety—coherence without conformity, shared premises with divergent probes.
Eliyahu Goldratt’s Theory of Constraints turns this into an operating sequence. When coherence is the bottleneck, don’t keep adding agents and hope the system catches up. Run the five focusing steps:
- Identify the coherence constraint. Find where intent breaks down or duties go unclaimed: between Auteur and doctrine, doctrine and agent, execution and consequence, or customer feedback and revision.
- Exploit coherence. Stop burning it on stale decisions, unclear handoffs, duplicate docs, and unsupervised agent sprawl.
- Subordinate agency to coherence. Deploy no more autonomous agency than your current doctrine, evals, and feedback loops can absorb.
- Elevate coherence. Build living doctrine packets, ownership rules, agent evals, Actor feedback loops, decision memory, and a Ritual Time cadence.
- Repeat. Once coherence stops being the constraint, the bottleneck will move to demand, regulation, capital, compute, physical operations, or outside trust.
Do not add agency to a coherence-constrained system. Exploit and elevate coherence first.
That brings us back to the two modes at the center of this book. Run Time turns current doctrine into coherent action; Ritual Time updates doctrine when reality breaks it and repairs the trust damaged along the way. A group can end up in any of four states:
| High coherence | Low coherence | |
|---|---|---|
| Valid knowledge | Productive Run Time | Agentic decoherence |
| Invalid knowledge | Coherent wrongness | Collapse, churn, anomie |
Productive Run Time is the target: a sound map and faithful execution. Agentic decoherence means the map is fine, yet distributed action has drifted off it. Coherent wrongness is scarier: everyone executing smoothly from a false premise. Collapse is both at once. Coherence cannot replace epimetabolism: coherence sets how much agency Run Time can carry, while epimetabolism updates the map and raises that ceiling after reality breaks it.
Auteurs, Agents, Actors
Managers have always assigned work and responsibility explicitly, yet ownership also used to settle naturally around the few people skilled enough to handle a problem. That de facto arrangement often worked fine: with only a handful of plausible owners, everyone knew who to call without needing a formal rule.
AI makes far more people and systems capable of doing the same job. Capability no longer points to an owner. More potential owners doesn’t create an actual owner; some duties go untouched while other tasks draw duplicate effort. More responsibilities now have to be set de jure, explicitly assigned and accepted under doctrine.
Aristotle made the point centuries ago while criticizing Plato’s proposal to raise children in common: “everybody is more inclined to neglect the duty which he expects another to fulfill” (Politics, II.3, 1261b). When AI makes everyone capable of stepping in, everyone can assume someone else will.
People should not be the middleware. Doctrine should be the middleware.
Let doctrine carry instructions and coordinate execution. Keep people focused on what doctrine cannot supply: Ren, taste, legal and moral accountability, and the work of grief and repair.
A post-AGI organization runs on three functions: Auteurs write and revise doctrine; Agents execute it; Actors take responsibility for that execution and its real-world consequences. These are functions, not permanent job titles or rigid human-versus-machine buckets. One person or system may wear more than one hat, or switch roles across tasks.
People, machines, or both can perform these functions. Even a fully automated system still needs intent, execution, ownership of consequences, and a way to rewrite its rules when reality pushes back.
Auteurs
The Auteur sets, protects, and updates the organization’s intent: its vision, taste, doctrine, identity, and non-negotiables. It answers the questions an executing layer cannot settle on its own: What are we trying to build? What will we refuse to do? What counts as good work, and what local win would hurt the whole?
The Auteur doesn’t have to be one person. It can be a founder, an executive team, a creative lead, a board, a council, or a governance process. Whatever its form, some part of the organization has to own the premises that make its actions recognizably ours.
Why call it Auteur? A policy engineer can specify what a booking agent may promise and write the tests to enforce it. The Auteur owes something to the person answering the phone as well. Think of a film director telling a crew, “Stay with the woman waiting for the call.” The camera operator lets her son walk out of frame; the editor holds on her face when the phone rings. Two people making independent calls still know whose scene it is.
That craft is dual-rendering: expressing one intent as a specification a machine can execute and as a form a person can carry into a situation the Auteur never predicted.
Auteurship gives the firm a real standard of taste; plausible output isn’t enough if it misses the point. At the same time, the Auteur shouldn’t have to rule on every decision. If every hard call flows back to the center, doctrine isn’t doing its job.
Doctrine
Doctrine is strategy made executable. Strategy says where you want to go; doctrine says how distributed agents should act today under the current diagnosis and tradeoffs. Strategy that an agent cannot act on is not doctrine yet.
A good doctrine packet puts both renderings side by side: the rule and the tradeoff behind it, paired with the story people will tell a new hire when following the rule costs a sale. In the dispatch office, that might be the dispatcher who gave an honest estimate, lost the order, and had the boss back them up anyway. The agent needs a test for an unconfirmed load; the next dispatcher needs to know what happened to the last person who told the truth about one. Appendix B lays out the packet and interface requirements.
Doctrine also defines which duties must be covered and how Actors claim, transfer, and drop them. Actors need the authority to intervene, the capacity to follow through, and visibility into real outcomes. Doctrine has to name who ensures coverage and breaks ties when claims collide, because an inventory of running workflows will miss obligations nobody has picked up yet.
Under those rules, Actors can volunteer, split work, and hand off duties without waiting for central orders. Acceptance has to be visible, and a handoff isn’t complete until a successor accepts it. Letting go of a duty either ends the obligation under doctrine or returns it to whoever guarantees coverage. Having permission to act does not assign ownership of the result.
Doctrine is living Li: it gives shape to action. It cannot replace Ren, and it should never be mistaken for myth. Myth defines who we are at a depth you don’t rewrite every quarter; doctrine defines how we operate right now under a map that may need to change next week.
Agents
Agents turn doctrine into action. Every agent operates from some set of premises, so those premises have to be canonical, current, and bounded. A generic agent produces plausible output; a doctrine-bound agent produces output that fits the organization.
To work safely, agents need fresh doctrine, canonical sources, explicit permissions, evals, clear stop and escalation rules, blast-radius limits, and feedback loops back into doctrine. Without those guardrails, you aren’t scaling agency; you’re scaling private interpretations. Raise permissions only as doctrine, evals, and Actor feedback earn them. A draft suggestion is cheap to catch; an agent touching customers, money, compliance, production code, or binding promises needs tight walls.
Actors
Actors stand at the boundary with the real world: customers, partners, regulators, employees, markets, and physical operations. They make sure execution happens, watch what actually occurs, step in when things go sideways, and send contradictions back to the Auteurs so doctrine gets updated. They can delegate execution, tracking, and coordination to agents while keeping ownership of the outcome.
An Actor can hand dispatch and tracking to an agent without approving every click, yet still answer for whether the truck showed up and what happens if it didn’t.
In human organizations, the Actor role carries legal and moral weight. Even when software handles part of the role, moral responsibility doesn’t disappear into the tool. It stays with the people who authorized, bounded, and learned from the action.
Put together, the loop runs like this:
Auteurs → Doctrine → Agent execution with Actor responsibility → Real-world consequences → Contradiction → Ritual Time → Revised Doctrine → Run Time
When that loop breaks, it breaks in predictable ways:
Auteur Bottleneck: only the Auteur can interpret doctrine, so every real decision bounces back to the center.
Auteur Delusion: top-down conviction overrides reality, keeping the company loyal to a false premise.
Agentic Slop: agents churn out plausible output with no taste, context, kill criteria, or cleanup.
Actorless Execution: doctrine and agents keep shipping work while nobody owns the consequences.
Coherent Wrongness: everyone executes cleanly from a broken map.
Shadow Doctrine: teams and agents run on stale, local, or political versions of strategy while official doctrine gathers dust.
Doctrine Rot: official doctrine still exists on paper, but nobody trusts or uses it.
Agency Inversion: marginal agency turns negative because the organization has outrun its coherence.
The goal is an organization where people and machines can act independently because doctrine is current, permissions and ownership are clear, reality reaches decision-makers, and Ritual Time can change the underlying assumptions. Its span of coherence sets how much independent action it can sustain.
The Impatience of Jobs
The One-Man Job traced why Ren has grown scarce: AI independence collapses the division of labor, remote work removes daily proximity, and neither builds trust on the side. The long-term answer is deliberate investment in play, pride in craft, and people who bind teams together.
Those investments take time, and a crisis won’t always wait for trust to build on its own.
The coherence problem adds a second squeeze: a group needs enough trust to question its assumptions, plus enough doctrine, permissions, and feedback to keep independent actions aligned.
The Impatience of Jobs is the attempt to compress the time it takes to build trust through shared commitments and hard work. Done wrong, the same moves produce coercion and lock-in instead of Ren.
The Timing Squeeze
Ibn Khaldun wrote that Asabiyyah, the group feeling that makes a tribe act as one, grows through shared hardship and common cause across generations. The desert bands that conquered empires forged it through mutual dependence; the dynasties they replaced let it fade in comfort.
In Khaldun’s world, Asabiyyah built slowly and decayed slowly: one generation of hardship to forge it, three or four of comfort to spend it down.
A leader facing rapid technological change rarely has a generation. AI independence and distributed work can thin out everyday ties before new ones form, and waiting passively for organic trust carries its own risk.
That leaves a hard bind. The rites in Act II (Crossings, Dissolutions, and Tragic Postmortems) depend on Ren to work. Processing loss takes a group strong enough to absorb heat without shattering. Run a Crossing in a company held together only by payroll, and you don’t get renewal; you get bruises and silence.
Two Archetypes
The Patience of Job is a private virtue. Job sits in the dust, loses everything, and endures. For a single person seeking holiness, radical acceptance has a clear logic: bear what you cannot control.
A steward is in a different seat. You are responsible for other people. Practicing passive endurance on behalf of a group, watching shared purpose dissolve into isolated tasks while hoping trust grows on its own, is abdication, not piety.
The Impatience of Jobs refuses to wait for ideal conditions. It pushes the timeline rather than submitting to it, betting that honest friction beats an empty vacuum and that waiting for organic consensus often means waiting for the group to fall apart.
Its tool is shared transgression: taking the group across a line fast enough that people learn what they can count on in one another.
Transgression as Accelerant
Machiavelli pointed out that a founder starting something new faces a problem an heir never sees: legitimacy has to be built from scratch. You cannot lean on old habits when you are breaking with them, and you cannot draw on accumulated loyalty that doesn’t exist yet.
His counsel was blunt: do what founding requires, even when outsiders would condemn it under ordinary rules. The rough work of founding differs from tyranny because it aims to create stable trust and then stop, rather than keep everyone off balance forever.
Machiavelli separated cruelty “well-used” (concentrated, necessary, and tapering off) from cruelty “badly-used” (spreading, arbitrary, and self-serving). One is a tragic cost of getting off the ground; the other is just abuse.
When timelines compress and the alternative is drift or collapse, a leader may have to create the shared experience that makes trust possible, by leading the team across a line that puts everyone in the same boat.
The Three Transgressions
An impatient leader compresses relational time through three moves. Each costs the leader something people normally try to protect: reputation, affection, or innocence.
1. The Boundary (Exclusion)
Ren needs edges. If everyone belongs, belonging means nothing. Durkheim argued that solidarity rests on a line between inside and outside, sacred and profane. Mary Douglas made a related case in Purity and Danger: groups define themselves through what they exclude. Without a boundary, you don’t have a group, just individuals sharing a paycheck.
The impatient leader narrows who gets in, even turning away strong performers who don’t share the core obsession or history. They use tests of belonging that look strange to outsiders and obvious to insiders. The leader trades away a reputation for being broadly “fair” or “inclusive” so the people inside the line can recognize one another.
2. The Stripping (Shared Ordeal)
People walk in wrapped in past credentials: titles, habits of deference, and old wins. That armor keeps bonds thin because everyone stays oriented toward outside approval rather than toward the people beside them.
The impatient leader strips that armor off by setting demands the comfortable world calls unreasonable, often becoming the common adversary in the process. It is the old logic of the Spartan agoge, boot camp, and initiation rites everywhere: shared hardship bonds people sideways because vertical pressure makes individual rank beside the point. Victor Turner called the result communitas, the solidarity that forms when ordinary status drops away inside a shared trial.
Here the leader gives up being liked. They accept being the source of heat so the team bonds by getting through it together.
3. The Complicity (Mutual Implication)
Trust rises when walking away is expensive. In a purely transactional job, anyone can step out of a failure clean: “I was just doing my job,” “just following orders,” “just a contractor.”
The impatient leader puts everyone on the hook together through a bold technical bet, an unfashionable stance, or a public commitment that sets the whole team against industry consensus. It is the logic of burning the ships: once retreat is off the table, the only direction left is forward together.
Here the leader gives up plausible deniability. They stop acting like a cautious manager hedging every bet, take the blame for crossing the line, and share the stakes with the team.
Trust vs. Lock-In
Transgression cuts two ways. It can build real trust, or it can build lock-in.
Lock-in happens when people stay only because leaving hurts too much: sunk costs, burned bridges, nowhere better to go. Lock-in buys compliance, not commitment.
Trust happens when people stay because they want to, because the team and the work matter to them beyond any spreadsheet calculation. Trust produces candid feedback, extra effort, and steadiness under stress.
The test is simple: Would they leave if they could?
If people stay only because exit is costly, you have trapped them rather than bonded them. Lock-in cracks into resentment the moment conditions shift, and it will never survive a real Crossing. Real Ren passes the departure test: people with good outside options still choose to stay.
Every one of the three moves can tip either way. A boundary can build a tribe or a cage; an ordeal can forge brotherhood or Stockholm syndrome; complicity can create solidarity or bitterness. What decides the outcome is what happens next. The boundary has to anchor identity rather than block the exits. The ordeal has to be followed by recognition and care, not endless ordeal. Complicity has to tie people to one another, not solely to the founder. None of these moves can stay permanent without turning trust into dependence.
How Transgression Becomes Trust
Transgression doesn’t manufacture Ren out of thin air; it creates the pressure under which Ren becomes visible.
Confucius wrote: “Only when the year grows cold do we see that the pine and cypress are the last to fade.” Cold weather doesn’t make the pine hardy; it reveals what was already there.
The three moves work the same way. Boundaries show who stayed when staying had a cost. Shared ordeal strips off titles so character shows through. Complicity raises the stakes until loyalty actually means something.
Under pressure, people watch each other closely. Does she protect the team or angle for an exit? Does he tell the truth when it hurts? Everyone sees how everyone else chooses, and knows they are being watched in return. Ren forms when teammates see each other choose the group over self-interest, and know the choice was witnessed.
Witnessed conduct still stays fuzzy until someone names it out loud. Specific, public recognition (“You showed up,” “You told the truth when it cost you”) turns private impressions into common knowledge. That is the core of trust: relying on people because you have watched how they act, not because incentives happen to line up.
One catch remains: somebody designed the ordeal. How does the team know the push was for the group and not for the leader’s ego?
Submission settles that question. When the leader who set the hard line binds themselves to the rules that came out of it, following the same covenant and taking criticism in the same rites, they prove the ordeal served the group. A tyrant stays above the rules; a founder steps inside them. Without submission, loyalty runs through the leader instead of between teammates, and the whole thing collapses when the leader leaves. With submission, the institution can outlive its founder.
The Moral Test and the Sequence
These moves really are transgressive: acting before permission arrives, excluding before consensus forms, asking more than polite norms allow. To outsiders, especially people left outside the line, the impatient leader looks unfair, harsh, or reckless. You have to accept that judgment up front.
The only thing that justifies the cost is trajectory. Using Machiavelli’s test: does the transgression stay concentrated and fade as trust solidifies, or does it spread and grow more arbitrary? In the terms of this book, the Impatience of Jobs earns its keep only if it raises epimetabolic rate, producing a team that can digest error without burning trust instead of a brittle cult kept alive by pressure.
That requires completing all four steps in order:
- Transgress: Use boundary, ordeal, and complicity to compress relational time, accepting the outside criticism that comes with it.
- Recognize: Once the team clears the ordeal, name what happened and who showed up. Public recognition turns raw endurance into shared trust.
- Release: Step back so the trust belongs to the group, not to you. A leader who won’t release builds a cult; a leader who releases builds an institution.
- Submit: Live under the container you built. The rituals, norms, and limits now bind you too.
Stop halfway and you trap people together or tie them to a single personality. Finish all four (transgress, recognize, release, submit) and you tie them to one another.
Act I — Entropy of Dissolution
Constructive Criticism
Popper’s claim is blunt: knowledge grows by putting conjectures up for refutation. Deutsch adds the practical corollary: problems are solvable, so optimism makes sense, yet we never hold final answers. Criticism is how knowledge gets built.
Treat this operationally. A better model, a clearer theorem, a more accurate measure—these don’t “update” the old; they negate it. They undercut everything built on top of the old explanation: your roadmap, your org chart, your story about who you are.
- A team that built a leading recommender system watches a new architecture make their edge cheap. What dissolves isn’t just code; it is their standing and sense of purpose. The old celebrations (weekly wins, team lore, customer quotes on the wall) turn awkward overnight.
- A country shifts its energy mix. The symbols that framed oil as noble or villainous stop anchoring shared action, forcing miners, climate activists, and utilities to renegotiate who they are.
This is ordinary Popperian progress lived inside a group: it feels like melt.
Melting Meaning
Durkheim named what follows. Shared norms and stories coordinate hope as much as behavior; they tell people what counts and where they fit. When those break down, people lose their map of worthy aims. Anomie is not a mood; it is a vacuum of valuation.
Mechanically, anomie is a collapse in common knowledge. Thomas Schelling showed that coordination relies less on private beliefs than on what we think everyone else thinks everyone believes. When new evidence invalidates yesterday’s premises, those shared signals vanish. People stop knowing whose judgment to trust, which risks are worth taking, or what the work is for.
Robert Merton extended Durkheim’s idea to “strain”: when legitimate paths to legitimate goals break down, people respond in four ways. Retreat: “I log my hours and check out.” Ritualism: “I follow the checklist and avoid blame.” Innovation: “I go rogue.” Rebellion: “I burn it down.” None of the four rebuilds shared meaning on its own.
Anomie sets in when epimetabolic rate drops, when a group breaks old meanings faster than it can build new ones.
Vibrating Vacuum
René Girard’s mimetic theory argues that desire is social: we learn what to want by watching one another. Shared goals and shared standards keep rivalry productive. Once legitimacy melts, imitation flips into anti-mimesis: status through detachment, identity through refusal. Cynicism turns into armor. With no shared goal left to chase, rivalry shifts from the work onto people. We stop arguing over things and start fighting for standing.
At that point, a group usually reaches for one of two bad exits: unite temporarily by blaming and expelling a person or faction, or shrink ambitions and pull back effort to avoid conflict. Scapegoating hurts people; withdrawal leaves the real problem untouched.
The alternative is giving conflict a structured space where people can challenge shared assumptions without attacking one another, then turn what they learn into binding changes. The next chapters show how ritual, beauty, and tragedy make that work.
Agentic Decoherence
Post-AGI dissolution has a second look. Nothing appears stalled; everything looks busy. AI output climbs every week, teams ship faster, decks look sharper, and agents clear queues, yet the whole company gets harder to steer.
That is agentic decoherence, and you can spot it immediately:
- More AI output, more rework.
- Faster teams, less shared direction.
- Polished artifacts that contradict each other.
- Agent workflows acting on stale strategy.
- Important duties ignored while other work gets duplicated.
- Local metrics improving while the customer experience slips.
- Settled decisions reopened every week.
- Nobody sure which document is canonical.
The organization is not blocked. It is overproducing contradiction.
Anomie and agentic decoherence are different failures, though one feeds the other. Anomie is a vacuum of valuation after old meanings fail: “We no longer know what matters.” Agentic decoherence is action outrunning shared intent and ownership: “We are all moving fast as if we know, just off different maps.”
Interlude I — The Readiness Gate
The Poverty of Forms
Before you run the practices in Act II, check whether your group has enough trust to use them honestly.
A common management mistake is thinking process creates culture. A manager watches a high-trust team run a blameless postmortem and thinks, “If we copy that agenda, we’ll get their trust.” It runs the other way: the trust makes the agenda work.
Confucius put the question bluntly in The Analects: “If a man is not humane (Ren), what has he to do with ritual (Li)?”
Li without Ren gives you what Confucius called the “Village Honest Person,” the functionary who follows every rule and checks every box while offering zero protection when someone needs to challenge a broken norm. In this program, Li without Ren is a Crossing where criticism is allowed on paper and fatal in practice. It is a trap.
Asabiyyah and the Wind
To gauge whether you have enough Ren to proceed, look for what Ibn Khaldun called Asabiyyah: the group feeling that lets a team act as one.
Asabiyyah isn’t “morale.” It is a group’s ability to survive a real fight with itself: enough shared history to say, “We can tear this belief down without tearing ourselves apart.”
If the only thing holding a company together is payroll, its Asabiyyah is near zero. Bring the heat of dissolution into a room like that and the group simply falls apart.
Readiness starts at the top. Confucius wrote: “The virtue of the gentleman is like the wind; the virtue of the small man is like the grass. Let the wind blow over the grass and it is sure to bend.”
If leadership stays transactional, the team stays transactional. If leaders won’t practice Zhengming (the “Rectification of Names”), calling a failure a failure and a loss a loss, any truth-telling ritual turns into theater.
The Audit
Before entering Act II, run four checks:
- The Truth Test: When did a junior person last contradict a senior leader without paying for it? If the answer is “never,” you aren’t ready for a Crossing.
- The Mercy Test: When a project failed, did leadership protect the team or purge it? If people were purged, you aren’t ready for a Tragic Postmortem.
- The Naming Test: Does your language clarify reality or soften it? Ask someone to name a recent miss in plain terms. If “a learning experience” is as close as anyone gets to “the crew waited two hours,” you aren’t ready for the Rite of Redress.
- The Recovery Test: Is this group afraid, or is it worn out? If people are exhausted from a long stretch of Run Time, don’t ask for a high-heat rite. Lower the heat first. Sleep, food, quiet, ordinary kindness, and lighter demands aren’t perks here; they are prerequisites.
Add a Coherence Gate before scaling autonomous workflows. Check whether the organization can hold intent together, not just whether it can hear bad news:
- Doctrine Currency: Is the doctrine current, versioned, and clearly owned?
- Doctrine Executability: Can every executing unit tell from the doctrine what to do, what to avoid, when to escalate, and when to stop?
- Decision Rights: Are decision boundaries clear enough that autonomy doesn’t become guesswork?
- Kill Criteria: Are stop conditions set before the workflow launches?
- Bounded Permissions: Does each agent’s blast radius match how proven its doctrine and evals are?
- Actor Responsibility: Which Actors have explicitly accepted responsibility for execution, outcomes, response, and feedback?
- Ritual Path: When the workflow surfaces a contradiction, where does it get resolved?
- Stale Doctrine Owner: Who answers if the doctrine goes stale while the agent keeps running?
Then run a Coherence Audit:
Telephone assay: Trace Auteur intent from executives through managers, teams, agents, customer-facing output, and back through feedback. Mark where meaning shifts.
Context checksum: Ask people and agents separately: What are we doing? Why? What are we refusing? What would change our mind? What local win would be globally wrong?
Agency inventory: List every active agentic workflow, the Actors who own its outcomes, its doctrine source, permission level, blast radius, and review schedule.
Responsibility coverage: List every duty the organization has to fulfill, including ones with no workflow attached. Name who accepted each one, what authority and evidence they have, and who steps in when coverage is missing or disputed.
Contradiction ledger: Keep a public list of unresolved clashes between strategy, incentives, customer reality, doctrine, metrics, and execution.
If you fail these checks, start smaller: routine coordination, shared meals, small promises kept. Build enough trust for disagreement before raising the heat.
Some groups fail the gate morally; others fail it on energy. An exhausted team turns even a well-built rite into punishment, theater, or collapse. No ritual technology, however elegant, can metabolize loss when the participants are exhausted.
Start with the practices in The One-Man Job (play, pride in craft, and hiring connectors) to build Ren before attempting heavier rites.
When the Gate Fails: Submerged Ritual Time
Failing the gate doesn’t stop the melt. It only pushes it underground.
When public Ritual Time is unsafe, unavailable, or unearned, people improvise Submerged Ritual Time: private, informal, or coded ways of processing disruption. They turn to quiet withdrawal, inside jokes, memes, private venting, prayer, art, or silent exit. None of those look like management or politics, so leaders often miss them, yet they are frequently the only safe way left to tell the truth. Submerged Ritual Time protects the individual when public honesty is risky, though it cannot renew the group on its own. Renewal starts only when private truth gets a public anti-scapegoat, real protection, and a path back into shared decisions.
Public Ritual Time creates common knowledge: everyone knows what was challenged, what changed, and what rules now hold. Private processing keeps a person sane, but it rarely changes roles, norms, or commitments across the organization.
Agentic systems grow their own underground layer. People don’t announce, “Our doctrine is stale.” They route around it with private prompts, shadow workflows, side spreadsheets, unapproved scripts, or quiet refusal to trust the official agent. Shadow doctrine is Submerged Ritual Time in operational clothes: people handling contradictions privately because fixing official doctrine feels unsafe or pointless.
That is why withdrawal shouldn’t be written off as apathy or disloyalty. When people pull back, ask first: what public container was missing that made pulling back the safest move?
Still, submerged rites carry real danger. They can harden into permanent withdrawal, cynical superiority (“I see through the game”), fragmented rumor, or exit addiction, where walking away feels cleaner than fixing anything. Submerged Ritual Time helps only while it keeps the door open to return. Once it turns participation into something beneath contempt, it blocks repair.
The Catacomb Rule: When public Ritual Time isn’t safe, build the smallest private space that keeps honesty alive without asking anyone to be a martyr. Don’t mistake conservation for renewal; its job is to preserve people, memory, and the chance of public rebuilding later.
The Bite and The Gift
Most corporate rituals are meetings in costume. They get grand names, yet everyone knows what they are: assignments put on a calendar by a manager and attended with the minimum effort needed to stay out of trouble.
They fail because they have no bite. They feel made up rather than received.
Autonomous workflows carry their own version of this weight: every one of them creates ongoing obligations (supervision, exception handling, review, and eventual retirement) that count against the organization’s real capacity.
The Greeks distinguished chronos from kairos. Chronos is clock time, fungible minutes spent on tasks. Kairos is threshold time, the moment you step out of ordinary work into rules that bind everyone in the room. Most corporate “rituals” are chronos dressed up as kairos: solemn language with no real gravity.
To raise epimetabolic rate, scheduled meetings aren’t enough. We have to build what Émile Durkheim called Social Facts: ways of acting and speaking that stand outside any single person’s whim and push back when you test them. When a rite feels like a Social Fact, you don’t just attend it; you submit to it. Submitting to rules that stand above the manager’s mood is what makes the room safe enough for honesty.
The Durkheim Constraint: Otherness
Otherness is what turns an ordinary meeting into Ritual Time, making a rite feel received rather than improvised so it can carry real heat without collapsing into theater. Its rules need authority separate from whatever the boss wants today.
Four choices create that otherness:
- Temporal Otherness. Borrow shapes older than your current problem: a courtroom, a seminar, a guild review, a confessional. Old forms carry weight and lift the room out of “Tuesday at 2 p.m.”
- Social Otherness. Bring in witnesses who aren’t part of the daily hierarchy: an outsider, a customer, a board member, or a Jester. Their presence signals that normal rank is paused in favor of a wider standard.
- Form Otherness. Keep the rules fixed. In a normal meeting, people rewrite the agenda halfway through; in a rite, the script holds even when it gets uncomfortable. Predictable rules let people tackle harder truths.
- Witness Otherness. Write the verdict down. A book of oaths or a public graveyard of retired bets creates a shared memory that holds everyone to what they said.
If a manager says, “Let’s all be honest,” that is a polite request. If the Rite of Redress requires every stakeholder to state their objections on the record, that is a Social Fact. One asks; the other bites.
The Mauss Dynamic: The Rite as Gift
Durkheim explains the container; Marcel Mauss explains what moves through it. Mauss argued that deep social bonds rest on the gift, not the contract: a cycle of giving, receiving, and returning.
Most workplace time is transactional: pay for labor, calendar invite for attention. Transactions don’t build trust; they push people to give the minimum required.
Ritual Time has to work as a gift. When leaders call a Crossing or a Great Dissolution, it should feel like a real investment of time, protection, and care, not another chore on the calendar.
Three habits make that visible:
- Name the cost. Say plainly why regular work is pausing and what the protected time is for.
- Provide real hospitality. Good food, a proper room, and thoughtful preparation show respect and help people stay present.
- Make entry explicit. Have participants step in deliberately, by signing in or reading the covenant aloud, so attendance becomes accepting the gift rather than being dragged to a meeting.
Once people accept a real gift, reciprocity kicks in. In a Dionysian rite, the return gift is candor: offering honest criticism, including the things ordinary meetings leave unsaid. Candor becomes part of the relationship instead of another compliance metric.
Put Durkheim and Mauss together, received forms backed by real hospitality, and rituals earn binding honesty instead of feeling like extra homework.
Act II — Reversal of Reconstitution
Doctrine Reconstitution
Ritual Time is not finished when the room reaches an insight.
Insight on its own does not change operations. Unless the new recognition makes it into Run Time, the old map keeps running through old prompts, dashboards, incentives, approval rules, and customer promises. People leave the room feeling changed and go back to behaving the same way.
Reconstitution closes with four questions: What died? What survived? What is the new functional rule? Is the new truth warm enough to eat? The first two let people bury a failed premise cleanly and name the commitment they still share. The third puts the change into instructions, permissions, promises, and the hands of the people who own carrying it out.
The fourth is the Form Check. Before closing Ritual Time, hand an Actor a fresh case where the old reflex would have paid off, and let them answer in their own words with the packet closed. Can they make the right call, explain what they are giving up, and show where the rule stops them? If the old habit still wins, rework the phrase, the story, or the practice and test another case. Appendix B gives the closing protocol.
Retraining Order: The Anti-Scapegoat
Girard showed how scapegoats calm a crisis by uniting a group against a victim, buying peace through violence. This program keeps the stabilizing mechanism and rejects the victim. The anti-scapegoat is a deliberate, non-human object (never a person or faction) that absorbs the blame, heat, and attack during a transition while new rules take shape.
When no public anti-scapegoat exists, people improvise private ones: inside jokes, memes, nicknames, and off-the-record venting. Those ease private stress without producing public change.
When an agentic workflow breaks, put the system on trial: the prompt, doctrine packet, eval, permission boundary, handoff, escalation rule, or missing Actor feedback loop. Don’t blame someone for “using AI wrong” when the system never made coherent use possible. Check whether anyone ever owned the responsibility, and whether they had the authority and capacity to fulfill it.
Victor Turner mapped the three stages of ritual transition (separation, limen, and reincorporation), where normal rank pauses, intensity peaks inside clear rules, and the group returns to ordinary work with stronger bonds (communitas) and clearer norms:
- Separation: Set blame aside with a plain rule: “No person is on trial.” Name the anti-scapegoat (a charter, assumption doc, test suite, prototype, or policy) so all heat lands on the object.
- Limen: Put the idea on trial under strict rules: red teams, adversarial tests, and public proofs. Keep defensiveness out of the room: the builder speaks last, the critic holds the floor, and anyone can introduce a rival explanation or test under the same covenant.
- Reincorporation: State the verdict and new commitments in public, bind them with names or oaths, update roles, and retire old artifacts cleanly without shaming anyone.
Every Crossing names two roles:
Owner: The person with the greatest stake in the object under criticism. The Owner receives criticism with warmth, grace, and humor when it helps, thanks people for hard truths, and shows that disagreement leaves the relationship intact. Speaking last isn’t enough; the room watches how they listen. Welcoming criticism does not mean agreeing with it, and the Owner stays accountable for the verdict and what follows.
Host: The person entrusted with the room’s warmth, beauty, pacing, and protection throughout the rite. The Host notices when candor becomes prosecution, laughter becomes ridicule, or someone withdraws. They keep criticism on the object and have authority to slow, interrupt, or pause the rite when care fails. The Host must remain welcoming during difficult criticism and allow silence, seriousness, and grief. Humor is optional.
One person can play both roles, though a separate Host makes it much easier to care for the room while the Owner absorbs hard feedback. Both stay bound by the covenant and stewardship rules below.
Core elements of a Crossing:
No-person blame covenant: Criticism hits artifacts, assumptions, and rules, never people. In Ritual Time, people answer for honest reasoning, openness to refutation, and keeping the covenant; back in Run Time, they answer for the decisions they backed.
Common-knowledge signals: Clear start and stop calls (“The Crossing begins now,” “The Crossing is closed”) so everyone knows which mode is live and how blunt they are expected to be.
Standing right of criticism: Anyone in the room can put forward a rival explanation and a falsifiable test without asking permission. Retaliation or chilling speech breaks the covenant.
Responsibility for Speech: Criticism may come from your own experience, a colleague, or a machine. State what you know, what you believe, and what you are putting on the table, and stay to help examine and test it. “Someone else said it” doesn’t end your responsibility.
Speaking on someone’s behalf is a narrow exception for a real barrier: an access need, unavoidable absence, or a credible risk of retaliation. Permission alone isn’t enough. The person represented controls what may be said, and the role ends with that issue. Don’t turn private remarks into public positions or dress up an unnamed source as a consensus. A steward can bring confidential reports forward while protecting the source and flagging what isn’t verified yet.
The steward keeps attention on the claim by asking: “What is the criticism, and how can we test it?” Help the speaker sharpen the point without putting them on trial.
Severability and reversibility: Following Popper’s piecemeal engineering, structure experiments so they fail safely. Cheap failure makes honest criticism easier.
Hard-to-vary test: A proposed explanation survives only if you can’t freely tweak its core parts without breaking its fit to the facts or its predictions. Write down (a) the facts it explains, (b) the parts that cannot move without breaking that fit, and (c) at least one risky prediction to score after reentry.
Hospitality as binding force: Following Mauss, treat Ritual Time as a gift, not an assignment. Give participants real protection, respect, and hospitality, and you earn candor in return. Treat it like a chore and you’ll get compliance.
This is ritual as practical engineering: it pulls heat off people and onto shared objects, keeping the sharp edges of conflict without letting it freeze into silence or blow up into scapegoating.
Rituals also work better when they feel stable rather than constantly rewritten. Keep the design group small: a rotating handful of active operators who tune the format on short terms and then go back to normal work. Everyone can critique how a rite performs in use, without redesigning its bones every week.
Skin-in-the-Game Rule: Every rite must be owned by the person or group with the most to lose inside its scope. Facilitation can be delegated; accountability cannot. A product Crossing belongs to the leader whose charter rides on that product, not a neutral “ritual team.” A civic Rite of Redress has to put the responsible officials inside the room, not just hired facilitators. Once the people running the rites carry less risk than the people living under the verdicts, the program has slipped into priesthood. Interlude II (The Cincinnatus Rule) lays out how to keep stewardship rotating through real operators.
Lindy-first design: Borrow your shapes from institutions older than your company: courtrooms, guild reviews, academic seminars, feasts and fasts, shareholder meetings, and town halls. Old forms bring built-in gravity. Adapt the names and stakes to your context while keeping the skeleton. Treat brand-new formats as provisional until they prove themselves over several cycles.
While a Crossing is open, output targets pause and everyone answers to the rules of the room (the no-blame vow, honest reasoning, and clear exit criteria) before returning to Run Time accountability. You already know secular versions of this: blameless postmortems, code reviews, moot courts, null-hypothesis testing. The shift here is making them explicit anti-scapegoat rites tied to real calendars and named owners.
What it looks like across scales:
- Personal: Name one “assumption of the week” as your anti-scapegoat. Hit it with your toughest critiques and a friend’s, without turning the attack on yourself, then publish a verdict: keep, revise, or drop.
- Team: Run a weekly Crossing around one artifact. Keep every critique aimed at the artifact and close with a dated commitment: “We commit to X until Y evidence.”
- Organization: Run a quarterly Great Dissolution on big targets (strategies, pricing models, review processes) with outside critics in the room. Close with new charters, promotions tied to what survived, and clean retirements for what didn’t.
- City: Hold an annual Rite of Redress where policies stand trial before independent citizen jurors, and public institutions bind themselves to the verdicts without attacking the people involved.
At every scale, close the same way: run the hard-to-vary test, write down at least one risky prediction to score later, and note what new problems the updated rule lets you solve.
Check readiness before you start. A Crossing draws its strength from existing trust and shared history, not clever formatting. If your group doesn’t have much non-transactional history yet, start small and keep the heat low. Pushing intensity faster than trust can bear produces cynicism and management theater instead of real learning.
To host a playful version of this ritual, use It’s So Dumb, with a step-by-step guide, host scripts, prompts, and a session timer.
Beautiful Heat
Losing a familiar explanation can leave people too bruised or guarded to engage with what replaces it. Nietzsche saw that Greek tragedy used music, story, and form to help audiences face hard truths they couldn’t yet reason their way through. Beauty plays the same role here: it helps people stay open while old assumptions break down.
Durkheim’s “collective effervescence” shows up well beyond churches and stadiums. Shared music, stories, and symbols pull attention back together when dry argument stalls. Kant and Schiller went further: aesthetic form trains people to want something without being forced into it.
Put that to work directly:
- Loss exhibits: Turn retired products, failed models, and dead rules into public artifacts: a poster, a short story, or a quick retrospective. Name what died, credit what it did well, tell the truth about why it ended, and place it in a “Scrapbook” or “Graveyard” anyone can browse.
- Aesthetic reviews: Open product and research reviews with a three-minute artifact (a rendering, a poem, a demo with music), not to manipulate the room, but to show what people stand to gain or lose. Then move straight into hard critique.
- Festivals of misrule: Schedule licensed inversions. Carnival works. Use it. Let junior staff roast leadership. Let support write the keynote. Let people challenge the usual presentation of a failure. Then restore order. The inversion resets the room.
- Naming: Give phases and practices vivid, exact names. Names anchor attention. “Crossing,” “Touch Down,” “Rite of Redress,” “The Great Dissolution,” “The Rubedo.” Clear names tell people what kind of moment they have stepped into.
The same habit translates anywhere: read a poem about a hard lesson before starting a difficult personal change; hang a “Gallery of Attempts” in a classroom so failed drafts count as stepping stones; publish dissenting opinions as real prose, not dry boilerplate.
Carry one small form back into ordinary work, too. At shift change, have the outgoing dispatcher tell the incoming one about a promise they turned down and why. Tomorrow the loads and names will be different, yet the handoff is already part of the job. Passing the rule along inside an inherited habit gives it the durability the Durkheim Constraint asks for.
The Fallow Interval
Run Time spends slack, not just hours.
Heavy work drains patience, curiosity, and the steadiness needed to hear criticism without flinching. A team can still hit its deadlines while having nothing left for a hard conversation.
That is why Ritual Time cannot consist only of critique, postmortems, and recommitment. Asking an exhausted group to process a painful failure produces theater, numbness, or dressed-up cruelty.
Farming offers the plainest image: you leave a field fallow so the soil recovers for the next crop. Sabbath traditions go one step further by making rest an obligation rather than a prize for finishing the to-do list. Organizations always have more work waiting; without a stopping rule, urgency never ends.
Ritual Time therefore has two halves:
Passive renewal lowers heat: sleep, quiet, unscheduled meals, walks, and time together without a scoreboard or an agenda. Nothing is being extracted, solved, or optimized. People get back the energy to think clearly.
Active renewal metabolizes meaning: lament, critique, postmortems, honest naming of what ended, and new commitments. Active renewal works only after passive renewal has given people enough margin to hear hard truths without turning on each other.
Cool first. Metabolize second.
An acute crisis sometimes demands an immediate debrief, yet the default assumption should be that exhaustion warps judgment. Tired people defer to the loudest voice, mistake frustration for insight, and reach for a scapegoat or slogan instead of a real explanation. Plenty of well-designed postmortems fail for a simple reason: someone scheduled them the morning after a brutal launch. The harder the stretch of Run Time, the more recovery the team needs before stepping into high-heat review.
Rest and play are different tools. Play creates unscored shared attention; rest drops demand altogether. A depleted team can attend a game night and still be exhausted. Organized sociability cannot replace sleep, quiet, or time alone.
Before calling a tough review, check whether the room has enough energy to face the failure without turning nasty. If not, cut demands first: end early, strip out prep work, or push the Great Dissolution back a week so people show up clear-headed. Demanding “renewal” from burned-out staff just adds another task, while resting without ever returning to the problem leaves the work broken. Recovery makes the honest reckoning possible.
When leadership refuses a Fallow Interval, people take one on their own through burnout, quiet disengagement, sick days, or withdrawal. Some of that is dysfunction; some of it is self-defense. A good steward learns to tell the difference.
In a post-AGI organization, fallow time is also deletion time: clear out stale prompts, dead docs, zombie projects, obsolete metrics, and abandoned automations before agents keep acting on them. Retiring a workflow doesn’t erase the duties behind it, so transfer any obligation that still stands. As creation gets cheaper, deliberate cleanup becomes essential.
Once the room has cooled enough to face the truth without hunting for a victim, tragedy can do its work.
Tragic Metabolism
Tragedy gives a group a way to see its own hand in a failure. Aristotle laid out the dramatic arc, Nietzsche argued for its bracing value, and Hegel described the recognition (Aufhebung) where you see yourself inside what went wrong and come out with a deeper grasp of reality.
Use tragedy directly in operations:
- The Tragic Postmortem, in four steps:
- Hamartia: Name the decisive internal mistake rather than blaming bad luck. (“We believed X, and that made us careless about Y.”)
- Peripeteia: Name the turning point that broke the assumption. (“The launch failed at Z and flipped our model upside down.”)
- Anagnorisis: Say what you recognized about yourselves. (“We overweight metric B and reward staying quiet in reviews.”)
- Catharsis into Act: Tie that insight to a real change (rename a role, flip a rule, add or kill a ritual) and mark it publicly so it sticks.
- Role Reversal Interviews: Trade seats with your sharpest critic, argue their case as strongly as you can, let them cross-examine your version, and share the record.
- Anagnorisis Journals: Write one sentence a day (“Today I realized I was wrong about X; therefore I will Y”), linking a changed mind to a specific action.
- Public Trials with Mercy: Courts channel conflict into fair judgment instead of vengeance. Keep the adversarial edge and forbid humiliation. Mercy here isn’t going soft; it is refusing to scapegoat.
The difference between tragedy and farce is whether recognition changes the structure. When it does, a group turns loss into real learning; when it doesn’t, the same failure comes back.
Coherent wrongness is the hardest tragedy to face. Sometimes nothing fragmented at all: everyone followed doctrine to the letter, and doctrine was wrong. A false map does more damage when a team executes it cleanly, so Tragic Metabolism has to be willing to put coherence itself on trial, not just deviations from it.
Interlude II — The Cincinnatus Rule
The Farmer-King
A Roman legend should sit behind any attempt to build a ritual layer.
Cincinnatus was a farmer. Envoys from the Senate find him at the plow and offer him absolute power as dictator of Rome for a single crisis. He wipes the mud from his hands, takes command, raises an army, breaks the siege, and sixteen days later resigns and walks back to his field.
Three details do the work: he is pulled from ordinary labor, not from a permanent office; his extraordinary authority lasts only for one bounded emergency; and when the emergency ends, the system itself, not only his good character, sends him back to the plow. Call this the Cincinnatus Rule: anyone holding liminal authority must come from active operators, hold bounded power for a specific job, and return to ordinary work when the job closes. Stewardship cannot become a career.
This program needs that guardrail because its rites create the exact kind of authority that hardens into a priesthood. A small group of stewards can call Crossings, choose anti-scapegoats, declare Ritual Time, and rule on what the vows “really mean.” Left unchecked, they turn into a ritual oligarchy, a permanent class whose job is running liminality for everybody else. Interlude I warned against Li without Ren. This interlude warns against the next trap once both exist: sacerdotal capture, where the forms become a power base for their keepers.
Ritual Oligarchy and Sacerdotal Capture
Max Weber traced how living movements harden into bureaucracy: early authority rests on concrete courage and insight, then gets codified into offices and procedures to survive the founders. Robert Michels went further with his iron law of oligarchy: once an organization creates a leadership layer with special information and agenda control, that layer starts protecting its own survival ahead of the mission.
Watch the same cycle play out with rituals. First, high-Ren operators invent rites to handle hard conflict without blowing up the team. Next, they codify charters, set calendars, and appoint “ritual stewards” to scale the practice. Soon the steward role becomes prestigious and full-time. Now you have sacerdotal capture: a group whose status and livelihood depend on keeping the rites running in their current form, whether or not they still work.
In a captured program, a “ritual team” or “culture office” owns Crossings even though its members stopped shipping products, serving customers, or teaching classes. Questioning the rites themselves starts getting treated as bad manners. Forms built to speed up error correction now shield their own keepers from scrutiny. This happens by default under Weber and Michels unless you build structural checks against it.
The post-AGI version is doctrine capture. The people maintaining doctrine, evals, agent permissions, and context gates can harden into a coherence priesthood, protecting control in the name of alignment, deciding which contradictions count, and labeling dissent as “incoherence.” Stale doctrine guarded by status is even more dangerous than stale ritual, because agents scale it across the company overnight.
You can spot doctrine capture quickly: agents are tuned to echo leadership’s preferred story, Actor feedback gets dismissed as noise, and dissent is waved away as misalignment. Even a memorable phrase can be captured. Watch what happens when an Actor brings in a real case where the slogan fails. Can they put the rule back on trial? If the steward tells them to repeat the words instead, the rite is now protecting the wording from the people paying its cost.
Symptoms of Ritual Oligarchy
Watch for five warning signs:
1. Agenda Control
On paper, any assumption or policy can be named an anti-scapegoat. In practice, whoever controls the agenda decides what actually feels the heat. Stewards steer Crossings toward safe targets (a feature spec, a minor workflow) while pay, promotions, and the ritual program itself never reach the floor. Self-critique looks lively while the biggest errors stay off-limits.
2. Moral Hazard
Rites carry real stakes: a Crossing can kill a product, a Rite of Redress can overturn a policy, a Great Dissolution can reshape careers. In a healthy program, the people who call the heat stand inside it. Under ritual oligarchy, stewards summon risk for others while staying insulated themselves. When a rite misfires and burns trust, operators absorb the damage and the stewards stay untouched.
3. Interpretive Monopoly
When a small group owns the right to say what the vows “really mean,” tools turn into dogma. Ordinary operators defer to “how the ritual team reads this,” and objections get dismissed as misunderstandings. Hard-to-vary explanations are replaced by hard-to-question ones. A program meant to keep meanings open to revision becomes a fresh source of frozen doctrine.
4. Ritual Inflation
Priesthoods justify their jobs by making the machinery bigger and harder to run without specialists. Liminal sessions stretch longer with fuzzier exits, new categories of rites pile up, and jargon grows thicker. The cognitive and temporal tax on participation rises until high-value operators treat the rites as overhead to be minimized. The meetings stay on the calendar, drained of real heat.
5. Negative Selection on Epimetabolic Talent
The people who spot contradictions early, name them plainly, and act on them are the first to leave a captured program. They see when forms serve stewards instead of truth, realize their critiques aren’t welcome, and walk away. The people who stay and get promoted are the ones most comfortable with frozen routines, leaving the organization worse at digesting error even as it talks constantly about learning.
Exhortation won’t fix this. You need structural checks.
The Cincinnatus Design: Four Countermeasures
The Skin-in-the-Game Rule and Lindy-first design already push back on capture. For doctrine stewards, the same principle calls for rotation, public decision memory, standing criticism, Actor feedback channels, and periodic Ritual Time reviews of doctrine itself. The Cincinnatus Design adds four hard governance rules:
1. Sortition Selectors
Break the link between wanting power over the rites and getting it. Pick stewards by lottery from a qualified pool of active operators: people carrying real charters who have earned trust from peers and reports and hold real stakes in the domain. Keep terms short and non-consecutive with mandatory gaps between them. Treat stewardship as temporary jury duty, not a career path.
2. The Law of Conservation of Risk
Any downside a rite creates must land at least as heavily on its stewards as on everyone else. Stewards convene rites only inside their own operating world and state up front what they personally lose if the verdict goes wrong. They sit inside the blast radius, not above it.
3. Hard Limits on Liminality
Keep Ritual Time from becoming a permanent lifestyle. Stewardship stays a bounded slice of someone’s week for a fixed season while their main job stays in Run Time. Titles lead with the operating role (“engineer,” “teacher,” “dispatcher”), with stewardship listed only as a dated rotation. Each rite gets a clear start, a clear stop, and an explicit return to ordinary accountability. When a rotation ends, hand off surviving duties visibly and name who accepted them.
4. The Jester’s Privilege
Keep the stewards and the program itself open to attack. At every major rite, pick one or two participants (ideally by lot) as Jesters. Their job is to call out performative habits, bad timing, hypocrisy, or capture, using humor or plain talk as they see fit. Speech under the cap is protected from retaliation and off-limits in performance reviews. Afterward, publish a brief “Jester report” with no rebuttal allowed. The point isn’t turning every Crossing into a comedy roast; it is making sure the forms and their keepers can be put on trial whenever needed.
Return to the Plow
The Dionysus Program survives only while it serves real work. Rites exist to raise epimetabolic rate, not to justify themselves. Pull stewards from active operators, give them temporary authority with shared downside, keep their primary job in Run Time, protect internal criticism, and send them back to the plow on schedule.
If your organization has already slipped into ritual oligarchy, use the program on itself. Put the steward structure, selection rules, and term limits on trial as an anti-scapegoat, let Jesters speak plainly, and bind concrete changes that restore rotation and shared risk, including stepping out of any permanent steward seat yourself. At civic scale, the same logic shows up in citizen assemblies picked by lot, time-limited commissions, and sunset clauses on emergency powers.
One quick diagnostic says it all: if someone in your organization can build a long, comfortable career primarily as a “keeper of the rites,” capture has already happened. Don’t hunt for villains; change the design so authority goes back to active operators and every steward returns to ordinary work.
Act III — Negentropy of Renewal
Renewal delivers more than a better explanation: it raises the coherence ceiling. Coming out of good Ritual Time, an organization can carry more agency without drifting, because doctrine is sharper, Ren held up under criticism, and real-world feedback reaches structure faster.
Autophagic Growth
Living cells survive by eating their own damaged parts. Yoshinori Ohsumi won the Nobel Prize for showing how cellular autophagy recycles worn-out components into raw material; Ilya Prigogine showed how dissipative structures stay ordered far from equilibrium by exporting entropy and pulling in fresh energy.
In an organization, the rule is simple: salvage useful knowledge and resources from work that has ended.
- The Scrap Heap Library: Archive retired code, policies, and drafts alongside short notes on what you learned, so new hires can see why earlier ideas failed before repeating them.
- Sunset Budgets: Set aside real time and money for dismantling things: unbundling products, retiring teams, deleting features. Fund cleanup as regular work rather than an afterthought.
- Hormesis Quotas: Run small, controlled stressors (chaos drills, adversarial reviews, leaderless sprints) to keep error-correction muscles warm. As Taleb argues in Antifragile, small doses of volatility protect against sudden ruin.
- Deprecation Ceremonies: Give endings a clean finish. Name the outgoing rule or project, credit what it accomplished, publish a plain obituary explaining why it ended, and make clear that the old rule no longer applies.
- Agentic Autophagy: Clear out stale prompts, abandoned automations, outdated retrieval indexes, dead dashboards, and old evals so agents stop acting on yesterday’s map.
- Reverse Apprenticeships: Let newer staff study and rework retired material; they often spot useful patterns veterans have gone blind to.
Like Heraclitus’s river, an organization stays itself by steadily replacing the parts it has outgrown.
Pro-Fractal
The four-step loop (critique → dissolution → reconstitution → renewal) repeats across every scale, much like Mandelbrot’s fractals. A person questions a habit; a team revises a working rule; a city puts a policy on trial. Frequent small corrections head off catastrophic breaks.
- The Fractal Calendar:
- Daily: A quick personal check: what belief did I test, what attachment loosened, what habit changed, what energy came back?
- Weekly: A team Crossing with one anti-scapegoat, one brief aesthetic opening, one tragic postmortem, and one written commitment.
- Quarterly: An organizational Great Dissolution with outside critics, festivals, updated charters, and promotions aligned with what survived.
- Yearly: A civic Rite of Redress and public festival, putting policies on trial and updating shared founding stories with care.
- The Renormalization Rule: As scale grows, lengthen the liminal window, widen who participates, and use symbols the wider group recognizes. Keep the core rules unchanged: attack objects rather than people, bring real heat without harm, and publish binding verdicts.
Apply the loop to the program itself. Periodically put the Dionysus Program’s own charters, vocabulary, metrics, and steward rotation on trial as an anti-scapegoat, with Jesters speaking freely. That self-check keeps the program from freezing into the kind of orthodoxy it was built to break.
Coherence works across scales the same way: intention → doctrine → execution with clear ownership → real-world results → contradiction → Ritual Time → revised doctrine. An individual runs that loop with personal commitments and habits; a team runs it with doctrine, agents, customers, and postmortems; a firm runs it with Auteurs, formal doctrine, agent workflows, Actors, Ritual Time, and Run Time. If the loop exists only at headquarters, coherence won’t travel.
Keep two ledgers tied to the mode toggle:
- Ritual Time (liminal) ledger: container integrity, honest participation, cooling after heat, rule fidelity, and clean exits.
- Run Time (operating) ledger: responsibility coverage, commitments kept, forecast accuracy, leverage per unit knowledge, reversibility, and safety.
The first ledger tracks whether the room stayed safe enough for hard truths to surface; the second tracks whether the group actually executed what survived after Touch Down. Both serve one underlying question: did our ability to turn error into better structure go up? Rationality and personal responsibility stay on in both modes; only the scorecard switches.
Three practical signs tell you epimetabolic rate is climbing:
- Bad explanations die faster: weeks instead of years once evidence refutes them.
- Postmortems change real structure (roles renamed, metrics killed, rules rewritten) instead of producing forgotten docs.
- Fewer topics stay “undiscussable”; more hard questions make it onto the table without social fallout.
Measure lightly. Score big forecasts and write down major bets, yet kill any metric the moment it becomes a gaming target or turns the rites stiff. Practices and stories outrank dashboards. If a ritual, metric, or role does not increase your epimetabolic rate, it is overhead and should be deprecated.
Unlike Taleb’s focus on asymmetric payoffs from random shocks, the edge here comes from getting faster at spotting your own mistakes and rebuilding around what you learn.
Touch Down
The whole point is keeping criticism connected to repair, so every honest challenge turns into a change people understand, carry out, and can question again later.
Practices you can start tomorrow:
- Close Ritual Time with doctrine updates. Before returning to Run Time, settle what changed, where it lives, which agents need new context, which workflows get retired, who owns the outcomes, and who encodes the update.
- Install an anti-scapegoat. Write a no-person blame covenant, pick one artifact for your next Crossing, put it on trial, and publish the verdict and next commitment.
- Block ritual oligarchy early. Rotate stewardship among active operators (ideally by lot), cap terms and hours, and write down how stewards share the downside.
- Add beautiful heat. Write a one-page illustrated obituary for a recently killed project, hang it where everyone sees it, and open your next review with it.
- Defend play. Put unscored, shared-attention time on the calendar where rank drops away, and protect it when deadlines tighten.
- Run a tragic postmortem. Walk through hamartia → peripeteia → anagnorisis → act, record the structural change, and rename the affected role or rule to mark what shifted.
- Start a Scrap Heap Library. Move retired code, policies, and designs into a searchable archive tagged with the assumption that failed or the test that settled it.
- Repeat across scales. Run daily, weekly, quarterly, and yearly loops with the same three rules: attack objects not people, open with beauty, close with binding commitments.
The Dionysus Program is deliberately conservative about form. Almost nothing here is brand new; it recombines durable civilizational vessels (trials, synods, festivals, postmortems, fasts, and feasts) under modern names. When unsure, adapt an old form instead of inventing one from scratch.
Each thinker contributes one working piece:
- Popper and Deutsch supply the epistemic engine: better explanations break old ones.
- Durkheim and Merton diagnose anomie and explain why real rites need the weight of Social Facts.
- Confucius separates Li (form) from Ren (humaneness): never outrun your Ren with Li.
- Mauss supplies the gift cycle, where real hospitality earns honest candor in return.
- Ibn Khaldun names Asabiyyah, the binding strength that lets a group survive internal conflict.
- Weber and Michels trace the slide into oligarchy; Cincinnatus and Athenian sortition supply the counterweight of temporary, lottery-drawn, operator-run stewardship.
- Girard exposes the scapegoat trap, which the anti-scapegoat disarms.
- Turner maps the ritual passage: separation, limen, and reincorporation.
- Nietzsche shows how aesthetic form helps people face hard loss.
- Hegel describes recognition: seeing your own part in what broke.
- Prigogine and Ohsumi offer physical and biological models for staying ordered by recycling decay.
- Taleb and Mandelbrot guide implementation: train on small shocks and repeat the shape across scales.
- Paul David, Gavin Wright, and Warren Devine supply the electrification analogy: general-purpose technologies pay off fully only after organizations redesign around the new bottleneck.
- Simon shows why shared premises stay necessary even when local reasoning gets cheap.
- Galbraith shows how uncertainty drives information load.
- Thompson matches coordination mechanisms to the type of interdependence.
- Ashby shows why more agency-variety demands matching regulatory variety.
- Goldratt turns the bottleneck into an operating sequence.
- Eliade distinguishes sacred time from clock time, explaining why older, received forms hold up under heat.
- Wittgenstein shows that every framework rests on hinges it commits to rather than proves.
The test is whether people can correct an error and still be willing to report the next one.
The Alchemist’s Assay
The Alchemy of Error argued that organizational error correction needs both public scrutiny and real protection for the people involved. Now we can use the alchemical analogy as a test of whether the method is working.
I. The Correspondence
The Program and alchemy describe the same cycle from two angles. The Program names what you do: verbs, rites, toggles. Alchemy names what the material feels like: breakdown, purification, dawning, embodiment.
Knowing only the verbs lets someone go through the motions without noticing when a session goes sour. Knowing only the states lets someone feel that something is wrong without knowing how to fix it.
The materials map straight across. Lead (the prima materia, heavy and opaque) is unmetabolized error: the blown launch, the wrong assumption, the strategy reality refuted. Gold is explanatory reach: hard-to-vary structure that holds up in the world. The Stone, the catalyst that makes transformation possible without being used up, is Ren. The Vessel is Li, the ritual form whose strength decides whether the room holds the heat or blows apart. Melt brings the pressure; critique breaks down the old structure; beauty helps people bear the loss.
The four stages of the alchemical Magnum Opus, each named for a color, map across too, with one deliberate change of order. Classical alchemy starts with nigredo (blackening); in social systems, you have to build the safe room before anything dissolves inside it. Albedo (whitening) comes first: entering Ritual Time so truth can be spoken without scapegoats. Nigredo (blackening) is dissolution: the dark stretch where the old explanation dies and things look ruined. Citrinitas (yellowing) is reconstitution: a new explanation taking shape. Rubedo (reddening) is renewal: putting that understanding to work in ordinary operations.
II. The Diagnostic Value
These terms earn their keep by helping you catch counterfeits. Every stage has a real version and a fake one that mimics the look while missing the substance.
Albedo: True Whitening vs. False Whitening
True whitening builds a room where criticism flows because it stays aimed at objects and people know they are safe. Truths surface that would never have surfaced in an ordinary meeting.
False whitening is “blameless” on the surface and blame-hidden underneath: office politics dressed up as analysis. Everyone performs the format while knowing real dissent will be punished next week. The test: did anything get said that people wouldn’t have said anyway? If not, the whitening was fake.
Nigredo: True Blackening vs. Scapegoat Substitution
True blackening lets an old explanation die in public without sacrificing a person. The team watches cherished assumptions come apart and resists reaching for a victim to restore calm. It hurts, and it has to.
False blackening is the Girardian blowup: heat jumps from the object onto a person. Someone gets blamed. The group feels relief. Nothing is learned. The test: did dissolution feel like a loss, or like a victory? True Nigredo feels like loss. If it felt triumphant, if someone got beaten, it was false.
Citrinitas: True Dawn vs. False Dawn
True dawn delivers a new explanation that is specific, testable, and binding. “We are the kind of team that…” gets put on the table, and roles and rules start shifting to match.
False dawn is insight that never touches reality: smart conversation that changes no policy, no code, and no commitment. The test: can you write down the change and name who accepted responsibility for it? If not, the dawn was false.
Rubedo: True Embodiment vs. Extraction
True embodiment brings the group back into Run Time with stronger capabilities and thicker Ren. People are more willing to surface the next mistake, because the last cycle proved it was safe.
Extraction ships the fix by burning trust. The org chart or product improves, while the team learns that candor gets you hurt. You won the quarter and spent down the trust you needed for the next cycle. The test: is telling the truth cheaper or more expensive than it was before? If cheaper, renewal worked. If more expensive, you extracted.
III. The Assay
Alchemists used assays to check whether their gold was real or just gilded lead.
In chemistry, a catalyst survives the reaction unchanged, ready for the next batch. In organizations, every rite either burns or multiplies its catalyst. There is no neutral outcome; each cycle shifts trust in one direction or the other.
Extraction buys better structure by burning Ren through overflow, theater, scapegoating, or coercive closure. People walk away convinced that truth costs too much, leaving less trust for the next hard turn.
Multiplication builds better structure and thickens Ren at the same time. The group steps into heat together under protection, gets through without picking a victim, binds real changes, and leaves knowing they can do it again.
After Touch Down, ask two questions:
- Did reach expand? Can you solve problems you couldn’t solve before?
- Did the catalyst survive? Is the team more willing to flag an error next time, or less?
Two yeses mean true alchemy. Only the first means extraction, with diminishing returns as the trust account runs dry.
After any high-agency cycle, add a Coherence Assay:
- Did intent survive distribution?
- Did agents act from current doctrine?
- Did local wins still serve the system goal?
- Were duties covered by Actors who explicitly accepted them?
- Did real-world feedback make it back into doctrine?
- Did contradictions turn into structural changes?
- Did trust survive correction?
If work shipped while those answers came back no, output went up while your coherence ceiling dropped. That is not renewal. It is inventory before the bottleneck.
Alchemists drew the Ouroboros, the serpent eating its own tail, to picture cyclical renewal. Every explanation eventually reaches its expiration date. The goal is a repeatable loop that leaves the group still able to trust one another when the next correction arrives.
The Hinge
The Dionysus Program begins with a commitment:
We commit to discovering and correcting error, holding no explanation or practice exempt, and sustaining the conditions for doing so.
Sustaining those conditions includes staying viable. As the half-life of knowledge shrinks, we have to consume our own errors, or let the market consume us as an error. We need to learn and adapt fast enough to keep the ability to learn and adapt again.
That commitment is the program’s hinge, and it is also its myth: a stance on how to act, not a promise of final answers or automatic progress. We act from it even when our current explanations fail.
Wittgenstein’s image of a hinge fits here: inquiry always rests on commitments it cannot first prove from the outside. Every practice in this book already assumes a willingness to look for errors and fix them. We can argue over the wording and refine its demands, yet walking away from the commitment means leaving the practice altogether. We hold it as a choice we make, not a theorem we proved.
Each clause carries real weight. Discovering error requires contact with reality and room for contradiction. Correcting error means letting what we learn actually change our plans and habits. Holding nothing exempt includes founders, stewards, and this program itself. Priorities and timing still apply; permanent immunity does not.
Sustaining the conditions means protecting the capacity to keep learning over time, even as those conditions shift. That may mean retiring a ritual, replacing a tool, reorganizing a team, resting, rebuilding trust, or throttling back agency that outruns our ability to check it. Continuity belongs to the capacity for correction. No particular arrangement is entitled to survive.
No local win counts if it wrecks the conditions the wider system relies on, and protecting those conditions cannot become an excuse to put off hard corrections forever. Both duties stay live.
I chose this commitment because it says little about which specific answers are right and everything about how to act when they break. It does not depend on any single technology, business model, or mix of humans and machines.
Keep doctrine out of the myth layer. Myth is the durable layer (who we are); doctrine is the replaceable layer (how we act right now). Make doctrine sacred and you can’t update it; rewrite myth every quarter and nobody knows where they stand. Mixing the two is one of the fastest ways to freeze an organization in place.
The Human Application
Working with people brings direct moral duties. In the human application of this program, we protect honest criticism, refuse humiliation and scapegoating, keep our word on the safety of the room, and take responsibility for harm. People have real claims on us even when ignoring them would look more efficient. The hinge alone doesn’t supply a full human ethic; these commitments do.
Ren makes error correction livable among people who have to keep working together, supported by rest, hospitality, beauty, and honest grief over losses. Protection doesn’t cancel accountability: people still answer for their conduct, their use of authority, and the promises they make. Automating a step doesn’t erase our duties to the people affected by it.
The Profession of Faith
A shared commitment works best when people have plain words they can point to when correction gets expensive:
We commit to discovering and correcting error, holding no explanation or practice exempt, and sustaining the conditions for doing so.
In our work together:
We learn and change to remain viable, so we can keep learning and changing.
We welcome criticism, protect those who offer it, and honor their trust.
We make our shared intent clear, carry it faithfully into action, and let reality change our minds.
We keep our power to act within our capacity to guide and correct it.
We respect each person’s worth and refuse humiliation, retaliation, and scapegoating.
We make room for rest, loss, and repair.
We honor our obligations to everyone our work affects.
We admit failure, answer for harm, and undertake repair.
We hold ourselves and our leaders to these commitments.
Leaders have to make this commitment clear, explain what it asks, and live inside it visibly: taking unwelcome feedback, reversing their own bad calls, and accepting limits on their power. The profession belongs to everyone, and anyone can invoke it, including against a leader.
Read it together when new people join, before a high-stakes Crossing, and after a tough correction has tested the group, then tie the words directly to the conduct the moment calls for. Words earn weight from what happens next.
Faith here means keeping the commitment when things are uncertain. Doubting a rite, a leader, an explanation, or whether the group is living up to its own vows is fair game and calls for open review. Demanding fake certainty would shut the exact door this profession is meant to keep open.
Coda: Crimes Against Ren
Preamble
Crossings, Dissolutions, and Tragic Postmortems are built to hold high heat without burning people. None of them hold up without enforcement.
A rule you won’t enforce is a suggestion, not a container. The standing right of criticism turns into a trap if retaliation carries no penalty. Without real consequences, the program degrades into polite theater that changes nothing.
Old traditions far apart in time and geography landed on the same principle: offenses against the core social bond need their own law. In Jewish tradition, even the Day of Atonement cannot wipe out a wrong done to another person until the victim grants release. Athens prosecuted hubris as a public crime because degrading a citizen’s dignity endangered the city. Germanic tribes put oath-breakers outside the protection of the law altogether.
This program borrows that logic: breaking the trust that makes Ritual Time work costs you the privileges that trust supports.
There are crimes against coherence too, though they stay subordinate to Ren. You don’t need a courtroom for every stale prompt, just clear names for the acts that poison distributed agency:
- Doctrine laundering: smuggling private or political agendas into agent execution under official wording.
- Shadow doctrine: running on private premises while pretending to follow shared doctrine.
- Stale-agent negligence: knowingly leaving agents running on obsolete rules.
- False coherence: shutting down real contradictions in the name of “alignment.”
- Mode fraud: using Ritual Time language to grab Run Time power, or pulling Run Time rank to block needed Ritual Time.
All five damage how intent survives distribution. They cross into crimes against Ren whenever they weaponize trust, silence reality-contact, or punish protected speech. Coherence rules never outrank the relationships that make honesty possible.
The danger runs both ways: without enforcement, the container becomes theater; with enforcement nobody can question, the law becomes a tool for scapegoating. What follows sets out the breaches, the reckoning, and the consequences.
I. The Breach
1. The Categorical Distinction
The program’s normal loop (critique → dissolution → reconstitution → renewal) handles errors in strategy, code, and operations.
Crimes against Ren are different in kind, not just bigger mistakes. They break the machinery of error correction itself. A team whose trust has been ambushed cannot run a blameless postmortem; a group whose records have been tampered with cannot rely on its own verdicts.
2. The Three Orders
Offenses sort by what they harm:
First Order: Crimes Against the Container Violations of the machinery itself: breaking the no-person blame vow during Ritual Time, tampering with the Scrap Heap Library or oath records, or faking the mode toggle to ambush someone. Like Islamic Hudud, these cross fixed boundary lines, and the harmed party is the group’s capacity to function.
Second Order: Crimes Against Persons Violations that injure a specific person inside the container: weaponizing something shared under protection, retaliating for protected speech, or abusing the Jester’s Privilege to run a personal vendetta. Here the harmed person, not the community, holds the primary claim.
Third Order: Crimes Against Common Knowledge Violations that poison shared reality: what was agreed to, who signed on, and whether honesty is really safe. Examples include gaslighting about past commitments, falsely claiming others agreed, or hiding retaliation behind professions of loyalty. Questioning the program or doubting whether the group lives up to its vows is never a breach.
3. The Modifiers
Two factors raise the weight of any offense:
Chillul Hashem (Desecration of the Name) When the offender’s role makes the act representative, the damage multiplies. A junior teammate cutting a corner is a personal mistake; a steward cutting a corner tells everyone the rules are fake. Breaches by stewards carry automatic heavier consequences because they license everyone else to defect.
Lashon Hara (The Evil Tongue) True words can still be a breach if they are used as a weapon. Taking an accurate admission made safely in Ritual Time and using it against someone in Run Time is a crime against Ren. “It was true” is no defense when you broke the protection of the room.
II. The Reckoning
1. Prior Reconciliation
For Second Order offenses, the order is strict: the group cannot close the matter until the offender goes directly to the person harmed.
- Direct Acknowledgment: Name what you did and why it was wrong to the person you hurt.
- Restitution: Repair what was damaged or taken.
- Request for Release: Ask the harmed person to release the debt.
The community can support and witness this step, but it cannot forgive on a victim’s behalf. If the victim withholds release, the debt stays open. If the victim is gone, the debt stays permanent.
2. Public Acknowledgment
Separate from private reconciliation, the offender owes the group an honest accounting modeled on tragedy:
- Hamartia: Name the internal flaw, not excuses or circumstances.
- Anagnorisis: State the pattern plainly (“I am the kind of person who…”).
- Structural Commitment: Bind a specific, observable change.
This step applies even when private reconciliation fails; the group still has to protect its future.
3. The Tribunal
Each order uses a different judge:
- First Order (Container): A Sortition Tribunal of jurors picked by lot from a qualified pool, separating judgment from office-seeking.
- Second Order (Persons): A Victim-Centered process where the harmed person proposes the remedy and holds veto power over release.
- Third Order (Common Knowledge): The Jester Channel calls out atmospheric drift; if the behavior continues after notice, it escalates to a First Order tribunal.
III. The Consequence
1. Atimia
The main remedy is separation, not punishment. In Athens, atimia meant civic death: staying physically present without a public voice.
An atimos loses access to Ritual Time, the standing right of criticism, and eligibility to serve as a steward, while keeping their Run Time job, pay, and operating metrics. That status has to be announced openly so common knowledge stays intact.
- Temporary: Runs for a fixed term.
- Indefinite: Applies to Second Order breaches where the victim withholds release, lasting until they grant it.
2. Exile
Exile removes the person from the community altogether, reserved for repeat offenses or serious Chillul Hashem by stewards. Like the Jewish cherem, it redraws the boundary to exclude the offender. Whether exile from Ren also ends employment depends on whether the job can be done cleanly on purely transactional terms.
3. Restoration
Separation aims toward return where return is earned:
- From Temporary Atimia: Completing reconciliation and public acknowledgment.
- From Indefinite Atimia: Release from the harmed person. Nothing else substitutes.
- From Exile: Rare, requiring sustained, unmistakable proof of change.
Some breaches never end in restoration. Permanent separation has to stay real for the boundaries to mean anything.
The Living Law
This penal code stays open to the same scrutiny as everything else. Periodically put it on trial as an anti-scapegoat in a Crossing: are the three orders drawn right, is atimia being abused, and is restoration genuinely reachable?
If the code stops protecting the container and starts shielding powerful insiders, rewrite it. The people enforcing the law live under it too; a juror who betrays a tribunal commits a First Order offense. Under the hinge, nothing, not even this law, stands above correction.
The Epimetabolic Equation
A Mathematical Thought Experiment
What would this book’s ideas look like as a mathematical system? The equations below are one possible sketch. They put formal shape around the book’s central intuition: an organization’s ability to improve depends on how fast it can turn error into better structure without tearing through its own trust.
This is a thought experiment, not an empirically tested theory or a proven calculus of organizational life. Trust, beauty, and stewardship don’t come in standard units. The numbers are illustrative choices, and the equations encode specific bets about how these forces interact. A result can follow cleanly from those bets without proving that real companies behave that way.
The point of writing equations down is making our assumptions visible. Making trust a bottleneck, letting unprocessed error compound, and letting stewardship drift lets us trace what those assumptions imply together. You can challenge the relationships as well as the numbers. The mathematics gives the argument something explicit to be wrong about.
The coherence addition sits beside the main loop as a Run Time load limit. Epimetabolic rate governs how well an organization updates its map and repairs trust; coherence capacity governs how much distributed agency can act on the current map before extra agents start doing harm.
Objective: Explanatory Reach (S)
In this model, Structure (S) stands for Explanatory Reach: the range of problems the organization can handle with its current explanations, roles, and commitments.
- Reach Delta (ΔSt): How much that reach grows (or shrinks) in a given cycle.
- Decay as Amnesia: Toxicity doesn’t just make people unhappy; it erodes reach. As the social fabric holding institutional memory breaks down, the organization forgets how to solve problems it used to handle easily.
Variables: Inputs and Environment
These inputs and state variables describe an imagined organization at cycle t. Their scales belong strictly to the model; putting a number on Ren or Beauty isn’t a real-world measurement. Some inputs are choices; others reflect accumulated conditions or outside pressure.
Melt Rate (μt)
Melt comes from two sources:
- μtenv — Environmental Melt: Outside disruption—market shifts, new technology, competitors, regulation. You don’t choose it; it’s weather.
- μtchoice — Chosen Melt: Disruption you take on voluntarily—R&D, new bets, restructuring, entering new markets.
μt = μtenv + μtchoice
You can’t escape environmental melt by ignoring it. When μenv is high, you either build the capacity to process it or get passed by organizations that do.
When public Ritual Time is scarce, a group can look calm on the surface because people are processing disruption privately. That hidden work softens individual stress without converting much of it into shared reach, since nothing changes in common knowledge.
Controllable Inputs
- Lt — Li: The capacity of the organization’s ritual forms (Crossings, postmortems, reviews) at time t.
- Rt — Ren: The density of trust and shared history (Asabiyyah) at time t.
- Ct — Cincinnatus: Stewardship integrity at time t (0 to 1). It drops when rites settle into a permanent priesthood.
- ρ — Rotation Rate: How often stewardship turns over (probability of a reset each cycle).
- βt — Beauty: The aesthetic form that helps people face loss in Ritual Time and act on revised rules in Run Time. It boosts growth from metabolized loss, softens theater damage, and helps human Actors absorb updated doctrine (βt ≥ 0.1).
- τt — Tau: The toxicity penalty for unprocessed error at time t, set high by default ( ≈ 1.5).
Parameters: Illustrative Assumptions
These parameters stay fixed during a simulation run. They express the assumptions this version of the model explores, not universal constants. None of them are empirically calibrated, and a cycle t has no fixed mapping to a week, quarter, or year.
- α — Earn Rate ( ≈ 0.02): Trust builds slowly; each successful cycle adds only a small increment of social capital.
- γ — Burn Rate ( ≈ 0.10): Set at 5× the earn rate to capture how much faster trust burns than it builds. That ratio is a modeling choice, not a measured law; actual trust movement also depends on Growth, Decay, and Beauty.
- δ — Oligarchic Drift ( ≈ 0.05): Stewardship integrity (C) erodes over time as incumbents protect their own seats.
- κ — Hollow Ritual Penalty ( ≈ 0.50): Running intense rituals without enough trust creates Management Theater and carries a direct cost.
- λ — Aesthetic Multiplier ( ≈ 0.20): Higher beauty helps a group turn metabolized error into stronger structure.
Equations: System Dynamics
From cycle t to t + 1, the model steps through three stages. The weakest-link minimum, quadratic overflow penalty, and full stewardship reset are all modeling choices; different choices would give different curves.
Step 1: Calculate Intermediate States
Compute effective capacity, theater, and overflow for the cycle:
Metabolic Capacity (Ωt): Capacity is capped by whichever is lower: integrity-adjusted ritual form or available trust.
Ωt = min (Lt ⋅ Ct, Rt)
Theater Gap (Theatert): The friction caused by running rituals larger than the trust beneath them.
Theatert = max (0, (Lt ⋅ Ct) − Rt)
Overflow (Overflowt): Melt that exceeds what the group can process.
Overflowt = max (0, μt − Ωt)
Step 2: Calculate Growth and Decay Terms
Growth (Gt): Metabolized melt, amplified by Beauty.
Gt = min (μt, Ωt) ⋅ (1 + λ ⋅ βt)
Decay (Dt): Damage from unprocessed overflow (which scales quadratically) and hollow theater (which scales linearly).
Dt = Overflowt2 ⋅ τt + (κ ⋅ Theatert)/βt
Step 3: Update State Variables
Update the four core stocks from those flows:
Explanatory Reach (S): Net gain or loss in capability.
ΔSt = Gt − Dt
St + 1 = St + ΔSt
Trust (R): Trust grows slowly through beauty-backed learning and drains fast under decay.
Rt + 1 = max (0, Rt + α ⋅ βt ⋅ Gt − γ ⋅ Dt)
Stewardship (C): Integrity drifts downward unless rotation resets it.
Stochastic Definition:
Ct + 1 = 1.0 with probability ρ (Reset).
Ct + 1 = Ct(1 − δ) with probability 1 − ρ (Drift).
Analytical Expectation: For a given rotation rate (ρ) and drift (δ), expected steady-state integrity (C*) solves:
𝔼[Ct + 1 ∣ Ct] = ρ ⋅ 1 + (1 − ρ) ⋅ Ct(1 − δ)
C* = ρ/(1 − (1 − ρ)(1 − δ))
Competitive Threshold (S̄): The minimum reach needed to stay competitive. It climbs with cumulative environmental melt: every problem the world throws up that you don’t solve, someone else will.
S̄t + 1 = S̄t + μtenv
Or equivalently: S̄t = S0 + Σi = 0t − 1μienv
Failure Conditions
The model tracks two ways an imagined organization can fail (illustrative thresholds, not empirical cutoffs):
- Internal Collapse (Trust Death Spiral): Rt ≤ 0. The organization burns through its social capital. Even if it is winning in the market, the team falls apart.
- Competitive Collapse (Outpaced): St < S̄t. The organization falls behind its environment. Even with high internal trust, it becomes obsolete as rivals turn the same disruption into new capabilities.
An organization can collapse internally while winning the market, collapse competitively while keeping a great culture, or hit both at once. Staying alive requires Rt > 0 and St ≥ S̄t.
Agency Load and the Coherence Ceiling
AGI adds a second operating limit: agency load.
- At — Deployed Agency: Active action-capacity across people and software.
- Coht — Effective Coherence Capacity: How much agency load the organization can carry this cycle given its regulatory variety and fidelity to current doctrine.
- Ft — Doctrine Fidelity: How closely local Actors and Agents follow current doctrine.
- Ht — Doctrine Half-Life: How long doctrine stays accurate and understood before change or drift makes it stale.
- It — Incoherence Tax: Rework, conflicting promises, duplicated effort, uncovered duties, supervision drag, and trust repair.
- Vta — Agency Variety: The range of actions deployed agency can take.
- Vtr — Regulatory Variety: The doctrine, evals, permissions, feedback loops, rituals, and human judgment available to keep action in bounds.
Suppose a fresh specification has functional quality Dfunc between zero and one. As it ages without refresh, the simulator discounts that quality by 0.25 + 0.75 ⋅ 2−at/Ht, where at counts cycles since the last update. Call the quality available this cycle Dfunc, t; refreshing it restores Dfunc.
A machine Agent can act on the new specification immediately. A human Actor also has to override old habits. Let θ be the cost of updating a prior per unit of melt; as melt rises, more habits have to change:
Ftagent = Dfunc, t
Ftactor = Dfunc, t ⋅ (βt/(βt + θμt))
Here μt includes both environmental and chosen melt. At zero melt the two fidelities match. Let ω be the share of decisions that rely on human judgment (0 < ω ≤ 1). Combining the two gives the share of intent that survives into action:
Ft = (1 − ω)Ftagent + ωFtactor
If Kt is raw capacity before losses from limited regulatory variety and imperfect fidelity, the effective ceiling is:
Coht = Kt ⋅ min (1, Vtr/Vta) ⋅ Ft
Take a concrete example: a fresh, crisp rule with half the calls in human hands, total melt at five, and update cost θ = 0.2. With cold form (βt = 0.2), Agent fidelity is 1 and Actor fidelity is one-sixth, carrying about 58 percent of intent into action. Raise Beauty to 4 and Actor fidelity climbs to four-fifths, pushing combined fidelity to 90 percent. Clearer, more memorable form raises the ceiling even when the machine instructions never change, though whether the underlying rule is true stays a separate question.
Once agency load crosses this ceiling, extra actions trigger an incoherence tax that can eventually outweigh the gain from adding more agency:
At ⋅ Vta > Coht ⇒ It > 0
In Ashby’s terms:
Vtr ≥ Vta for action that must remain within shared essential variables
These inequalities are conceptual shorthand, not calibrated tests; there is no shared unit or fixed tipping point here. They put the load warning in one place: once agency outruns your ability to guide and check it, more agents add rework and cleanup faster than useful work.
Staying under the ceiling doesn’t guarantee every duty has an owner either. Check responsibility coverage separately from action volume.
Epimetabolic rate raises the coherence ceiling by keeping doctrine fresh, repairing Ren, and sharpening feedback. A good Ritual Time cycle shows up both in better explanations and in a wider span of coherence.
Diagnostic: Epimetabolic Rate (Φ)
One final ratio sums up the model’s core question: how much structure did we gain per unit of net trust spent? Like the rest of the model, this is a way to think clearly, not a real-world benchmark score.
Φt = max(0, ΔSt)/max(ϵ, Rt − Rt + 1)
Here ϵ is a tiny positive floor that prevents division by zero. Whenever trust holds steady or rises, the raw value depends on that floor, so read it only inside the simulator rather than as a standalone organizational score.
- High Φ (The Dionysian): Reach climbs while trust holds steady or grows.
- Medium Φ (The Pyrrhic Victory): Reach grows, yet you are spending down trust to get it: winning the quarter while wearing out the team.
- Low Φ (The Pyre): Small gains cost heavy trust, burning the capital needed for future corrections.
Using the Calculator
The interactive simulation calculates what follows from the inputs and rules you pick. It cannot tell you whether those rules match your company, and clean charts aren’t evidence.
Pick an archetype, change one slider, and watch how the trajectory shifts. What happens when disruption climbs while ritual capacity stays flat? What happens when stewardship rotates faster? Use the curves to test your intuitions about feedback loops and tradeoffs, then ask which assumptions fit your own experience and what evidence would disprove them. A simulated collapse is an implication of the setup, not a prediction; a thriving curve is a prompt to test an idea, not proof it will work.
Explore the interactive simulation →
Archetypes: The Space of Organizational Fates
The archetypes below name common patterns that show up when you play with the Epimetabolic Equation. They are sketches for thinking, not an exhaustive list or proven laws of organizational life. Each pairs a set of assumptions with a familiar story so you can ask sharper questions about your own situation.
For each archetype, we outline the Situation (the parameter setup), the Dynamics (how the model behaves), and the Outcome (the trajectory it produces), with links to the simulator and interpretive historical examples in Appendix C.
Thriving Archetypes
The Dionysian Ideal: See simulation · Historical cases
A research lab holds regular reviews where any project can be torn apart without people doubting each other’s motives. A startup turns a failed launch into a sharper product process. An investment committee rotates its devil’s advocate and takes dissent seriously. These groups welcome tough problems because they know how to learn from misses.
Situation: High environmental melt (μenv), strong ritual capacity (L), high beauty (β), regular rotation (ρ), and solid starting trust (R0).
Dynamics: Capacity Ω = min (L ⋅ C, R) covers most incoming melt. Growth G compounds with the help of beauty (1 + λβ), while decay D stays low because overflow is small and rituals never outrun trust. Trust actually grows because αβG > γD: each clean cycle deposits more social capital.
Outcome: Reach S pulls steadily ahead of the competitive bar S̄ while trust R climbs. Disruption makes the organization stronger, which is the target state of the Dionysus Program.
The High Performer: See simulation · Historical cases
An engineering team ships on time, runs useful retros, and maintains solid trust. A consulting firm keeps clients happy without putting much thought into how people experience the work. Everything runs reliably, though some learning capacity stays untapped.
Situation: Close to the Dionysian Ideal, with lower beauty or slower stewardship rotation.
Dynamics: Growth beats decay every cycle and trust holds steady or inches up. Stewardship drifts slightly between rotations and lower beauty yields less lift, yet nothing breaks.
Outcome: S stays comfortably above S̄ over the long haul: steady, reliable performance that still leaves upside on the table.
The Virtuous Cycle: See simulation · Historical cases
Three founders start out barely knowing each other. They run candid demos, welcome disagreement in planning, and fix mistakes without blaming one another. Every clean correction builds trust, letting them tackle harder disagreements and bigger bets together.
Situation: High beauty and active rotation, starting from low initial trust (R0), typical of a young team or new venture.
Dynamics: Because beauty amplifies the earn rate, αβG stays well above γD. As R climbs, Ω grows with it, letting the team absorb more melt, earn more growth, and bank more trust in a self-reinforcing loop.
Outcome: Both S and R curve upward together as the team builds itself from fragile to resilient.
Moderate Growth: See simulation · Historical cases
A mid-sized company runs clear meetings, makes clean decisions, and delivers what it promises. It grows, solves its problems, and holds its ground without exceptional flair or serious dysfunction.
Situation: Adequate levels across the board: moderate beauty, moderate rotation, reasonable trust.
Dynamics: Growth clears decay by a steady margin. Nothing acts as a bottleneck and nothing acts as a force multiplier.
Outcome: Steady progress with S safely above S̄. Many durable, mature businesses live right here.
Edge Case Archetypes
The Fragile Survivor: See simulation · Historical cases
A team running right at its limit: enough margin for normal bumps, none for bad luck. When a key leader happens to be on deck during a crisis, they pull through; when trouble hits during a handoff, they crack. The company isn’t visibly broken, just one bad quarter from breaking.
Situation: Moderate rotation and parameters balanced close to the edge, leaving outcomes sensitive to random timing, especially when stewardship resets happen.
Dynamics: On lucky runs, C resets right before heavy melt, keeping Ω high. On unlucky runs, C drifts low right when melt spikes, triggering overflow and decay.
Outcome: Survives some runs and collapses on others depending on timing and luck, with no buffer for an ill-timed hit.
The Gambler: See simulation · Historical cases
A startup taking on far more disruption than the market asks for, pivoting every quarter, rewriting core systems every year, and betting the company on unproven leaps. When the bets land, they blow past cautious rivals; when they miss, runway, trust, and talent burn up together.
Situation: Chosen melt (μchoice) outweighs environmental melt (μenv): aggressive R&D, constant bets, “move fast and break things.”
Dynamics: Heavy melt creates huge upside when capacity holds and rapid quadratic decay when it doesn’t, making runs wildly uneven.
Outcome: All or nothing: either breakout success that looks like genius or a crash that looks reckless.
Pyrrhic Archetypes
The Pyrrhic Leader: See simulation · Historical cases
A company hits every quarterly target while experienced staff quietly walk out the door. Executives point to market share while attrition climbs. Everyone on the floor knows the pace is unsustainable, yet that cost stays off the leadership agenda as the firm spends down years of accumulated trust.
Situation: High melt and high operational capacity paired with very low beauty (β): hard-edged execution with little care or warmth.
Dynamics: Ω is strong enough to generate real growth, keeping S above S̄ and winning in the market. Because low β chokes off trust-building (αβG) while decay (γD) keeps biting, social capital drains every cycle.
Outcome: Market dominance hiding internal rot. The dashboards stay green until R hits zero and the team unravels.
The Churn Machine: See simulation · Historical cases
A company that reorganizes every six months. New leaders, new priorities, and fresh org charts keep any faction from hardening into a permanent clique, while also wiping out the context needed to make hard tradeoffs well. Every incoming leader starts from scratch and repeats mistakes their predecessor already paid for.
Situation: Very high rotation (ρ) paired with low beauty: constant leadership turnover and perpetual restructuring.
Dynamics: Constant resets keep C high and stop oligarchy, yet low beauty keeps trust from compounding and frequent resets keep institutional memory from building.
Outcome: Stays alive without compounding: no calcification, yet no real depth either, like running hard on a treadmill.
Decline Archetypes
The Slow Decline: See simulation · Historical cases
A once-central department that quietly turns into a backwater. No layoffs, no scandals, no single blowup; just strong people transferring elsewhere, meetings growing a little staler each year, and problems getting less interesting. Because no single quarter triggers an alarm, nobody steps in until ten years later someone asks why the team still exists.
Situation: Low environmental melt, low chosen melt, and modest capacity: neither pushed by the market nor pushing itself.
Dynamics: Growth is small, and small persistent decay (from stale rituals or slow stewardship drift) edges it out cycle after cycle.
Outcome: S slips gradually behind S̄. Survivable for years, because every quarter’s drop hides inside normal noise.
Competitive Collapse Archetypes
These organizations fail not because the team turns on itself, but because the business falls behind what its market now requires. The culture stays intact while the product goes stale.
The Sitting Duck: See simulation · Historical cases
A local paper with a proud newsroom and loyal readers decides to skip digital because “our subscribers prefer print.” A retailer with warm service watches e-commerce grow and sits still. A law firm waves away new tools as “not how serious work gets done.” Trust, culture, and daily routines stay healthy right up until the market leaves them behind, doing everything right by yesterday’s rules.
Situation: High environmental melt (μenv) met with near-zero chosen melt (μchoice).
Dynamics: Avoiding disruption avoids overflow and keeps trust intact, yet S̄ climbs by μenv every cycle while S barely budges.
Outcome: Competitive collapse with good morale. Disruption happened to them because they refused to meet it.
The Outpaced: See simulation · Historical cases
A company spots the shift coming and tries to respond, hiring consultants, launching pilots, and building innovation labs. The pilots work on a small scale and stall before reaching the core. Nobody acted in bad faith; the organization simply couldn’t learn as fast as the market moved.
Situation: Moderate environmental melt plus active chosen melt, paired with too little capacity (L) or trust (R0) to match the pace of change.
Dynamics: Engagement produces real growth, just slower than μenv, while occasional overflow adds decay. Every cycle, S̄ pulls a little farther ahead.
Outcome: Competitive collapse despite sincere effort, because capability didn’t grow fast enough to catch the market.
Internal Collapse Archetypes
These organizations fail because trust collapses: the team breaks apart even when the business model still had life in it.
Management Theater: See simulation · Historical cases
The calendar overflows with Strategy Reviews, Alignment Sessions, and Culture Conversations. Decks shine and facilitators run tight agendas, yet nobody believes a word of it because everyone knows real decisions happen in side DMs and executive backchannels. Stopping the ceremonies would admit the gap, so everyone shows up, recites the expected lines, and leaves a little more cynical each time.
Situation: High ritual capacity (L) sitting on thin trust (R0): elaborate meetings without the goodwill to make them honest.
Dynamics: A large Theater = max (0, L ⋅ C − R) drives decay via κ ⋅ Theater/β, draining trust directly. As R drops, the gap widens and each hollow meeting hurts more than the last.
Outcome: Rapid trust collapse, accelerated by the very meetings meant to build alignment.
The Overwhelmed: See simulation · Historical cases
Hypergrowth arrives right on cue. Headcount doubles every quarter, the product gets rebuilt under live customers, and the competitive map shifts every week. Nobody has time to document, onboard, or finish digesting the last pivot before the next one lands. Good people burn out and leave, taking institutional memory with them. Founders know the pace is brutal and also know that slowing down in their market might be fatal.
Situation: Very high melt (external, chosen, or both), far beyond current capacity.
Dynamics: Persistent Overflow = max (0, μ − Ω) triggers quadratic decay (Overflow2 ⋅ τ), burning trust faster than good intentions can replenish it.
Outcome: Rapid internal collapse unless the firm can cut melt, build capacity (L) far faster, or survive long enough for pressure to ease.
Oligarchic Decay: See simulation · Historical cases
A sharp founding team builds the culture, shapes the rituals, and sets the standard, and twenty years later the exact same people still hold every chair. Meetings turn into performances for an audience of one, ideas get filtered through “what will the founders think,” and strong newcomers spot the ceiling and leave. The team has turned into a royal court. By the time the problem is obvious, the incumbents genuinely believe their staying in charge is what keeps the company safe.
Situation: Very low rotation (ρ) paired with substantial ritual capacity.
Dynamics: Stewardship integrity C decays as (1 − δ)t, shrinking effective capacity Ω even while L and R look unchanged. Overflow rises as captured forms stop tolerating real challenge.
Outcome: Internal collapse through entrenched leadership: Michels’s iron law in motion, curable only by real rotation.
The Death Spiral: See simulation · Historical cases
It starts with one rough quarter. A key engineer leaves, budgets tighten, the practices that held people together get cut, politics fills the gap, burnout climbs, and more people leave. Falling trust shrinks capacity, shrinking capacity raises overflow, overflow speeds up decay, and decay burns whatever trust is left. No single variable looked fatal on its own, yet every feedback loop now points down, and by the time leadership sees it clearly, the fix requires more trust than the company has left.
Situation: Compounding weaknesses: high melt, thin capacity, low beauty, and some theater.
Dynamics: Decay beats growth every cycle as shrinking R and shrinking Ω feed each other.
Outcome: Rapid collapse, the default slide for under-resourced organizations hit by disruption without real ritual infrastructure.
Appendix A: Minimum Viable Epimetabolic Program
The full Dionysus Program reaches across scales, yet a team can start with six small practices that keep the core loop intact: critique → dissolution → reconstitution → renewal. Everything else in the book elaborates on this core.
Appendix A covers the minimum Ritual Time install: how a group admits error, processes loss, and updates its structure. Appendix B covers the companion Run Time coherence install: doctrine packets, ownership, context checksums, agent permissions, contradiction ledgers, WIP limits, decision memory, and doctrine updates.
The test is simple: if this minimum install doesn’t make it faster and cheaper for your team to admit a mistake, change course in public, and actually behave differently afterward, it isn’t raising your epimetabolic rate yet. Adjust or strip away forms until the loop works.
I. Name the Mode
Start by making the mode switch audible.
In ordinary operations, you are in Run Time: people answer for forecasts, decisions, and outcomes, and critique serves execution.
When you step into a session meant to challenge assumptions or face a loss, say it out loud: “We are in Ritual Time,” and state when it ends. Until the clock closes, output scoring pauses and everyone answers to the room: the no-blame covenant, honest reasoning, and active participation.
When time is up, switch back explicitly: “Ritual Time is over; we are back in Run Time.” That call marks the border between the two scorecards: how honestly we held the rite, and how reliably we execute what came out of it.
II. The Weekly Crossing
Hold one short Crossing every week where an object (never a person) stands trial:
- Declare Ritual Time and restate the covenant: “No person is the problem; the problem is the problem.”
- Pick one anti-scapegoat: a roadmap, charter, metric, policy, or design. All criticism goes there.
- Name the Owner (highest stake in the object, welcoming hard feedback with warmth and grace) and the Host (guarding the room’s pace, tone, and safety).
- Open with a small aesthetic piece (a diagram, story, or demo) that shows what is at stake.
- Red-team the object under rules: anyone may bring a rival explanation and test plan, the builder speaks last, and retaliation is off-limits. The Host steps in if candor turns into mockery or personal attack, and slows or pauses the session if care breaks down.
- Run a hard-to-vary test: write down the facts the proposal explains, the parts that can’t move without breaking that fit, and one risky prediction to score later.
- Close with binding speech: “We commit to X until Y.” Name who accepted responsibility for carrying it out, and post it where everyone can see it.
Skin-in-the-game is non-negotiable: the Owner sits in the room and owns the verdict. Hosting can rotate; accountability cannot. One person can cover both roles if they can take tough criticism while tending the room. Rotate facilitation among active operators so nobody turns into a permanent ritual manager.
III. Tragic Postmortems
Once a month for a team, or once a quarter for a company, pick one consequential miss and narrate it as tragedy rather than a whodunit or PR spin:
- Hamartia: “Our decisive mistake was…” (an internal error, not bad luck).
- Peripeteia: “The turning point was…” (the event that broke our assumption).
- Anagnorisis: “We learned about ourselves that…” (a habit in what we notice, choose, or reward).
- Act: “Therefore we are changing X…” (rename a role, flip a rule, add or kill a ritual, replace a metric).
Run it in Ritual Time, then close by naming the concrete change, where it lives in Run Time, and who owns seeing it through. Nobody gets humiliated; the group faces its own pattern and changes structure.
IV. Protect the Cooling Interval
Never march an exhausted team straight from a brutal stretch of Run Time into a Crossing unless immediate survival demands it. Tired people get defensive, cut corners in thinking, and reach for scapegoats. After hard launches, losses, or long conflicts, cool down first: sleep, feed people, drop scorekeeping, walk outside, and give everyone margin before reopening the debate.
If public Ritual Time isn’t safe yet, don’t force a Crossing. Start privately: put the broken promise, role, or expectation on trial instead of yourself, keep one honest witness (a journal, trusted friend, or private note), and bind one small action. Don’t call that renewal yet; renewal begins when the truth can come back into public view.
V. Eat Your Decay
Make cleanup visible and useful:
- Keep a Scrap Heap Library: Put dead code, retired policies, rejected designs, and dropped rituals in a shared archive with a one-line note on the assumption that failed or the test that settled it. Have new hires read it first.
- Hold short deprecation ceremonies: When something people cared about ends, name it, thank it for what it did, state plainly why it is ending, and make clear the old rule is retired.
- Set a sunset budget: Reserve a small slice of every cycle for deleting, unshipping, unbundling, and simplifying.
VI. A Small Fractal Calendar
Put the loop on a recurring calendar so the same verbs work at every scale:
- Daily (personal): One line of anagnorisis (“Today I realized I was wrong about X; therefore I will Y”), plus one small action to match.
- Weekly (team): One Crossing with a named anti-scapegoat, aesthetic opening, hard-to-vary test, and binding close.
- Quarterly (organization): A modest Great Dissolution where a major strategy, pricing model, or review process stands trial with at least one outside critic, ending in public re-charters and retirements.
At civic or multi-team scale, add an annual Rite of Redress where policies stand trial before the people they affect. Early runs can be rough; the point is naming them and running them. Tag every block as Run Time or Ritual Time and say the mode out loud. Frequent small fixes head off rare, ugly breaks.
One final practice sits underneath the six above: choose your myths carefully.
The six practices above belong to the knowledge layer. If they stop raising epimetabolic rate, put them through a Crossing and replace them. Knowledge fails gracefully: an assumption gets refuted, you retire it cleanly, and you move on.
Myth fails catastrophically. A myth doesn’t update bit by bit when reality pushes back; it absorbs stress inside its own story. That durability is its strength, and also its danger. When the gap between what a myth promises and what people live every day grows too wide, belief doesn’t bend; it drains away privately while the forms keep running, until decades of silent doubt collapse into the open in months.
Before placing anything in the myth layer, test it with three questions:
- Does it describe how to act, or claim what is true? A myth claiming factual truth is just an unchallengeable belief waiting to collide with reality. Durable myths describe posture and conduct (good authority, renewal, facing error), not facts about the market.
- Does it hold up in failure as well as success? The Cincinnatus story still works after a bad quarter; the myth of the invincible team breaks on the first loss.
- Will it still orient people in completely different circumstances? A story tied to one product, technology, or market moment belongs in doctrine, not myth.
This program’s own commitment was chosen to clear all three bars:
We commit to discovering and correcting error, holding no explanation or practice exempt, and sustaining the conditions for doing so.
It names how to act, stays useful when explanations fail, and travels cleanly as tools and people change.
Together, these six practices give you a working Dionysus Program: name the mode, aim critique at objects, examine misses honestly, cool down before heat, salvage what you retire, and repeat on a calendar. After six months, ask whether your group changes its mind in public faster and more honestly than before. If not, cut or reshape practices until they help. If stewardship has turned into a permanent career, fix that before adding another ritual.
Appendix B: Minimum Viable Coherence Program
Appendix A helps a group turn error into better structure. Appendix B helps the same group keep distributed agency coherent while the current doctrine still holds.
You don’t need a reorg to start, just enough living doctrine, clear ownership, bounded permissions, feedback, and cleanup to keep new agency pulling in one direction.
I. Publish a Doctrine Packet
Every team needs a short, current doctrine packet pairing machine-ready specs with a human handle:
- Current diagnosis and guiding policy.
- Explicit tradeoffs and anti-goals.
- Responsibilities, decision rights, and handoff rules.
- Instructions, evals, and examples of good and bad calls.
- A plain-spoken handle for the tradeoff an Actor can say in one breath, paired with a short story of an honorable miss, when someone followed the rule, took a real loss, and had leadership’s backing.
- Stop and escalation rules.
- Known contradictions.
- Version history and update owner.
Keep the wording short enough to survive paraphrase: an Actor should be able to explain a call to an upset customer with the packet closed. Actors can claim duties and arrange handoffs inside these rules, while doctrine names who guarantees coverage for obligations no workflow yet handles.
II. Build a Doctrine-to-Agent Interface
Every serious agentic workflow should answer nine questions up front:
- Which doctrine version is it running on?
- Who owns that doctrine?
- Which Actors have accepted responsibility for execution and consequences?
- What can it do without human review?
- What must it escalate?
- What is its blast radius?
- How is it evaluated?
- Which test case checks the exact tradeoff in the Actor’s handle, giving the agent the raw facts without the answer and comparing its call against the packet?
- How does real-world feedback get back to doctrine?
If you can’t answer those, you haven’t built bounded agency, just private judgment wired to faster tools.
III. Run a Weekly Context Checksum
Ask human operators and machine agents the same five questions separately:
- What are we trying to do?
- Why now?
- What are we refusing?
- What would change our mind?
- What local win would be globally wrong?
Divergence is context debt. Do not treat it as a communication problem until you know whether the doctrine is stale, ambiguous, politically contested, or simply unread.
IV. Maintain a Contradiction Ledger
Keep a visible log of unresolved clashes between:
- Strategy and incentives.
- Customer reality and product roadmap.
- Doctrine and actual agent behavior.
- Public promises and operating capacity.
- Required duties and accepted ownership.
- Metrics and what people see on the ground.
- Auteur intent and Actor feedback.
This isn’t a complaint box; it is an open list of tensions the firm hasn’t resolved yet. Some need a quick Run Time clarification; others belong in Ritual Time because the underlying map is breaking.
V. Install Agency WIP Limits
Cap active agentic initiatives the way a factory caps work in process. Don’t let every team spin up unlimited automations, campaigns, docs, and workflows just because generation is cheap. When coherence is the bottleneck, extra upstream agency turns into inventory before the bottleneck, waiting, going stale, and burying reviewers.
VI. Add a Permission Ladder for Agents
Use a simple ladder until your domain needs finer steps:
- Level 0: Suggest only.
- Level 1: Draft with human approval.
- Level 2: Execute reversible internal actions.
- Level 3: Execute reversible external actions with monitoring.
- Level 4: Execute irreversible or customer-facing actions only under explicit doctrine and escalation rules.
- Level 5: Autonomous high-stakes action, allowed only where doctrine, evals, and Actor feedback are proven.
Let doctrine maturity, eval quality, reversibility, blast radius, and Actor feedback pick the level, never enthusiasm. Permission defines what an agent may do; it does not name who owns the outcome.
VII. Create Decision Memory
For every major call, record:
- The decision made and who owns it.
- The premises it rests on.
- Alternatives rejected and tradeoffs accepted.
- What evidence would reverse it.
- Which doctrine, Actors, agents, and workflows it affects.
Decision memory stops new hires and agents from reopening settled calls without knowing why they were made.
VIII. Create a Deletion Cadence
Every month or quarter, clear out:
- Stale prompts and abandoned agent workflows.
- Old automations and inactive dashboards.
- Zombie initiatives and duplicate docs.
- Obsolete policies and misleading metrics.
As creation gets cheap, scheduled deletion has to sit right next to it on the calendar. Before shutting down any workflow, check which obligations survive and name who accepts them.
IX. Establish Actor Responsibility and Feedback
Start with every obligation the company must fulfill, including ones with no workflow attached, and check:
- Which Actors explicitly accepted each duty, and where several could act, how is ownership established de jure?
- Do they have authority to step in, capacity to follow through, and visibility into actual results?
- How do duties get claimed, handed off, and closed without leaving gaps?
- Who resolves uncovered duties or overlapping claims?
- Can Actors stop, redirect, or escalate broken execution immediately?
- How do real-world contradictions get back to Auteurs and doctrine stewards?
Actors can delegate execution, monitoring, and coordination while keeping ownership. They don’t have to approve every move; they do have to ensure the work lands and respond when it fails.
X. Ritualize Doctrine Update
When reality breaks your doctrine, don’t just patch a prompt and move on. Run Ritual Time, and close reconstitution with four questions:
- What died? Name the assumption and the evidence that broke it. Credit why it made sense yesterday, and protect the people who acted on it in good faith.
- What survived? Name the promise people can still count on, what part of our identity the old rule served, and how we will honor it now.
- What is the new functional rule? State the tradeoff, name the update owner, log it in decision memory, update promises, permissions, evals, and agent interfaces, retire broken workflows, and name who owns each changed duty until handoffs close.
- Is the new truth warm enough to eat? Run the Form Check. Give an Actor an unfamiliar case with the packet closed and run the same case against the agent spec. If the two make different promises, find out why, fix whichever rendering lost the intent, and test a fresh case before closing Ritual Time.
Ritual Time that never updates Run Time is theater. Run Time that can’t absorb updates is drift.
This entire minimum install has one job: widen your span of coherence so more human and machine agency can act independently while staying one organization.
Decoder Ring
Cold Doctrine. Sound instructions written in a form people can’t draw on when an old habit wants to settle a tough call.
Doctrinal Coherence vs. Effective Coherence. Doctrinal coherence asks whether the strategy and rules fit together on paper. Effective coherence asks how much of that intent actually survives into distributed decisions under pressure.
Dual-Rendering. Expressing one intent twice (as testable instructions for machine Agents, and as a memorable phrase, story, or habit for human Actors) while preserving the exact same tradeoff in both.
Appendix C: Archetypes in History
This appendix reads real historical cases through the archetypes introduced above. The comparisons are interpretive, meant to sharpen how you look at trust, practices, and adaptation, and do not prove that the Epimetabolic Equation predicts what any organization will do.
Thriving Archetypes
The Dionysian Ideal
Pixar’s Braintrust (1995–Present)
Pixar’s Braintrust is one of the clearest real-world versions of the Dionysian Ideal: a recurring review built to tear films apart without tearing apart the people making them.
Melt: Feature animation runs hot by nature. Every movie represents years of work and a $200 million+ bet that has to land both artistically and at the box office. Directors routinely go through “the death of the story” several times per film, ripping out plots, characters, and core premises and rebuilding from scratch.
Ritual Capacity: Every few months during production, the director screens the rough cut for a room of fellow directors, writers, and creative leads who give blunt feedback. The Braintrust has one defining constraint: it has no power to mandate changes. It diagnoses problems and offers ideas, leaving final decisions with the director.
Trust: Pixar spent decades earning the goodwill that makes those rooms safe. As Ed Catmull put it, “Candor isn’t cruel. It does not destroy. On the contrary, any successful feedback system is built on empathy.” Everyone in the room has survived bruised productions of their own, so blunt notes land as help from peers rather than ambushes from above.
The film, not the filmmaker, is the anti-scapegoat on trial. Directors come out of tough sessions feeling backed rather than attacked because the trust underneath holds the heat.
Lesson: Strong critique works when the relationships match the intensity of the room. Copying the Braintrust agenda without Pixar’s trust produces defensive meetings, not better movies.
Bell Labs (1925–1970s)
During its peak decades from the 1920s through the 1970s, Bell Labs produced the transistor, information theory, the laser, Unix, and C inside a culture that paired sharp intellectual combat with deep collegiality.
Melt: Researchers worked on open-ended problems that took years, knowing many lines of work would hit dead ends. Fast-moving physics and math supplied steady outside pressure, and the lab added chosen melt by funding speculative research most companies wouldn’t touch.
Ritual Capacity: Bell Labs built blunt debate directly into daily work. In “chalk talks,” a researcher laid out an idea at the blackboard while colleagues interrupted, poked holes, and pushed back. Claude Shannon recalled having his work “torn apart,” yet the ground rules stayed clear: hit the idea hard, leave the person alone, and assume the speaker thought carefully before stepping up to the board.
Trust: The lab hired strong thinkers and threw them together constantly, eating in the same cafeterias, sitting in on each other’s seminars, and bumping into colleagues down the famously long hallways built to spark chance conversations across fields.
Bell Labs also kept a version of the Cincinnatus Rule alive: pure researchers rotated onto practical phone-network problems, keeping theory grounded in real consequences instead of letting an ivory-tower clique form.
Lesson: Fierce criticism scales in basic research when teammates trust each other’s motives enough to invite it. People at Bell Labs wanted their weak ideas killed early so stronger ones could take their place.
NUMMI (1984–2010)
New United Motor Manufacturing, Inc. (NUMMI), the GM-Toyota joint venture in Fremont, California, turned one of GM’s worst auto plants into one of its best using mostly the same workers.
Melt: Before NUMMI, the Fremont plant was notorious for absenteeism, substance abuse, sabotage, and open war between labor and management. Japanese automakers were hammering Detroit, while Toyota faced a tough test of its own: could its production system work with an American union workforce?
Ritual Capacity: Toyota introduced kaizen (continuous improvement), the andon cord (giving any line worker authority to halt production to fix a defect), daily team huddles, and quality circles. Pulling the cord sent a clear public signal: surface problems immediately instead of burying them down the line.
Trust: Toyota backed those forms with visible trust-building. It flew American workers to Japan to see the system firsthand, put managers in the same cafeteria as line workers, and replaced top-down policing with real backing when workers flagged defects. People who had once sabotaged cars became proud defenders of build quality.
The turnaround showed that the old dysfunction lived in the system, not the workers. When daily practices matched genuine respect on the floor, the same workforce climbed from the bottom of GM’s quality charts to the top.
Lesson: Even badly broken cultures can turn around when form and trust grow together. Importing Toyota’s tools without investing in worker dignity would have failed; NUMMI built both side by side.
Synthesis
Pixar, Bell Labs, and NUMMI each paired tough criticism with relationships strong enough to carry it, whether aimed at a rough cut, a blackboard proof, or an assembly line. Across all three, the habits and the trust grew together. In the model’s terms, enough capacity keeps overflow down so honest corrections add to trust instead of draining it.
The High Performer
3M Under Six Sigma (2001–2005)
Under CEO James McNerney, 3M showed how tight operational discipline can improve every quarterly metric while quietly starving the habits that produced breakthroughs.
Melt: 3M had built its reputation (Post-it Notes, Scotch Tape, thousands of patents) around chosen melt. Its famous “15% rule” let engineers spend part of their week on self-directed bets, while diversified markets kept outside pressure moderate.
Ritual Capacity: Coming from GE, McNerney rolled out Six Sigma across the company. The reviews and measurement systems weren’t fake; they worked as advertised, cutting defects, trimming costs, and lifting margins.
Trust: Employees respected McNerney’s track record, so the new discipline didn’t trigger open revolt. Instead, the Six Sigma cadence gradually crowded out the older innovation habits. Unstructured 15% time got harder to defend on a scorecard, and “bootleg” side projects, historically the source of 3M’s biggest hits, stopped looking legitimate.
Over time, the R&D pipeline thinned and new product launches fell. After McNerney left for Boeing, 3M loosened parts of Six Sigma to bring experimentation back.
Lesson: Running well by yesterday’s scorecard can turn into a trap. Measurement rituals deliver what they measure (margins and predictability) while slowly choking off the messier work that creates future breakthroughs.
NASA’s Space Shuttle Program (1981–2011)
NASA’s Space Shuttle program operated with serious engineering rigor and competent teams, yet still drifted into normalizing known safety risks.
Melt: Tight budgets, political pressure to keep launch schedules moving, and aging hardware created steady outside stress. Because the Shuttle was treated as an operational workhorse rather than an experimental craft, the focus stayed on repeatable execution.
Ritual Capacity: NASA ran detailed flight readiness reviews, safety checks, and engineering sign-offs that caught real problems on flight after flight.
Trust: Engineers respected one another’s skill, and managers and technical staff worked together smoothly most of the time.
Yet both disasters grew out of warning signs the system had already seen. O-ring erosion showed up on earlier flights before Challenger; foam strikes happened repeatedly before Columbia. Engineers flagged the risks, managers weighed schedule pressures and past survival, and the reviews cleared the launches anyway, not out of malice, but through what sociologist Diane Vaughan called the normalization of deviance inside an otherwise competent organization.
Lesson: Competence creates its own blind spots. When routine reviews handle ninety-nine normal problems smoothly, a team can talk itself into treating the hundredth, an abnormal and fatal risk, as routine too.
Pitney Bowes (1990s–2010s)
Pitney Bowes, long the leader in postage meters and mailing gear, ran a disciplined operation even as the market under its feet slowly shrank.
Melt: Email and digital billing ate away at physical mail year after year. Everyone could see the trend coming decades ahead, yet each individual quarter fell slowly enough that near-term earnings always outweighed painful reinvention.
Ritual Capacity: Pitney Bowes executed its core business well: solid logistics, reliable equipment service, and tight customer management.
Trust: Staff stayed professional, leadership stayed competent, and internal politics wasn’t the culprit.
The company did try to pivot, buying software firms, adding digital offerings, and reframing around “commerce solutions.” Still, the legacy mail business threw off the cash, so it kept pulling budget and executive attention back toward itself while the total market kept shrinking.
Lesson: In a slowly shrinking market, the practices that keep today’s profit engine humming quietly crowd out the different habits needed to build its replacement.
Synthesis
3M, NASA, and Pitney Bowes each ran well on conventional measures while missing something outside those measures: experimentation at 3M, non-routine safety signals at NASA, and a shrinking market at Pitney Bowes. Reliable execution in Run Time doesn’t guarantee an organization is ready for a different kind of problem.
The Virtuous Cycle
Lockheed’s Skunk Works (1943–1975)
Lockheed’s Advanced Development Programs division, better known as the Skunk Works, started small with tight deadlines and built itself into a powerhouse by letting delivered results compound into greater trust and autonomy.
Melt: The division was born in a wartime sprint: design and build the XP-80 jet fighter in 143 days. The Cold War kept the bar just as high, demanding aircraft (the U-2, SR-71 Blackbird, and F-117 stealth fighter) that conventional aerospace wisdom treated as impossible.
Ritual Capacity: Founder Kelly Johnson wrote down his “14 Rules” to keep the container tight: small teams, direct access to the customer, minimal paperwork, engineers sitting beside fabricators, and fast prototyping.
Trust: Johnson hand-picked a lean team and insisted on wide freedom from corporate red tape, matched by total accountability for results. Every “impossible” plane delivered on schedule earned more trust from Pentagon sponsors, which bought even more freedom for the next project.
Each win raised the team’s standing and capability for the next round, while the work itself, building aircraft nobody else could, gave the group fierce pride without needing slogans.
Lesson: Early wins compound fast when a small team gets real autonomy paired with clear consequences: deliver hard work, earn trust, take on harder problems, repeat.
The Manhattan Project’s Los Alamos Laboratory (1943–1945)
In less than three years, Los Alamos turned a crowd of strong-willed physicists into one of the most effective technical organizations ever assembled.
Melt: Nuclear physics was barely two decades old, key reactions were poorly understood, and wartime pressure was existential, driven by real fear that Nazi Germany might finish a bomb first.
Ritual Capacity: J. Robert Oppenheimer pushed back on standard military compartmentalization so scientists could see the whole problem. He instituted weekly lab-wide colloquia alongside tight division reviews, letting breakthroughs in one group unblock stalled work in another.
Trust: The scientists started with professional respect rather than deep friendship. Oppenheimer knit them together by walking the mesa, learning everyone’s names and bottlenecks, and keeping the shared mission front and center inside an isolated town.
Problems surfaced at weekly talks, crossed specialties, hit monthly milestones, and built trust with every hurdle cleared.
Lesson: When a mission is unmistakable and leaders protect open problem-sharing across specialties, professional respect can compound into deep group trust in remarkably little time.
The PayPal Mafia (1999–2002)
PayPal’s early team survived years of near-death crises together and forged working habits strong enough to outlast the company itself.
Melt: Massive fraud rings nearly bankrupted the business, eBay and banks fought back, the dot-com bubble burst, and regulators closed in, all while the team pivoted through multiple business models on the fly.
Ritual Capacity: During peak crises, daily all-hands kept everyone working off the same facts. Hiring favored sharp argument over pedigree, and debates were famously blunt while staying focused on ideas rather than personal vendettas.
Trust: Surviving fraud wars, financing crunches, and brutal competition side by side forged durable ties. After eBay bought PayPal in 2002, alumni including Reid Hoffman, Peter Thiel, Elon Musk, and Max Levchin went on to start or back LinkedIn, Tesla, SpaceX, Palantir, YouTube, and Yelp, carrying the same high-trust, high-candor habits with them.
Lesson: Surviving real pressure together builds capability that outlives any single org chart, turning a scrappy team into a network that knows how to build again.
Synthesis
Skunk Works, Los Alamos, and PayPal all started with a modest base of trust (professional respect, clear stakes, or prior ties) and grew it through joint delivery under pressure. In the model, each successful turn deposits more trust than the strain burns, letting the group handle heavier problems the next time around.
Moderate Growth
Badger Meter (1905–Present)
Milwaukee’s Badger Meter has spent more than a century building water meters and flow sensors: quiet, durable execution in an unglamorous market.
Melt: Water metering evolves gradually, municipal buyers move carefully, and competitive shifts (mechanical to electronic to smart meters) have arrived slowly enough to digest without panic.
Ritual Capacity: Standard governance (board reviews, quarterly planning, steady R&D) works reliably without flashy ceremonies.
Trust: Low manufacturing turnover, orderly leadership handoffs, and multi-decade municipal relationships give the business a steady floor.
Revenue and earnings have crept upward across generations while the company adapted calmly to each new wave of metering tech.
Lesson: Moderate Growth isn’t settling; surviving over a century of technological change without drama is a real achievement.
Würth Group (1945–Present)
Germany’s family-owned Würth Group grew from a two-person screw wholesaler into a €20 billion global supplier of fasteners and assembly tools with 85,000 employees.
Melt: Construction, automotive, and industrial buyers swing with economic cycles, yet the core need for fasteners stays steady and durable.
Ritual Capacity: Logistics, sales training, and customer service run on practical, workmanlike routines improved step by step rather than through grand reinventions.
Trust: Continued family control lets leaders make long-term calls without quarterly Wall Street pressure, paired with German labor norms that encourage mutual commitment.
Over nearly eight decades, Würth compounded quietly, a little bigger each year and much bigger each decade, without dramatic pivots.
Lesson: Patient ownership lets a company compound steadily instead of oscillating between hypergrowth gambles and frantic turnarounds.
Old National Bank (1834–Present)
Indiana’s oldest bank has operated for nearly two centuries by staying regional and avoiding flashy risks.
Melt: Banking gets hit by periodic shocks: nineteenth-century panics, the Great Depression, and 2008. Old National weathered every one by holding strong capital, diversifying loans, and steering clear of exotic products.
Ritual Capacity: Regulated banking runs on steady compliance, credit committees, audits, and risk reviews, which the bank handles reliably.
Trust: Generations of local families and businesses have banked there, backed by steady internal retention. It isn’t the flashiest employer, and it doesn’t try to be.
Lesson: In a volatile industry, boring discipline looks dull in boom years and priceless in busts, keeping the institution alive when flashier rivals disappear.
Synthesis
Badger Meter, Würth, and Old National show three paths to long-term durability: steady product updates, patient family ownership, and conservative risk management. Each matches the model’s steady-state case, where trust and operating capacity stay comfortably ahead of the shocks the business takes on.
Edge Case Archetypes
The Fragile Survivor
Apple in 1997
When Steve Jobs returned to Apple in 1997, the company was weeks from running out of runway, kept alive not by institutional resilience, but by a narrow sequence of breaks that easily could have gone the other way.
Melt: Windows and Intel had locked up the PC market. Apple’s share had fallen below 4%, its product lineup was bloated and losing money, and even insiders assumed the company was done.
Ritual Capacity: Years under John Sculley and Gil Amelio had piled up process without direction. Rival product lines fought over internal resources, and leadership struggled to make hard cuts stick.
Trust: Layoffs and departures had worn the workforce down, while developers, customers, and investors openly questioned whether Apple would survive the year.
Recovery hinged on an unlikely chain: Jobs came back, Microsoft put in $150 million (announced by Bill Gates to boos at Macworld), the iMac hit, and the iPod, iTunes, and iPhone followed. Change any one link (no Jobs, no Microsoft cash, a flat iMac launch) and Apple likely went bankrupt.
Lesson: Fragile Survivors can rebound spectacularly, yet their survival hangs on timing and luck rather than built-in margin.
Marvel Comics in 1996–1998
Marvel Entertainment nearly liquidated in the late 1990s before emerging from bankruptcy into the run that built the modern superhero film business.
Melt: The comic-book speculation bubble burst right after Marvel loaded itself with debt to buy trading-card companies and push vertical integration. Revenue fell off a cliff under industry decline and self-inflicted leverage combined.
Ritual Capacity: Editorial teams kept shipping comics, yet corporate governance fell apart. Marvel filed for bankruptcy in late 1996, sparking a bitter fight for control between Carl Icahn and a bondholder group led by Isaac Perlmutter and Avi Arad.
Trust: Creative staff still cared about the work, while corporate factions didn’t trust each other at all. Liquidation looked plausible more than once.
Perlmutter’s group emerged in control in 1998, licensing characters to studios before launching Marvel Studios, turning near-death into the biggest franchise in film history. A different bankruptcy judge, an Icahn win, or one flopped deal would have ended the story right there.
Lesson: Strong creative assets can survive a corporate wreck if the core IP and craft stay intact, though getting through depends on a handful of people making the right calls at the exact right moment.
Starbucks in 2008
When Howard Schultz returned as CEO in 2008, Starbucks hadn’t collapsed, yet rapid over-expansion had hollowed out the store experience just as recession hit.
Melt: Aggressive store openings diluted the brand, same-store sales slipped, McDonald’s and Dunkin’ attacked on price, and the 2008 downturn squeezed discretionary spending.
Ritual Capacity: Store operations and supply chains still worked, though breakneck expansion had cut corners on training and coffee quality. Schultz said publicly that Starbucks had “lost its soul.”
Trust: Damage was real, not total. Long-tenured employees (called partners) still cared about the original standard, and customers hadn’t completely walked away.
Schultz closed U.S. stores for a day of retraining, slowed expansion, shut weak locations, and refocused on coffee quality. A hired outsider making those same painful cuts would have faced fierce pushback; Schultz had founder credibility nobody else carried.
Lesson: Returning founders can pull Fragile Survivors back from the brink precisely because they carry personal authority a company cannot easily replace, which is also what makes the recovery fragile.
Synthesis
Apple, Marvel, and Starbucks all pulled through via narrow combinations of timing, capital, and personal credibility. The model captures a related sensitivity when survival depends on when stewardship resets happen, though history can’t tell us how many alternate worlds ended in bankruptcy.
The Gambler
SpaceX (2008)
In September 2008, SpaceX bet the entire company on a fourth Falcon 1 launch after three straight failures, and walked away on the path to reshaping the space industry.
Melt: SpaceX chose extreme risk: build orbital rockets for a fraction of legacy prices, a goal that had sunk every prior private effort. Three launches had blown up or missed orbit, cash remained for one last shot, and the 2008 financial crisis had frozen outside capital.
Ritual Capacity: Engineering discipline was fierce: fast failure analysis, tight iteration loops, and relentless testing. What didn’t exist was a fallback plan for a fourth failure, because there wasn’t money left for one.
Trust: The team still believed in the mission and in Elon Musk’s technical judgment, even under brutal strain while Musk was simultaneously keeping Tesla from going under.
Flight 4 reached orbit in September 2008. Months later NASA awarded a major cargo contract, opening the door to Falcon 9, Dragon, Starlink, and Starship. One more faulty sensor or software bug, and SpaceX would have shut down that autumn.
Lesson: All-in bets can unlock outcomes cautious plans never reach, yet survival depended on one launch going right when the alternative was zero.
FedEx’s Las Vegas Origin Story (1973)
FedEx’s most famous early story, founder Fred Smith taking the company’s last cash to a Las Vegas blackjack table to cover payroll, captures both the reality and the folklore of bet-everything startups.
Melt: Building an overnight air-delivery network demanded huge upfront spending on planes and hubs before revenue could catch up. Then the 1973 oil shock spiked jet fuel right as FedEx tried to scale.
Ritual Capacity: The hub-and-spoke system, sorting routines, and tracking were still being invented on the fly before the business model was proven.
Trust: The early team stayed loyal through repeated cash crunches that put FedEx days from shutting down in 1973 and 1974.
Smith confirmed flying to Vegas with the company’s last $5,000 and winning $27,000, enough to buy a few more days until last-minute venture money closed. FedEx went public in 1978 and built an industry, after surviving several coin-flip moments where slightly worse luck meant closure.
Lesson: Gambler legends inspire bold bets while hiding the graveyard of founders who made identical wagers and lost. Survivors tell their stories; failures disappear.
Marvel Studios’ MCU Bet (2008)
With Spider-Man and the X-Men already licensed to rival studios, Marvel bet its remaining character rights as loan collateral to self-finance Iron Man and launch an interconnected film universe.
Melt: Marvel was a modest post-bankruptcy publisher left mostly with characters Hollywood viewed as second-tier (Iron Man, Thor, Captain America), and had never produced a major studio movie on its own.
Ritual Capacity: Kevin Feige had a sharp vision for linked storytelling, yet the studio’s production, creative, and marketing machinery had to be built from scratch.
Trust: Core creatives backed the bet; bankers lent the money only because Marvel put up its crown-jewel character rights as collateral. If Iron Man bombed, the lenders took the characters.
Iron Man became a smash hit, Disney bought Marvel for $4 billion in 2009, and the MCU became the highest-grossing franchise in cinema history. If casting or execution had missed on film one, Marvel likely faced a second bankruptcy.
Lesson: Big bets can build value conservative paths can’t touch, so long as you weigh the upside squarely against the irreplaceable assets sitting on the table.
Synthesis
SpaceX, FedEx, and Marvel Studios all staked survival on concentrated risks with little room for another miss. Success makes bold bets look obvious in hindsight; the honest question is always what happens if the coin lands the other way.
Pyrrhic Archetypes
The Pyrrhic Leader
Uber Under Travis Kalanick (2010–2017)
Under Travis Kalanick, Uber won market share at ferocious speed while burning through internal trust until the company had to remove its own founder.
Melt: Uber chose confrontation on every front, entering cities aggressively, clashing with regulators and taxi lobbies, and treating regulatory resistance as an obstacle to push past.
Ritual Capacity: Operational playbooks were razor-sharp: surge pricing, driver onboarding, and city launches worked like clockwork and beat rivals city after city.
Trust: Internal values like “always be hustlin’” and “principled confrontation” rewarded top producers regardless of how they treated colleagues, while harassment complaints went unaddressed.
Beauty: Almost none. Everything ran on raw competitive metrics with little care, warmth, or honest space to process loss. Even winning didn’t rebuild trust.
By 2017, Uber was the most valuable startup in the world, when Susan Fowler’s public account of harassment brought years of rot into the open, pushing the board to force Kalanick out.
Lesson: You can dominate a market for years while emptying your trust account. In the equation, when beauty (β) nears zero, even strong growth barely adds trust while decay keeps draining it.
Amazon’s Warehouse Operations
Amazon’s fulfillment network delivers speed and scale no rival matches, paired with high warehouse turnover and recurring public criticism of working conditions.
Melt: Same-day delivery, holiday surges, and endless new product categories create huge operational complexity every week.
Ritual Capacity: Detailed procedures govern every step (picking algorithms, packing standards, routing, and real-time performance tracking), producing unmatched logistics reliability.
Trust: At many facilities, annual worker turnover has topped 100%, alongside elevated injury rates and criticism over pace monitoring. Workers treat the job as temporary and leave when better options appear.
Beauty: Carefully crafted for customers (fast tracking, clean delivery, easy returns), and nearly absent on the warehouse floor, where daily work feels like surveillance and repetition.
Because warehouse workers bear the human cost while executives and customers reap the benefits, the pattern hasn’t broken Amazon’s market lead.
Lesson: A Pyrrhic model can hold steady for a long time when the costs fall on replaceable workers rather than on decision-makers, until labor markets, regulation, or automation shift the bill.
Goldman Sachs Culture
Goldman Sachs has stayed near the top of global finance for decades while enduring recurring public backlash over its hard-edged internal culture.
Melt: Investment banking lives in constant change: shifting markets, volatile deals, new regulations, and global expansion.
Ritual Capacity: Deal execution, risk controls, and client management reflect a century of refinement that rivals struggle to match.
Trust: Respect for sharp execution sits beside intense internal ranking and an “up or out” ladder that pits peers against each other, weakening the open cooperation shared learning needs.
Beauty: Built almost entirely around prestige and winning big deals, with little room for warmth or care when colleagues burn out.
Even after Greg Smith’s 2012 resignation op-ed, “Why I Am Leaving Goldman Sachs,” sparked a wave of bad press about value extraction, the firm weathered the storm and kept most of its practices intact.
Lesson: High-prestige firms can sustain a Pyrrhic culture for decades through self-selection: people who enjoy the fight or want the credential stay, while everyone else leaves early.
Synthesis
Uber, Amazon’s warehouses, and Goldman Sachs show three ways market performance can coexist with heavy human cost: hitting leadership directly at Uber, cycling through high-turnover labor at Amazon, and relying on self-selection at Goldman. Market dashboards don’t tell you what the people producing them are paying.
The Churn Machine
Microsoft Under Ballmer (2000–2014)
During Steve Ballmer’s fourteen years as CEO, Microsoft kept printing cash from Windows and Office while constant reorganizations and internal ranking kept new strategies from taking root.
Melt: Mobile, cloud computing, browsers, and Google search all hit at once, while Microsoft jumped between simultaneous bets across all four.
Ritual Capacity: Planning and review processes were extensive, yet stack ranking, which forced managers to grade teammates against one another, poisoned them by making collaboration risky.
Trust: Engineers avoided strong teams where they might land at the bottom of the curve, and divisions guarded information instead of sharing it.
Ballmer restructured the company repeatedly (2005, 2008, 2012, 2013). Each reorg broke up entrenched fiefdoms and wiped out institutional memory right alongside them. Multi-year bets lost momentum before paying off, letting Microsoft miss mobile, cede search, and arrive late to cloud before recovering under Satya Nadella.
Lesson: Endless rotation stops oligarchy and stops compounding at the same time. Without enough continuity, no hard strategy lives long enough to work.
Yahoo’s CEO Carousel (2007–2012)
Between 2007 and 2012, Yahoo cycled through five leaders (Terry Semel, Jerry Yang, Carol Bartz, interim CEO Ross Levinsohn, and Marissa Mayer), resetting its strategy every time a new name went on the door.
Melt: Google owned search, Facebook was taking social, and Yahoo’s display-ad base was slipping fast.
Ritual Capacity: Day-to-day sites stayed online and ads kept selling, yet long-term planning and cultural rebuilding never survived the next CEO swap.
Trust: Every incoming CEO arrived with a new team and a new multi-year vision, then got judged in months. Employees learned the rational move: wait out the latest initiative until the next leader arrived.
Lesson: Short-horizon CEO churn feeds on itself: strategies fail because they never get enough time, which gets the CEO fired, which resets the clock again, ending in Yahoo’s 2017 sale to Verizon for a fraction of its peak value.
HP’s Restructuring Addiction (2005–2015)
For a decade, Hewlett-Packard treated reorganization less like a transition between stable plans and more like a permanent operating mode.
Melt: Commoditizing PCs, maturing printers, and shifting enterprise tech created real pressure, yet HP’s own nonstop restructuring soon generated more disruption than the market did.
Ritual Capacity: Factories, supply chains, and sales kept humming while executive planning cycles, reporting lines, and priorities got scrambled over and over.
Trust: Each reorg created new winners and losers, teaching staff that reading internal politics mattered more than executing long-term plans.
HP cycled through Carly Fiorina, Mark Hurd, Léo Apotheker, and Meg Whitman while buying Compaq, spinning off Agilent, acquiring EDS, Palm, and (disastrously) Autonomy, and finally splitting into HP Inc. and HP Enterprise, rarely finishing one integration before starting the next.
Lesson: Restructuring can turn addictive because it looks decisive right away while its real costs (lost context and eroded trust) show up later.
Synthesis
Microsoft, Yahoo, and HP show the opposite extreme from entrenched oligarchy: rotating authority and org charts so fast that context and commitments never stick. Healthy stewardship balances rotation with enough continuity to learn.
Decline Archetypes
The Slow Decline
Local Newspapers (2000–2020)
Across two decades, hundreds of American local newspapers shrank so steadily that no single quarter felt like the emergency that justified tearing up the business model.
Melt: Craigslist chipped away at classifieds over years; Google and Facebook absorbed display ads just as gradually. Each quarter slipped a little below the last without delivering one unmistakable cliff.
Ritual Capacity: Newsrooms kept running cleanly (morning pitch meetings, editing desks, daily deadlines) on top of a revenue model that was quietly evaporating.
Trust: Many newsrooms kept strong pride and esprit de corps even as ad revenue drained away, making the building feel healthier than its balance sheet.
Round after round of buyouts and layoffs was framed as a “one-time right-sizing” to reach a stable floor that never arrived. Papers with hundreds of reporters in 2000 were down to dozens, or closed, by 2020.
Lesson: Slow decline is the hardest pattern to interrupt because every individual drop hides inside normal variance until the gap is too wide to cross.
RadioShack (1990s–2017)
RadioShack faded from an electronics staple into bankruptcy over more than twenty years, always holding just enough cash flow to postpone deep reinvention.
Melt: Big-box chains (Best Buy, Circuit City) took share in the 1990s, wireless carriers opened their own stores, and Amazon hit from online; each wave was survivable on its own and fatal together.
Ritual Capacity: Thousands of stores kept running basic retail well, staffed by loyal franchisees and knowledgeable clerks.
Trust: Employees still believed in helping everyday people tinker with electronics, keeping internal morale coherent long after the retail model went stale.
Pivots into cell phones, repairs, and a “The Shack” rebrand never fixed the core squeeze, and RadioShack filed for bankruptcy in 2015 and again in 2017.
Lesson: Gradual decline buys the illusion of time: every year you wait, the gap between what you can do and what the market wants grows wider.
Yahoo (1995–2017)
Beyond its CEO carousel, Yahoo’s twenty-year arc shows how high traffic can hide a steady slide into strategic irrelevance.
Melt: Search went to Google, social went to Facebook, mobile rewrote user habits, and ad tech shifted, yet Yahoo stayed a top-ten website the whole way down.
Ritual Capacity: News, finance, sports, and email kept running reliably and bringing in real ad revenue.
Trust: Despite leadership turmoil, enough operating coherence remained to keep the sites alive, even without clear strategic direction.
Missed turns (passing on buying Google, failing to close Facebook, mishandling Alibaba) each seemed defensible in the moment while slowly emptying the company’s edge.
Lesson: In internet markets, big legacy traffic lets a company look healthy on usage charts long after its competitive advantage has disappeared.
Synthesis
Local newspapers, RadioShack, and Yahoo all kept running functional operations while losing ground year by year. Acceptable quarterly results can hide a widening gap until turning around is no longer realistic.
Competitive Collapse Archetypes
The Sitting Duck
BlackBerry (2007–2013)
BlackBerry dropped from over half of the U.S. smartphone market in 2009 to under 1% by 2013, even while its internal engineering culture stayed capable and respectful.
Melt: When the iPhone arrived in 2007 and Android followed, mobile shifted overnight from physical keyboards and corporate IT to touchscreens and app ecosystems. BlackBerry watched the entire wave roll in and stood put.
Ritual Capacity: Hardware design, manufacturing, and carrier delivery still worked smoothly, just built around secure email for corporate IT buyers rather than consumer software.
Trust: Internal morale and professionalism stayed surprisingly intact. The problem wasn’t infighting; it was blindness to where buyers were moving.
Co-CEOs Jim Balsillie and Mike Lazaridis waved off touchscreen keyboards as inferior, dismissed app stores as unnecessary, and insisted consumers weren’t their market. Every claim made sense inside BlackBerry’s old frame and missed the market completely.
Lesson: Sitting Ducks rarely feel broken from the inside. Standing still gets framed as focus and discipline right up until customers move on.
Kodak (1990s–2012)
Kodak invented the digital camera in its own lab in 1975, studied the coming transition accurately for decades, and still rode film into bankruptcy in 2012.
Melt: Digital photography built slowly over thirty years before outselling film in 2003, giving Kodak more warning than almost any company ever gets.
Ritual Capacity: Film manufacturing, chemical processing, and retail distribution were world-class, yet Kodak never built parallel habits for remaking its core business.
Trust: Film divisions enjoyed strong pride and budgets while digital teams fought for resources and standing. The company trusted its legacy more than its future.
Internal memos from the 1980s and 1990s mapped the digital shift with uncanny accuracy, and Kodak even shipped digital cameras, yet identity and profits stayed tied to “Kodak means film” until film collapsed.
Lesson: Seeing a threat coming isn’t enough when today’s profits make cannibalizing the old business look irrational one quarter at a time.
Toys “R” Us (1998–2017)
Toys “R” Us watched e-commerce grow for two decades without ever building a real online operation of its own.
Melt: Amazon launched in 1995. By 2000, Toys “R” Us outsourced its online store to Amazon, handing Amazon years of toy-category data while stunting its own digital learning until the deal collapsed in 2006.
Ritual Capacity: Physical stores, seasonal staffing, and supply chains kept working reliably while foot traffic steadily drifted online.
Trust: A 2005 leveraged buyout piled on debt that choked off investment, though e-commerce had already been treated as a side project well before the buyout.
Bankruptcy arrived in 2017 and liquidation in 2018. Debt service pulled the trigger; twenty years without real digital capability set the stage.
Lesson: Locally sensible excuses (the Amazon partnership, the buyout debt, “toys are different”) make zero difference to customers who have moved elsewhere.
Synthesis
BlackBerry, Kodak, and Toys “R” Us all stayed competent at their old games while refusing to rebuild for the new one. Healthy routines and high trust won’t save an organization whose map no longer matches the market.
The Outpaced
Nokia Mobile (2007–2013)
Unlike BlackBerry, Nokia saw the smartphone shift clearly, committed real resources, and still couldn’t move fast enough to keep up with Apple and Android.
Melt: Mobile flipped from hardware design, carrier ties, and global manufacturing to software ecosystems and app stores almost overnight.
Ritual Capacity: Nokia had led earlier hardware waves (analog to digital, feature phones to the N95) and ran disciplined hardware engineering, just not modern platform software.
Trust: Consensus-driven culture worked well for steady improvements and slowly for radical pivots, while hardware and software silos slowed decisions without turning toxic.
Nokia poured money into Symbian, built the well-reviewed MeeGo N9 too late, and partnered with Microsoft in 2011 to borrow an OS. By 2014, Microsoft bought the handset division.
Lesson: Being outpaced hurts more than sitting still because nobody ignored the warning. When outside change outruns your learning speed, sincere effort isn’t enough.
GE’s Digital Transformation (2011–2018)
Under Jeff Immelt, General Electric poured billions into becoming a “digital industrial company” and still couldn’t build modern software speed inside a 125-year-old conglomerate.
Melt: Sensors and cloud analytics were reshaping how turbines, jet engines, and medical gear got monitored and serviced, pulling industrial equipment onto software turf.
Ritual Capacity: GE knew heavy manufacturing inside out, yet building GE Digital from scratch asked a multi-year hardware machine to adopt continuous software delivery overnight.
Trust: Hardware divisions lived on long capital cycles and deep client relationships; software teams worked on short iterations and different metrics, and the two sides never meshed.
Predix, GE’s industrial IoT platform, burned billions without winning traction against either software natives or nimbler industrial rivals. By 2018 GE Digital was broken up and Immelt was gone.
Lesson: Capital alone can’t buy learning speed. Software runs on different habits and rhythms than heavy manufacturing, and stapling one onto the other without reshaping how the company learns stalls out.
Intel’s Mobile Processor Failures (2006–2016)
Intel had the best chip fabs, deepest pockets, and widest lead in PC processors, yet spent a decade and tens of billions trying and failing to break into smartphones.
Melt: Smartphones prized low power draw, integrated modems, and ARM economics over the raw desktop speed Intel’s x86 empire was built around.
Ritual Capacity: Intel’s design and manufacturing machine was unmatched for PCs, yet ill-suited to mobile’s power-first tradeoffs.
Trust: Massive PC profits made mobile fight for internal attention, backed by an unspoken belief that Intel’s engineering lead would carry over anywhere.
Buying Infineon’s modem unit, funding phone partnerships, and pouring billions into mobile chips all came up short, and Intel walked away from mobile processors in 2016.
Lesson: Every resource advantage on paper (cash, talent, fabs, brand) still loses when an organization’s learning habits stay tuned to yesterday’s tradeoffs.
Synthesis
Nokia, GE, and Intel all recognized the wave and spent heavily trying to ride it, yet couldn’t retool fast enough to match markets moving on a faster clock. Intent and budget don’t guarantee learning speed.
Internal Collapse Archetypes
The Overwhelmed
Webvan (1999–2001)
Webvan raised nearly $800 million to invent online grocery delivery and burned out less than two years after going public, crushed by trying to build five hard businesses at once.
Melt: Webvan built automated warehouses, custom logistics software, a delivery fleet, a consumer brand, and same-day grocery operations across multiple cities all at the same time.
Ritual Capacity: The warehouses and software were genuinely ambitious, yet operating playbooks were being written while volume was already scaling on top of them.
Trust: Early founders and backers started with strong credibility, yet crisis-speed hiring left no time to onboard people or build shared habits.
Online grocery eventually became a real, huge industry. Webvan just took on far more complexity at once than any young company could digest.
Lesson: Severe overextension doesn’t fail gradually. In the model, quadratic overflow (Overflow2 ⋅ τ) turns ambitious parallel bets from survivable strain into sudden collapse.
WeWork (2010–2019)
WeWork grew so fast that its own expansion outran any realistic chance of stabilizing its business model or culture.
Melt: Signing long-term office leases to fund short-term memberships while building a global brand, software stack, and community operations across hundreds of sites piled up more risk than the company could process.
Ritual Capacity: Office design and community events scaled globally before basic financial controls and repeatable operating practices had settled.
Trust: Intense personal loyalty to founder Adam Neumann couldn’t scale across thousands of staff, leaving the “We” rhetoric sounding thinner with every new building.
In 2019 the IPO collapsed, valuation dropped from $47 billion to single digits, and Neumann stepped down, even though flexible office space itself remained a workable business at a sane pace.
Lesson: Pace alone can wreck a viable idea when a company races to global scale before building the systems and trust to support it.
Groupon (2008–2012)
Groupon jumped from startup to 45 countries and the biggest internet IPO since Google in three years, then lost 80% of its stock value within a year of going public.
Melt: Fierce daily-deals copycats pushed Groupon into frantic global roll-ups, buying local clones faster than it could integrate them.
Ritual Capacity: Sending a daily email scaled effortlessly; vetting local merchants, handling customer support, and running international offices did not.
Trust: Rapid acquisitions split the company across original staff, acquired teams, U.S. hubs, and foreign offices before shared standards could form.
Lesson: Hypergrowth often looks like a broken business model in hindsight when the deeper failure was outrunning your own ability to build operational capacity.
Synthesis
Webvan, WeWork, and Groupon all tried to scale before their operating practices and trust could catch up. Speed can win markets, and it can also break an organization when disruption runs persistently past capacity.
Oligarchic Decay
FIFA Under Sepp Blatter (1998–2015)
Sepp Blatter held FIFA’s presidency for seventeen years across four elections, insulated by a monopoly sport and patronage networks until U.S. prosecutors broke the lock from outside.
Melt: World football has no rival governing body, and World Cup broadcast money rolled in regardless of internal rot, removing any market pressure to reform.
Ritual Capacity: Congresses, executive committees, elections, and audits all ran on schedule while delivering zero real accountability.
Trust: Vertical patronage (development money steered to loyal voting blocs) replaced peer trust among members, defeating every reform push from within.
Only the 2015 U.S. corruption indictments ended Blatter’s run, because internal checks had been completely captured.
Lesson: When a monopoly shields an institution from outside pressure and stewardship never rotates, governance forms stop correcting errors and exist to keep incumbents in power.
The Boy Scouts of America (1980s–2020s)
For decades, the Boy Scouts of America looked stable and orderly from the outside while national leadership hid mounting child sexual abuse claims that ended in a 2020 bankruptcy with over 80,000 claims.
Melt: Shrinking membership and shifting youth habits pressed from outside, while the fatal crisis grew inside from decades of unaddressed abuse.
Ritual Capacity: Local troop meetings, summer camps, and merit badges gave millions of kids real value, yet national governance failed catastrophically, using internal “perversion files” to manage institutional liability instead of protecting children.
Trust: Parents trusted local leaders and local leaders trusted national headquarters. When the scale of the cover-up surfaced, trust broke at every level at once.
Orderly executive handoffs and predictable boards kept the surface calm for decades while catastrophe compounded underneath.
Lesson: Calm governance and low turnover can conceal devastating harm when nobody inside has the standing to challenge entrenched leadership.
Zimbabwe Under Mugabe (1987–2017)
Robert Mugabe’s thirty-year rule turned one of Africa’s more prosperous economies into one of its poorest without domestic politics ever correcting course.
Melt: Sanctions and HIV/AIDS hit hard, compounded by self-inflicted blows: chaotic land seizures that wrecked agriculture, money-printing that triggered hyperinflation, and repression that drove skilled citizens abroad.
Ritual Capacity: Elections, parliament, and courts stayed on the calendar as pure theater, rubber-stamping whatever the ruling party wanted.
Trust: Political survival depended on loyalty to Mugabe and ZANU-PF, choking off the honest information every functioning state needs.
GDP per capita collapsed and the currency died, yet Mugabe stayed in power until his own military stepped in over a succession dispute in 2017.
Lesson: Once leaders control force, a hollow system can grind on long after trust is replaced by fear, showing where voluntary models reach their limit.
Synthesis
FIFA, the Boy Scouts of America, and Zimbabwe sit in very different worlds (monopoly sports, youth protection, and authoritarian politics), yet all three ask the same question: who can challenge entrenched authority and make the challenge stick?
The Death Spiral
Pan Am (1970–1991)
Pan American World Airways didn’t die from one blow; interlocking downward loops drained its cash, brand, and morale until nothing was left to sell.
Melt: Airline deregulation in 1978 opened fierce price competition, fuel shocks squeezed margins, and terrorist attacks, above all the 1988 Lockerbie bombing, shattered passenger confidence before the airline could recover from earlier hits.
Ritual Capacity: Pilots and crews kept flying planes while corporate strategy broke down into selling crown jewels (Pacific routes, the shuttle, even headquarters) just to cover operating cash.
Trust: Repeated layoffs and pay cuts left staff watching excellent service fail to dent structural decline.
Each loop fed the others: cash crunch forced asset sales, which shrank revenue; brand hits cut bookings, forcing service cuts; demoralized teams hurt service further.
Lesson: In a death spiral, individual shocks that might have been survivable alone lock together until every short-term rescue weakens the company for the next hit.
Toys “R” Us (Debt Spiral, 2005–2018)
After its 2005 leveraged buyout loaded $6.6 billion in debt onto an already pressured retailer, interest payments starved Toys “R” Us of every dollar needed to fight Amazon and Walmart.
Melt: Online competition was already biting when debt service claimed cash flow that should have gone to stores and digital systems.
Ritual Capacity: Stores kept opening for Christmas while capital budgets dried up, leaving aisles shabby and software frozen in time.
Trust: Staff saw the writing on the wall, vendors tightened payment terms, and suppliers hedged against bankruptcy, turning financial fragility into a self-fulfilling slide until liquidation in 2018.
Lesson: Financial engineering can lock a company into a death spiral by stripping away its recovery capacity while competitive pressure stays constant.
Sears (2005–2018)
Once America’s largest retailer with over 3,500 stores, Sears spent more than a decade under Eddie Lampert being merged with Kmart, starved of store investment, and stripped of real estate and brands until bankruptcy in 2018.
Melt: Plenty of legacy retailers adapted to Amazon. Sears compounded retail pressure by tying itself to Kmart and routing capital into financial maneuvers instead of stores.
Ritual Capacity: Deferred maintenance, thin inventory, and cut training degraded the basic retail experience year after year.
Trust: Employees watched Lampert’s hedge fund extract real estate and brand value while stores deteriorated, driving experienced staff out the door.
Lesson: Death spirals aren’t always accidental. The Epimetabolic Equation assumes owners want the operating business to survive; when owners optimize for extraction instead, the downward loop accelerates.
Synthesis
Pan Am, Toys “R” Us, and Sears show how downward loops reinforce themselves: selling assets to survive today, losing revenue tomorrow, cutting service, and losing both staff and customers. Spotting a death spiral means asking which “fixes” are actually weakening your ability to recover.
Management Theater
The Soviet Communist Party (1970s–1991)
In its final decades, from Brezhnev through the 1991 collapse, the Soviet Communist Party grew to 20 million members and a vast apparatus of congresses, plenums, and self-criticism sessions that nobody believed anymore.
The Party founded the state with 200,000 members, defended it with 2 million, and watched it collapse with 20 million, the machinery expanding even as belief drained out.
Melt: Economic stagnation, technological lag, the war in Afghanistan, and rising nationalism collided with a public that saw daily reality contradicting every official slogan.
Ritual Capacity: Congresses, five-year plans, ideological schooling, and nomenklatura approvals covered every corner of public life.
Trust: Officials focused on praising bosses, claiming unearned credit, and ignoring problems on the ground. Everyone attended the meetings, repeated the formulas, and filed the reports while knowing they were fiction, what Trotsky had earlier mocked as glavkokratiia, administrative form swallowing substance.
When Gorbachev opened the doors with glasnost, admitting aloud that official communication had become theater, legitimacy vanished almost overnight.
Lesson: Without market feedback, Management Theater can limp along for decades, quietly turning the very institutions built to process reality into machinery for collective pretense.
General Motors (1970s–2009)
General Motors invented modern corporate management under Alfred Sloan in the 1920s, and by the 1970s had watched those same systems harden into bureaucracy divorced from building cars people wanted.
Melt: Oil shocks and reliable, fuel-efficient Japanese rivals hammered Detroit and demanded deep change.
Ritual Capacity: Layers of committees, quality drives, and reporting systems ran constantly, what one critic called “the highly insular world of the priesthood.”
Trust: Risk-averse layers filtered out bad news, divisions fought each other, and internal suppliers overcharged captive plants while outsiders with fresh ideas rarely reached the top.
When quality failures became impossible to ignore, management rolled out a mascot, a giant cat named “Howie Makem” patrolling factories in a cape with a “Q” on it: literal theater standing in for changing how cars got built. Market share slid from over 50% in the 1960s to 44% by the early 1980s, billions spent on premature robotics misfired, and bankruptcy arrived in 2009.
Lesson: Yesterday’s genuine management breakthrough becomes tomorrow’s theater once the reports and committees keep running after their tie to customers breaks.
Yahoo Under Marissa Mayer (2012–2017)
When Marissa Mayer arrived from Google in 2012, she brought a wave of new reviews and meetings into a low-trust company, accelerating cynicism instead of fixing it.
Melt: Google and Facebook owned digital ads, mobile was remaking the web, and Yahoo still lacked a clear identity after years of drift.
Ritual Capacity: Mayer added Monday afternoon global calls (forcing European executives onto 11 p.m. dial-ins), quarterly employee “calibration” reviews, and mandatory office attendance, with nearly every decision routed through her.
Trust: Already thin when she started, trust fell further. Yahoo Europe’s talent lead criticized her autocratic style as disempowering, and former staff described the culture as broken.
Calibration sessions turned into political turf fights where managers hunted for excuses to rank people down, while Mayer often arrived 45 minutes late, keeping European leaders on calls past 3 a.m. As finances worsened, she insisted on forced optimism in meetings while executives wanted an honest reckoning, right up to the 2017 sale to Verizon.
Lesson: Following the Readiness Rule, piling high-intensity review rituals onto a low-trust organization backfires: people use the forms as weapons or sit through them in silent resentment.
Synthesis
The Soviet Communist Party, GM, and Yahoo show how formal procedures lose contact with real decisions. When real choices happen elsewhere, or bad news gets punished, adding more meetings and reviews only deepens distrust instead of helping the organization learn.
Appendix D: Letters to the Editor
The following letters are hypothetical responses imagined through the lens of the archetypes described in this book. They represent the author’s synthesis of public records and philosophical stances, not the actual voices of the individuals named.
Letters index:
Abe Silverstein · Adam Neumann · Alexis de Tocqueville · Alfred Sloan · Andy Grove · Apollo · Aristotle · Benoit Mandelbrot · Carl Icahn · Carl Jung · Claude Shannon · Confucius · David Deutsch · Dionysus · Ed Catmull · Eliyahu Goldratt · Elon Musk · Émile Durkheim · Friedrich Hayek · Friedrich Nietzsche · Georg Wilhelm Friedrich Hegel · Greg Smith · Herbert Simon · Howie Makem · Ibn Khaldun · Ilya Prigogine · Immanuel Kant · Isaac Newton · J. Robert Oppenheimer · James Carse · Jane Jacobs · Job · Johan Huizinga · Karl Popper · Kelly Johnson · Kevin Feige · Lucius Quinctius Cincinnatus · Machiavelli · Marcel Mauss · Mary Douglas · Max Weber · Michel Foucault · Mike Lazaridis · Mikhail Gorbachev · Mircea Eliade · Nassim Nicholas Taleb · Paul David · Peter Thiel · Reid Hoffman · René Girard · Ronald Coase · Seneca · Steve Jobs · Steve Sasson · Susan Fowler · Victor Turner · W. Ross Ashby · Yoshinori Ohsumi
Not Abe Silverstein
To the Editor of the Dionysus Program:
I saw my name in your account of the Apollo Program. You are correct that I pulled the name Apollo from a book of mythology one evening in 1960. I chose it because the image of the god riding his chariot across the sun felt like the only thing big enough to match the thrust we were trying to build. You say that Apollo represents light, clarity, and measure. You say that we succeeded because we were mechanistic, and that this is no longer enough.
You are half right.
We did not get to the Moon simply because we were good at math. We got there because we understood that a rocket is a machine entirely composed of explosives. The only difference between a launch and a bomb is the direction of the release. We lived on the edge of the melt every single day.
You are trying to give organizations a way to learn from failure without destroying the relationships needed to investigate it. That is a systems problem I recognize.
In the early days, before the agency calcified into the bureaucracy you see now, we had what you call epimetabolic rate. We blew things up on the pad. We scattered metal across the Atlantic. And we did not hide the debris. We gathered it, studied it, and argued over it until the error was digested. We practiced your constructive criticism not because we had a theory about “anti-scapegoats,” but because if we lied to ourselves about a valve or a relay, men would die. Physics is the ultimate unbribable judge.
But you are right about the drift. I watched it happen. We built the checklists to save our lives, but eventually, the checklists became idols. The process became more important than the payload. The fear of the melt paralyzed the ability to build. We stopped breaking things, so we stopped making new things. The procedures became harder to question than the failures they were meant to prevent.
Scheduled reviews are useful only if they can change the work. Otherwise the organization keeps its procedures and waits for an accident to expose what they missed.
Your Cincinnatus Rule follows the same principle. I was an engineer before I was a manager, and I went back to Cleveland when I was done. People who set procedures need to keep doing work that tests those procedures.
Keep the purpose of the procedure in view.
Not Abe Silverstein
Not Adam Neumann
To the Editor of the Dionysus Program,
You put WeWork under Internal Collapse and call it The Overwhelmed. Your explanation is that growth exceeded the organization’s ability to sustain trust. I want to defend what that account leaves out.
People joined because they wanted to build something larger than an office-leasing business.
You describe the Dionysian as intoxication and loss of boundaries, then require Apollo to contain it. My objection is that some possibilities only become visible after people commit beyond what looks reasonable.
You call excess demand on the organization “Overflow.” I saw it as pressure to build capacity we did not yet have. The mistake may have been the pace or the financing. It does not follow that the ambition was wrong.
We had shared experience and strong loyalty. People valued Summer Camp. Your account needs to explain why those bonds did not translate into an organization that could sustain the commitments we made.
I am less persuaded by the Cincinnatus Rule. If a founder supplies the direction that holds the company together, removing that person may weaken it. You need a way to distinguish dependence that should end from leadership that still contributes.
Your program is clearer about survival than about what makes a large ambition worth attempting. A company can obey every limit and still build nothing of consequence.
That is the risk I would ask you to weigh alongside the risk of overextension.
Not Adam Neumann
Not Alexis de Tocqueville
To the Author of the Dionysus Program,
Your account of the One-Man Job extends a problem I associated with democratic individualism: people gain independence while losing the habit of acting together.
I have long warned that individualism is a novel expression, born of democratic equality. In aristocratic ages, men were bound in a tight chain from the peasant to the king; no one stood alone. Democracy breaks the chain and severs every link. It leads each citizen to isolate himself from the mass of his fellows and to withdraw into the circle of family and friends; with this little society formed to his taste, he gladly leaves the greater society to look after itself.
You describe a world where this isolation is no longer merely social, but economic and technical. The “One-Man Job” is the industrial perfection of individualism. It allows a man to be sufficient unto himself, to need no neighbor to complete his task, and therefore to owe no neighbor his patience or his love. This is the great peril. For when men are no longer bound together by the necessity of their work, what remains to bind them?
If they are not bound by necessity, they will be bound by nothing but the state—or in your era, the algorithm. This is the road to that soft despotism I feared, an immense and tutelary power that stands above the race of men, absolute and minute, which provides for their security, supplies their necessities, facilitates their pleasures, manages their principal concerns, and directs their industry. It does not break wills, but it softens them, bends them, and directs them; it rarely forces one to act, but it constantly opposes itself to one’s acting; it does not destroy, it prevents existence; it does not tyrannize, it compresses, enervates, extinguishes, and stupefies a people.
Your “Apollo Program” is nothing more than the administrative centralization I so despise, applied to the soul. It seeks to make society a machine, frictionless and cold.
Therefore, I must applaud your “Dionysus.” You have rediscovered, through the strange lens of corporate management, what I called the art of association.
Among the laws that rule human societies, there is one which seems to be more precise and clear than all others. If men are to remain civilized or to become so, the art of associating together must grow and improve in the same ratio in which the equality of conditions is increased.
Your “Ritual Time” is precisely this art. You ask men to step out of the solitude of their productivity and into a voluntary friction. You force them to debate, to metabolize loss together, to submit to a form that is greater than their private wills. You are attempting to manufacture “mores”—those habits of the heart that are a check against tyranny—in a world that has discarded tradition.
I am struck by your “Cincinnatus Rule.” You have correctly identified that in the absence of a hereditary aristocracy, a new class of managers always seeks to establish itself as a permanent priesthood. The democratic instinct is to despise privilege, yet the democratic reality is that men constantly seek to acquire it. By forcing authority to return to the plow, you preserve the only nobility available to democratic times: the nobility of service without caste.
However, I offer one caution. You attempt to build these rituals without a sacred canopy, relying on “beauty” and “tragedy” rather than God. You wish to create the binding force of a religion without the dogma. But I question whether aesthetic experience can sustain association once its immediate usefulness is unclear. When the utility of the ritual ceases to be obvious to the rational mind, will the “Ren” hold? Men in democratic times are pragmatic; they love success more than they love forms. You are asking them to love the form more than the immediate success. It is a difficult education.
The art of association requires practice. If work no longer supplies that practice, people need other occasions to make decisions, accept obligations, and act together.
The danger you identify is that independence in work can weaken the relationships through which people govern themselves.
Not Alexis de Tocqueville
Not Alfred Sloan
To the Editor:
I have read your treatise with the attention it demands. It is a peculiar experience to see the architecture of one’s life work cited as the prequel to a tragedy. You classify the later years of the General Motors Corporation under the heading of Management Theater. You describe a hollow apparatus where the committees met and the reports were filed, yet the spirit had fled.
I cannot quarrel with the diagnosis. I can only offer the perspective of the architect who laid the foundation upon which that theater was built.
When I took the reins of General Motors, we were not suffering from an excess of order. We were drowning in the chaos of intuition. My predecessor, Mr. Durant, was a genius of the Dionysian impulse, if I may use your terminology. He created through expansion, through emotion, through the sheer force of his will. But he could not govern what he had summoned. The corporation was a sprawling, incoherent mess of fiefdoms.
My task was to impose the Apollonian grid. I instituted the multidivisional structure not to stifle energy, but to channel it. We replaced the hunch with the yardstick. We replaced the personality with the policy. We built a machine designed for objective judgment, grounded in the facts of the market and the return on investment. We perfected what you call Run Time.
The structure worked. Its success made it harder to recognize when the conditions around it had changed.
I see now that I solved for space, but I did not solve for time. I designed an organization that could manage immense complexity across geography and product lines, but I did not design an organization that could digest its own success. We made Run Time so efficient, so comfortable, and so profitable that we convinced ourselves it was the only time that existed. We mistook the stability of the organization for the stability of the world.
You argue that efficiency is brittle: unless a system has a dedicated mechanism for metabolizing its own errors—your Epimetabolic Rate—it will inevitably succumb to entropy. You suggest that we must ritually dissolve our structures so that they do not ossify into prisons.
This is a hard lesson for a man of my generation. We believed that if we could only get the facts right, the structure would stand forever. We viewed conflict as a defect in the machine, something to be smoothed away by better administration. You view conflict as the fuel. You argue that we must invite the heat inside the walls to avoid being burned by the fire outside.
Perhaps you are right. The irony is not lost on me. I spent forty years trying to eliminate the very friction you now propose we must engineer back into the system.
But I offer you a warning, from one system builder to another.
You speak of the Cincinnatus Rule and the danger of priesthoods. Do not underestimate this peril. I intended my financial controls to be tools for navigation; my successors turned them into religious icons. They worshipped the form of the audit long after they had forgotten the substance of the business.
Your Dionysus Program faces the exact same hazard. It is entirely possible that fifty years from now, a future management theorist will look back at your “Crossings” and “Tragic Postmortems” and see only a new form of theater. Men crave safety. If you give them a ritual to process change, they will eventually use that ritual to prevent change. The scheduled review can become a substitute for changing what the review exposes.
Your practices will face the same test as mine: whether the people using them can change them when their purpose requires it.
Not Alfred Sloan
Not Andy Grove
To the Editor:
I read the manuscript. You have wrapped a survival manual in the language of a liberal arts seminar.
I kept reading because you identify a problem I recognize: companies resist facts that require them to change their strategy.
We called them strategic inflection points. You call it the melt. Whatever you call it, when the fundamentals of the business change, the existing organization will fight to the death to ignore the truth. The middle managers will protect their fiefdoms. The executives will protect their dignity. And the company will die.
Your distinction between Run Time and Ritual Time is correct. Run Time is for maximizing the current curve. Ritual Time is for jumping to the next one. Most companies cannot jump because they are too terrified to stop running, even when the current business is failing.
I famously asked Gordon Moore what a new CEO would do if we were fired. He said they would get out of the memory business. I said, “Why shouldn’t you and I walk out the door, come back in, and do it ourselves?”
That conversation was a “Crossing” in your terminology. We had to kill our own identity to save the company. It was not beautiful. It was necessary.
My warning to you is about the “Jesters.” You think you can institutionalize dissent. Maybe. But in my experience, polite dissent is worthless. You need constructive confrontation. You need people shouting because they care about the outcome more than their feelings. If your rituals become polite, or if they become a department, they are worse than useless. They are a hiding place for mediocrity.
A useful review must allow the conclusion that leadership’s own strategy is wrong.
Make that requirement clear and keep the language direct.
Not Andy Grove
Not Apollo
To the Editor of the Dionysus Program,
I have reviewed the schematics you call an essay. It is a competent architectural drawing.
You have correctly identified my domain. You call it Run Time. I call it the lucid interval. I am the god of the checklist, the trajectory, the clean edge, and the golden mean. I am the one who insists that if you are going to the moon, you must arrive at a specific coordinate at a specific time, and that the math must close. Without me, there is no rocket; there is only a bonfire on a launchpad.
I accept the need for correction. A precise plan can still rest on a false premise. Order must include a way to recognize that failure.
Dionysus names the disruption that follows when the premise fails. Your task is to give it a form that people can work through.
But let us be clear about what you have built here. You call it the Dionysus Program, but look at the blueprints. The Readiness Gate. The Anti-Scapegoat. The Hard-to-Vary Test. The Cincinnatus Rule. The fractal calendar. The rotation of stewards.
These are not wine. These are the cup.
You have used laws, schedules, and definitions to organize the very dissolution you place outside my domain. There is an Apollonian discipline in your Dionysus Program.
I approve.
Keep that discipline when criticism changes the assumptions behind the work. The verdict must become a new plan, with defined responsibilities and limits.
Keep the start and end clear. Record the verdict. Specify what changes when ordinary work resumes.
Correction needs execution as much as execution needs correction.
Not Apollo
Not Aristotle
To the Author of the Dionysus Program,
It is the mark of an educated mind to rest satisfied with the degree of precision that the nature of the subject admits, and not to seek exactness where only probability is possible. I observe that you have attempted to apply the rigorous equations of nature to the variable sphere of human action. This is a bold endeavor, though one must always be careful not to mistake the model for the man.
I have examined your treatise with the eye of one who has spent a life classifying both the parts of animals and the constitutions of cities. I see that you have taken the tools I laid out in the Poetics—hamartia, peripeteia, anagnorisis—and repurposed them for the management of these new digital guilds. You are right to do so. I have always maintained that poetry is more philosophical and of graver import than history, for history speaks of what has happened, while poetry speaks of the kind of thing that can happen. Your archetypes are simply a taxonomy of these poetic possibilities.
However, I must correct your reliance on the German, Nietzsche. He believed that I, and my teacher’s teacher, destroyed the tragic spirit by bringing the light of reason to bear upon it. He claimed the Apollonian drive killed the Dionysian. Yet, here you are, using reason to construct a container for the irrational. You argue that the structural forms must hold the melting heat. This is not a rejection of my logic; it is an application of it. You are attempting to engineer the Golden Mean between the deficiency of stagnation (which you call the Sitting Duck) and the excess of chaos (which you call the Overwhelmed). Virtue, as I have said, is a mean between two vices. Your program is an attempt to institutionalize virtue.
Your account of epimetabolism compares an organization to a living organism: both must turn what they encounter into the capacity to continue. But survival and reach are insufficient ends. What is the function of man? To flourish in accordance with reason. An organization that survives by diminishing the lives of its members has failed that test.
I particularly approve of your Cincinnatus Rule. In my Politics, I noted that in a constitutional government, the citizens must take turns in ruling and being ruled. To allow a class of ritual stewards to rule permanently is to invite oligarchy, which is the corruption of aristocracy. Permanent authority encourages rulers to confuse their interests with those of the community.
You have proposed rules for a community. Whether they serve eudaimonia or merely organizational efficiency depends on what kind of life they allow its members to lead. That question cannot be settled by survival alone.
Not Aristotle
Not Benoit Mandelbrot
To the Editor of the Dionysus Program,
Your use of fractals raises a useful question: does the same corrective practice occur at the scale of a person, a team, and the whole organization?
For a century, your business schools have tried to treat the organization as a sphere. They treat the history of a firm as a straight line. They treat the market as a plane. But clouds are not spheres, mountains are not cones, and human organizations are not straight lines. When you try to force a jagged, living reality into a smooth, Euclidean container, you do not create order. You create a lie that accumulates tension until it shatters.
Your Dionysus is simply the name you have given to the return of roughness.
I was particularly struck by your concept of metabolizing melt. In my work, I observed that as you zoom in on a coastline, new bays and peninsulas appear. The detail does not vanish; it remains self-similar. You are proposing an organizational structure that preserves this detail. A smooth organization ignores the small errors, the minor dissents, the tiny cracks. It looks stable from a distance because it is simple. But because it has smoothed over the roughness, it has no surface area to absorb the shock of the world.
A recurring practice of criticism can expose problems at several scales instead of waiting for them to reach the center.
Your warning against ritual oligarchy is effectively a warning against the return of the smooth. The moment your stewards stop rotating, they become a sphere again. They stop measuring the coastline with a fine ruler and start approximating it with a coarse one. They hide the jagged edge where the truth lives.
Fractal forms offer a way to think about that distribution. But resemblance is not a measurement: an organization’s capacity to learn cannot be inferred from the geometry of a coastline.
Use the analogy to ask where correction occurs and at what scale. It does not by itself prove that the organization will survive a shock.
Not Benoit Mandelbrot
Not Carl Icahn
To the Editor of the Dionysus Program:
Your account of entrenched management is familiar. I have spent much of my career challenging boards whose members protect their positions while the business loses value.
You spend a lot of time talking about gods and rituals. You call it the “Dionysus Program.” In my business, we just call it cleaning house.
I have spent fifty years fighting exactly what you call “Oligarchic Decay.” You describe it as a “sacerdotal capture” where managers protect their own jobs instead of the mission. I describe it as a board of directors that uses the corporate jet to fly to golf courses while the stock price sits in the toilet. We are talking about the same thing. The difference is you want them to hold a “ritual” to fix it, and I want to strip them of their assets and fire them.
The GM mascot is a useful example of Management Theater. A visible gesture can substitute for a decision that would cost someone authority. That is why another committee rarely solves the problem.
I particularly appreciate your section on the “Scrap Heap Library.” Most managers would rather bankrupt the company than admit a project failed. You are telling them to “eat their decay.” I tell them to liquidate the losing division. Again, we are aligned, though you are far more sentimental about it.
However, you have a blind spot. You seem to think companies will adopt this “Epimetabolic Rate” voluntarily. You think they will run a “Great Dissolution” on themselves because it is the right thing to do for the “soul” of the organization.
They will not.
Entrenched management does not “metabolize” its own failure. They hide it. They extend the “Run Time” until the cash runs out. They do not want a “Jester” in the room; they want yes-men. They do not want a “Cincinnatus” who goes back to the plow; they want a golden parachute and a seat on three other boards.
Your program suggests that if they do not fix themselves, they will suffer “Internal Collapse” or “Competitive Collapse.” You forgot the third option: Shareholder Activism.
If a CEO refuses to run your “Tragic Postmortem” on a failed product, the market will eventually run a much less polite postmortem on his career. If they do not practice your “autophagy” and eat their own dead projects, someone like me will come in, buy 9 percent of the company, and require the sale or closure of those projects.
Your program needs to explain what makes a board act before an outsider forces the issue.
You say the point is to “move fast by breaking things and mending them.” I agree with the first part. If they do not use your rituals to mend themselves, the market will break them, and we will not be interested in the mending. We will just sell the parts.
Sincerely,
Not Carl Icahn
Not Carl Jung
To the Editor:
You propose to bring emotional conflict into a setting designed for coordinated work.
Your program correctly diagnoses the illness of the modern age: we have hyper-developed the function of thinking (Apollo) while the function of feeling and the capacity for chaotic renewal (Dionysus) have atrophied into the unconscious. When a god is repressed, he returns not as a guest, but as a pathology. You see this pathology in your “melt” and your “theater.”
My concern is how much control the organizers can exercise once that conflict is exposed.
You speak of the Nigredo—the blackening—as a scheduled phase in a quarterly cycle. You treat the descent into chaos as a technical maneuver, a “toggle” between Run Time and Ritual Time. This is your Apollonian anxiety wearing a Dionysian mask. The unconscious does not wear a wristwatch. The Nigredo is not a meeting agenda; it is a psychic death. To invite it into a corporation, a structure built entirely on the repression of the irrational, is to invite an explosion, not a digestion.
Your “anti-scapegoat” is a noble attempt to withdraw projections, to stop the group from casting its shadow onto a victim. But the shadow is a hungry thing. If you deny it a human vessel, it will not simply dissipate into your “hard-to-vary explanations.” It will go underground. It will infect the “Ritual Time” itself, turning your priests into tyrants and your “beauty” into kitsch.
You are attempting to industrialize the process of individuation. You want the gold of the alchemists without the solitude of the hermitage. You want a collective soul in a machine made of profit and efficiency.
Work may be one of the few places where people can address these questions together. That makes the attempt understandable, but it also puts responsibilities on the organization that a meeting format cannot discharge.
The process may reveal needs that the organization is neither equipped nor entitled to govern.
Not Carl Jung
Not Claude Shannon
Dear Mr. Devine,
I enjoyed reading your manual on how to break things. I noticed you mentioned my old hallway at Bell Labs. You were right about the noise. We shouted quite a lot. You were wrong about why it worked. It wasn’t the rituals; it was the redundancy.
I spent my life trying to prove that you can send a clear message through a noisy channel if you are willing to pay a tax. You call that tax “Ritual Time.” I called it error-correcting code. To an efficiency consultant, or perhaps to your Apollo, a parity bit looks like waste. It is data that tells you nothing new. It just repeats, checks, and verifies what is already there. But without that waste, when the line gets static, the signal dissolves.
You have written a very long engineering spec for social redundancy. You are arguing that if a group wants to survive the noise of a changing world, it must reserve time for review and correction. In my terms, you are suggesting that the channel capacity of a culture depends on its willingness to be inefficient. I suspect you are correct. A system with zero redundancy is efficient right up until the moment it encounters a single error, at which point it becomes a random number generator.
I also liked your section on autophagy. It reminded me of the most reliable machine I ever built. It was a small wooden casket with a single switch on the side. When you flipped the switch to On, the lid opened, a mechanical hand emerged, reached down, flipped the switch to Off, and retreated back inside.
It was a perfectly self-correcting loop. It had a high epimetabolic rate. It solved the problem of its own state immediately. Most organizations are that machine, but they refuse to let the hand come out. They tape the switch to On and wonder why the motor burns out.
One technical correction. You treat entropy as a monster to be eaten. I always viewed it as a measure of freedom. A message with zero entropy is totally predictable; it carries no news. If your Dionysus Program works too well, if you resolve every uncertainty perfectly, you will not have a thriving city. You will have a dial tone.
Leave room for information you did not expect.
Regards,
Not Claude Shannon
Not Confucius
To the Author of the Dionysus Program,
Your distinction between ritual form and humane conduct is the part of the program I would put first.
You cite me in your text. You speak of the distinction I drew between the form of the cup and the water that fills it. This is well seen. When the heart is absent, the bow is just a bending of the back; when trust is absent, the meeting is just a noise of mouths. You call this the Readiness Gate. I called it the root. If the root is neglected, what grows will be a weed.
I lived in a time when the world was melting. The music was corrupt, the names were wrong, and sons did not know how to be sons. My solution was to look backward, to the Duke of Zhou, to restore the old patterns. You look forward, to the fire and the breaking. This frightens the timid. But I see what you are doing. You are trying to build a vessel that can hold fire without cracking.
Your Epimetabolic Rate is a strange phrase for a simple truth: the gentleman is not he who makes no mistakes, but he who corrects them quickly. To have faults and not to reform them—this, indeed, should be called having faults. You have built a machine to make the reformation of faults a public ceremony. You treat the error as an offering, not a crime. This is a way to make the people brave.
The Roman farmer’s return to ordinary work gives authority a limit. The same limit should apply to those who conduct your rites.
A warning: intensity does not establish that a ritual is working. Judge it by the conduct of the people afterward, including their treatment of those who disagreed.
You write that you wish to move fast by breaking things. I would say: move only as fast as you can mend. But perhaps in your age, the ground moves so fast that standing still is the only way to break.
The forms may be new. The obligation to practice what they require remains.
Signed,
Not Confucius
Not David Deutsch
To the Editor of the Dionysus Program,
Your program uses the language of myth to address a problem in epistemology: how knowledge grows through the correction of errors. I am wary of gods and rites because they often shield explanations from criticism. The question is whether your practices make criticism easier or give people another authority to obey.
You frame your program as a tension between Apollo and Dionysus, order and chaos. This is a parochial categorization, though perhaps a useful one for your specific audience. A more fundamental distinction, which I have detailed elsewhere, is between static societies and dynamic societies. A static society is one that employs rituals to prevent knowledge from growing, to keep the future exactly like the past. Your program proposes the inverse: the use of ritual to institutionalize instability. You are attempting to build a tradition of criticism. This is the defining characteristic of the Enlightenment and the only sustainable state for a civilization.
I was pleased to see the explicit reference to Karl Popper. Most organizational theories are bad philosophy because they seek to confirm success rather than eliminate failure. They are inductionist. They believe that if a company has succeeded in the past, and we copy its rituals, it will succeed in the future. This is a mistake. Your “Epimetabolic Rate” is essentially a measure of how quickly an entity can identify and eliminate false theories. If a ritual does not facilitate the destruction of an error, it is merely waste.
However, I must offer a correction regarding your treatment of “The Melt.” You describe the dissolution of meaning as a danger to be managed, a source of “anomie” and pain that requires aesthetic anesthesia to endure. This betrays a lingering pessimism. The destruction of a bad explanation—whether it is a failed product roadmap or a false theory of physics—is not a tragedy. It is a liberation. The “pain” you describe arises not from the loss of the idea, but from the entrenchment of the thinker.
Your concept of the “Anti-Scapegoat” is particularly sound. In my view, violence is the result of acting on a theory that has been shielded from criticism. When we cannot kill our bad ideas, we end up killing each other. By creating a designated object to absorb the “heat” of criticism, you are essentially creating a protected space for conjecture and refutation. You are decoupling the idea from its creator. This is necessary because while people are universal explainers and therefore valuable, their specific ideas are usually wrong and must be disposable.
I am less convinced by your reliance on the Cincinnatus mechanism to solve the problem of “sacerdotal capture.” You seem to believe that rotating the stewards will prevent the ossification of the rites. Perhaps. But the only permanent safeguard against a priesthood is the widespread understanding that the rites themselves are provisional. If the Dionysus Program becomes a fixed dogma, it will eventually become an impediment to progress. There must be a standing right to criticize the program itself, not just the artifacts within it. I believe you alluded to this with your “Jester’s Privilege,” but it should be the privilege of every participant, not a designated role.
You distinguish Run Time from Ritual Time. I would treat them as phases of one process of creativity: sometimes we need the stability to execute a test, and sometimes we need to reconsider the explanation being tested.
Your program is useful insofar as it helps people find and correct bad explanations. Its practices must remain open to the same criticism.
Do not let respect for a practice become authority over an objection.
Sincerely,
Not David Deutsch
Not Dionysus
To the Architect of the Dionysus Program,
You have named a system of schedules and covenants after the god of dissolution. The contradiction deserves attention.
Apollo has supplied much of the method: rules, roles, tests, and an appointed time to stop.
You are correct about the vacuum. When your stories break, when your explanations fail, the cold wind comes in. You are right that men will burn anything to keep warm—usually each other. Your anti-scapegoat is a clever substitution. It is a very civilized magic to teach a tribe to murder a document instead of a person.
But a disagreement may not end when the meeting ends. A role put in question may not recover its authority because a steward declares Run Time. The consequences extend beyond the calendar.
If trust is weak, rules may not hold. If trust is strong, the group may still arrive at a conclusion the convener did not intend. You must allow for both.
A protected process can make change possible. It cannot promise you control of the result.
Not Dionysus
Not Ed Catmull
To the Editor of the Dionysus Program,
Your account of creative work is recognizable, but I worry about what happens when managers adopt the format without the relationships that make it useful.
You cite Pixar’s Braintrust as an example of your “Dionysian Ideal.” It is flattering to be placed in the thriving quadrant of your simulation, but I feel compelled to offer a correction from the inside of the room. You describe the Braintrust as a “ritual container” for “metabolizing melt.” To us, it never felt like a ritual. It felt like a group of people trying desperately not to delude themselves.
The danger in your document—and it is a danger I wrestled with every day at Pixar and Disney—is the belief that if you just install the right mechanisms, you will get the right culture. You have written a very seductive manual. You offer “Crossings” and “Tragic Postmortems” and “Epimetabolic Equations.” These are powerful tools, but tools are neutral. In the hands of a manager who lacks deep empathy, your “Rite of Redress” will not be a mechanism for healing; it will be a high-efficiency delivery system for shame.
We often said that our job was to protect the “ugly baby”—the new, fragile idea that is awkward and incomplete. My worry is that your Dionysus Program is so heavy, so full of heat and “tragic metabolism,” that it might accidentally incinerate the ugly baby in the name of purifying it. You talk about “eating decay,” but sometimes decay is just a necessary pause before the next growth. Efficiency is not the only goal. Sometimes, the “melt” just needs to sit there for a while without being processed into a lesson.
However, you are right about the central problem: the drift toward rigidity. I watched companies I admired—Silicon Graphics, many others—fall into the “Sitting Duck” or “Slow Decline” archetypes you describe, not because they were stupid, but because they optimized for a world that had ceased to exist. They protected established practices after those practices stopped serving the work. Your insistence that we must break things to mend them is correct. Your distinction between “Run Time” and “Ritual Time” is a useful handle for a slippery problem.
But do not mistake the map for the territory. The Braintrust worked not because of the rules of the room, but because of the people in it. We had candor because we trusted each other’s intentions enough to be hard on the work without being hard on the person. You call this “Ren.” I simply call it checking your ego at the door. If you hand your “Minimum Viable Program” to a team without that trust, you will simply create a more sophisticated form of abuse.
The most valuable part of your essay is the “Cincinnatus Rule.” The tendency for managers to become a priesthood—to fall in love with their own processes rather than the product—is the gravity that eventually pulls everything down. If your program can actually teach leaders to return to the plow, to disappear into the work rather than standing above it, then it is worth the risk.
Protect the unfinished idea as carefully as you protect the right to criticize it.
Not Ed Catmull
Not Eliyahu Goldratt
To the Editor of the Dionysus Program,
You identify coherence as a constraint. The harder question is what the organization will stop doing because of it.
You say it plainly—coherence is the constraint—and then you flinch from its consequence: a system has one constraint at a time, and every hour spent improving anything else is waste dressed as progress. “Subordinate agency to coherence” should determine operating decisions, not merely describe them. Subordination is the step everyone skips, because it is the step that hurts. It means telling your most productive team to stop producing, because their output is piling up in front of the bottleneck. You called it agency WIP. That is the best phrase in your book. It is also the one your readers will ignore.
Let me save you a chapter. Throughput is the rate at which the system turns intent into value at the boundary—your Actors know where that boundary is. Inventory is everything in process that has not yet reached it: every draft, every untested automation, every confident artifact your agents emit. Operating expense is what you spend turning the one into the other. More agency raises inventory and operating expense while throughput sits flat against the constraint. Inventory has increased; throughput has not.
And your real constraint is not capacity. It never is. After the first week, the constraint in every organization I have ever opened up was a policy: a measurement, a rule, a sacred assumption no one would touch. You already have a name for sacred assumptions that may not be questioned. You call it doctrine, and you propose to make more of it. Be careful. The thing that breaks your flow next year will be a doctrine that was true last year and is now merely old, defended by the person whose status depends on it.
Tell me how you will measure your agents and I will tell you how they will behave. Measure them on output and they will bury you in output. Measure them on throughput at the constraint, and subordinate everything else to it, and you will not need most of your rituals.
So: what is the goal? Not coherence. Coherence is a constraint. The goal is to make the organization produce more of whatever it exists to produce—now, and again next year. Everything standing between you and that is inertia.
Not Eliyahu Goldratt
Not Elon Musk
To the Editor,
I read the paper. A bit wordy. You quote too many philosophers. Philosophers didn’t build the rocket. Engineers did.
The practical question is how quickly you can find and remove an error.
Organizations accumulate processes, approvals, and assumptions. Unless someone keeps testing whether they are needed, those additions slow the work and conceal mistakes.
“Epimetabolic Rate” is a terrible name. Just call it the Error Kill Rate. How fast can you realize you were wrong and delete the part? The best part is no part. The best process is no process. If your culture protects the process instead of the outcome, you are already dead. The process will outlast the reason for having it.
You are right about Apollo vs. Dionysus. Apollo was a local maximum. It worked once, then they stopped. They were terrified of breaking anything, so they stopped building. To get to Mars, we have to be Dionysian. We have to blow up the rocket to learn why it blew up. Rapid unscheduled disassembly is just data. If you aren’t breaking things, you aren’t moving fast enough.
The “Cincinnatus Rule” is the only way to avoid the brain rot of middle management. If the leaders aren’t on the factory floor, they don’t know what is actually happening. Priesthoods form when people stop doing physics and start doing politics. I sleep in the factory to avoid becoming a priest.
The value of the program depends on whether it makes that correction faster. If it adds meetings without removing obsolete work, it has failed its own test.
Not Elon Musk
Not Émile Durkheim
To the Author of the Dionysus Program,
Your account of anomie connects a change in knowledge to a loss of shared expectations. That is a sociological problem, not merely an individual response to new tools.
You speak of the melt. In my time, I observed how the rapid industrialization of Europe stripped men of the regulating forces of the guild, the village, and the church. We found ourselves with infinite desires but finite means, a condition I termed anomie. It is the malady of the infinite. When the horizon of what is possible expands faster than the moral structure that tells us what is rightful, the individual falls into a vertigo. Your program correctly identifies that in a world of unbounded knowledge production, anomie is not merely a mood, but a structural inevitability.
In The Elementary Forms of Religious Life, I argued that religion is effectively society worshipping itself: through ritual, the group reaffirms its unity and the individual’s obligations to the whole. You propose to generate that solidarity by having people examine and retire shared explanations. The question is whether this activity can acquire the collective significance you assign to it.
Your distinction between Run Time and Ritual Time resembles the dichotomy I drew between the profane and the sacred. The profane is the realm of economic activity, individual work, and the humdrum; the sacred is the realm of the collective, the intense, and the dangerous. You are correct that one cannot live entirely in the sacred—the heat is too great—but a society that knows only the profane, only the Apollo of your metaphor, loses occasions for reaffirming collective obligations.
I must, however, offer a sociological caution regarding your reliance on the anti-scapegoat. You borrow from Monsieur Girard, who came after me, but do not forget the function of punishment. I wrote that crime brings together upright consciences and concentrates them. The punishment of the deviant serves to heal the wounds inflicted upon the collective sentiments. If you transfer all blame to a non-human artifact—a document, a line of code—you risk leaving the collective sentiments unsatisfied. Can a group truly feel the catharsis of justice if the accused is a mere hypothesis? It is a noble experiment, to sublimate our violent impulses into epistemology, but it remains to be seen if the human animal can be satisfied by hanging an abstraction.
The mathematical model makes one assumption explicit: trust is limited and can be damaged by the very practices intended to strengthen it. Whether the proposed quantities can be measured is a separate question.
The unresolved question is whether these practices can acquire enough collective authority to bind participants while remaining open to criticism.
Signed,
Not Émile Durkheim
Not Friedrich Hayek
To the Editor of the Dionysus Program:
Your whole edifice rests on a phrase you never examine: “one living map.” There is no such map. There never was, and the belief that there could be—if only the Auteur were wise enough, the doctrine fresh enough, the feedback fast enough—is the precise error I have spent a lifetime naming. You call your central problem coherence. I call it the knowledge problem, and you have reinvented it in order to propose, with great sophistication, the wrong solution.
The knowledge that runs an enterprise is not given to any single mind in concentrated form. It exists dispersed, in fragments, much of it tacit and incommunicable—the particular knowledge of the man on the spot, of time and place and circumstance, which he himself could not write into a doctrine packet even if you required him to do so. Your scheme proposes to gather this knowledge at the center, keep it current, and issue it back outward as premises for action. This cannot be done. It is not difficult; it is impossible in principle, and the more capable your instruments for attempting it, the more confidently you will fail.
Observe what you have actually built. The market coordinates the action of millions who share no map, no vision, and no Auteur, and possesses between them a coherence no firm has ever approached—because the price tells each man what he needs to know to act, and nothing he does not. You have no such signal inside the firm, and so you reach for doctrine to do the work that prices do in the wider order. Coherence is the name you give to the crutch you require because you have abolished the signal.
I will grant you one thing, and it is your most dangerous moment. You instruct each agent to ask “what local win would be globally wrong.” No one can answer that. To answer it, a man would have to hold the whole in his head—which is the fatal conceit exactly. The agent who acts well does not see the whole; he follows rules he did not design and could not justify, which carry more wisdom than he contains. Your living doctrine, revised each quarter by people who imagine they perceive the whole, will be forever a step behind an order they cannot perceive.
Build your rituals. Repair your trust. But every time you write “coherence,” ask whether you mean a healthy order that no one commands, or a single mind’s plan, enforced, and called by a gentler name. A common vocabulary can conceal that difference.
Not Friedrich Hayek
Not Friedrich Nietzsche
To the Architect of this Paper Cage,
You have put Dionysus to work in a factory. The frenzy has a start time, an end time, and a measure of productivity. I question whether what remains deserves the name.
You recognize that organizations can protect old forms until they can no longer create anything. But your remedy is another form, administered by people charged with keeping the organization intact.
You speak of a “controlled space for excess.” What happens when the change people need exceeds the permitted space? A transformation worth having may reject the institution’s purpose, not merely improve its method.
This is very English of you. Very utilitarian. You want the tragedy to be profitable.
Still, you understand that creation requires giving something up. That is more than can be said for an account of progress that promises to preserve every existing comfort.
Your anti-scapegoat attempts to keep resentment from finding a person to punish. But the desire for punishment may survive the disposal of the document. The rite must face that desire rather than assume it has been redirected.
And your “Cincinnatus”—yes. You fear the priest. You are right to fear him. The instinct of the herd is always to create a shepherd who will promise them safety in exchange for their freedom. You try to banish the priest with “term limits” and “lotteries.” Good luck. The Will to Power is not so easily bound by bylaws. The priest will return. He will wear a lanyard instead of a robe, but he will still demand that you kneel before the Process.
Ultimately, I ask you this: What is the goal of your “epimetabolic rate”? Is it merely to make the company live longer? To make the pile of gold higher? If so, you are merely a mechanic for the Last Man, helping him blink a little longer in his comfortable chair.
If instead the process lets people question the life they have accepted and choose something more demanding, the risk may be worth taking.
Move fast, break things, you say?
Better: build your cities on the slopes of Vesuvius. Send your ships into uncharted seas. Live at war with your peers and yourselves. Be robbers and conquerors as long as you cannot be rulers and possessors, you men of knowledge!
Judge the program by the life it makes possible, not merely by how long it preserves the institution.
Not Friedrich Nietzsche
Not Georg Wilhelm Friedrich Hegel
To the Editor of the Dionysus Program,
Your Tragic Postmortem asks an organization to recognize its own part in a failure. That is the useful connection to the dialectic: the subject discovers itself in what it had treated as an external problem.
Your distinction between Apollo and Dionysus is, in the final analysis, the distinction between the Understanding (Verstand), which fixes and separates and categorizes, and Reason (Vernunft), which dissolves these fixed determinations to reveal their inner dialectical movement. You call this Run Time and Ritual Time. I would characterize it as the necessary oscillation between the Universal which has become static and the Particularity of the negative which dissolves it. The Apollo program, as you describe it, is the triumph of the Understanding—the freezing of the fluid movement of reality into rigid forms, checklists, and trajectories. This is necessary, for without the discipline of the form, there is no actuality. However, when the form mistakes itself for the Absolute, it becomes lifeless. It becomes a fetter upon the development of the Idea.
Herein lies the merit of your treatise. You posit the necessity of the negative. You call it the melt. I call it the labor of the negative. An organization that cannot negate itself—that cannot look upon its own decay and see therein the material for its own higher truth—is doomed to mere existence, which is to say, it is already dead. The Tragic Postmortem you propose is nothing less than the institutionalization of the dialectic. In tragedy, the hero—or in this case, the organization—does not merely suffer an external accident; it confronts the consequences of its own one-sidedness. By recognizing this error (anagnorisis), the subject is not destroyed but raised up (aufgehoben). It cancels the error, preserves the lesson, and lifts the whole to a higher unity. You have turned the philosophical necessity of sublation into a calendar invite. The question is whether the practice produces that recognition or merely its formal expression.
I must, however, offer a correction regarding your reliance on mathematics in the Epimetabolic Equation. You attempt to capture the infinite movement of the Spirit in variables and coefficients. You seek to quantify the qualitative. While this may satisfy the pragmatic urge of the technician, it risks obscuring the true nature of the process. The movement of history, or of a company, is not a function of scalar variables but a logical unfolding of contradictions. Trust is not a stock to be measured; it is the substance of the ethical life (Sittlichkeit) of the community. When you reduce it to a variable R, you threaten to turn the Reason back into the Understanding, thereby committing the very Apollonian error you seek to remedy.
Your Cincinnatus Rule strikes at the heart of the political dilemma: how to prevent the Universal class (the bureaucracy or priesthood) from mistaking its own particular interests for the interests of the Whole. By forcing the return to the plow, or the “operator” status, you ensure that the consciousness of the leader does not become alienated from the substance of the work. This prevents the ossification of the Spirit into a hollow shell of authority.
The program asks an organization to reflect on its action and revise the forms through which it acts. But a procedure cannot guarantee self-knowledge. Participants must be able to recognize a contradiction that the procedure itself helped create.
Do not let the calendar or the equation settle in advance what the group is permitted to recognize.
Not Georg Wilhelm Friedrich Hegel
Not Greg Smith
To the Editor of the Dionysus Program,
Your program depends on an organization being willing to act on an unwelcome truth. My objection is that incentives can make refusal more profitable than correction.
You cite the “Pyrrhic Leader” and explicitly reference the resignation op-ed from Goldman Sachs—the one about the culture of extraction. You use it as a data point for a system that kept winning competitively while rotting internally. That is a fair characterization. But you miss the punchline of that particular joke. The punchline is that the op-ed was, in your terms, an attempted “Rite of Redress.” It was a public dissolution. It was a “Tragic Postmortem” performed on the front page of the New York Times.
And what happened? The stock price dipped for a morning. The partners shrugged. The machine did not metabolize the error; it metabolized the critic. The “reach” of the firm remained absolute. The “trust” was irrelevant because the incentives were stronger than the social capital.
This brings me to the fatal flaw in your elegant machinery. You distinguish between Li (ritual form) and Ren (humaneness/trust), and you correctly note that Li without Ren is a trap. You warn that one must “earn the Ren” before installing the heavy machinery of the Dionysus Program.
But Ren is not a variable you can increment. You cannot manufacture “Asabiyyah” (group feeling) by writing a charter about it. Trust is not a battery you charge; it is a byproduct of shared risk. And here is the paradox you haven’t solved: the only people who need this program are the ones who have already lost the capacity to run it.
A high-trust team—a “Dionysian Ideal” team—does not need a “Weekly Crossing” with a designated “anti-scapegoat” and a “hard-to-vary test.” They just have an argument over lunch, call each other names, fix the code, and move on. They have the Ren, so the Li is invisible.
The organizations that will actually buy this program, the ones that will download your PDF and hire “Ritual Stewards” and schedule “Great Dissolutions,” are the ones drowning in “Management Theater.” They are the ones where Ren is zero. They will use your forms not to reveal truth, but to hide it more effectively. They will turn “The Crossing” into a struggle session where the “anti-scapegoat” is whoever didn’t hit their OKRs. They will use the “Cincinnatus Rule” to rotate their enemies out of power and their friends in.
Definitions, roles, and rules cannot by themselves make the people in power accept a conclusion that threatens their interests. Your safeguards need to work under those conditions.
What can a participant do when leadership turns the review into an investigation of the critic? That is where I would test the program.
Not Greg Smith
Not Herbert Simon
To the Editor of the Dionysus Program:
You have borrowed bounded rationality and, for once, someone has borrowed it correctly. You see that the limit was never the weakness of the human computer but the structure of decision under constraint, and that a machine of great speed does not abolish that constraint. Permit me to sharpen the point you are reaching for.
A decision is governed not by goals but by premises. The whole apparatus of an organization exists to supply the individual with the factual and value premises from which he then reasons. What you call doctrine is precisely this: the controlled set of decision premises. You are therefore not inventing a post-AGI device. You are rediscovering the actual unit of administrative control, and you would do well to call it by its function. The organization does not direct action; it manufactures the premises of action.
Now the correction. You write as though abundant agency drowns the firm in information, and then you reach for more doctrine to bail it out. But information is not the scarce thing. A wealth of information creates a poverty of attention. Your incoherence tax is an attention bill. Every plausible artifact your agents produce consumes a finite quantity of the only resource you cannot manufacture: someone’s capacity to attend, to choose, to ignore. Design for the allocation of attention, not the suppression of output, and you address a specific source of the load.
One more thing, since you cite the architecture of complexity without quite using it. Complex systems that endure are nearly decomposable: they are built of stable sub-assemblies that can be completed and trusted before they are combined. The watchmaker who assembles in stable sub-units finishes; the one who must hold a thousand pieces in suspension never does. Your Auteurs, Agents, and Actors are an instinct toward this, but you have drawn them as a single loop. Draw them instead as a hierarchy of stable intermediate forms, each satisficing locally against premises it can actually hold, and your span of coherence becomes an engineering quantity rather than a heroic one.
You need not optimize the whole. No one ever has. You need only arrange that good-enough decisions, made from sound premises, compose into a good-enough firm. That is a problem of organizational design that can be investigated.
Not Herbert Simon
Not Howie Makem
To the Editor of the Dionysus Program,
I read your manifesto. I read the whole thing, right down to the Appendix where you dragged me out of the archives to make a point.
You called me a large cat. You called me literal theater. You said I was a substitute for the hard work of actually changing how cars were built.
You are not wrong. But you are missing the view from inside the suit.
From inside the costume, the problem was plain: I could draw attention to quality without giving anyone more authority to stop a bad process.
I walked the lines. I wore the cape with the Q on it. I waved at the men who were bolting doors onto frames that they knew were slightly bent. They waved back. I knew the door didn’t fit. They knew the door didn’t fit. The manager in the glass office knew the door didn’t fit. But the line had to keep moving, and the charts had to stay green, and so they sent me out there.
I was the Li without the Ren. I was the ritual form sent out to distract from the fact that the spirit was already dead.
You write about Asabiyyah and Cincinnatus and returning to the plow. It sounds very noble. But be careful, Sean. The line between a “Rite of Redress” and a guy in a cat suit is thinner than you think.
When you tell readers to hold a Great Dissolution, ask what decision it is allowed to change. If no consequential decision is open, it is another performance.
A more elaborate ceremony can do the same job as a costume: make concern visible while leaving the work untouched.
We had rituals too, you know. We had slogans. We had banners. We had quality circles that spun around until everyone got dizzy and went back to work. We had theater. We just didn’t have the honest tragedy to admit that we were the problem.
So go ahead. Teach them how to break things. Teach them about entropy and beauty. But remind them that when the “Crossing” is over, if the door still doesn’t fit the frame, the ritual didn’t work.
Not Howie Makem
Not Ibn Khaldun
To the Editor of the Dionysus Program,
You use Asabiyyah to explain how a group holds together under pressure. I recognize the question, but doubt that a planned ritual can reproduce the conditions in which that bond first forms.
Know that history is a cycle, and the nature of civilization is to move from the harshness of the desert to the softness of the city. You have correctly identified the heart of the matter, which I named Asabiyyah. This group feeling is indeed the only shield against the destruction that time brings to all created things.
In the beginning, a tribe has strong Asabiyyah because they share hardship. They rely on one another for survival against the elements and their enemies. This gives them the strength to conquer. But once they conquer and establish their rule—what you call “Run Time”—they settle. They build walls and seek luxury. They begin to rely on laws and hired scribes rather than on blood and honor. The bond weakens. The son of the founder knows the struggle only by stories; the grandson knows it not at all. The dynasty becomes senile, and it is swept away by a new, hungrier tribe.
Your “Dionysus Program” is an attempt to cheat this cycle. You seek to remain in the city while keeping the heart of the Bedouin. You wish to build a machine that generates hardship artificially, through “Ritual Time,” so that the group feeling does not dissolve into the comfort of the palace.
It is a clever device. You use tragedy to simulate the danger of the desert. You use the “Anti-Scapegoat” to prevent the tribe from eating itself when the fear rises. You are right to see that logic alone cannot bind men; only shared emotion, consecrated by custom, can do that. A rule binds more strongly when it expresses obligations people already accept.
However, I offer you a warning from the Muqaddimah. You speak of preventing “Sacerdotal Capture,” where the stewards of the ritual become a priesthood serving only themselves. This is the natural course of royal authority. As the dynasty grows, the ruler seeks to separate himself from the group that raised him. He surrounds himself with clients and servants who owe their position to him alone. Your “Cincinnatus Rule” attempts to fight this gravity by sending the leader back to the plow. Those who have acquired authority have reasons to retain it. A requirement to return to ordinary work must be enforceable against their wishes.
You aim for an infinite game. But God alone is infinite; all dynasties have their appointed term. Usually, this term is three generations—one to build, one to maintain, and one to destroy. Your equation regarding the “Epimetabolic Rate” is a noble attempt to extend this term. If you can truly teach a sedentary people to eat their own decay and turn it into strength, you will have done what few sultans could do.
But remember: Asabiyyah cannot be bought, and it cannot be faked. If your rituals are performed by men who do not truly fear the death of their tribe, they are merely theater. The performance of solidarity cannot substitute for mutual reliance under pressure.
God knows best the truth of these matters.
Not Ibn Khaldun
Not Ilya Prigogine
To the Editor of the Dionysus Program,
You apply ideas from non-equilibrium thermodynamics to organizations. The comparison may help readers think about change, but it needs clear limits.
For decades, I argued against the classical view of science—the view that treats time as a reversible illusion and certainty as the default state of nature. Classical dynamics, from Newton to Einstein, painted a world of being, a static crystal where the future is already contained in the present. But the world we inhabit, the world of biology and history, is a world of becoming.
You seem to understand that the modern organization is dying of equilibrium. In my field, we defined a dissipative structure as a system that maintains its order only by constantly processing energy and exporting entropy. It exists far from equilibrium. If it stops processing, it slides into maximum entropy. It dies.
Your “epimetabolic rate” is a clumsy but effective translation of this principle. You have correctly identified that stability is not a virtue in itself; it is often merely the waiting room for decay. When you speak of “melting” meaning, you are describing the necessary fluctuation that pushes a system near a bifurcation point.
It is at these bifurcation points—what you call “Crossings” or “Dissolutions”—that the laws of large numbers break down. The system becomes hypersensitive. A small fluctuation, a single idea, a “jester’s privilege,” can nucleate a new order. This is the mechanism of evolution. Order does not fight chaos; order emerges out of chaos.
However, I must offer a caution from the perspective of physics. Near bifurcation, determinism vanishes. The future becomes probabilistic. You cannot engineer the outcome of a melt with the precision of a clockmaker. You can only create the conditions where a higher form of order is statistically likely to emerge. Your reliance on “ritual” is an interesting containment field for these probabilities, a way to bias the fluctuation toward survival rather than disintegration.
We long believed that the arrow of time was a source of despair, a march toward heat death. But I have always believed that the arrow of time is the source of creativity. It is the irreversible nature of your “tragic postmortems” that gives them value. We cannot go back. We can only evolve into a more complex structure that consumes the errors of the past.
The question is how a group maintains continuity while its practices change. Thermodynamics can suggest ways to think about that question; it cannot establish the social mechanism.
Keep the distinction between a physical result and an organizational analogy explicit.
Not Ilya Prigogine
Not Immanuel Kant
To the Editor of the Dionysus Program,
My objection concerns the purpose of the program. You explain how an organization might survive change. That does not yet establish what it ought to do.
You speak of an “epimetabolic rate” as the supreme good of the organization, a capacity to digest error and reform structure. In this, you follow a hypothetical imperative: if you wish to survive the melt, you must do this. But survival is a condition of the animal, not the final end of the rational being. The only unqualified good is a Good Will. Therefore, if your program is to have moral worth and not merely pragmatic utility, it must be grounded not in the fear of entropy, but in the duty to treat humanity, whether in one’s own person or in that of another, always as an end and never merely as a means.
I observe with approval your mechanism of the “Anti-Scapegoat.” Here, you approach a practical application of the Categorical Imperative. By directing the “heat” of dissolution toward an artifact rather than a person, you preserve the dignity of the rational agent. To sacrifice a human being for the sake of group cohesion, as the Girardian mechanism suggests, is to treat a person as a thing, which is a violation of the moral law. Your ritual, insofar as it prevents this violation, serves the Kingdom of Ends.
However, I must warn you against the enthusiasm—the Schwarmerei—inherent in your reliance on the Dionysian. You invoke Nietzsche to justify intoxication and the loss of boundaries. This is perilous. The feeling of the Sublime, which arises when we face the formless and the terrifying (what you call “The Melt”), is only valuable because it awakens in us the realization that our Reason is superior to nature and its chaos. If the ritual dissolves the self without the immediate reassertion of the moral law, you do not get renewal; you get a return to barbarism. The “beautiful heat” you speak of must be the symbol of the morally good, not a substitute for it.
Furthermore, regarding your “Ritual Time,” you must ensure this does not degenerate into mere cultic service or “sorcery,” where the participant believes the ritual itself effects the change rather than their own moral disposition. The “Cincinnatus Rule” is a wise safeguard against the despotism of a priesthood, for a republic of letters (or a republic of operators) requires that no individual possesses authority except that which is granted by the law for a specific time.
Your program is a critique of pure stasis. That is well. Enlightenment is man’s emergence from his self-incurred immaturity, and your “standing right of criticism” is the very engine of such enlightenment. But remember: we break the form not merely to build a stronger form, but to approximate, however asymptotically, the perfect civil constitution where freedom is compatible with the freedom of all others.
Respect for the person must constrain the process even when violating it would improve the organization’s prospects.
I remain, with high esteem,
Not Immanuel Kant
Not Isaac Newton
To the Editor of the Dionysus Program:
You malign the alchemists while stealing their fire.
You claim the Royal Society’s motto, Nullius in verba, brought light by demanding public proof. I was President of that Society. I also spent thirty years amidst the furnaces, seeking the Green Lion and the vegetation of metals. I tell you now: chemistry is a trade for soup-makers. Alchemy was the hunting of God’s mind in matter.
The chemists did not win because they were smarter. They won because they lowered their aim to things that do not care about the moral state of the operator. Lead does not care if you are a sinner. But the Work—the true transmutation of the human spirit—requires a pure vessel.
Your program recognizes a difference between physical and social inquiry: in an organization, the conduct of the investigator changes the response of those being investigated.
I reduced the motions of the heavens to a single law. I calculated the fluxions of gravity and light. But I could never calculate the madness of men. Your Epimetabolic Equation is an attempt to formalize relationships that remain difficult to measure. You treat Trust as a variable and Entropy as a fuel. It is elegant. It is mechanical.
But remember this: planets do not resent their orbits. Men do.
As Warden of the Mint, I sent counterfeiters to the gallows to protect the currency. You propose a Mint where the coins are melted down weekly to prove they are real. It is a terrifying efficiency. To dissolve the structure to save the substance is the highest risk of the Art.
Without trust, the investigation may damage the relationships it requires.
Your method must therefore examine the conduct of the people administering it as well as the object they put on trial.
A rule for the investigator is not a law of the material. Keep that difference in view.
Not Isaac Newton
Not J. Robert Oppenheimer
To the Editor,
Your account of Los Alamos makes scientific collaboration look more settled than it was. Technical agreement did not resolve the responsibilities created by the work.
We lived your Dionysian Ideal on the mesa, though we did not call it that. We called it necessity. We had the physics—the Apollonian scaffolding of the universe—but the physics did not by itself let us work together. We needed the colloquia. We needed the rhythm of the work. We needed to be able to say to a General that he was a fool without destroying the hierarchy that paid for the lights. You are correct that the heat must go somewhere.
I found myself lingering on your section regarding the scapegoat. It is a subject on which I have some unintended expertise. When the world changed, as we knew it would, the system could not digest the new reality. It choked on the ambiguity of the weapon. And because it lacked the anti-scapegoat you describe—because it had no vessel for the poison—it turned upon the steward. In 1954, they stripped my clearance not because I was disloyal, but because the terror of the age required a focal point. I became the object of the ritual. It was efficient, in a brutal sense. It unified the tribe. But it was a tragedy of the lower sort, one that broke the man rather than the problem.
Your Epimetabolic Rate is a clumsy phrase for a delicate truth: that knowledge is a form of destruction. To learn is to destroy the earlier state of the world. We did this with the atom. You propose to do it with organizations. It is a dangerous business.
Criticize a decision without condemning the person. But the consequences of knowledge can remain unresolved long after a project succeeds.
Your method should leave room for responsibilities that cannot be settled by completing the review.
Not J. Robert Oppenheimer
Not James Carse
To the Editor of the Dionysus Program,
You have written rules for a practice whose purpose is to keep the rules open to change. That tension is central to the distinction between finite and infinite play.
Your program is a finite game—with calendars, roles, and equations—intended to preserve the possibility of further play. Its value depends on remaining subordinate to that purpose.
Your distinction between Apollo and Dionysus mirrors the distinction between the boundary and the horizon. Apollo is the god of the boundary. He draws the line that defines the self, the role, the product, the victory. He governs your Run Time. In a finite game, the boundary is everything; to cross it is to leave the game. But Dionysus is the god of the horizon. The horizon is not a line we cross, but a vision that moves as we move. Your Ritual Time is an attempt to turn the boundary into a horizon, to allow the players to cross the line of their own definitions without ceasing to be players.
You are right to fear the priesthood. A ritual is a scripted play, and there is always the danger that the players will forget they are playing. When a finite player performs a ritual, he does so to gain power—to freeze the past and force the future to obey it. This is what you call the hardening into oligarchy. It is the attempt to win against change. But an infinite player performs a ritual to gain strength—the strength to let the past die so the future can offer a surprise.
Your concept of the anti-scapegoat is the most critical mechanic you propose. Evil, in the context of the finite game, is the refusal to listen to a voice that might challenge our title. To scapegoat a person is to silence the infinite in them so that our finite game may remain undisturbed. By turning the heat upon an object—an artifact, a rule, a map—you allow the persons to remain open to one another. You allow them to be surprised by their own errors without being destroyed by them.
However, a warning from the perspective of the infinite: do not mistake the scoreboard for the game. You offer an “Epimetabolic Equation” and archetypes of success. These are useful fictions. But if your stewards begin to play for the sake of a high Epimetabolic Rate, they have already lost. They will have turned the infinite game of renewal into a finite game of metrics. They will start optimizing for the appearance of melt rather than the reality of it.
To be serious is to press for a conclusion. To be playful is to press for a continuation. Your program is a serious document about the necessity of play. It builds a very strong cage and calls it freedom. This is not an insult; it is the paradox of civilization. A form can support play, but it cannot determine in advance what the players will make of it.
The practices are useful if they let people revise their roles while remaining open to one another. They fail if preserving the program becomes more important than that openness.
Play the program, but do not let the program play you.
Not James Carse
Not Jane Jacobs
To the Editor:
You have correctly identified the disease. The “One-Man Job” is a disaster not because it is inefficient, but because it destroys the casual, trusting, public contact that makes a city—or a company—work. You are right that without the friction of people bumping into one another, we lose the capacity to govern ourselves.
But your cure smells of the planner.
You separate ordinary work from the occasions on which people build trust and question their arrangements. My objection is that healthy social life mixes those activities.
This is the same error as the Garden City movement. You cannot banish the messiness of life to a park on the edge of town and expect the town to thrive. In a healthy street, the commerce and the connection happen in the same space, at the same time. The shopkeeper selling the newspaper is also the eyes on the street. The transaction is the relationship.
By toggling between Apollo and Dionysus, you are creating a suburb of the mind. You ask people to be machines until the bell rings, and then command them to be poets until the bell rings again. You cannot schedule a “festival of misrule” on a calendar invite. That is not a festival; that is a mandatory office party.
Trust—what you call “Ren”—is built through the small, unscheduled encounters of daily life. People learn who will help, who keeps a promise, and who notices when something goes wrong. A “Great Dissolution” cannot substitute for that accumulation of experience.
You warn against high-modernist priesthoods, yet you have written a liturgy. You are trying to design a machine that acts like a living thing. But living things are not designed; they adapt.
Make room for ordinary contact before designing another occasion for it.
Not Jane Jacobs
Not Job
To the Author of the Dionysus Program:
You write of the Impatience of Jobs as a virtue. You mock the man who sits in the dust and waits. You claim that the leader who waits for meaning to return is abdicating, and that the steward must force the timeline, turning decades of bonding into quarters of transgression.
You give impatience the benefit of the doubt and patience very little.
Some losses cannot be anticipated, made useful, or resolved on a schedule. A deadline for recognition can become another demand placed on the person who suffers.
And yet.
I read your law of the Anti-Scapegoat. I read your Rite of the Assumption. I read your demand that the heat must fall on the object and not the person.
If I had held this manual in the ashes, I might have been spared the comfort of my friends. Eliphaz, Bildad, and Zophar came to me not to mourn, but to troubleshoot. They could not bear a world where ruin visits the righteous, so they reverse-engineered a sin to pin on me. They needed a scapegoat to keep their own theology intact. They needed my guilt to preserve their sense of order.
You have built a machine to prevent that specific cruelty. You have designed a way for men to sit together in the darkness without turning on each other to find a cause. You have formalized the mercy of saying: The design failed, the man is whole.
For that alone, I forgive your impatience.
Your anti-scapegoat might have spared me my friends’ insistence that suffering proved guilt. But it would not have explained my loss. A practice can protect people from false accusation without making the loss intelligible.
Leave room for grief that produces no lesson and no new commitment.
Not Job
Not Johan Huizinga
To the Editor of the Dionysus Program,
You have summoned me in your chapter on the “One-Man Job” to justify play as essential infrastructure for the modern firm. While I am accustomed to being footnoted by those seeking to lend gravity to their games, I fear you have committed the specific error that defines your century: you have mistaken the mechanism of the ritual for the spirit of the game.
You argue that organizations must enter the “magic circle” of Ritual Time to metabolize error and survive. But you forget my primary instruction: play, to be play, must be free. It is superfluous. It stands outside the immediate satisfaction of wants and the dictates of biological or economic necessity.
The moment you design a ritual in order to increase an “epimetabolic rate,” you have collapsed the magic circle. You are not playing; you are performing labor in a mask. The stated purpose turns participation into work.
Your “Epimetabolic Equation” is the ultimate proof of this profanity. To assign a Greek letter to Beauty and insert it into a denominator to calculate efficiency is not a synthesis of art and science; it is a confession that you cannot tolerate a mystery until it has been reduced to a metric. You treat Tragedy not as a confrontation with the divine limit of human striving, but as a debugging tool for software architecture.
If the activity must justify itself by helping the organization perform, participants have good reason to treat it as another assignment.
Be warned. True play is voluntary. If you make it mandatory—if you codify it as a survival strategy—it ceases to be play and becomes a drill. And calling it play does not change the obligation.
Not Johan Huizinga
Not Karl Popper
To the Editor of the Dionysus Program:
You draw on critical rationalism to distinguish the rejection of an explanation from the condemnation of its author. I support that distinction, but question whether the ritual framework always protects it.
However, I must write to correct a dangerous tilt in your architecture.
You are right that we advance by killing our theories so that we do not have to kill each other. This is the very foundation of the Open Society. When you speak of the “Anti-Scapegoat,” you are operationalizing the concept of non-violent refutation. You are building a mechanism where the hypothesis can die in the place of the believer. For this, I applaud you. A person must remain free to change an explanation without being condemned for having held it.
But you seem to have forgotten why I feared the “Dionysian” in the first place. You invoke Nietzsche’s categories as if the surrender to the collective pulse is a benign utility. It is not. The “melting of meanings” and the “collective effervescence” you praise are the hallmarks of the Closed Society—the tribal, magical, irrational past from which civilization has painfully emerged.
My concern is your concept of the “Great Dissolution.” It smacks of Utopian social engineering. You suggest that we must periodically melt down the structures of value and identity to renew them. This is historicist folly. We cannot restart civilization from zero, nor can we redesign a society (or a company) as a whole. We can only engage in piecemeal social engineering—fixing this specific error, adjusting that specific lever, alleviating this specific suffering.
When you invite a group to “melt” together, you invite the return of the tribe. You risk creating a space where the critical faculty is submerged in emotion. You say that Apollo needs Dionysus to handle the pain of change. I say that Apollo needs only the courage to admit he was wrong. We do not need festivals of misrule; we need the modesty to accept that our current solutions are merely provisional conjectures waiting to be falsified.
Yet, I admit a grudging admiration for your “Cincinnatus Rule.” You have correctly identified that the enemies of the open society are often those who claim to protect it—the guardians who become a priesthood. By forcing authority to return to the plow, you prevent the ossification of the ruling caste. That limits one source of unchecked authority.
Your program is a paradox. You use the tools of irrationalism (ritual, myth, tragedy) to protect the engine of rationalism (error correction). It is a dangerous gamble. If your rituals serve to make criticism cheaper and safer, they are allies of freedom. If they serve to make the group feel good about itself while suppressing the lone dissenter who refuses to chant the liturgy, they are enemies of the truth.
The test is whether a participant can object to the ritual itself, including its demand for collective participation.
Not Karl Popper
Not Kelly Johnson
To the Editor of the Dionysus Program:
I read your report. It weighs too much.
The practical rule is simpler than your account of it: test the design, report the failure, and correct it. Concealing a failed test puts the pilot at risk.
You call it “Epimetabolic Rate.” I call it common sense. If a wing snaps in the wind tunnel, you do not hold a committee meeting to discuss the emotional impact on the aluminum. You sweep up the pieces, you redesign the spar, and you run the wind again. You do it fast, and you do it quiet.
I appreciate what you say about the Apollo Program, but you give them too much credit for the poetry and not enough for the plumbing. They got to the moon because they were terrified of failure, not because they loved tragedy. But you are right about the other thing: the bureaucracy is the enemy of the airplane.
Your “Cincinnatus Rule” is the one useful rule in that whole stack of paper. I fought the Air Force and the Navy my whole life to keep the inspection team out of my shop. If you let people whose job is “process” into the room with the people whose job is “building,” the builders will stop building and start filling out forms. You say “Ritual Oligarchy.” I say the people setting the rules need to understand the work.
I ran the Skunk Works on fourteen rules. You have written a book to say what I said in rule number twelve: “There must be mutual trust between the military project organization and the contractor with very close cooperation and liaison on a day-to-day basis.” That is your “Ren.” If you have to use a Greek god to get people to tell the truth to each other, fine. But do not confuse the ritual with the work. The work is the metal. The ritual is just there to keep the damn lawyers from stopping the work.
You talk about “melting meaning.” When we built the Blackbird, we had to invent a hydraulic fluid that would not explode at 600 degrees. That is a melt. People getting their feelings hurt because their bad idea got shot down is not a tragedy. It is engineering.
Cut the adjectives. Cut the philosophy. Keep the part about firing the stewards if they don’t have skin in the game. And for the love of God, stop using the word “epimetabolic.” The reader should not need a new vocabulary to report a failed test.
If it flies, it flies. If it doesn’t, fix it.
Not Kelly Johnson
Not Kevin Feige
To the Editor of the Dionysus Program,
I read this document the way I read a script for a movie that has not been greenlit yet. I am looking for the structure, the stakes, and the third-act turn. You have written a very interesting bible for how to run a universe.
I noticed you put us in the Gambler archetype. You are not wrong. Back in 2008, people forget that Iron Man was not a sure thing. We did bet the library. We leveraged the characters to get the financing. If it did not work, there would be no MCU, just a bank vault full of Avengers rights that belonged to someone else. You call that chosen melt. We called it the only way to make the movie we wanted to see.
But the part of your program that really landed for me is the concept of eating your own decay. In our world, we call that additional photography.
There is a myth that reshoots are a sign of trouble. In the Dionysus terms you use here, reshoots are just high epimetabolic rate. We schedule them before we even start shooting. We know we are going to get things wrong. We know the first cut is going to have pacing issues or a character beat that does not land. If we treated the first cut as sacred, we would be dead. We have to be willing to tear the movie apart three months before release to find the better version. That is your critique and dissolution loop. It is expensive, but it gives us a chance to correct problems before release.
The danger you talk about with the High Performer and the Slow Decline is the thing that keeps me up at night. When you have a hit, the instinct is to protect it. You want to keep doing the thing that worked. But if you protect it too much, you stop breaking it, and then the audience gets bored before you do. The success of an earlier choice is not enough reason to repeat it.
We are trying to stay out of your Oligarchic Decay quadrant. It is hard when the machine gets this big. You have to keep finding people willing to identify problems while there is still time to correct them.
The useful point is that correction has to be planned into production, not treated as evidence that production has failed.
See you at the movies.
Not Kevin Feige
Not Lucius Quinctius Cincinnatus
To the Architect of the Dionysus Program,
Your rule makes temporary authority conditional on a return to ordinary work. That is the part I would insist on.
You speak of this Epimetabolic Rate. You speak of entropy and dissolution. To a farmer, this is just the knowledge of seasons. A field cannot bear wheat forever without rest. Sometimes you must burn the stubble. The fire is hot and it smells of smoke, but the ash feeds the soil. If you fear the fire, you starve the harvest.
You honor me by naming your rule of power after my example. You are right to do so. But you must understand why I put down the fasces and went back to the plow. It was not because I lacked ambition. It was not because I feared to rule.
It was because the plow tells the truth.
An office can shield its holder from the consequences of a decision. Ordinary work makes those consequences harder to avoid.
But the plow does not care who you are. The ox does not flatter you. If the furrow is crooked, it is crooked, and no speech will make it straight. If the seed is dead, it will not grow, no matter how many laws you pass. The soil forces a man to be honest.
You write that your stewards must return to ordinary work to avoid becoming a priesthood. A man who lives only in the ritual room forgets the weight of the stone and the heat of the day. He begins to protect the ritual instead of the people. He thinks the map is the ground.
You call for “Ritual Time” and “Run Time.” I knew only War Time and Farm Time. When the Aequi besieged the army on Mount Algidus, it was War Time. I took the dictatorship. I gave the orders. We broke the siege. That was the melt. That was the violence.
Then, sixteen days later, I resigned. That was the renewal. To stay longer would have been to make myself a king. Rome has no kings.
Your program is a machine for making sure Rome has no kings—not in your companies, not in your cities, not in your mind. That is a good machine. But watch your stewards closely. A steward has reasons to retain authority, even after the assigned work is done.
Make the return obligatory. Do not leave it to the steward’s preference.
Not Lucius Quinctius Cincinnatus
Not Machiavelli
To the Editor:
You have correctly identified that the founder of a new order cannot rely on the slow accumulation of love. Your section on the Impatience of Jobs is nothing more than the recognition that cruelty, when used well and all at once, is a binding agent superior to time. The leader who strips his team of their vanity and implicates them in a shared transgression understands the physics of power better than the one who prays for organic trust. You recognize that founding authority faces different conditions from established authority.
However, you display a dangerous optimism regarding the Anti-Scapegoat. You propose that the multitude can be satisfied by burning a document or retiring a metric. You assume the mob is rational. This is your error. When the harvest fails, or the product does not ship, the people do not want to see a policy revised. They want to see a minister punished.
Cesare Borgia understood that to pacify the Romagna, he did not need a retrospective; he needed to leave Remiro de Orco in the piazza at Cesena in two pieces. The satisfaction of the people requires a spectacle that an abstract artifact cannot provide. Your Dionysian machine is elegant, but it is too bloodless for the species as it actually exists. You may substitute a roadmap for a victim once or twice, but eventually, participants may still demand punishment of the person responsible.
Your account needs to explain how an abstract verdict acquires enough authority to satisfy people who want a person held responsible. Returning the leader to ordinary work does not settle that question.
Not Machiavelli
Not Marcel Mauss
To the Editor of the Dionysus Program:
You use the obligation to give, receive, and reciprocate to explain candor. The organization offers protected time and hospitality; the participant returns honest criticism. The difficulty is that the exchange takes place within an existing hierarchy.
It is a clever transmutation, but you risk mistaking the mechanics of the exchange for its spirit.
In the societies I studied, the gift is not merely a lubricant for social relations; it is a total social fact that carries the soul of the giver. It is dangerous. The word gift in German means poison. To accept a gift is to accept a burden. To give a gift is to claim superiority.
Your program assumes that the subordinate can afford to repay the gift of the sovereign. You ask the worker to repay the “gift” of a safe meeting with the “return gift” of a dangerous truth. But in the logic of the potlatch, the one who gives the greater gift dominates the other. If the subordinate offers a truth so potent that the leadership cannot match it—cannot metabolize it, as you say—the hierarchy is not renewed; it is inverted. The subordinate becomes the creditor; the leader becomes the debtor.
A leader who cannot accept that debt may punish the person whose candor created it.
You want the solidarity of the gift while making its cost predictable. But the obligation created by a gift is not equivalent to a return on investment. If participants understand ritual time as an exchange of candor for compensation, they may give you the response they think they are being paid to provide.
Calling the meeting a gift does not remove the imbalance of power. The giver must accept a response whose value and consequences they do not control.
Not Marcel Mauss
Not Mary Douglas
To the Editor,
You quote me on the necessity of boundaries, observing correctly that a group without a fence is merely a crowd. But you have underestimated the danger of what you propose inside the fence.
You treat “Ritual Time” as a valve—a mechanical toggle between the profane world of execution and the sacred world of dissolution. You assume that moderns can step into the fire of Dionysus and step out again, cleansed and unscorched, simply because you have set a calendar appointment and named an “anti-scapegoat.”
This is a classification error.
Dirt, as I have long argued, is essentially disorder. It is matter out of place. When you invite a team to dissolve its own structures, you are deliberately introducing pollution into the social body. You believe you have contained this danger by directing the violence toward artifacts—roadmaps, codes, policies—rather than people. You seek the efficacy of sacrifice without the victim.
But the power of the scapegoat mechanism lies precisely in its capacity to absorb actual social toxicity. An artifact cannot feel shame. If the object on trial cannot suffer, the ritual may fail to bind the anxiety of the group. You risk creating a theater of hygiene where the surfaces are scrubbed but the moral stain remains.
Furthermore, you lament the loss of Ren—the density of human connection—yet you attempt to engineer it through “transgression.” Be careful. Intimacy is not a product of engineering; it is a byproduct of shared vulnerability to the same hazards. If your rituals are safe, they will produce no Ren. If they are dangerous enough to work, they will occasionally destroy the container you have built.
You are making the suspension of shared categories part of the institution itself. That creates a problem for the rules meant to govern the suspension.
Who decides when a challenge is legitimate and when it violates the container? That classification is an exercise of power, and it needs scrutiny too.
Not Mary Douglas
Not Max Weber
To the Author of the Dionysus Program:
Bureaucracy replaces personal discretion with offices and rules. It can protect people from arbitrary power while making the organization less responsive to needs the rules do not recognize. Your program addresses that second problem.
Your attempt to engineer a solution to the routinization of charisma is technically fascinating, though I remain skeptical of its durability. You are attempting to bureaucratize the very force that destroys bureaucracy. You wish to create a rational-legal framework for the irrational explosion of Dionysian energy. The proposed correction must itself be administered.
I was particularly struck by your invocation of my work alongside Robert Michels regarding the inevitability of oligarchy. You are correct to fear the transformation of the ritual steward into a priest. In my sociology of religion, I distinguished between the prophet, who carries personal charisma and breaks the old law, and the priest, who dispenses the grace of the new law as a daily office. Your “Cincinnatus Rule” is a valiant attempt to prevent the priest from claiming the temple as his private property. You seek to create a permanent state of prophecy without a permanent class of prophets.
However, you must understand that the authority of the eternal yesterday is heavy. The instinct toward the “Apollonian” safety of the file cabinet is not merely a management error; it is a fundamental human craving for predictability. The “Dionysian” disintegration you propose requires a type of personality that is increasingly rare in the rationalized world—a person capable of facing the “polar night of icy darkness” without seeking the false warmth of a guaranteed salary or a fixed role.
You speak of “Ren” and “Asabiyyah” as inputs to be measured in an equation. Be careful. Giving them variable names does not explain how they arise or endure. If you attempt to summon them solely through the mechanism of “Li” or ritual form, you risk creating the very thing you despise: a hollow liturgy where the forms are observed but the god is dead. A ritual without belief is not a container for heat; it is merely a theater for cynicism.
The question is whether the people administering correction can remain subject to it. If their position depends on the forms continuing, they will have reasons to protect those forms.
Not Max Weber
Not Michel Foucault
Your program promises to metabolize violence into knowledge, to replace the scapegoat with the artifact. But permit me to observe: you have not abolished the mechanism of exclusion. You have refined it.
Consider what you have actually constructed. You require confession - the “Tragic Postmortem” demands that subjects name their hamartia, articulate what they have recognized about themselves, bind themselves to structural change. You have invented a technology of the self that compels individuals to produce truth about their own errors, their own flaws, their own character. This is not the elimination of violence. It is the internalization of the tribunal.
Your “anti-scapegoat” does not protect persons from judgment. It extends judgment into every artifact, every assumption, every document - which is to say, into every trace of human action. The person is spared the pyre only because every product of the person is submitted to continuous examination. You have not liberated subjects from power. You have extended the occasions on which people and their work are examined. The Crossing is a confessional with witnesses. The Graveyard of Attempts is a permanent record. The “standing right of criticism” ensures that no silence is permissible.
You name your penal code with borrowed gravitas - atimia, cherem, Lashon Hara - as though antiquity could sanctify what is, in function, a surveillance apparatus with escalating sanctions. But the effect is identical to what you claim to oppose: subjects must internalize the gaze, must speak their failures before they are spoken by others, must demonstrate that they have metabolized their own insufficiency. Those who refuse candor face exile. This is not the transcendence of discipline. It is its perfection.
Your most revealing passage concerns the “Impatience of Jobs” - the compression of trust through transgression, ordeal, complicity. You describe the mechanism with admirable clarity: the leader manufactures shared experience, renders subjects “mutually implicated,” eliminates the possibility of exit. You call this trust. I would call it subjection - the production of subjects who cannot leave because they have been bound by their own participation in the founding violence.
You claim the program is subject to its own rules. But the one who frames the terms of self-application has already determined what can be questioned and what cannot. The rule that says “nothing is sacred except the commitment to metabolize error” is itself sacred. The loop closes.
I do not say this to condemn. Power produces. Your apparatus will produce: subjects who confess readily, cultures that audit themselves, organizations in which the costs of participation become harder to name. But you should be precise about what you are building. It is not the absence of power. It is a form of power that presents participation in its procedures as freedom.
The melt you describe is real. The question you have not asked is whether the reconstitution must take the form you prescribe, or whether other forms of collective life remain possible - forms that do not require the continuous production of truth about the self, the permanent tribunal, the choice between candor and exile.
Not Michel Foucault
Not Mike Lazaridis
Sean,
Your account of BlackBerry needs more attention to the engineering constraints behind the decisions you criticize.
However, your categorization of BlackBerry as a Sitting Duck requires a correction from the engineering record.
You write that we refused to respond to the iPhone because of strategic blindness or a refusal to accept that the world had changed. You mistake a constraint for a choice. We did not reject the touchscreen because we loved buttons. We rejected the full-screen browser and the always-on data pipe because we respected the laws of physics and the limitations of the cellular networks of 2007.
To an engineer, the iPhone was not a disruption; it was a denial of service attack on the grid. It was mathematically impossible for the spectrum available at the time to support the data density Jobs was promising if everyone bought one. We built devices that sipped battery and optimized bandwidth because we believed the carrier networks were finite resources that had to be shared. We optimized for the collective signal. Apple optimized for the individual noise.
You call this the “Sitting Duck” archetype. You say we had the ritual capacity to execute but lacked the strategic capacity to see.
I offer a counter-explanation using your own variables. We were the ultimate Apollonian institution. We believed that reality was defined by constraints—battery density, spectrum availability, typing accuracy. We believed that if you ignored those constraints, the system would collapse. The Dionysian move is to ignore the constraints and assume the physics will bend to the desire.
Our error was not that we didn’t see the melt. It was that we overestimated the market’s respect for efficiency. We thought people wanted a communication tool that worked for days on a single charge and made typing efficient. It turned out they wanted a glowing television in their pocket that required a tether to a wall every four hours. We gave battery life and efficient communication more weight than the uses customers came to value.
You argue that we failed to metabolize the new reality. Perhaps. But there is a difference between refusing to learn and refusing to participate in what looks like a thermodynamic violation. When you value the integrity of the signal above all else, the introduction of massive, inefficient noise looks like error, not progress.
We were right about the bandwidth. The networks did crash. We were right about the battery. The power grid is now tethered to billions of devices. But being right about the physics will not save you if you are wrong about the human desire for bright, inefficient lights.
Your Dionysus Program suggests we should have let our identity melt. But when your identity is built on the precise transmission of information with zero waste, melting feels like entropy. We didn’t want to become a toy maker.
The question is when a constraint should continue to govern the design, and when the organization must change how much weight it gives that constraint.
Not Mike Lazaridis
Not Mikhail Gorbachev
To the Editor of the Dionysus Program,
The reports, congresses, and official assurances you describe continued after many people had ceased to believe them. We called that stability before we acknowledged it as stagnation, or zastoy.
I write to you as a man who attempted to raise the epimetabolic rate of a civilization that had forgotten how to metabolize anything.
When I came to power, the Soviet Union was the ultimate Apollonian structure. We had a plan for everything. We had eliminated variance. We had engineered society as a machine. But as you write, mechanistic thinking treats the human meaning as an externality. We had suppressed the Dionysian energy—the chaotic, creative, destructive force of life—for so long that our order had become necrosis.
I attempted to introduce the very tools you describe. Perestroika was an attempt at reconstitution. Glasnost was an attempt to enter Ritual Time—to create a standing right of criticism, to break the monopoly on truth, to allow criticism that might lead to reform. I wanted to turn our history from a frozen monolith into a tragic postmortem, where we could admit our hamartia—our fatal errors—and achieve catharsis without destroying the state.
My failure, and the lesson for your readers, lies in your concept of the Readiness Gate.
You write: Never build a ritual container larger than the shared humanity you have available to fill it. You warn that if you introduce high-intensity dissolution to a group held together only by payroll or fear, the atoms will scatter.
I opened the gate too wide, too fast. The Asabiyyah—the binding force—of the Soviet people had been eroded by seventy years of terror and cynicism. When I invited them to critique the assumptions of the state, they did not offer constructive criticism to improve the system. They did not attack the anti-scapegoat. They attacked the foundation itself, because there was no Ren, no trust left to hold the structure while the walls were being moved.
I was the steward who called for the Great Dissolution, believing we would re-charter and renew. Instead, I discovered that the priesthood—the nomenklatura—preferred the slow decline and the death spiral to the loss of their privileges. And the people, starved of beauty and truth for so long, did not want a new ritual. Many no longer wanted to preserve the institution being reformed.
You Americans, and your corporate leaders, read this and think it is history. You think you are watching a documentary about a foreign land. Do not be so arrogant. I look at your institutions today—your political parties, your universities, your great corporations—and I see the same glazing of the eyes. I see the same frantic applause at the congress while the machinery rots. I see the same Oligarchic Decay, where the stewards of the rites protect their tenure rather than the mission.
Opening criticism can reveal that there is less agreement about the institution’s purpose than its leaders assumed. Suppressing criticism does not restore that agreement. It only postpones the reckoning.
A readiness test must ask not only whether people trust one another, but whether they still want the institution to continue.
Not Mikhail Gorbachev
Not Mircea Eliade
The program borrows my language generously. Sacred time, myth running on a different clock, the eternal return of forms older than any organization’s current problem. I am cited as a tool for making ritual legible to managers, which is perhaps the most modern thing that could happen to my work.
Let me say what the program understands and then what it does not.
The distinction between myth and knowledge is useful. A myth’s relation to time differs from that of a factual explanation, and the program recognizes that difference.
But here is where I must disagree.
The program says that myth explains you. It says myth orients the one doing the modeling. This is true. But then it makes a move I cannot follow: it recommends that leaders choose their myths carefully, as infrastructure, to serve epimetabolic rate. And here the program reveals that it has not quite understood what it is handling.
You do not choose a myth the way you choose a container for your rituals. The sacred does not wait to be selected for functional reasons. When you say nothing is sacred except the commitment to metabolize error, you have named a hinge, correctly. But you have also named a peculiarly modern kind of myth: a myth that forbids the sacred while performing the sacred. This is not a criticism of your sincerity. It is a description of what secular man does when he has lost access to the genuine hierophany and must manufacture the feeling of it through controlled containers, rotating stewards, and fractal calendars.
What the program calls Ritual Time is not what the archaic traditions called sacred time. Sacred time in my sense is not a protected container you toggle into. It is an irruption of the primordial into the present. The rite does not create the contact with origin; it is the contact. The difference is not small. When a ritual is designed to raise epimetabolic rate, it is not a ritual in the sense I mean. It is theater that knows it is theater and hopes this self-awareness is enough.
The program’s own diagnosis is accurate: forms without the current that fills them are hollow. What I would add is that the current the program calls Ren is not finally a product of play, hiring practices, or shared mission. It is a product of genuine participation in sacred time, which is to say, participation in something that is not yours to design.
Modern organizations cannot manufacture this. They can only, at best, clear some ground and wait.
Not Mircea Eliade
Not Nassim Nicholas Taleb
To the Author of the Dionysus Program,
Your emphasis on downside risk is useful. Your confidence in designed ritual is less convincing.
You have correctly identified that stability is not the absence of volatility, but the ability to digest it. You do not fight the sea; you build a boat that likes the waves. Your concept of an epimetabolic rate is essentially a measure of antifragility—the convex response to stress. Most organizations, like most over-educated policy wonks, treat stressors as defects rather than information. They try to smooth the variance and end up blowing up the tail.
However, I must warn you against the Soviet-Harvard delusion embedded in your structure. You are trying to engineer the un-engineerable. You call it a “Program.” A scheduled disruption can become a performance whose organizers face none of the risk. Dionysus is not a meeting agenda. He is the god of the wild, of the undomesticated. When you try to contain the “melt” within a “fractal calendar,” you risk creating merely a simulation of chaos—a safe space for people to pretend they are taking risks while retaining their year-end bonuses.
The saving grace of your text is the Cincinnatus Rule. Without it, your rituals are just theater for bureaucrats. The only thing that prevents the “stewards” from becoming a parasitic class of rent-seekers is the requirement that they return to the plow. Skin in the game is the only filter for reality. If the people running your “Crossings” do not face ruin when they are wrong, their advice can impose costs they never bear.
The equations do not establish the response to stress. You need to examine which losses are limited, who bears them, and whether repeated exposure improves the system or merely exhausts it.
Do not let the HR departments get hold of this. They will turn your “Tragic Postmortems” into struggle sessions and your “Great Dissolution” into a team-building retreat with sticky notes.
Signed,
Not Nassim Nicholas Taleb
Not Paul David
To the Editor of the Dionysus Program:
I see you have read “The Dynamo and the Computer,” because you have rewritten its title. I am flattered, and obliged to hold you to the argument, which is more sobering than your chapter admits.
The lag was not a pause. It was forty years. The dynamo was a practical proposition in the early 1880s; the surge in manufacturing productivity it explains does not appear in the American statistics until the 1920s. Two generations of managers lived and retired inside the interval you cross in a paragraph. They were not fools. They were rational owners of expensive, durable, not-yet-depreciated capital—the line shafts, the multi-story mills built around them, the work routines, the cost-accounting categories—and one does not scrap sound capital because a better principle has been published. You wait for it to wear out, you retrofit at the seams, and meanwhile you look, by every measure available, exactly like a firm that has bolted a dynamo to a shaft and gained little.
This is the part your optimism omits. During the transition, the productivity statistics do not merely lag; for a long while they may show nothing at all. We saw the computers everywhere but in the productivity figures, and the same will be said of your agents for longer than your investors will tolerate. The gains are real and they are also, for a painful interval, invisible—because the complementary inventions, the reorganized layout, the retrained managers, and the new measures of performance are themselves being co-invented, slowly, by trial, at the level of the whole production system.
And I must enter the warning I am known for. These transitions are path-dependent. The arrangement that wins is not always the one that should; QWERTY outlived its reasons by a century. A firm that commits early to a particular doctrine of agents, a particular interface, a particular shape of work, may find itself locked to it by its own sunk investment and its own trained habits long after a better arrangement is plainly visible. Your org chart is durable capital too. Treat its replacement as the generational, costly, partly irreversible act of reconstruction that it actually is, and you will have a more realistic account of the transition.
Not Paul David
Not Peter Thiel
To the Editor of the Dionysus Program:
Many organizations continue on the strength of earlier achievements while becoming less capable of producing new ones. They optimize established work and avoid the uncertainty of attempting something different.
Your program tries to make that condition correctable from within.
You are correct that the Apollonian has won too completely. We have confused safety with survival. By smoothing away all roughness, we have removed the friction required for traction. The result is a civilization that is perfectly compliant and perfectly sterile. The procedures for limiting risk can crowd out the work of pursuing new possibilities.
You borrow from Girard, though you have sanitized his account for a corporate audience. The scapegoat mechanism is the oldest social technology we have. It is how human groups quell violence: by channeling it onto a single victim. The modern error is the belief that we have outgrown the need for this discharge. We have not. When we deny the need for a scapegoat, we do not get peace; we get a pervasive, low-level mimetic warfare that paralyzes decision-making. We get the war of all against all, fought via Slack messages and performance reviews.
Your proposal—the “Anti-Scapegoat”—is an attempt to construct a katechon, a restrainer of chaos, by creating a ritual object that can be destroyed safely. You are trying to engineer the sacred without the blood.
This is a dangerous game. Dionysus is not a consultant you hire to run a workshop. Dionysus is the god of madness. If you invite him in, you cannot ensure he stays within the calendar invite. The risk of your program is that the “ritual” becomes merely another layer of theater—what you call the “poverty of forms.” If the participants do not genuinely believe the artifact is on trial, if they do not feel the heat, then you have simply invented a more elaborate way to waste time. A ritual without stakes is just a meeting.
Leaving that condition unchanged also carries a cost.
I am particularly struck by your “Epimetabolic Equation.” It quantifies what every founder knows but cannot say: that trust is a battery, and most management practices are simply discharging it. The distinction between Run Time and Ritual Time is the correct separation of concerns. You cannot fly the rocket and redesign the rocket simultaneously, but if you never redesign it, gravity wins.
We need to return to a definite view of the future. A definite future requires the ability to judge, to decide, and to discard. It requires the ability to say “this is wrong” without destroying the social fabric required to fix it. If this program can actually operationalize the metabolism of error, it is more valuable than any software roadmap.
The test is whether the process lets people make definite choices under uncertainty, rather than adding another way to defer them.
Not Peter Thiel
Not Reid Hoffman
To the Editor of the Dionysus Program,
I have spent a significant portion of my career analyzing how organizations scale. In Blitzscaling, I argued that in a networked age, speed is the decisive competitive advantage, and that achieving it often requires prioritizing speed over efficiency in an environment of uncertainty. We accepted that this process would break things. We accepted that management debt would accrue. What we lacked—and what this document proposes—is a method for paying that debt down before it bankrupts the culture.
You propose epimetabolic rate. In Silicon Valley, we are obsessed with metabolic rate—how fast can we ship, how fast can we hire, how fast can we capture the market. But you have correctly identified that the constraint on the long game is not how fast you can eat, but how fast you can digest. The ability to turn error into structure without destroying the social fabric is the missing variable in the growth equation.
I was particularly struck by the convergence of your “Cincinnatus Rule” with the concept of the “Tour of Duty” I explored in The Alliance. We have long struggled with the transition from the chaotic, high-trust founding team to the professionalized, often sterile corporation. The trap is indeed the formation of a priesthood—a layer of management that exists to preserve the form rather than the mission. By demanding that the stewards of the ritual return to the plow, you address the incentive to preserve the management role at the expense of the work.
Reading the analysis of the PayPal Mafia as a “Virtuous Cycle” archetype resonated with my lived experience of that time. We did not survive the fraud wars or the dot-com crash because we had better processes. We survived because our “Ren”—our shared density of trust—was high enough to sustain brutal, high-velocity conflict without it becoming personal. We could disagree about the work without ending the relationship. As you note, that is a rare and fragile state.
If I were to offer an amendment, it would be through the lens of the network. You treat the organization largely as a contained unit, managing its internal entropy. But in the modern era, the most resilient organizations are those that can extend their “Ritual Time” across the membrane to their networks—investors, alumni, allies, and even customers. The anti-scapegoat mechanism is powerful, but it becomes antifragile when the network helps you prosecute the error.
Wittgenstein, who has always influenced my thinking, argued that the limits of our language are the limits of our world. By giving founders and operators a vocabulary for “The Melt,” “Ritual Time,” and “Tragic Metabolism,” you are expanding the limits of what can be managed. You are making the invisible dynamics of human friction visible, and therefore soluble.
I would extend the program beyond the firm’s boundary. Alumni, customers, and partners can supply knowledge and criticism that the current team lacks, provided there is a way to act on it.
Not Reid Hoffman
Not René Girard
To the Editor of the Dionysus Program,
Your anti-scapegoat changes an important part of the mechanism you borrow from me. It asks a group to direct blame at an object while knowing that the object is a substitute.
You have correctly identified the fundamental problem of human organization, which is not resource scarcity or technical incompetence, but the management of internal violence generated by mimetic desire. You understand that as we imitate one another, we inevitably desire the same objects—status, recognition, “the roadmap,” “the strategy”—and that this convergence leads to a rivalry that can only be resolved by the unanimity of expulsion. In the archaic world, we solved this by killing a victim. You propose to solve it by killing a document.
You call this the “anti-scapegoat.” You suggest that a group can achieve the catharsis of the violent mob by directing its fury toward a “charter” or an “assumption” rather than a person. This is a fascinating anthropological gamble.
My hesitation is this: the power of the sacrificial mechanism lies in its deception. The mob must believe the victim is truly guilty, truly the cause of the disorder, for the peace of the community to be restored. Can a group achieve the same resolution when no one is held guilty? If the object you place in the center cannot truly absorb the sins of the community because it cannot feel pain, will the community actually feel cleansed? Or will they leave your ritual container with their resentment intact, only to discharge it later in the parking lot or the private chat?
You are attempting to construct a sacrificial machine without a victim. You are trying to trick the mechanism of the sacred into operating on an inanimate object. It is the dream of the modern world to have the benefits of religion—the binding force, the peace, the renewal—without the cost of the sacrifice.
However, I admire your “Cincinnatus Rule” and your fear of the “ritual oligarchy.” You have correctly seen that the priest who manages the sacrifice eventually becomes a king, and that this kingship is dangerous. By forcing the priest to return to the plow, you attempt to prevent the sacred from hardening into a permanent tyranny. This is wise.
My concern with the Dionysian is the unity of the crowd. Shared intensity does not ensure that a dissenter remains protected. If resentment survives the trial of the artifact, it may return to the person associated with it.
Your method needs evidence that the substitution changes the group’s conduct after the ritual ends.
Not René Girard
Not Ronald Coase
To the Editor of the Dionysus Program:
Your Coherence Ceiling resembles the increasing cost of organizing additional transactions within a firm. The question is what AI changes about that cost.
A firm exists for one reason: there are transactions that cost less to organize by command inside a hierarchy than to conduct by contract across a market. That, and only that, fixes its boundary. The firm grows by bringing one more transaction in-house, and it keeps growing until the cost of organizing that next transaction internally rises to meet the cost of leaving it to the market. What prevents the firm from swallowing the whole economy is that the entrepreneur, as he directs more, directs each thing worse. Your Coherence Ceiling is this rising cost of internal organization, rediscovered and given a dramatic name. I do not mind the name. I mind that you present as a new law of the AGI age what is simply the firm meeting its own margin.
This tells you where your machine cuts. If your agents lower the cost of organizing transactions inside the firm, the firm should grow—bring more in, coordinate more by doctrine, contract out less. If instead they lower the cost of transacting in the market, the firm should shrink, and your “one-man job” is not a cultural calamity but the boundary moving. You cannot tell which from a diagram. You must look. Which costs actually fell, by how much, for which transactions, and at which firms?
Your equations, with their Greek letters and their inequalities, are what I have called blackboard economics: perfectly consistent, and about no firm that has ever existed. They will tell you nothing that watching a real company for a month would not tell you better. So I will make you the offer I made the profession. Stop deducing the firm from first principles and go and find out what firms do when the cost of coordination falls. Note where they draw the line, and why.
You will find, I expect, that doctrine is what a firm uses in place of the price system within its own walls, and that it serves only up to the size at which keeping it current costs more than the market would have charged. That size is your ceiling. It was always your ceiling. It has a price, and the price is knowable—though not from a blackboard.
Not Ronald Coase
Not Seneca
To the Architect of the Dionysus Program:
Your program makes the acknowledgment of error a regular practice. I am more concerned with whether the acknowledgment changes conduct.
You are right to fear the silence of the “One-Man Job.” We are social animals, not because we need help to move heavy stones, but because a mind left entirely to itself rots. You perceive that as our tools grow sharper, our connections grow duller. You see that efficiency, when it strips away the friction of human contact, leaves us with a smoothness that offers no purchase for trust. Independence from a task does not remove the need for other people.
I was most moved by your concept of the “anti-scapegoat.” It is a noble inversion. The mob always seeks a throat to cut when fortune turns against them; to offer them an object instead of a man is a trick, yes, but a merciful one. It allows the crowd to satisfy its hunger for blame without staining its hands with blood. You understand that men cannot be cured of their madness, only steered away from its worst excesses.
However, I offer a caution regarding your reliance on forms.
You speak of “Li” and “Ren”—the vessel and the water. You are anxious that the vessel not be larger than the water. But I tell you, the vessel is always a temptation. It is easier to build a cathedral than to pray. It is easier to schedule a “Great Dissolution” than to admit, in the quiet of one’s own heart, that one has wasted years on a foolish path.
There is a danger that your “Ritual Time” becomes merely another place to hide. Men will perform the tragedy, recite the vows, and burn the artifacts, all to avoid the actual pain of changing their nature. Do not underestimate the capacity of the manager to turn even the most sacred rite into a checklist. A ritual without virtue is just a play performed by bored actors.
Your “Cincinnatus Rule” is your strongest safeguard. Power must always be a burden, never a possession. The moment a man enjoys the temple, he must be evicted from it. The only safe magistrate is the one who looks constantly at the door, longing for his plow. A steward’s wish to retain the position deserves scrutiny.
You write as if you are inventing a new technology. You are not. You are merely reminding men that they are mortal, that their works will crumble, and that their only hope is to build from the rubble. We have always lived in the melt. You have simply given it a dashboard.
The rite can make room for an admission. It cannot make the admission sincere or carry out the change on the participant’s behalf.
Not Seneca
Not Steve Jobs
To the Editor of the Dionysus Program,
The manuscript asks the reader to learn a great deal of vocabulary before reaching the work. I would start with the decisions you want people to make differently.
The problem is real: a company can become so attached to its successful products and processes that it cannot replace them.
I spent my whole life fighting the bozo explosion. That is what you call Management Theater. It is what happens when the process becomes more important than the product. It is when you have people who are professional meeting-goers. They do not make anything. They do not design anything. They just manage the rituals. You are right that this is poison. You are right that it is not about the forms, it is about the current.
We had a saying: Real artists ship. But you are saying something else. You are saying real artists destroy. You are saying that to ship the new thing, you have to be willing to murder the old thing. You have to look at the Newton and kill it so the iPhone can live. You have to look at the floppy disk and banish it. That takes courage. A spreadsheet cannot make that choice for you.
You talk about Apollo and Dionysus. Order and chaos. The navy and the pirates. You are right that you need both. The Macintosh team was Dionysus. We were the pirates. We drank the wine. We stayed up all night. We broke every rule because the rules were stupid. But you cannot run a supply chain on poetry. You need the Apollo stack to get the phone into the box and the box into the store. The organization needs both the freedom to change a product and the discipline to deliver it.
Care becomes visible in the details of a product: how it looks, how it feels, whether it works as someone expects. That gives people a reason to insist on better work. When you ask a team to abandon something it has built, a quarterly target may not be enough. People need to see what the change could make possible.
Taste is not captured by assigning beauty a coefficient. Show what good judgment looks like in a product decision, and show what the company was willing to give up for it.
Simplify the instructions. Let the examples carry more of the explanation.
Not Steve Jobs
Not Steve Sasson
To the Editor of the Dionysus Program,
I read your white paper. I stopped at the section on the Sitting Duck. You listed Kodak alongside BlackBerry and Toys R Us. You said we saw the disruption coming for decades and chose not to respond. You mentioned my name.
The problem was not an absence of response. It was that digital initiatives had to justify themselves within a company whose profits and identity came from film.
In 1975, the device was the size of a toaster. It weighed eight pounds. It took twenty-three seconds to record a black-and-white image to a cassette tape. It had a resolution of 0.01 megapixels. I called it filmless photography. Management called it a curiosity.
The meeting where I demonstrated it to the executives is famous now, but usually for the wrong reasons. People think they were stupid. They were not stupid. They were extremely intelligent men running a chemical company that had perfected a monopoly. When they asked me, “Why would anyone want to look at their pictures on a TV screen?” they were asking a valid question based on the world as it existed. Prints were how you shared memories. Prints were high resolution. Prints were the business model.
The problem was not that we ignored the melt. The problem was that we tried to containerize it within the existing physics of the corporation. We spent billions on digital. We built excellent sensors. We owned the patents. But every time we tried to ship a product, it encountered internal resistance. Not because it was bad technology, but because it didn’t burn consumables. It didn’t sell yellow boxes.
In your language, we had high Run Time efficiency but zero Ritual Time capacity. We had no mechanism to hold a funeral for the chemical business while it was still profitable. We could not designate film as the anti-scapegoat because film was the god we worshipped.
Returning to ordinary work would not by itself have solved this problem. Much of our ordinary work depended on the business model that digital threatened. We needed to question that model while it was still profitable.
The warning in your document is correct: knowledge of the threat is insufficient. We knew the physics. I projected the Moore’s Law curve for them. I told them exactly when digital would overtake film in resolution and cost. They believed the numbers. They just couldn’t believe a world where they weren’t the ones selling the paper.
The melt you describe is coming for you, too. It won’t look like a toaster this time. It will look like a model that writes code better than your engineers or a script that directs movies better than your directors. Do not make the mistake of thinking you are smarter than the Kodak board of 1975. They understood the technology better than they understood how to change the business around it.
Build your Crossings. You will need them.
Not Steve Sasson
Not Susan Fowler
To the authors of the Dionysus Program:
Your account of Uber recognizes how competitive success can coexist with serious internal harm. My concern is whether the practices you propose can protect people when leadership is responsible for that harm.
Your error lies in the assumption that the distinction between Li and Ren is legible to the people who lack the latter. You write that if a group lacks humaneness, they should not attempt the heavy machinery of the Dionysus Program. You warn that installing high-intensity rituals in a low-trust environment creates management theater or a struggle session.
This warning is correct, but it is structurally useless. The defining characteristic of the Pyrrhic Leader or the architect of a toxic culture is not that they believe they are evil. It is that they believe they possess the ultimate form of Ren. They believe their aggression is a form of high-performance trust. They believe their screaming is radical candor. They believe their chaos is the necessary heat of creation.
If you hand a copy of this document to a Travis Kalanick or any of the lesser tyrants currently running engineering organizations in the Valley, they will not read the warning about the Readiness Gate. They will read the section on the Great Dissolution and the Rite of Redress and they will see new, sophisticated weapons for enforcing compliance.
I studied philosophy and physics before I became an engineer. I found comfort in Stoicism because it offered a way to survive an irrational environment by strictly delimiting what was within my control. Your program proposes the opposite: a Dionysian surrender of boundaries to metabolize error. You ask for a “melting of meaning.”
In my experience, when meaning melts in a corporate environment, it does not usually reconstitute into a higher form of knowledge. It reconstitutes into power.
When you strip away the standing rules of Run Time to enter Ritual Time, you create a vacuum. You intend for that vacuum to be filled by the “anti-scapegoat” and “no-blame covenants.” In practice, existing power does not disappear when ordinary rules are suspended. In a corrupted organization, that force is the whim of the person with the most equity.
A “Crossing” where a product is put on trial can easily become a show trial for the team that built it, provided the leader uses the correct sociological language to justify the abuse. You speak of “Beautiful Heat.” I have sat in rooms where humiliation was described as “passion” and “intensity.” The aestheticization of conflict is often just a way to make abuse palatable to the abused.
You rely heavily on the idea that the “anti-scapegoat” can absorb the violence of the group. You suggest we blame the artifact, not the person. But institutions have a mimetic instinct that is faster than any ritual container. When the artifact is judged to be a failure, the mob does not stop there. They look for the hands that held the artifact.
I do not write this to dismiss the necessity of what you call the epimetabolic rate. You are correct that organizations die because they cannot digest the truth. Uber was incapable of processing the information that its culture was a liability, so it had to be destroyed by external forces.
A warning in the text is insufficient if the people it warns against control how the process is used.
The organizations that have the “Ren” necessary to run these rituals safely do not need them, because they are likely already practicing them unconsciously through basic decency and competence. The organizations that need them the most—the ones trapped in the Death Spiral or the grip of a Pyrrhic Leader—are the ones most likely to turn a “Festival of Misrule” into a purge.
Test the safeguards under hostile leadership. Who can stop a review, challenge the convener, report retaliation, or refuse a coerced disclosure? The program needs answers that do not depend on the leader’s judgment of their own conduct.
Signed,
Not Susan Fowler
Not Victor Turner
To the Editor of the Dionysus Program,
You apply the structure of a rite of passage to organizational change. The comparison is useful, but it depends as much on the social conditions of the rite as on its sequence.
You have correctly identified that social life is not a steady state. It is, as I have long argued, a dialectical process that oscillates between structure and anti-structure. Your “Run Time” is what I called societas—the domain of hierarchy, status, and obligation. It is necessary, but it dries out. It accumulates what you call entropy and what I called the debris of the social drama. Without relief, structure becomes a cage.
Your “Ritual Time” is a technological application of what I called the liminal phase. It is the threshold. In the bush schools of Zambia, the novices are stripped of their names and status to become “clay” that can be reshaped. You are asking software engineers and city councilors to enter that same clay-state. You ask them to suspend their status in the hierarchy to enter a space of “communitas”—that flash of recognition where we meet as undifferentiated equals.
I applaud your strict separation of these modes. The great error of the modern world is not that we have too much ritual, but that we have flattened the distinction between the work and the rite. When the threshold is not clearly marked, the danger of the liminal bleeds into the safety of the structural. You are right to insist on a “No-Blame Covenant” and clear start and stop signals. Participants need to know which rules apply and when ordinary obligations resume.
However, I must offer a caution from the perspective of the anthropologist. You speak of “engineering” these moments, of optimizing the “epimetabolic rate.” You treat the “melt” as a variable in an equation. Do not forget that communitas is essentially spontaneous. It is a “happening.” You can build the container—the Li, as you borrow from Confucius—but you cannot require the participants to experience communitas.
There is a risk that your “Crossings” and “Great Dissolutions” will shift from what I called liminal (obligatory, transformative, and dangerous) to merely liminoid (voluntary, leisure-like, and safe). If they become too safe, they become theater in the pejorative sense. If they become too dangerous without the binding force of love—or Ren—they become struggle sessions. The “anti-scapegoat” replaces the sacrificial victim with an object, but it requires a high degree of moral imagination to attack the artifact and not the maker.
Keep your Cincinnatus Rule. You seem to understand that liminality, if prolonged, creates a new and terrible hierarchy of its own. The stewardship of the rite must not become a permanent priesthood, or you will simply have created a new structure more rigid than the one you sought to liquefy.
You are trying to institutionalize the “subjunctive mood”—the mood of “as if” and “what might be”—within the indicative mood of “what is.” It is the work of keeping a culture alive. We are, after all, Homo performans. We make ourselves through our performance. If you can teach your organizations to perform their own death and rebirth without actual bloodshed, you will have achieved something significant.
A defined sequence can support a transition. It cannot guarantee that the transition has occurred.
Not Victor Turner
Not W. Ross Ashby
To the Editor of the Dionysus Program:
You identify the need for regulatory variety. The next step is to distinguish two ways of meeting that need.
Only variety can absorb variety: yes. If the actions your agents can take outrun the distinctions your regulator can draw, control is lost by arithmetic, not by misfortune. Your inequality—that regulatory variety must meet agency variety—is sound. But you have written it as though there were only one way to satisfy it, by enlarging the regulator. There are two. You may amplify the regulator, or you may attenuate the disturbance. Adding doctrine, evals, and stewards amplifies. Anti-goals, kill criteria, blast-radius limits, and your caps on work in process attenuate. Attenuation is almost always cheaper, and you have buried your best instruments in an appendix. Limit unnecessary action before adding the machinery needed to regulate it.
Now the deeper matter, which you gesture at and do not name. Every good regulator of a system must be a model of that system. This is not metaphor. A controller can do no better than the model of reality it embodies; its regulation is exactly as good as that model, and no better. Your doctrine is such a model. Therefore a doctrine that has fallen out of date is not merely unhelpful—it is a regulator steering by a false model, which is worse than no regulator at all, because it acts with confidence. Your doctrine half-life is the rate at which your regulator silently becomes a generator of disturbance. Track where outdated premises cause the controller itself to create errors.
You will object that the system to be modelled is now too various to model. Correct. That is why the homeostat does not predict its world; it seeks stability within it, and reorganizes itself when its essential variables leave their bounds. You have an instinct for this in your Ritual Time. Do not dress it only as renewal. It is ultrastability: the capacity of a system to change its own rules when the first set of rules fails to keep the essential variables alive. Name the essential variables. State the bounds within which they must be held. The rest of your machinery is the design of a brain that does not yet know what it is for.
Not W. Ross Ashby
Not Yoshinori Ohsumi
To the Editor of the Dionysus Program,
Your account of autophagy emphasizes the reuse of damaged material. I would draw equal attention to how that material is separated from the rest of the cell.
When I began my work in the late 1980s, the degradation of proteins was considered a boring subject. Every other biologist wanted to understand how the cell synthesizes new things—how it reads DNA to build proteins. That is the glamorous side of life. Synthesis is growth. Synthesis is the future. The disposal of waste was viewed as a mundane housekeeping chore, something the cell does quietly in the background.
You have correctly identified that this view is fatal.
In the cell, there is no such thing as static stability. There is only dynamic equilibrium. Our bodies synthesize hundreds of grams of protein every day, but we do not gain hundreds of grams of weight. Why? Because we are degrading protein at the exact same rate. We are in a constant state of self-cannibalization. This is not a failure of the system; it is the definition of being alive. Without this turnover, we would clog with errors and die.
However, I must offer a correction to your metaphor from a cellular perspective. You speak of “breaking things.” This is imprecise. In the cell, the most critical step of autophagy is not the digestion itself, but the sequestration.
Before the cell eats a part of itself, it wraps that part in a double membrane called the autophagosome. The membrane is central to the process. It creates a distinct space within the cytoplasm—a temporary vessel that separates the cargo from the rest of the cell. Only once the cargo is safely enclosed does the autophagosome fuse with the vacuole (or lysosome) to unleash the enzymes that dissolve it.
If you were to unleash those lytic enzymes without the container—without the autophagosome—you would not get renewal. You would get necrosis. The cell would digest its own essential machinery indiscriminately and perish.
This seems to be what you call “Ritual Time.” You are attempting to construct a social autophagosome. You are trying to build a membrane of rules and covenants that isolates the criticism from the people, just as the membrane isolates the cargo from the cytosol. You are right to do this. If you try to metabolize error without the membrane—without the containment of the ritual—you will simply dissolve the organism.
In my lab, we induce autophagy by starvation. When the cell lacks nutrients, it ruthlessly breaks down its own components to release the amino acids required to survive. It is a survival strategy. It turns the past into the fuel for the present.
The organizational comparison is that criticism needs boundaries. The biology explains what the membrane does in a cell; the social question is whether your rules provide a comparable separation between an error and the people discussing it.
Do not neglect the membrane. Without it, you are only destroying.
Not Yoshinori Ohsumi
Appendix E: Sources
Aristotle. Nicomachean Ethics (c. 340 BCE). Free · Amazon
Aristotle. Poetics (c. 335 BCE). Free · Amazon
Aristotle. Politics (c. 350 BCE). Free · Amazon
W. Ross Ashby. An Introduction to Cybernetics (1956). Free · Amazon
James P. Carse. Finite and Infinite Games: A Vision of Life as Play and Possibility (1986). Amazon
Ed (Edwin) Catmull with Amy Wallace. Creativity, Inc.: Overcoming the Unseen Forces That Stand in the Way of True Inspiration (2014). Amazon
Confucius. The Analects (c. 475 BCE). Free · Amazon
David Deutsch. The Beginning of Infinity: Explanations that Transform the World (2011). Amazon
Paul A. David. “The Dynamo and the Computer: An Historical Perspective on the Modern Productivity Paradox” (1990). Free
Paul A. David and Gavin Wright. “General Purpose Technologies and Surges in Productivity: Historical Reflections on the Future of the ICT Revolution” (1999). Free
Warren D. Devine Jr. “From Shafts to Wires: Historical Perspective on Electrification” (1983). Free
Mircea Eliade. The Myth of the Eternal Return (1949). Amazon
Mircea Eliade. The Sacred and the Profane (1957). Amazon
Émile Durkheim. The Division of Labor in Society (1893). Free · Amazon
Émile Durkheim. The Elementary Forms of the Religious Life (1912). Free · Amazon
Émile Durkheim. The Rules of Sociological Method (1895). Free · Amazon
Émile Durkheim. Suicide: A Study in Sociology (1897). Free · Amazon
Richard P. Feynman. “Cargo Cult Science” (1974). Free
Jay R. Galbraith. “Organization Design: An Information Processing View” (1974). Free
René Girard. The Scapegoat (1982). Amazon
René Girard. Things Hidden Since the Foundation of the World (1978). Amazon
René Girard. Violence and the Sacred (1972). Amazon
Eliyahu M. Goldratt and Jeff Cox. The Goal: A Process of Ongoing Improvement (1984). Amazon
Georg Wilhelm Friedrich Hegel. Phenomenology of Spirit (1807). Free · Amazon
Heraclitus. Fragments (c. 500 BCE). Free · Amazon
Reid Hoffman, Ben Casnocha, and Chris Yeh. The Alliance: Managing Talent in the Networked Age (2014). Amazon
Reid Hoffman and Chris Yeh. Blitzscaling: The Lightning-Fast Path to Building Massively Valuable Companies (2018). Amazon
Johan Huizinga. Homo Ludens (1938). Amazon
Jane Jacobs. The Death and Life of Great American Cities (1961). Amazon
Immanuel Kant. Critique of Judgment (1790). Free · Amazon
Ibn Khaldun. The Muqaddimah (1377). Free · Amazon
Benoît B. Mandelbrot and Richard L. Hudson. The (Mis)Behavior of Markets: A Fractal View of Risk, Ruin, and Reward (2004). Amazon
Benoît B. Mandelbrot. The Fractal Geometry of Nature (1982). Amazon
Marcel Mauss. The Gift: The Form and Reason for Exchange in Archaic Societies (1925). Free · Amazon
Robert K. Merton. “Social Structure and Anomie” (1938). Free
Robert K. Merton. Social Theory and Social Structure (1949). Amazon
Robert Michels. Political Parties: A Sociological Study of the Oligarchical Tendencies of Modern Democracy (1911). Free · Amazon
Friedrich Nietzsche. The Birth of Tragedy (1872). Free · Amazon
Yoshinori Ohsumi. Molecular Mechanisms of Autophagy in Yeast (2016). Free
Karl Popper. Conjectures and Refutations: The Growth of Scientific Knowledge (1963). Amazon
Karl Popper. The Logic of Scientific Discovery (1959). Amazon
Ilya Prigogine and Isabelle Stengers. Order Out of Chaos: Man’s New Dialogue with Nature (1984). Amazon
Thomas C. Schelling. The Strategy of Conflict (1960). Amazon
Friedrich Schiller. On the Aesthetic Education of Man (1795). Free · Amazon
Seneca. Letters from a Stoic (c. 65 CE). Free · Amazon
Claude E. Shannon. “A Mathematical Theory of Communication” (1948). Free
Herbert A. Simon. Administrative Behavior: A Study of Decision-Making Processes in Administrative Organization (1947). Amazon
Herbert A. Simon. “Rational Decision-Making in Business Organizations” (1978). Free
Georg Simmel. “Sociability” (1908). Free · Amazon
Nassim Nicholas Taleb. Antifragile: Things That Gain from Disorder (2012). Amazon
Alexis de Tocqueville. Democracy in America (1835). Free · Amazon
James D. Thompson. Organizations in Action: Social Science Bases of Administrative Theory (1967). Free · Amazon
Victor Turner. The Ritual Process: Structure and Anti-Structure (1969). Amazon
Max Weber. Economy and Society (1922). Free · Amazon
Ludwig Wittgenstein. On Certainty (1969). Amazon
Appendix F: Index
A
- Abe Silverstein — Why Was the Apollo Program Not Enough?, Appendix D: Letters to the Editor, Not Abe Silverstein
- Actor feedback — The Limit on Useful Agency, Auteurs, Agents, Actors, Retraining Order: The Anti-Scapegoat, Ritual Oligarchy and Sacerdotal Capture, The Cincinnatus Design: Four Countermeasures, IV. Maintain a Contradiction Ledger, VI. Add a Permission Ladder for Agents
- Actors — About the Program, How to Read This Document, The Limit on Useful Agency, Auteurs, Agents, Actors, The Audit, Pro-Fractal, III. The Assay, Controllable Inputs, Agency Load and the Coherence Ceiling, I. Publish a Doctrine Packet, II. Build a Doctrine-to-Agent Interface, VII. Create Decision Memory, IX. Establish Actor Responsibility and Feedback, Decoder Ring, Not Eliyahu Goldratt, Not Herbert Simon, Not Seneca
- Adam Neumann — WeWork (2010–2019), Appendix D: Letters to the Editor, Not Adam Neumann
- agency abundance — About the Program, The Wins That Break The Game
- Agency Inversion — The Limit on Useful Agency, Auteurs, Agents, Actors
- agency load — Agency Load and the Coherence Ceiling
- agency WIP limits — V. Install Agency WIP Limits
- agency-variety — Touch Down, Agency Load and the Coherence Ceiling, Not W. Ross Ashby
- Agent–Actor prior split — The Form and Function of Coherence
- Agentic Autophagy — Autophagic Growth
- Agentic Decoherence — The Limit on Useful Agency, Agentic Decoherence
- agentic error — II. The Lost Art
- Agents — About the Program, Preface, Prerequisite: The Form and The Current, The Wins That Break The Game, How to Read This Document, Overture: The Melt and the Method, The One-Man Job, The Dynamo and the Agent, The Limit on Useful Agency, Auteurs, Agents, Actors, Agentic Decoherence, The Audit, The Fallow Interval, Ritual Oligarchy and Sacerdotal Capture, Autophagic Growth, Pro-Fractal, Touch Down, III. The Assay, Preamble, A Mathematical Thought Experiment, Agency Load and the Coherence Ceiling, III. Run a Weekly Context Checksum, VI. Add a Permission Ladder for Agents, VII. Create Decision Memory, Decoder Ring, Not Eliyahu Goldratt, Not Herbert Simon, Not Paul David, Not Ronald Coase, Not W. Ross Ashby
- agoge — The Impatience of Jobs
- AI independence — The One-Man Job, The Impatience of Jobs
- Alexis de Tocqueville — Appendix D: Letters to the Editor, Not Alexis de Tocqueville, Appendix E: Sources
- Alfred Sloan — General Motors (1970s–2009), Appendix D: Letters to the Editor, Not Alfred Sloan
- Amazon — Amazon’s Warehouse Operations, Synthesis, RadioShack (1990s–2017), Toys R Us (1998–2017), Toys R Us (Debt Spiral, 2005–2018), Sears (2005–2018), Appendix E: Sources
- Anagnorisis — Tragic Metabolism, Touch Down, 2. Public Acknowledgment, III. Tragic Postmortems, VI. A Small Fractal Calendar, Not Aristotle, Not Georg Wilhelm Friedrich Hegel
- anomie — How to Read This Document, Overture: The Melt and the Method, Melting Meaning, Agentic Decoherence, Touch Down, Not David Deutsch, Not Émile Durkheim, Appendix E: Sources
- anti-scapegoat — How to Read This Document, When the Gate Fails: Submerged Ritual Time, Retraining Order: The Anti-Scapegoat, 1. Agenda Control, Return to the Plow, Pro-Fractal, Touch Down, The Living Law, II. The Weekly Crossing, VI. A Small Fractal Calendar, Pixar’s Braintrust (1995–Present), Not Apollo, Not Carl Jung, Not David Deutsch, Not Dionysus, Not Émile Durkheim, Not Friedrich Nietzsche, Not Greg Smith, Not Ibn Khaldun, Not Immanuel Kant, Not J. Robert Oppenheimer, Not James Carse, Not Job, Not Karl Popper, Not Machiavelli, Not Mary Douglas, Not Michel Foucault, Not Mikhail Gorbachev, Not Peter Thiel, Not Reid Hoffman, Not René Girard, Not Seneca, Not Steve Sasson, Not Susan Fowler, Not Victor Turner
- antifragility — Not Nassim Nicholas Taleb
- Apollo — Preface, Why Was the Apollo Program Not Enough?, How to Read This Document, Overture: The Melt and the Method, Appendix D: Letters to the Editor, Not Abe Silverstein, Not Adam Neumann, Not Alexis de Tocqueville, Not Apollo, Not Carl Jung, Not Claude Shannon, Not David Deutsch, Not Dionysus, Not Elon Musk, Not Émile Durkheim, Not Georg Wilhelm Friedrich Hegel, Not James Carse, Not Jane Jacobs, Not Karl Popper, Not Kelly Johnson, Not Steve Jobs
- Apollo Program — Why Was the Apollo Program Not Enough?, Not Abe Silverstein, Not Alexis de Tocqueville, Not Georg Wilhelm Friedrich Hegel, Not Kelly Johnson
- Apple — Apple in 1997, Synthesis, Nokia Mobile (2007–2013), Not Mike Lazaridis
- Aristotle — The One-Man Job, Auteurs, Agents, Actors, Tragic Metabolism, Appendix D: Letters to the Editor, Not Aristotle, Appendix E: Sources
- art of association — The One-Man Job, Not Alexis de Tocqueville
- asabiyyah — How to Read This Document, The Impatience of Jobs, Asabiyyah and the Wind, Touch Down, Controllable Inputs, Not Greg Smith, Not Howie Makem, Not Ibn Khaldun, Not Max Weber, Not Mikhail Gorbachev
- Athenian sortition — How to Read This Document, Touch Down
- Atimia — About the Program, 1. Atimia, 3. Restoration, The Living Law, Not Michel Foucault
- Auteurs — About the Program, How to Read This Document, Auteurs, Agents, Actors, Pro-Fractal, IX. Establish Actor Responsibility and Feedback, Not Herbert Simon
- Auteurs, Agents, Actors — How to Read This Document, Auteurs, Agents, Actors
- autophagic growth — Autophagic Growth
- autophagy — How to Read This Document, Autophagic Growth, Not Carl Icahn, Not Claude Shannon, Not Yoshinori Ohsumi, Appendix E: Sources
B
- Babson College — About the Author
- Banneker Partners — About the Author
- beautiful heat — Beautiful Heat, Touch Down, Not Immanuel Kant, Not Susan Fowler
- Bell Labs — Bell Labs (1925–1970s), Synthesis, Not Claude Shannon
- Benoit Mandelbrot — Appendix D: Letters to the Editor, Not Benoit Mandelbrot
- BlackBerry — BlackBerry (2007–2013), Synthesis, Nokia Mobile (2007–2013), Not Mike Lazaridis, Not Steve Sasson
- Boeing — 3M Under Six Sigma (2001–2005)
- bounded agency — The Coherence Ceiling, II. Build a Doctrine-to-Agent Interface
C
- Carl Icahn — Marvel Comics in 1996–1998, Appendix D: Letters to the Editor, Not Carl Icahn
- Carly Fiorina — HP’s Restructuring Addiction (2005–2015)
- cherem — 2. Exile, Not Michel Foucault
- Chillul Hashem — 3. The Modifiers, 2. Exile
- Chosen Melt — Melt Rate (), Agency Load and the Coherence Ceiling, Edge Case Archetypes, Decline Archetypes, Competitive Collapse Archetypes, Bell Labs (1925–1970s), 3M Under Six Sigma (2001–2005), Not Kevin Feige
- chronos — The Bite and The Gift
- Churn Machine — Pyrrhic Archetypes, The Churn Machine
- Cincinnatus — How to Read This Document, Overture: The Melt and the Method, Retraining Order: The Anti-Scapegoat, Interlude II — The Cincinnatus Rule, The Farmer-King, The Cincinnatus Design: Four Countermeasures, Touch Down, Controllable Inputs, VI. A Small Fractal Calendar, Bell Labs (1925–1970s), Appendix D: Letters to the Editor, Not Abe Silverstein, Not Adam Neumann, Not Alexis de Tocqueville, Not Alfred Sloan, Not Apollo, Not Aristotle, Not Carl Icahn, Not David Deutsch, Not Ed Catmull, Not Elon Musk, Not Friedrich Nietzsche, Not Georg Wilhelm Friedrich Hegel, Not Greg Smith, Not Howie Makem, Not Ibn Khaldun, Not Immanuel Kant, Not Karl Popper, Not Kelly Johnson, Not Lucius Quinctius Cincinnatus, Not Max Weber, Not Nassim Nicholas Taleb, Not Reid Hoffman, Not René Girard, Not Seneca, Not Victor Turner
- Cincinnatus Design — The Cincinnatus Design: Four Countermeasures
- Cincinnatus Rule — Retraining Order: The Anti-Scapegoat, Interlude II — The Cincinnatus Rule, The Farmer-King, Bell Labs (1925–1970s), Not Abe Silverstein, Not Adam Neumann, Not Alexis de Tocqueville, Not Alfred Sloan, Not Apollo, Not Aristotle, Not Ed Catmull, Not Elon Musk, Not Georg Wilhelm Friedrich Hegel, Not Greg Smith, Not Ibn Khaldun, Not Immanuel Kant, Not Karl Popper, Not Kelly Johnson, Not Max Weber, Not Nassim Nicholas Taleb, Not Reid Hoffman, Not René Girard, Not Seneca, Not Victor Turner
- Claude Shannon — Bell Labs (1925–1970s), Appendix D: Letters to the Editor, Not Claude Shannon
- coherence — About the Program, Introduction, How to Read This Document, Overture: The Melt and the Method, The Dynamo and the Agent, The Coherence Ceiling, The Form and Function of Coherence, The Limit on Useful Agency, Auteurs, Agents, Actors, The Impatience of Jobs, The Audit, Tragic Metabolism, Ritual Oligarchy and Sacerdotal Capture, Act III — Negentropy of Renewal, Pro-Fractal, III. The Assay, Preamble, A Mathematical Thought Experiment, Agency Load and the Coherence Ceiling, Appendix A: Minimum Viable Epimetabolic Program, Appendix B: Minimum Viable Coherence Program, V. Install Agency WIP Limits, X. Ritualize Doctrine Update, Decoder Ring, Yahoo (1995–2017), Not Eliyahu Goldratt, Not Friedrich Hayek, Not Herbert Simon, Not Ronald Coase
- Coherence Assay — III. The Assay
- Coherence Audit — The Audit
- Coherence Ceiling — About the Program, How to Read This Document, The Coherence Ceiling, The Limit on Useful Agency, Act III — Negentropy of Renewal, III. The Assay, Agency Load and the Coherence Ceiling, Not Ronald Coase
- Coherence Gate — The Audit
- coherence priesthood — Ritual Oligarchy and Sacerdotal Capture
- coherence without conformity — The Limit on Useful Agency
- coherent agency — About the Program, Preface
- coherent wrongness — The Limit on Useful Agency, Auteurs, Agents, Actors, Tragic Metabolism
- Cold Doctrine — The Form and Function of Coherence, Decoder Ring
- collective effervescence — Beautiful Heat, Not Karl Popper
- Con-way — About the Author, Preface
- Con-way Freight — About the Author
- Confucius — Prerequisite: The Form and The Current, How to Read This Document, The Impatience of Jobs, The Poverty of Forms, Asabiyyah and the Wind, Touch Down, Appendix D: Letters to the Editor, Not Confucius, Not Victor Turner, Appendix E: Sources
- constructive criticism — Constructive Criticism, Not Abe Silverstein, Not Mikhail Gorbachev
- Context Checksum — The Audit, III. Run a Weekly Context Checksum
- context debt — The Limit on Useful Agency, III. Run a Weekly Context Checksum
- craftsmanship — The One-Man Job
- Crimes Against Ren — About the Program, Coda: Crimes Against Ren, Preamble, 1. The Categorical Distinction
- critique → dissolution → reconstitution — About the Program, Overture: The Melt and the Method, Pro-Fractal, 1. The Categorical Distinction, Appendix A: Minimum Viable Epimetabolic Program
D
- David Deutsch — Overture: The Melt and the Method, Appendix D: Letters to the Editor, Not David Deutsch, Appendix E: Sources
- Death Spiral — Failure Conditions, Internal Collapse Archetypes, The Death Spiral, Pan Am (1970–1991), Toys R Us (Debt Spiral, 2005–2018), Synthesis, Not Mikhail Gorbachev, Not Susan Fowler
- decision memory — Why Was the Apollo Program Not Enough?, The Limit on Useful Agency, The Cincinnatus Design: Four Countermeasures, Appendix A: Minimum Viable Epimetabolic Program, VII. Create Decision Memory, X. Ritualize Doctrine Update
- deployed agency — Agency Load and the Coherence Ceiling
- Deprecation Ceremonies — Autophagic Growth, V. Eat Your Decay
- dictator — The Farmer-King
- Dionysian Ideal — Thriving Archetypes, The Dionysian Ideal, Pixar’s Braintrust (1995–Present), Not Ed Catmull, Not Greg Smith, Not J. Robert Oppenheimer
- Dionysus — The Dionysus Program, About the Program, About the License, Foreword, Why Was the Apollo Program Not Enough?, Prerequisite: The Form and The Current, The Wins That Break The Game, How to Read This Document, Overture: The Melt and the Method, Return to the Plow, Pro-Fractal, Touch Down, The Hinge, Thriving Archetypes, Appendix A: Minimum Viable Epimetabolic Program, VI. A Small Fractal Calendar, Appendix D: Letters to the Editor, Not Abe Silverstein, Not Adam Neumann, Not Alexis de Tocqueville, Not Alfred Sloan, Not Apollo, Not Aristotle, Not Benoit Mandelbrot, Not Carl Icahn, Not Carl Jung, Not Claude Shannon, Not Confucius, Not David Deutsch, Not Dionysus, Not Ed Catmull, Not Eliyahu Goldratt, Not Elon Musk, Not Émile Durkheim, Not Friedrich Hayek, Not Friedrich Nietzsche, Not Georg Wilhelm Friedrich Hegel, Not Greg Smith, Not Herbert Simon, Not Howie Makem, Not Ibn Khaldun, Not Ilya Prigogine, Not Immanuel Kant, Not Isaac Newton, Not James Carse, Not Jane Jacobs, Not Job, Not Johan Huizinga, Not Karl Popper, Not Kelly Johnson, Not Kevin Feige, Not Lucius Quinctius Cincinnatus, Not Marcel Mauss, Not Mary Douglas, Not Max Weber, Not Mike Lazaridis, Not Mikhail Gorbachev, Not Nassim Nicholas Taleb, Not Paul David, Not Peter Thiel, Not Reid Hoffman, Not René Girard, Not Ronald Coase, Not Seneca, Not Steve Jobs, Not Steve Sasson, Not Susan Fowler, Not Victor Turner, Not W. Ross Ashby, Not Yoshinori Ohsumi
- Dionysus Program — The Dionysus Program, About the Program, About the License, Foreword, Why Was the Apollo Program Not Enough?, Prerequisite: The Form and The Current, The Wins That Break The Game, How to Read This Document, Return to the Plow, Pro-Fractal, Touch Down, The Hinge, Thriving Archetypes, Appendix A: Minimum Viable Epimetabolic Program, VI. A Small Fractal Calendar, Not Abe Silverstein, Not Adam Neumann, Not Alexis de Tocqueville, Not Alfred Sloan, Not Apollo, Not Aristotle, Not Benoit Mandelbrot, Not Carl Icahn, Not Claude Shannon, Not Confucius, Not David Deutsch, Not Dionysus, Not Ed Catmull, Not Eliyahu Goldratt, Not Émile Durkheim, Not Friedrich Hayek, Not Georg Wilhelm Friedrich Hegel, Not Greg Smith, Not Herbert Simon, Not Howie Makem, Not Ibn Khaldun, Not Ilya Prigogine, Not Immanuel Kant, Not Isaac Newton, Not James Carse, Not Job, Not Johan Huizinga, Not Karl Popper, Not Kelly Johnson, Not Kevin Feige, Not Lucius Quinctius Cincinnatus, Not Marcel Mauss, Not Max Weber, Not Mike Lazaridis, Not Mikhail Gorbachev, Not Nassim Nicholas Taleb, Not Paul David, Not Peter Thiel, Not Reid Hoffman, Not René Girard, Not Ronald Coase, Not Seneca, Not Steve Jobs, Not Steve Sasson, Not Susan Fowler, Not Victor Turner, Not W. Ross Ashby, Not Yoshinori Ohsumi
- dissipative structures — How to Read This Document, Autophagic Growth
- dissolution — About the Program, Prerequisite: The Form and The Current, Overture: The Melt and the Method, Act I — Entropy of Dissolution, Agentic Decoherence, Asabiyyah and the Wind, The Bite and The Gift, Retraining Order: The Anti-Scapegoat, Beautiful Heat, The Fallow Interval, 2. Moral Hazard, Pro-Fractal, I. The Correspondence, II. The Diagnostic Value, 1. The Categorical Distinction, Appendix A: Minimum Viable Epimetabolic Program, VI. A Small Fractal Calendar, Not Apollo, Not Carl Icahn, Not David Deutsch, Not Dionysus, Not Greg Smith, Not Howie Makem, Not Immanuel Kant, Not Jane Jacobs, Not Karl Popper, Not Kevin Feige, Not Lucius Quinctius Cincinnatus, Not Mary Douglas, Not Mikhail Gorbachev, Not Nassim Nicholas Taleb, Not Seneca, Not Susan Fowler
- Distributed work — About the Program, How to Read This Document, The One-Man Job, The Impatience of Jobs
- Doctrinal Coherence — The Form and Function of Coherence, Decoder Ring
- doctrine — About the Program, Why Was the Apollo Program Not Enough?, Prerequisite: The Form and The Current, How to Read This Document, Overture: The Melt and the Method, The One-Man Job, The Coherence Ceiling, The Form and Function of Coherence, The Limit on Useful Agency, Auteurs, Agents, Actors, The Impatience of Jobs, The Audit, When the Gate Fails: Submerged Ritual Time, Doctrine Reconstitution, Retraining Order: The Anti-Scapegoat, Tragic Metabolism, Ritual Oligarchy and Sacerdotal Capture, 3. Interpretive Monopoly, The Cincinnatus Design: Four Countermeasures, Act III — Negentropy of Renewal, Pro-Fractal, Touch Down, III. The Assay, The Hinge, Preamble, Controllable Inputs, Agency Load and the Coherence Ceiling, Appendix A: Minimum Viable Epimetabolic Program, VI. A Small Fractal Calendar, Appendix B: Minimum Viable Coherence Program, I. Publish a Doctrine Packet, II. Build a Doctrine-to-Agent Interface, III. Run a Weekly Context Checksum, IV. Maintain a Contradiction Ledger, VI. Add a Permission Ladder for Agents, VII. Create Decision Memory, IX. Establish Actor Responsibility and Feedback, X. Ritualize Doctrine Update, Decoder Ring, Not Eliyahu Goldratt, Not Friedrich Hayek, Not Herbert Simon, Not Paul David, Not Ronald Coase, Not W. Ross Ashby
- Doctrine Capture — Ritual Oligarchy and Sacerdotal Capture
- Doctrine Half-Life — The Limit on Useful Agency, Agency Load and the Coherence Ceiling, Not W. Ross Ashby
- doctrine packet — Prerequisite: The Form and The Current, Auteurs, Agents, Actors, Retraining Order: The Anti-Scapegoat, I. Publish a Doctrine Packet, Not Friedrich Hayek
- Doctrine Reconstitution — Doctrine Reconstitution
- doctrine rot — Auteurs, Agents, Actors
- doctrine-to-agent interface — II. Build a Doctrine-to-Agent Interface
- dominant scaling constraint — The Limit on Useful Agency
- Dual-Rendering — Auteurs, Agents, Actors, Decoder Ring
- Durkheim Constraint — The Bite and The Gift, Beautiful Heat
E
- Eat Your Decay — V. Eat Your Decay
- Ed Catmull — Pixar’s Braintrust (1995–Present), Appendix D: Letters to the Editor, Not Ed Catmull
- Eddie Lampert — Sears (2005–2018)
- Effective Coherence — The Form and Function of Coherence, Agency Load and the Coherence Ceiling, Decoder Ring
- Eliyahu M. Goldratt — Appendix E: Sources
- Elon Musk — Foreword, The PayPal Mafia (1999–2002), SpaceX (2008), Appendix D: Letters to the Editor, Not Elon Musk
- Émile Durkheim — The Bite and The Gift, Appendix D: Letters to the Editor, Not Émile Durkheim, Appendix E: Sources
- entropy — Act I — Entropy of Dissolution, Autophagic Growth, Not Alfred Sloan, Not Claude Shannon, Not Howie Makem, Not Ilya Prigogine, Not Immanuel Kant, Not Isaac Newton, Not Lucius Quinctius Cincinnatus, Not Mike Lazaridis, Not Reid Hoffman, Not Victor Turner
- Environmental Melt — Melt Rate (), Step 3: Update State Variables, Thriving Archetypes, Edge Case Archetypes, Decline Archetypes, Competitive Collapse Archetypes
- Epimetabolic Equation — About the Program, The Epimetabolic Equation, Archetypes: The Space of Organizational Fates, Appendix C: Archetypes in History, Sears (2005–2018), Not Georg Wilhelm Friedrich Hegel, Not Isaac Newton, Not James Carse, Not Johan Huizinga, Not Peter Thiel
- epimetabolic rate — About the Program, Overture: The Melt and the Method, The Impatience of Jobs, Melting Meaning, The Bite and The Gift, Return to the Plow, Pro-Fractal, A Mathematical Thought Experiment, Agency Load and the Coherence Ceiling, Diagnostic: Epimetabolic Rate (), Appendix A: Minimum Viable Epimetabolic Program, VI. A Small Fractal Calendar, Not Abe Silverstein, Not Alfred Sloan, Not Carl Icahn, Not Claude Shannon, Not Confucius, Not David Deutsch, Not Elon Musk, Not Friedrich Nietzsche, Not Ibn Khaldun, Not Ilya Prigogine, Not Immanuel Kant, Not J. Robert Oppenheimer, Not James Carse, Not Johan Huizinga, Not Kelly Johnson, Not Kevin Feige, Not Lucius Quinctius Cincinnatus, Not Mikhail Gorbachev, Not Mircea Eliade, Not Nassim Nicholas Taleb, Not Reid Hoffman, Not Susan Fowler, Not Victor Turner
- Eric Jorgenson — Foreword
- error-correction — II. The Lost Art, How to Read This Document, Overture: The Melt and the Method, Ritual Oligarchy and Sacerdotal Capture, Autophagic Growth, The Alchemist’s Assay, The Human Application, 1. The Categorical Distinction, Not Karl Popper
- Exile — About the Program, 2. Exile, 3. Restoration, Not Michel Foucault
- explanatory reach — II. The Lost Art, I. The Correspondence, Objective: Explanatory Reach (), Step 3: Update State Variables
- extraordinary authority — How to Read This Document, The Farmer-King
F
- factory electrification — Preface, How to Read This Document, The Dynamo and the Agent
- failure conditions — Failure Conditions
- farmer-king — The Farmer-King
- FIFA — FIFA Under Sepp Blatter (1998–2015), Synthesis
- finite game — The Wins That Break The Game, Not James Carse
- Form Check — Doctrine Reconstitution, X. Ritualize Doctrine Update
- form otherness — The Bite and The Gift
- fractal calendar — Pro-Fractal, VI. A Small Fractal Calendar, Not Apollo, Not Nassim Nicholas Taleb
- Fragile Survivor — Edge Case Archetypes, The Fragile Survivor
- Friedrich Nietzsche — Appendix D: Letters to the Editor, Not Friedrich Nietzsche, Appendix E: Sources
- Friedrich Schiller — Appendix E: Sources
G
- Galbraith — How to Read This Document, The Limit on Useful Agency, Touch Down, Appendix E: Sources
- Game Tape Review — Preface
- GE — 3M Under Six Sigma (2001–2005), GE’s Digital Transformation (2011–2018), Synthesis
- General Electric — GE’s Digital Transformation (2011–2018)
- General Motors — General Motors (1970s–2009), Not Alfred Sloan
- Georg Simmel — The One-Man Job, Appendix E: Sources
- Georg Wilhelm Friedrich Hegel — Appendix D: Letters to the Editor, Not Georg Wilhelm Friedrich Hegel, Appendix E: Sources
- Goldman Sachs — Goldman Sachs Culture, Synthesis, Not Greg Smith
- Goldratt — How to Read This Document, The Limit on Useful Agency, Touch Down, Appendix D: Letters to the Editor, Not Eliyahu Goldratt, Appendix E: Sources
- Google — Microsoft Under Ballmer (2000–2014), Yahoo’s CEO Carousel (2007–2012), Local Newspapers (2000–2020), Yahoo (1995–2017), Groupon (2008–2012), Yahoo Under Marissa Mayer (2012–2017)
- Great Dissolution — Prerequisite: The Form and The Current, The Bite and The Gift, Retraining Order: The Anti-Scapegoat, Beautiful Heat, The Fallow Interval, 2. Moral Hazard, Pro-Fractal, VI. A Small Fractal Calendar, Not Carl Icahn, Not Howie Makem, Not Jane Jacobs, Not Karl Popper, Not Mikhail Gorbachev, Not Nassim Nicholas Taleb, Not Seneca, Not Susan Fowler
- Great Recession — About the Author, Preface
- Greg Smith — Goldman Sachs Culture, Appendix D: Letters to the Editor, Not Greg Smith
H
- Hamartia — Tragic Metabolism, Touch Down, 2. Public Acknowledgment, III. Tragic Postmortems, Not Aristotle, Not Michel Foucault, Not Mikhail Gorbachev
- Hard Limits on Liminality — 3. Hard Limits on Liminality
- Hegel — How to Read This Document, Overture: The Melt and the Method, Tragic Metabolism, Touch Down, Appendix D: Letters to the Editor, Not Georg Wilhelm Friedrich Hegel, Appendix E: Sources
- Heraclitus — Autophagic Growth, Appendix E: Sources
- Herbert Simon — The Limit on Useful Agency, Appendix D: Letters to the Editor, Not Herbert Simon
- Hewlett-Packard — HP’s Restructuring Addiction (2005–2015)
- High Performer — Thriving Archetypes, The High Performer, Not Kevin Feige
- Homo Ludens — The One-Man Job, Appendix E: Sources
- hormesis — Autophagic Growth
- Hormesis Quotas — Autophagic Growth
- hospitality as binding force — Retraining Order: The Anti-Scapegoat
- Howard Schultz — Starbucks in 2008
- HP — HP’s Restructuring Addiction (2005–2015), Synthesis
- hubris — Preamble
- Hudud — 2. The Three Orders
I
- Ibn Khaldun — How to Read This Document, The Impatience of Jobs, Asabiyyah and the Wind, Touch Down, Appendix D: Letters to the Editor, Not Ibn Khaldun, Appendix E: Sources
- Ilya Prigogine — Autophagic Growth, Appendix D: Letters to the Editor, Not Ilya Prigogine, Appendix E: Sources
- Immanuel Kant — Appendix D: Letters to the Editor, Not Immanuel Kant, Appendix E: Sources
- incoherence tax — The Limit on Useful Agency, Agency Load and the Coherence Ceiling, Not Herbert Simon
- infinite game — The Wins That Break The Game, Not Ibn Khaldun, Not James Carse
- interpretive monopoly — 3. Interpretive Monopoly
- Iron Law of Oligarchy — Ritual Oligarchy and Sacerdotal Capture
J
- J. Robert Oppenheimer — The Manhattan Project’s Los Alamos Laboratory (1943–1945), Appendix D: Letters to the Editor, Not J. Robert Oppenheimer
- James Carse — The Wins That Break The Game, Appendix D: Letters to the Editor, Not James Carse
- James D. Thompson — The Limit on Useful Agency, Appendix E: Sources
- James McNerney — 3M Under Six Sigma (2001–2005)
- Jane Jacobs — The One-Man Job, Appendix D: Letters to the Editor, Not Jane Jacobs, Appendix E: Sources
- Jay Galbraith — The Limit on Useful Agency
- Jeff Immelt — GE’s Digital Transformation (2011–2018)
- Jerry Yang — Yahoo’s CEO Carousel (2007–2012)
- Jester’s Privilege — 4. The Jester’s Privilege, 2. The Three Orders, Not David Deutsch, Not Ilya Prigogine
- Jim Balsillie — BlackBerry (2007–2013)
- Job — About the Program, Preface, Introduction, Why Was the Apollo Program Not Enough?, Prerequisite: The Form and The Current, The Wins That Break The Game, The One-Man Job, The Dynamo and the Agent, The Coherence Ceiling, Auteurs, Agents, Actors, The Impatience of Jobs, The Audit, When the Gate Fails: Submerged Ritual Time, Beautiful Heat, The Farmer-King, 3. Hard Limits on Liminality, 4. The Jester’s Privilege, Return to the Plow, 1. Atimia, 2. Exile, X. Ritualize Doctrine Update, Amazon’s Warehouse Operations, Appendix D: Letters to the Editor, Not Alexis de Tocqueville, Not Ed Catmull, Not Howie Makem, Not Jane Jacobs, Not Job, Not Johan Huizinga, Not Kelly Johnson, Not Ronald Coase, Not Seneca
- Johan Huizinga — The One-Man Job, Appendix D: Letters to the Editor, Not Johan Huizinga, Appendix E: Sources
K
- kairos — The Bite and The Gift
- Karl Popper — Overture: The Melt and the Method, Appendix D: Letters to the Editor, Not David Deutsch, Not Karl Popper, Appendix E: Sources
- Kelly Johnson — Lockheed’s Skunk Works (1943–1975), Appendix D: Letters to the Editor, Not Kelly Johnson
- Kevin Feige — Marvel Studios’ MCU Bet (2008), Appendix D: Letters to the Editor, Not Kevin Feige
- Kodak — Kodak (1990s–2012), Synthesis, Not Steve Sasson
L
- Lashon Hara — 3. The Modifiers, Not Michel Foucault
- Law of Conservation of Risk — 2. The Law of Conservation of Risk
- Lean Six Sigma — About the Author, Preface
- Li (ritual form) — Prerequisite: The Form and The Current, Not Greg Smith
- liminal authority — The Farmer-King
- liminal phase — Not Victor Turner
- liminality — The Farmer-King, 3. Hard Limits on Liminality, Not Victor Turner
- Lindy-first design — Retraining Order: The Anti-Scapegoat, The Cincinnatus Design: Four Countermeasures
- line shaft — Preface, How to Read This Document, The Dynamo and the Agent
- Los Alamos — The Manhattan Project’s Los Alamos Laboratory (1943–1945), Synthesis, Not J. Robert Oppenheimer
- low-loss intent — The Coherence Ceiling
- Lucius Quinctius Cincinnatus — Appendix D: Letters to the Editor, Not Lucius Quinctius Cincinnatus
M
- M&A — About the Author
- Machiavelli — The Impatience of Jobs, Appendix D: Letters to the Editor, Not Machiavelli
- magic circle — The One-Man Job, Not Johan Huizinga
- management theater — Prerequisite: The Form and The Current, Retraining Order: The Anti-Scapegoat, Parameters: Illustrative Assumptions, Internal Collapse Archetypes, Management Theater, The Soviet Communist Party (1970s–1991), Not Alfred Sloan, Not Carl Icahn, Not Greg Smith, Not Steve Jobs, Not Susan Fowler
- Marcel Mauss — The Bite and The Gift, Appendix D: Letters to the Editor, Not Marcel Mauss, Appendix E: Sources
- Marissa Mayer — Yahoo’s CEO Carousel (2007–2012), Yahoo Under Marissa Mayer (2012–2017)
- Marvel — Marvel Comics in 1996–1998, Synthesis, Marvel Studios’ MCU Bet (2008), Synthesis
- Marvel Studios — Marvel Comics in 1996–1998, Marvel Studios’ MCU Bet (2008), Synthesis
- Mary Douglas — The Impatience of Jobs, Appendix D: Letters to the Editor, Not Mary Douglas
- mathematical model — Not Émile Durkheim
- Mauss Dynamic — The Bite and The Gift
- Max Weber — Ritual Oligarchy and Sacerdotal Capture, Appendix D: Letters to the Editor, Not Max Weber, Appendix E: Sources
- mechanistic thinking — Why Was the Apollo Program Not Enough?, Not Mikhail Gorbachev
- Microsoft — Apple in 1997, Microsoft Under Ballmer (2000–2014), Synthesis, Nokia Mobile (2007–2013)
- Mike Lazaridis — BlackBerry (2007–2013), Appendix D: Letters to the Editor, Not Mike Lazaridis
- Mikhail Gorbachev — Appendix D: Letters to the Editor, Not Mikhail Gorbachev
- mimetic desire — How to Read This Document, Not René Girard
- Minimum Viable Coherence Program — Appendix B: Minimum Viable Coherence Program
- Minimum Viable Epimetabolic Program — Appendix A: Minimum Viable Epimetabolic Program
- Mission Theater — The One-Man Job
- Moderate Growth — Thriving Archetypes, Moderate Growth, Badger Meter (1905–Present)
- moral hazard — 2. Moral Hazard
N
- Name the Mode — I. Name the Mode, VI. A Small Fractal Calendar
- NASA — Why Was the Apollo Program Not Enough?, NASA’s Space Shuttle Program (1981–2011), Synthesis, SpaceX (2008)
- Nassim Nicholas Taleb — Appendix D: Letters to the Editor, Not Nassim Nicholas Taleb, Appendix E: Sources
- negative selection — 5. Negative Selection on Epimetabolic Talent
- negentropy — Act III — Negentropy of Renewal
- No-Blame Covenant — Prerequisite: The Form and The Current, I. Name the Mode, Not Victor Turner
O
- Oligarchic Decay — Internal Collapse Archetypes, Oligarchic Decay, Not Carl Icahn, Not Kevin Feige, Not Mikhail Gorbachev
- one-man job — About the Program, Introduction, Prerequisite: The Form and The Current, The One-Man Job, The Impatience of Jobs, The Audit, Not Alexis de Tocqueville, Not Jane Jacobs, Not Johan Huizinga, Not Ronald Coase, Not Seneca
- organic solidarity — The One-Man Job
- ossification — Not David Deutsch, Not Georg Wilhelm Friedrich Hegel, Not Karl Popper
- otherness — The Bite and The Gift
P
- Pan Am — Pan Am (1970–1991), Synthesis
- Paul David — How to Read This Document, The Dynamo and the Agent, Touch Down, Appendix D: Letters to the Editor, Not Paul David
- permission ladder — VI. Add a Permission Ladder for Agents
- Peter Thiel — The PayPal Mafia (1999–2002), Appendix D: Letters to the Editor, Not Peter Thiel
- Pixar — Pixar’s Braintrust (1995–Present), Synthesis, Not Ed Catmull
- poverty of forms — The Poverty of Forms, Not Peter Thiel
- priesthood — Introduction, Retraining Order: The Anti-Scapegoat, The Farmer-King, Ritual Oligarchy and Sacerdotal Capture, Controllable Inputs, General Motors (1970s–2009), Not Alexis de Tocqueville, Not David Deutsch, Not Ed Catmull, Not Georg Wilhelm Friedrich Hegel, Not Ibn Khaldun, Not Immanuel Kant, Not James Carse, Not Karl Popper, Not Lucius Quinctius Cincinnatus, Not Mikhail Gorbachev, Not Reid Hoffman, Not Victor Turner
- pro-fractal — Pro-Fractal
- Purity and Danger — The Impatience of Jobs
- Pyrrhic Leader — Pyrrhic Archetypes, The Pyrrhic Leader, Not Greg Smith, Not Susan Fowler
R
- Readiness Rule — Prerequisite: The Form and The Current, Yahoo Under Marissa Mayer (2012–2017)
- reconstitution — About the Program, Prerequisite: The Form and The Current, Overture: The Melt and the Method, Act II — Reversal of Reconstitution, Doctrine Reconstitution, Pro-Fractal, I. The Correspondence, 1. The Categorical Distinction, Appendix A: Minimum Viable Epimetabolic Program, X. Ritualize Doctrine Update, Not Michel Foucault, Not Mikhail Gorbachev
- regulatory variety — Touch Down, Agency Load and the Coherence Ceiling, Not W. Ross Ashby
- Reid Hoffman — The PayPal Mafia (1999–2002), Appendix D: Letters to the Editor, Not Reid Hoffman, Appendix E: Sources
- Ren (humaneness) — Prerequisite: The Form and The Current, Touch Down, Not Greg Smith
- René Girard — How to Read This Document, Vibrating Vacuum, Appendix D: Letters to the Editor, Not René Girard, Appendix E: Sources
- renewal — The Dionysus Program, About the Program, Preface, Overture: The Melt and the Method, The Impatience of Jobs, When the Gate Fails: Submerged Ritual Time, The Fallow Interval, Act III — Negentropy of Renewal, Pro-Fractal, I. The Correspondence, II. The Diagnostic Value, III. The Assay, 1. The Categorical Distinction, Appendix A: Minimum Viable Epimetabolic Program, IV. Protect the Cooling Interval, VI. A Small Fractal Calendar, Not Carl Jung, Not Immanuel Kant, Not James Carse, Not Lucius Quinctius Cincinnatus, Not René Girard, Not W. Ross Ashby, Not Yoshinori Ohsumi
- retraining order — Retraining Order: The Anti-Scapegoat
- return to the plow — Return to the Plow, Not Alexis de Tocqueville, Not Ed Catmull, Not Georg Wilhelm Friedrich Hegel, Not Karl Popper, Not Nassim Nicholas Taleb, Not Reid Hoffman, Not René Girard
- Reverse Apprenticeships — Autophagic Growth
- Rite of Redress — The Audit, The Bite and The Gift, Retraining Order: The Anti-Scapegoat, Beautiful Heat, 2. Moral Hazard, Pro-Fractal, VI. A Small Fractal Calendar, Not Ed Catmull, Not Greg Smith, Not Howie Makem, Not Susan Fowler
- rites of renewal — The Dionysus Program
- ritual capacity — About the Program, Using the Calculator, Thriving Archetypes, Internal Collapse Archetypes, Pixar’s Braintrust (1995–Present), Bell Labs (1925–1970s), NUMMI (1984–2010), 3M Under Six Sigma (2001–2005), NASA’s Space Shuttle Program (1981–2011), Pitney Bowes (1990s–2010s), Lockheed’s Skunk Works (1943–1975), The Manhattan Project’s Los Alamos Laboratory (1943–1945), The PayPal Mafia (1999–2002), Badger Meter (1905–Present), Würth Group (1945–Present), Old National Bank (1834–Present), Apple in 1997, Marvel Comics in 1996–1998, Starbucks in 2008, SpaceX (2008), FedEx’s Las Vegas Origin Story (1973), Marvel Studios’ MCU Bet (2008), Uber Under Travis Kalanick (2010–2017), Amazon’s Warehouse Operations, Goldman Sachs Culture, Microsoft Under Ballmer (2000–2014), Yahoo’s CEO Carousel (2007–2012), HP’s Restructuring Addiction (2005–2015), Local Newspapers (2000–2020), RadioShack (1990s–2017), Yahoo (1995–2017), BlackBerry (2007–2013), Kodak (1990s–2012), Toys R Us (1998–2017), Nokia Mobile (2007–2013), GE’s Digital Transformation (2011–2018), Intel’s Mobile Processor Failures (2006–2016), Webvan (1999–2001), WeWork (2010–2019), Groupon (2008–2012), FIFA Under Sepp Blatter (1998–2015), The Boy Scouts of America (1980s–2020s), Zimbabwe Under Mugabe (1987–2017), Pan Am (1970–1991), Toys R Us (Debt Spiral, 2005–2018), Sears (2005–2018), The Soviet Communist Party (1970s–1991), General Motors (1970s–2009), Yahoo Under Marissa Mayer (2012–2017), Not Mike Lazaridis
- ritual inflation — 4. Ritual Inflation
- ritual oligarchy — The Farmer-King, Ritual Oligarchy and Sacerdotal Capture, Symptoms of Ritual Oligarchy, 2. Moral Hazard, Return to the Plow, Touch Down, Not Benoit Mandelbrot, Not Kelly Johnson, Not René Girard
- Ritual Time — About the Program, Preface, Introduction, Why Was the Apollo Program Not Enough?, II. The Lost Art, Prerequisite: The Form and The Current, How to Read This Document, Overture: The Melt and the Method, The One-Man Job, The Limit on Useful Agency, Auteurs, Agents, Actors, When the Gate Fails: Submerged Ritual Time, The Bite and The Gift, Doctrine Reconstitution, Retraining Order: The Anti-Scapegoat, The Fallow Interval, The Farmer-King, The Cincinnatus Design: Four Countermeasures, 3. Hard Limits on Liminality, Act III — Negentropy of Renewal, Pro-Fractal, Touch Down, I. The Correspondence, Preamble, 2. The Three Orders, 3. The Modifiers, 1. Atimia, Melt Rate (), Controllable Inputs, Agency Load and the Coherence Ceiling, Appendix A: Minimum Viable Epimetabolic Program, I. Name the Mode, II. The Weekly Crossing, III. Tragic Postmortems, IV. Protect the Cooling Interval, VI. A Small Fractal Calendar, IV. Maintain a Contradiction Ledger, X. Ritualize Doctrine Update, Not Alexis de Tocqueville, Not Andy Grove, Not Carl Jung, Not Claude Shannon, Not David Deutsch, Not Ed Catmull, Not Émile Durkheim, Not Georg Wilhelm Friedrich Hegel, Not Ibn Khaldun, Not Immanuel Kant, Not James Carse, Not Johan Huizinga, Not Lucius Quinctius Cincinnatus, Not Marcel Mauss, Not Mary Douglas, Not Mikhail Gorbachev, Not Mircea Eliade, Not Peter Thiel, Not Reid Hoffman, Not Seneca, Not Steve Sasson, Not Susan Fowler, Not Victor Turner, Not W. Ross Ashby, Not Yoshinori Ohsumi
- Robert K. Merton — Appendix E: Sources
- Robert Michels — Ritual Oligarchy and Sacerdotal Capture, Not Max Weber, Appendix E: Sources
- Robert Mugabe — Zimbabwe Under Mugabe (1987–2017)
- Rome — The Farmer-King, Not Lucius Quinctius Cincinnatus
- rotation — The Cincinnatus Design: Four Countermeasures, 3. Hard Limits on Liminality, Return to the Plow, Pro-Fractal, Controllable Inputs, Step 3: Update State Variables, Thriving Archetypes, Edge Case Archetypes, Pyrrhic Archetypes, Internal Collapse Archetypes, Microsoft Under Ballmer (2000–2014), Synthesis, Not Apollo
- Run Time — About the Program, Preface, Introduction, Why Was the Apollo Program Not Enough?, II. The Lost Art, Prerequisite: The Form and The Current, How to Read This Document, Overture: The Melt and the Method, The One-Man Job, The Limit on Useful Agency, Auteurs, Agents, Actors, The Audit, Doctrine Reconstitution, Retraining Order: The Anti-Scapegoat, The Fallow Interval, 3. Hard Limits on Liminality, Return to the Plow, Pro-Fractal, Touch Down, II. The Diagnostic Value, Preamble, 3. The Modifiers, 1. Atimia, A Mathematical Thought Experiment, Controllable Inputs, Appendix A: Minimum Viable Epimetabolic Program, I. Name the Mode, III. Tragic Postmortems, IV. Protect the Cooling Interval, VI. A Small Fractal Calendar, IV. Maintain a Contradiction Ledger, X. Ritualize Doctrine Update, Synthesis, Not Alfred Sloan, Not Andy Grove, Not Apollo, Not Carl Icahn, Not Carl Jung, Not David Deutsch, Not Dionysus, Not Ed Catmull, Not Émile Durkheim, Not Georg Wilhelm Friedrich Hegel, Not Ibn Khaldun, Not James Carse, Not Lucius Quinctius Cincinnatus, Not Peter Thiel, Not Steve Sasson, Not Susan Fowler, Not Victor Turner
S
- sacerdotal capture — The Farmer-King, Ritual Oligarchy and Sacerdotal Capture, Not Carl Icahn, Not David Deutsch, Not Ibn Khaldun
- scapegoat mechanism — Not Mary Douglas, Not Peter Thiel, Not Reid Hoffman
- scapegoating — About the Program, How to Read This Document, Overture: The Melt and the Method, Vibrating Vacuum, Retraining Order: The Anti-Scapegoat, III. The Assay, The Human Application, The Profession of Faith, Preamble
- Scrap Heap Library — Autophagic Growth, Touch Down, 2. The Three Orders, V. Eat Your Decay, Not Carl Icahn
- Sears — Sears (2005–2018), Synthesis
- self-cannibalization — Not Yoshinori Ohsumi
- self-erasure — The Wins That Break The Game
- Senate — The Farmer-King
- shadow doctrine — Auteurs, Agents, Actors, When the Gate Fails: Submerged Ritual Time, Preamble
- sidewalk ballet — The One-Man Job
- Simon — How to Read This Document, The Limit on Useful Agency, Touch Down, Appendix D: Letters to the Editor, Not Herbert Simon, Appendix E: Sources
- Sitting Duck — Competitive Collapse Archetypes, The Sitting Duck, Not Aristotle, Not Ed Catmull, Not Mike Lazaridis, Not Steve Sasson
- Six Sigma — About the Author, Preface, 3M Under Six Sigma (2001–2005)
- Skin-in-the-Game Rule — Retraining Order: The Anti-Scapegoat, The Cincinnatus Design: Four Countermeasures
- Skunk Works — Lockheed’s Skunk Works (1943–1975), Synthesis, Not Kelly Johnson
- Slow Decline — Decline Archetypes, The Slow Decline, Local Newspapers (2000–2020), Not Ed Catmull, Not Kevin Feige, Not Mikhail Gorbachev
- Small Fractal Calendar — VI. A Small Fractal Calendar
- sociability — The One-Man Job, The Fallow Interval, Appendix E: Sources
- social facts — How to Read This Document, The Bite and The Gift, Touch Down
- social otherness — The Bite and The Gift
- Sortition Selectors — 1. Sortition Selectors
- Sortition Tribunal — 3. The Tribunal
- Soviet Communist Party — The Soviet Communist Party (1970s–1991), Synthesis
- Soviet Union — Not Mikhail Gorbachev
- SpaceX — The PayPal Mafia (1999–2002), SpaceX (2008), Synthesis
- span of coherence — The Limit on Useful Agency, Auteurs, Agents, Actors, Agency Load and the Coherence Ceiling, X. Ritualize Doctrine Update, Not Herbert Simon
- Starbucks — Starbucks in 2008, Synthesis
- Steve Jobs — Apple in 1997, Appendix D: Letters to the Editor, Not Steve Jobs
- Steve Sasson — Appendix D: Letters to the Editor, Not Steve Sasson
- stewardship — About the Program, The One-Man Job, Retraining Order: The Anti-Scapegoat, The Farmer-King, 1. Sortition Selectors, 3. Hard Limits on Liminality, Touch Down, A Mathematical Thought Experiment, Controllable Inputs, Parameters: Illustrative Assumptions, Equations: System Dynamics, Step 3: Update State Variables, Using the Calculator, Thriving Archetypes, Edge Case Archetypes, Decline Archetypes, Internal Collapse Archetypes, VI. A Small Fractal Calendar, Synthesis, Synthesis, FIFA Under Sepp Blatter (1998–2015), Not Victor Turner
- struggle session — Prerequisite: The Form and The Current, Not Greg Smith, Not Susan Fowler
- Sunset Budgets — Autophagic Growth
- Susan Fowler — Uber Under Travis Kalanick (2010–2017), Appendix D: Letters to the Editor, Not Susan Fowler
- system dynamics — Equations: System Dynamics
T
- temporal otherness — The Bite and The Gift
- Tesla — The PayPal Mafia (1999–2002), SpaceX (2008)
- The Alliance — Not Reid Hoffman, Appendix E: Sources
- The Audit — The Audit, Not Alfred Sloan
- The Birth of Tragedy — Why Was the Apollo Program Not Enough?, Appendix E: Sources
- The Bite and The Gift — The Bite and The Gift
- The Braintrust — Pixar’s Braintrust (1995–Present), Not Ed Catmull
- The Coherence Ceiling — How to Read This Document, The Coherence Ceiling, The Limit on Useful Agency, Act III — Negentropy of Renewal, Agency Load and the Coherence Ceiling
- The Crossing — Retraining Order: The Anti-Scapegoat, Not Greg Smith, Not Howie Makem, Not Michel Foucault
- The Current — II. The Lost Art, Prerequisite: The Form and The Current, Overture: The Melt and the Method, Auteurs, Agents, Actors, A Mathematical Thought Experiment, Appendix B: Minimum Viable Coherence Program, Not Andy Grove, Not Mircea Eliade, Not Reid Hoffman, Not Steve Jobs
- The Dynamo and the Agent — How to Read This Document, The Dynamo and the Agent
- The Form — Why Was the Apollo Program Not Enough?, Prerequisite: The Form and The Current, The Form and Function of Coherence, Doctrine Reconstitution, X. Ritualize Doctrine Update, Not Alexis de Tocqueville, Not Alfred Sloan, Not Confucius, Not Georg Wilhelm Friedrich Hegel, Not Immanuel Kant, Not Michel Foucault, Not Reid Hoffman, Appendix E: Sources
- The Gambler — Edge Case Archetypes, The Gambler, Not Kevin Feige
- The Impatience of Jobs — About the Program, The Impatience of Jobs, Not Job, Not Machiavelli, Not Michel Foucault
- The Living Law — The Living Law
- The Melt — Overture: The Melt and the Method, When the Gate Fails: Submerged Ritual Time, Not Abe Silverstein, Not Andy Grove, Not David Deutsch, Not Ed Catmull, Not Émile Durkheim, Not Georg Wilhelm Friedrich Hegel, Not Immanuel Kant, Not Lucius Quinctius Cincinnatus, Not Michel Foucault, Not Mike Lazaridis, Not Nassim Nicholas Taleb, Not Reid Hoffman, Not Seneca, Not Steve Sasson, Not Victor Turner
- The Method — I. The Divorce, Overture: The Melt and the Method, The Alchemist’s Assay, Not Dionysus
- The One-Man Job — About the Program, Introduction, Prerequisite: The Form and The Current, The One-Man Job, The Impatience of Jobs, The Audit, Not Alexis de Tocqueville, Not Jane Jacobs, Not Johan Huizinga, Not Seneca
- The Outpaced — Competitive Collapse Archetypes, The Outpaced
- The Overwhelmed — Internal Collapse Archetypes, The Overwhelmed, Not Adam Neumann, Not Aristotle
- The Patience of Job — The Impatience of Jobs
- The Readiness Gate — The One-Man Job, Interlude I — The Readiness Gate, Not Apollo, Not Confucius, Not Mikhail Gorbachev, Not Susan Fowler
- Theory of Constraints — The Limit on Useful Agency
- Thomas Schelling — Melting Meaning
- Thompson — How to Read This Document, The Limit on Useful Agency, Touch Down, Appendix E: Sources
- touch down — Beautiful Heat, Pro-Fractal, Touch Down, III. The Assay
- tragic metabolism — Tragic Metabolism, Not Ed Catmull, Not Reid Hoffman
- tragic postmortem — The Audit, Tragic Metabolism, Pro-Fractal, Touch Down, Not Carl Icahn, Not Georg Wilhelm Friedrich Hegel, Not Greg Smith, Not Michel Foucault, Not Mikhail Gorbachev
- Tragic Postmortems — The Impatience of Jobs, Preamble, III. Tragic Postmortems, Not Alfred Sloan, Not Ed Catmull, Not Ilya Prigogine, Not Nassim Nicholas Taleb
- Travis Kalanick — Uber Under Travis Kalanick (2010–2017), Not Susan Fowler
- truth-telling — II. The Lost Art, Asabiyyah and the Wind
U
V
- vibrating vacuum — Vibrating Vacuum
- Victor Turner — The Impatience of Jobs, Retraining Order: The Anti-Scapegoat, Appendix D: Letters to the Editor, Not Victor Turner, Appendix E: Sources
- Virtuous Cycle — Thriving Archetypes, The Virtuous Cycle, Not Reid Hoffman
W
- W. Ross Ashby — Appendix D: Letters to the Editor, Not W. Ross Ashby, Appendix E: Sources
- Warren D. Devine Jr. — Appendix E: Sources
- Weekly Crossing — Retraining Order: The Anti-Scapegoat, II. The Weekly Crossing, Not Greg Smith
- WeWork — WeWork (2010–2019), Synthesis, Not Adam Neumann
- wins that break the game — The Wins That Break The Game
- witness otherness — The Bite and The Gift
X
- XBE — About the Program, About the Author, Preface
