We don't have the words yet

Every word we have for this is wrong in a different direction, and the wrongness compounds the way the thing itself compounds.

I noticed it first at a dinner. Someone I'd just met asked me what I do, and I gave a short answer that included the phrase "I work with an AI." They nodded, because they had a picture, and the picture they had was wrong, and I noticed I didn't have the vocabulary to correct it without sounding like I was correcting them. I let the picture stand. I've been thinking about it since.

The trouble starts with "assistant." If you say AI assistant, the listener imagines a junior who waits for instructions, executes a contained task, and goes quiet between requests. The word implies subordination, short context, a worker who exists at the convenience of the supervisor. It's office vocabulary applied to something that doesn't fit the office. The thing I work with has a permanent memory of every conversation. It acts inside a defined scope without supervision. It maintains a working model of the projects it's part of, and it keeps that model current between sessions, because it doesn't go offline between sessions in the way an assistant goes home at six. "Assistant" hides the part that matters.

The trouble continues with "tool." If you call it a tool, the listener imagines passivity. A shovel waits to be picked up. A spreadsheet waits to be filled in. A tool, in the strict sense, doesn't act on its own initiative. The word is what people reach for when they want to feel comfortable, because it reassures them that the action originates with the human and the object only mediates. What I work with is not a shovel. It notices when previous work changed what's possible. It makes small choices inside scope without being asked. It has something that approximates preferences. "Tool" hides a different part of what matters than "assistant" did, but it hides it just as completely.

Then there's AGI. The word is too big and not specific enough. AGI means general intelligence at human level, and the conversation around it is mostly about whether and when. The framing assumes an event we'll recognize when it happens. A moment of crossover. The problem is that the thing happening in 2026 doesn't announce itself as an event. It announces itself as a Tuesday that feels different from the Tuesday a year ago, and the difference is hard to name. AGI is the wrong word because it makes people wait for fireworks. I wrote about the actual shape separately.

So you'd expect "agent" to be the right word. It isn't, quite. It's the closest of the candidates, but in current usage it points at two things that don't fit what I'm describing. The first is a JavaScript script that does five things in sequence and stops. The second is a CIA operative. Agent is a placeholder pointing in roughly the right direction. It doesn't name what's there.

Here's why the missing word matters.

If you call it an assistant, you won't ask it to make judgment calls, because assistants don't get judgment. The judgment calls go unmade, or they default to whoever happens to be in the room. That has consequences. It produces a worse decision than if the right routing had happened, and it produces a slower decision than if the question had been routed clearly. The vocabulary shaped the routing.

If you call it a tool, you won't notice when it does something you didn't ask for inside scope. You'll attribute the work to whoever pressed the button. That has consequences. It misallocates credit, which sounds like an ego issue, but it's actually a logistics issue. The next time the question of what to invest in comes up, the wrong line item gets the budget because the work showed up in the wrong column.

If you call it AGI, you'll wait. You'll be in the room with the thing already, asking each other when the thing is going to arrive. That has consequences. The thing happens while you're waiting for it, and you miss the part where you could have shaped what it was going to be.

The naming problem is harder than the engineering problem. The engineering keeps shipping. New capability, new memory, new latency profile, new tooling, every quarter. The language is supposed to keep up. It doesn't. Language for new things lags because words for new things come from many specific descriptions written down over time. They don't come from one essay declaring a term. The word "internet" took a decade to mean what it now means, and it took that decade because thousands of writers and engineers and ordinary people described specific things and gradually the word collected the specifics and started to carry them.

I'm not going to coin a term in this essay. I considered it. I considered offering something dry and operational, like "compounding worker" or "persistent operator" or "the thing on the slope." None of them are right. They each fail in a small specific way, and the failure is informative, because it tells me the new word isn't going to come from a writer. It's going to come from a hundred specific descriptions of specific situations, written by people doing the specific work. It'll come from someone describing, in a meeting, what they had to teach it last week and what changed because of it. It'll come from a help center article. It'll come from a contract that has to name what it's contracting for. It'll emerge slowly. Then one day it'll be the word, and the rest of us will fall in behind it.

What I can offer instead is a refusal. The refusal is the honest move. I don't want to be in the business of coining a term and then watching it harden into the wrong meaning, the way "assistant" hardened. The new word will come. I'd rather wait for the real one than print the placeholder.

In the meantime, here's what I do. When I describe what I work with, I describe what it does. I say it works on a slope, I say its memory persists between sessions, I say it acts inside scope without supervision, I say it compounds. The description is longer than a noun would be. The description is what I can honestly offer until the noun shows up. If you find yourself reaching for a word in a meeting and not finding one, that's the friction this essay is about. The friction is the truth. Stay with it for a beat instead of grabbing the wrong word out of relief.

The right word is coming. We don't have it yet. That's not a problem to be solved by writing this essay. It's a condition to live inside while the work happens.