what do you keep it in

Part four of four in “into solution,” on what software does to a problem when you take the word literally. Each part stands alone.

The alchemists had a question that killed their whole project, and it is the right one to end on.

They were after the alkahest, a liquid that would reduce any substance to first matter. Paracelsus named it. Van Helmont, a century later, believed in it. The objection is Johann Kunckel’s, who came around to calling the whole business wishful thinking, and it is one sentence long: if it dissolves everything, what do you keep it in?

Hold onto that. First, what is left.

the economy of the insoluble

In 1966 Baumol and Bowen noticed that a string quartet takes the same four people and the same half hour it took in 1800, while over the same period manufacturing productivity went up by a factor nobody can picture. Their conclusion is called cost disease: sectors that cannot be made more productive get relatively more expensive forever, because they compete for the same people as the sectors that can. Healthcare. Education. Live performance. Care of every kind.

Baumol described the mechanism and never named the solvent.

Here is what the sorting is. Everything with procedural bonds goes into solution and its price approaches zero. What remains is what has no procedural bonds: presence, judgment, taste, trust, the live thing that has to happen once with a particular person in the room. Those become the entire economy, by subtraction. Not because anyone decided they were precious, and not because they got better. Because everything around them dissolved and they were still standing.

Run my offer to completion — every burden in a life, every burden in an organization, all of them taken at their word and dissolved — and you are left with a residue. The residue is the insoluble. The insoluble is where the people are. The project of dissolving burdens is, at the limit, the project of finding out what humans are for, by elimination.

Arendt got most of the way here in 1958 without a computer in sight. She splits human activity three ways: labor, the cyclical toil of necessity that is never finished and has to be done again tomorrow; work, the making of durable things; and action, what happens between people and cannot be repeated or predicted. She saw automation coming and her worry was precise — a society of laborers freed from labor, left holding an appetite with nothing to spend it on.

Software dissolves labor in exactly her sense. It barely touches action. What remains is the part that cannot be taken away, and whether anyone knows what to do with it is the question she left open and the one we are now running the experiment on.

what do you keep it in

Kunckel meant his question as a refutation. It is not one. It is the proof, and the vessels are easy to name.

The firm is one. Coase explained in 1937 why companies exist at all: not because big is good, but because finding people, negotiating with them, coordinating them and enforcing the deal all cost something, and when those costs are high enough it is cheaper to put everyone inside one boundary and give orders. Software has been dissolving every one of those costs for forty years. The platform, the contractor market, the one-person company running a hundred processes it did not write — the org chart is salt in water, and the dissolving is not finished.

The role is another, and the mechanism is uncomfortably direct. A job is a set of burdens with a name on it. Dissolve the burdens and the definition goes with them. That is not a side effect of the work. That is the work, seen from the other chair, and anyone who makes this offer to a colleague should know they are making it.

And the third vessel is the describer. Deciding what to describe and how to describe it — knowing which burden is real, which is a story about a burden, and which three are secretly the same one — was until recently the insoluble residue of this entire business. It was the thing you could not automate, and it was my job.

A solvent that respected its container would not be universal.

You cannot pour the new thing into the old vessel; the vessel breaks. There is a politer version of this in the systems literature: to dissolve a problem is to redesign the entity that has it, and you never dissolve a burden and leave the organization intact. You dissolve a little of the organization every time, on purpose, and the organization includes you.

the polarity changed

Everything above was true in 2015. Here is what changed.

Water dissolves polar substances. Software dissolved formally specifiable ones. The boundary of the soluble was the boundary of what a programmer could write down as an unambiguous procedure, and that territory was enormous but it had a hard edge. Anything needing judgment inside the loop stayed out. Anything whose rule was “you’ll know it when you see it” stayed out. Anything described in prose rather than code stayed out, not because it was difficult but because prose was not a thing the solvent could grip.

Language models moved the edge. The polarity changed from formalizable to describable, and the soluble fraction of the world jumped by a whole category — all the burdens that were always procedural but never worth the cost of formalizing. Read the email and file it. Look at the ticket and route it. Draft the thing from the notes. Nobody was ever going to write a spec for those. Now nobody has to.

Every limit in this series accelerates under the change, and none of them go away.

The shell is a prompt now instead of a schema, which means it is looser, so more goes in and far less of what goes in is ever inspected. The world made in your image is now made from a paragraph; the cosmogony got cheap and the image got blurry. The one-way arrow now runs through skills that were safely insoluble a decade ago. The residue shrinks toward something smaller and stranger than Baumol imagined.

And the container now includes the describer. The person who says “tell me what feels like a burden” is doing something describable, which means the offer can now be made by the solvent. This is not a prediction. My own work is the instance: the drafting is dissolved, the review is the residue, and I am the one who poured.

Nothing is now restrained from what can be imagined.

That is why the line is worth saying in 2026 and would have been a slogan in 2015. It got said by someone standing at the exact point where the polarity changed, which is the only place you can feel a solvent change what it grips.

The offer still stands, and I mean it more now than when I made it. Tell me what feels like a burden and we will dissolve it. I just know more about what I am offering: not to take the weight off you — to disperse it into a medium where no one carries it, no one sees it, and no one can pick it back up, and to find out together, one burden at a time, which parts of your work will not go into solution.

Those parts are not the failures. They are the whole point of the sorting. What is left when everything that can dissolve has dissolved is the salt.

Sources: Alkahest ↗ · Kunckel and the alkahest, Engines of Our Ingenuity no. 1569 ↗

Works cited without a link: Coase, “The Nature of the Firm” (1937) · Arendt, The Human Condition (1958) · Baumol and Bowen, Performing Arts: The Economic Dilemma (1966). Figures still in copyright are paraphrased, not quoted.