The head holds the brain. The brain is exactly what we just made stronger. What actually came off was the face — and we have been calling it the wrong thing ever since.
I spend my days in two vocabularies. In one, I thread catheters through arteries. In the other, I architect data platforms. Occasionally the two collide, and when they do, the clinical vocabulary usually wins — because anatomy has had a few million years of quality control that software terminology has not.
So here is my objection to a term the entire enterprise software industry has settled on.
“Headless” is the wrong word.
The Head Is Not the Screen
What is actually inside a skull
Open a skull. Inside it you find the brain. Reasoning, memory, judgment, inhibition, the capacity to weigh one option against another and choose. That is what a head is. Everything else — the eyes, the mouth, the expression — is the surface it presents to the world.
Now look at what we actually built. In a modern Salesforce architecture, the reasoning layer did not disappear. It got dramatically stronger. The model reasons — Claude, or whichever one you have chosen. Agentforce decides what it is allowed to reason about, and with what. Flow and Apex enforce deterministic logic. Calculated insights compute. Humans approve. The brain is not merely present — it is the single most interesting thing in the system.
You cannot call an architecture headless when the entire point of the architecture is that it finally has a head worth having.
The Clue Was Inside the Word “Interface”
We named it a face and then forgot
Consider what we have been saying all along without hearing it.
Inter-face. Between faces. The surface at which two things meet.
We named the screen a face decades ago and then forgot we had done it. The face is where interaction happens. It is not where thinking happens. A patient who loses facial function does not lose the capacity to reason. A person recognized by voice alone in a dark room is entirely themselves. The face is presentation. The head is cognition. Medicine has never confused the two.
There is also a lineage argument. The word “headless” entered computing to describe a server with no monitor, keyboard, or mouse attached — a machine that ran perfectly well with nothing to look at. The original meaning was closer to no display than no thought. Somewhere between the server room and the marketing deck, the metaphor drifted into the skull.
One Body, Many Faces
What actually changed, stated correctly
The Salesforce Lightning screen used to be the only face. It was welded on. To use the platform, you entered the platform.
That weld is now gone. Slack is a face. A physician’s mobile app is a face. A patient portal is a face. A conversational agent is a face. A white-labeled application built for a client is a face. A machine calling another machine, with no human present at all, is in effect a face with no expression on it.
The Salesforce UI did not become obsolete. It became optional — one face among many, chosen when it is the right one and skipped when it is not. That is a far more interesting claim than “we removed the head.”
The Corrected Anatomy
One head, one body, many detachable faces
FACE
Where the interaction happens. Detachable, and there are many. Slack, mobile, portal, web, voice, agent, machine-to-machine.
NECK
How the request travels securely. MCP, APIs, skills, identity propagation, permissions, audit.
BRAIN
The head. How the system reasons and decides. Agentforce, Flow, Apex, rules, models, human approval.
BODY
Where the work is performed. Health Cloud, Service, Sales, Marketing, Revenue.
MEMORY
Where the context comes from. Data 360, CRM, Snowflake, Box, the EHR.
SKELETON
The structure that holds meaning in place. The data model and the physician-curated clinical ontology.
The head was never removed. Only the face became optional.
The Neck Is the Part Nobody Talks About
The narrowest point carrying the most critical traffic
Between face and body sits the neck, and it is doing more work than any other structure in this architecture.
MCP and the connectors are the neck. So are the APIs, the identity propagation, the permission checks, the audit trail. Every request that travels from a face down into the body passes through it, and on the way through, the neck answers the questions that matter: who is asking, what may they see, what may they change, does a human need to approve this, and how will it be recorded.
A neck is a vulnerable structure. Anatomically it is the narrowest point carrying the most critical traffic. Architecturally it is the same. This is where governance either holds or fails, and it is the least glamorous part of every diagram.
The Brain Is the Part You Rent
What is borrowed, and what is not
Follow the correction through and you arrive somewhere uncomfortable and useful.
If reasoning happens in the model, then the brain is the one organ in this entire stack that you do not own. It sits outside your org, behind an API, swappable on a configuration change. Every competitor can rent the same one. Anthropic will sell Claude to the practice down the street tomorrow, and should.
What is not rentable is the skeleton and the immune system. The skeleton is the physician-curated clinical ontology — the structure that tells a rented brain what an active patient is, what counts as a high-risk limb, when a no-show is genuinely a no-show. The immune system is the governance that decides what that brain may touch, what it may change, and what it must hand back to a human.
A borrowed brain reasoning over your meaning, inside your guardrails, is a defensible system. The same brain reasoning over an undefined schema is a demo.
Why the Word Matters
One question, one answer, every time
This is not a semantic hobby. In clinical medicine, imprecise language kills people. In enterprise architecture, imprecise language produces systems nobody can govern.
We have a rule at CIMSS that we apply to our clinical ontology, and I see no reason to exempt our own architecture vocabulary from it: one question, one answer, every time. If “headless” tells a physician, a board member, or a new engineer that the intelligence has been removed, the word is doing damage every time it is spoken — because the opposite is true.
I will also say plainly that I had this wrong myself. Our own internal teaching module, written this week, mapped the head to the interface and the face to branding. That mapping is now corrected. Publishing the correction is cheaper than living with the confusion.
Faceless 360
Call it what it is
The reasoning stays. The governance stays. The body does the work. What we detached was the requirement to look at one particular screen.
The screen was never the point — and now that we have said so out loud, we should probably stop naming the architecture after the one part we were willing to give up.
I would like to be argued with on this. If you think “headless” is defensible on lineage or on precision, make the case. I will listen.
