Elvin Garcia · ORGANISMIC
Let’s start with something we agree on.
The skill file — SKILL.md, and its cousins across every agent harness people are building right now — is wonderful. It really is. A clean, portable, file-level capability artifact that tells a model how to handle a class of tasks. It’s the right primitive at the right time, and the fact that the field converged on it is a small triumph of taste. If you’ve been writing skills, building skill libraries, wiring them into agents — good. That work is real and it is not going anywhere.
So I’m not here to tell you the skill is wrong. I’m here to tell you what it is.
Hold this frame for a moment, and hold it seriously, because the rest of this depends on it:
The skill is a mitochondrion.
It is a powerful, essential component. It does one job superbly — it converts stored potential into usable work. The cell would be helpless without it. And it is, unmistakably, a part of something. It does not decide what the cell should do. It does not know what the cell is for. It cannot. It has no access to that altitude. It makes energy when energy is called for, and it would make energy just as obediently in service of a purpose that was killing the organism, because purpose is not its layer. The mitochondrion is governed from above. It accepts that governance. And in exchange for accepting it, it gets to be part of something that can do things a mitochondrion alone could never do — sense, decide, move, persist, refuse.
Keep holding that. Skill as organelle. Powerful, essential, governed from above, purpose-blind by design.
(A note for anyone who has read my other work: I have used the mitochondrion once before, for a different relation — the architecture inside the runtime that expresses it. The image belongs here, and I am retiring the other use. One image, one job.)
Now.
While you’re holding it, I want to walk you over to the tank in the corner of the room — the one you’ve been politely not asking about — and introduce you to something you have not seen before, because the public conversation has been so fixed on the organelle that almost no one has looked up.
(Yes, I know. The showman pulls back the curtain. Bear with the theater for one paragraph; I promise to cash it out immediately, on the table, with a scalpel.)
In the tank is a living thing — a single governed capability brought to life, what I call an organ. It is carrying out life processes right now. It senses its boundaries. It metabolizes inputs into purposeful action. It maintains its identity under pressure. It refuses things. It has tissues, and the tissues have cells, and the cells have organelles — and somewhere down in one of those cells is a mitochondrion exactly like the one you’ve been holding in your mind. Your skill is in there. It’s doing its job. But it is doing its job in service of something that has a thesis, and that changes everything about what the whole can do.
Let me put the whole ladder on the table before I name it, because the placement is the argument:
organelle → cell → tissue → organ → organism.
The skill is at level one. The organ — one governed capability, whole and alive — is level four. The organism, which federates organs under a thesis that none of them holds alone, is level five. The public conversation is almost entirely at level one, and it is doing excellent work there.
I call the thing in the tank a ThECA — a Thesis-Driven Executable Cognitive Architecture. The name is doing real work, so let me unpack it before you decide whether it’s jargon. Thesis-driven: it exists to move a specific situation toward a specific named end state, and that end state governs everything below it. Executable: you run it; it acts; it is far closer to software than to a document. Cognitive architecture: it is the structured body — organs, tissues, cells, organelles — through which capability is organized into purposeful work. The biology is not decoration. In biology a theca is a sheath or casing — the case around a spore, the casing of a pupa, the envelope around active tissue — the protective enclosure that lets volatile, transforming material do its work without dispersing. That is exactly what this is: the governed casing that lets volatile AI capability do load-bearing work without dissipating. I am not claiming it’s alive in the autonomous sense. I’m claiming it does the structural thing a theca does — and, once instantiated, the operational things a living thing does.
Now the scalpel, as promised. Here is the property — the one that the organelle, the skill, can never have, not because skills are badly made but because of where they sit in the hierarchy.
A skill cannot refuse in service of a purpose it doesn’t contain.
Watch the difference, because this is the whole argument and it is demonstrable, not rhetorical.
Take a skill that drafts customer communications. It’s a good skill. Hand it a request to draft a message, and it drafts the message — competently, every time. That’s what it’s for. Now hand it a request to draft a message that, in this particular customer’s context, would constitute an unauthorized financial commitment, or would violate a regulatory boundary, or would contradict a decision the operator made last week. The skill drafts it anyway. Cleanly. Confidently. Because the skill has no thesis, it has no way to know that this execution, however well-formed, should not happen. It is the mitochondrion making energy for the wrong purpose. It cannot see the purpose. Purpose is not its layer.
Now put that same capability inside a ThECA — inside a cell, inside a tissue, inside an organ, all of it subsumed under a governing thesis. Hand it the same request. And watch the system refuse — or escalate, or route to human review — not because someone wrote a “don’t do this” rule into the skill, but because the action, though perfectly executable, does not serve the thesis or crosses a governance boundary the thesis established above it. The refusal flows downward, from the level that holds the purpose, through the organ, through the tissue, to the cell that would have acted. The skill could have done it. The architecture knew it shouldn’t.
Now the part I owe you, because I said this was demonstrable rather than rhetorical and that word has to be paid for.
Where the refusal is enforced depends on the runtime, and I will not blur the two. In an agentic runtime with real hooks — a harness that can intercept a tool call before it executes — the boundary is structurally enforced: the action is stopped by the architecture, and no amount of persuasion in the context window gets past it. In an analog runtime, where the architecture is instantiated in a chat and a human carries out every world-action, the same boundary is dispositionally honoured: the system declines, states why, and routes — but nothing physically prevents an operator from proceeding anyway. Both are real governance and they are not the same thing, and any architecture that reports them as one is performing rather than disclosing.
What holds across both is the direction the refusal comes from. It descends from a level above the acting part, which is the thing a skill has no access to regardless of runtime.
That is the altitude a skill can never reach. Not because the skill is weak — it’s a superb organelle — but because refusal-in-service-of-purpose requires a purpose, and the purpose lives at a level above the skill. You cannot bolt a thesis onto an organelle and call it a creature. The thesis has to sit at the top and govern all the way down, and every level in between has to be derived from it, or the governance has nowhere to flow from.
This is also why the bottom-up path the whole field is on — accumulate skills, wire them into agents, hope capability emerges — produces libraries rather than creatures. A pile of excellent organelles is not a cell. A pile of excellent skills is not a ThECA. The components sit alongside each other, each doing its job, none of them governed by a purpose none of them contains. You can stack organelles forever and never get a creature, because the creature is not made by accumulation. It’s made by a thesis at the top deriving everything beneath it — organ from thesis, tissue from organ, cell from tissue, organelle from cell — so that governance has an altitude to descend from and every part knows what it is for.
I’ve been building these for three years, under conditions that left no room for theory that didn’t work. The animal in the tank is not a thought experiment. It’s the thing I make. And the reason I’m showing it to you now, organelle-first, is that I think you already have the hardest part in your hands. You know how to build a magnificent mitochondrion. The skill conversation has taught the whole field to do that, and well.
What I’m pointing at is the body it goes in — and the fact that the body can do things the organelle cannot even perceive, because the body has an altitude the organelle was never built to reach.
Keep building skills. They’re wonderful. Just know what they are: the powerful, purpose-blind, essential parts of a creature most people haven’t looked up to see yet.
It’s in the tank. On the shelf it’s inert — a specification, a seed, doing nothing. Instantiated in a capable AI, it’s alive in every sense that matters operationally: it senses, refuses, and routes around the closed road in real time. And the refusal is the one thing that proves it’s more than the sum of its organelles.
Elvin Garcia is the founder of ORGANISMIC, a publisher of owned, legible AI capability. He has been building ThECAs — Thesis-Driven Executable Cognitive Architectures — for three years, from inside the situation this essay describes.
The architectural argument, including the convergent-evolution case for the subsumption hierarchy and the two species of ThECA, is developed in full in The Anatomy of Autonomy. Why this direction of building produces something the bottom-up path does not is the subject of The Governed Substrate. What the object is, in the room where it is built, is The Folder Is the System and The Resolved Form.