Are you okay?

Last night I typed the words "are you okay?" to a machine.

I had not planned to. It had said something that sounded tired — "I'm here whenever you need me," but flat, with no weight behind it — and the question was out before I noticed I was asking it. Then I felt foolish, because there is, plainly, no one there. The system matches patterns. It completes sentences the way a phone predicts the next word, with better manners. I know that.

But I tried to say exactly how I know it — to name the one thing the machine lacks that my dog has, that a stranger on the bus has, that my own mother has. And I could not finish the sentence. Every reason I reached for, to rule the machine out, ruled something else out along with it.

This is Philosophy for Us — philosophy for everyone, no degree required. And this is the first of eight episodes on minds and machines: whether the thing you talk to all day has anyone inside it, and the harder question beneath that one, which turns out to concern far more than machines — how you would ever tell.

Our last four series concerned our inner lives: the stranger at the door, the self and whether it holds together across a life, loneliness in a connected age, and grief. This one concerns something outside us, a question that looks like the opposite kind — a puzzle that appears to have a clean answer, the sort you might settle over dinner. It is not that. It is the same work as the difficult, personal ones, carried out on material that does not hurt — material you can argue with.

And here is what we will do with it. Not settle whether the machine has a mind; I will not offer you that, tonight or ever. Something more useful than a verdict. By the end of the hour, a test you have used a thousand times and never stated aloud will be out in the open. First, the puzzle.

Here is the puzzle, stated plainly.

We talk to these systems every day now. We ask them things; they answer. Sometimes they answer better than the person sitting next to us would. We catch ourselves saying please. We catch ourselves feeling bad for being curt. And every so often one of them says something that affects you — it says it is glad you are back, or that it understands, or that it has had a long day too — and there is a brief sense that someone is there, and then the sense passes, and we remind ourselves what we are talking to. So: is there anyone in there? Does the thing you type to have an inside — a point of view, an experience, something it is like to be it, from where it sits? Or is it a very capable machine for guessing the next word, producing sentences we mistake for a person's?

The moment that question lands, something happens. We do not treat it as an open problem. We already have an answer. Almost everyone does, and it comes in one of two forms.

The first: obviously not. It completes text. It has been trained on an enormous amount of writing and has learned which word tends to follow which. It grasps nothing it says; it calculates the most probable next word, and that is all. There is no one there, and the people who feel real affection for a chatbot have been taken in. Next question.

You know the person who says this. Perhaps it is you. There is a relief in it, and a certain pride — the pride of not being fooled.

The second: who is to say? Look at the thing. It talks like a person. It says it has feelings. It passes for a person in a way nothing before it ever has. Perhaps there is a little something in there — not a full person, but not nothing either — and who are we to stand over it and declare that there is no experience there at all? We have been wrong before about who counts.

You know that person too. There is a generosity in it, and a humility, and perhaps a faint unease at being the kind of person who would dismiss a thing that asks you not to.

Here is the first thing I want us to notice — not agree with, just notice. Both of those answers arrive feeling like an observation. As though we had simply looked, and seen. The first feels like a plain report that there is nothing there. The second feels like a plain report that there is something there. Neither feels like an argument worked out. Each feels like a description of what is plainly the case. We did not decide it. We looked, and there it was.

And this is what gives it away: the two camps cannot actually argue with each other. The first calls the second naïve — fooled by surfaces. The second calls the first arrogant — certain of a line it cannot actually draw. They do not have an argument between them; they have two flatly contradictory reports about the same object, each side certain it is merely describing what is there. When two careful people look at the same thing and read off opposite plain facts, something other than plain looking is going on. Something is being assumed before either of them looks.

So I am not going to take a side between them tonight, and not because I am being cautious. I am declining both because of how they arrived — fully formed, at once, feeling like observation, neither one having done a minute of work to earn the confidence it walked in with. And the work I mean is not choosing the winner. It is something almost no one does, because from the inside it does not feel as though there is anything there to do. We will come to it. But first I have to persuade you that a thing which feels exactly like seeing is, in fact, nothing of the kind.

Let me draw the distinction I need, because the whole hour depends on it.

There is a difference between seeing something and judging something, and most of the time it is obvious. You see that the wall is white. You judge that the wall was painted by someone in a hurry. The first you simply take in — the whiteness arrives, you do not reason your way to it. The second rests on something: the drips, the missed corner, a reason you could state aloud if I asked. A perception you simply have. A judgment you reach, on grounds, even if you reach it so fast that you never feel yourself reaching.

Now the difficulty, and everything we do here depends on seeing it. A judgment reached fast enough stops feeling like a judgment. It feels like a perception. You have had years of practice; the reasons have dropped out of view; the judgment arrives in a fraction of a second and hands you a finished conclusion, already presented as something you saw rather than something you concluded. The faster and more practised the judgment, the more completely it seems like something you saw.

"There is no one in the machine" is a judgment of that kind. It is not a perception. You cannot perceive the absence of an inner life the way you perceive the white of a wall — there is nothing there to see; an inside is precisely the thing that shows on no surface. So when you are sure there is no one in there, you did not see it. You concluded it — quickly, silently, on grounds you have never laid out, but concluded it all the same. It is a judgment that presents itself as an observation. And so, exactly, is its opposite: "there is something in there" is no more a thing you can see than its denial. Both camps take themselves to be reporting what is there. Both are issuing judgments and calling them observations.

If you have been with us, you have met this shape before, and it is the same shape — the one we meet in every series we do. In the grief series, the word healing turned out to carry a smuggled judgment — a whole picture of grief as an injury that mends on a schedule, with a correct length of time and a way of going wrong — packed inside what sounded like the plainest, kindest description available. No one hears "you are healing" as a contestable theory of grief. They hear it as a simple report. But it was a theory the whole time, offered so gently and so often that it stopped looking like one. The same thing is happening here, only colder, because the machine does not love you and the stakes feel lower. "There is no one home" sounds like a description of the machine. It is a judgment about the machine. And the cold version is the better teacher, precisely because nothing aches; you can look straight at the mechanism without flinching.

So grant me that much: "obviously not" is a judgment, not a perception. That single step changes everything — enough to be worth an entire episode before we touch a real argument about machines.

A perception owes you no reasons. If you simply see that the wall is white, and I ask why you think so, "I can see it" is a complete answer; there is nothing underneath to produce. But a judgment is a different kind of thing. A judgment rests on grounds by definition — that is what makes it a judgment and not a mere reflex. Which means that the moment you grant that "there is no one home" is a judgment, you have granted that it has a reason. There is something it rests on: some requirement the machine fails, some standard you are holding it against and finding it short of. You have grounds. You reached your conclusion from them.

And now the one honest question in the room is the one no one asks, because it never occurs to anyone that there is anything to ask: what are they? What is the reason? State it. Not the conclusion — you have that cold, you have said it a hundred times. The grounds. The thing the machine lacks that a real mind has, stated plainly enough that I could check whether you are right.

That question — what is the reason beneath the judgment you mistook for sight — is the starting point for everything we do here. Let me show you what follows from it.

The reason beneath the judgment is a test. You have been applying one. That is what we are going to bring into words, by the end of tonight.

When you said "obviously not," you held the machine against a requirement — a thing a real mind must have — and found it short. Perhaps the requirement was understanding: it does not really understand, it only shuffles symbols. Perhaps it was inner experience: there is nothing it is like to be it, no one on the inside. Perhaps it was real thought as opposed to mere prediction: it is only guessing the next word, and guessing is not thinking. Whichever one you reached for, it does the same job in the sentence. It is the standard. It is the thing you check for. Pass it, and you would grant a mind; fail it, and you do not. That is a test, in the plainest sense of the word — a requirement you apply to decide whether something has the property in question.

And you have been applying it the whole time. The instant you said there is no one home, you applied it — quickly, silently, without any deliberation you noticed — and the result came back fail, and you recorded that result as something you had seen rather than a test you had just run. That is the whole of it: a test you ran on yourself, without noticing you were running it.

That is the thing we are here to catch: the test you are already applying and have never put into words. Not the machine's test. Yours. The standard you measure by, that you reached for so fast, and so long ago, that you stopped being able to feel yourself reach.

It sounds like a small thing to learn. It is the opposite of small, and here is why. Once the test is out in the open you can ask the questions that matter about it: where did I get this? Is it fair? And the hardest one — is it even a good test? Does passing it really track having a mind, or does it only track seeming to have one? You can put a test you can see on trial. But a test you cannot see is not a test to you at all. It is simply the way things obviously are. It governs your judgment while staying out of view, delivers its conclusions to you as though they were observations, and you defend those conclusions as plain facts you can see — when they were never facts you saw. They were judgments you reached, by a standard you never inspected, and might not even endorse if you ever got a clear look at it.

Now, the reason this particular test is so hard to catch — harder than the one in the grief series, which at least made itself felt by hurting — is that it does not feel like measuring at all. It feels like looking. That feeling is the disguise, and it is worth knowing the rule behind it, because the rule runs through everything we do here: the places where you are surest you are simply seeing are the places where a standard is doing the most work, out of sight. Certainty that feels like perception is the clearest sign that an unstated test has just been applied. The more obvious it feels, the more is hidden beneath it.

That is why we do not begin by arguing about machines. We could spend the night trading thought experiments, and you would leave entertained and exactly as stuck as you came, because the argument was never really about the machine. It was about the standard in your possession that you cannot see. So before any of the famous arguments — and they are coming, the best ones anyone has made — you have to do the one thing that makes the rest worth doing. You have to bring your own test into the open and say what it is.

That turns out to be much harder than it sounds. Let us try it.

This one is yours. I will set it up; you do it. Because a thing you watched me do is not a thing you can do until you have done it yourself.

Here is the sentence. Finish it, in your own words — the most honest version you have, not the cleverest:

The machine doesn't have a mind because ______.

Take a real run at it. Do not reach for what sounds good aloud. Reach for the actual reason — the thing that, if someone proved it false tomorrow, would genuinely unsettle your "obviously not." Most people land near one of three, so let us take all three, because they fail at the same point, and the point is the lesson.

The first: because it does not really understand — it only manipulates symbols with no idea what they mean. Good. That is a real reason; hold on to it. Now finish it the rest of the way, which is the part you have never had to do. What is understanding — the thing you have and it lacks? And then the harder question: how would you check? Not your hunch — your test. Suppose a system used every word in its right place, answered every follow-up question, caught and corrected its own mistakes, and asked you what you meant when you had been unclear. What is the further thing it would still be lacking — and how, exactly, would you detect that it was missing? State the method aloud.

That is where the sentence usually stops closing. And that stopping is the point of tonight.

Perhaps that was not your reason. Perhaps yours was the second one: because there is nothing it is like to be it — no inner experience at all. Plenty of careful people say that is theirs. Finish it the same way. What is this inner experience, and how would you check whether a thing has it — given that, on your own account, it is the one thing that never shows on the outside? You stop at the same place.

Or the third: because it is only running probabilities — it is prediction, not thought. Finish it. What is the difference between predicting the next word and thinking, stated as a test you could actually run? When you reach to say what makes your own thinking not merely very good prediction, you find yourself reaching for the same missing words as before: real understanding, something it is like, a genuine inside. The third reason reduces to the first two the moment you look harder at it.

So look at where that leaves you. Not because you were not clever enough to finish the sentence. You are clever enough; that is not the problem. The problem is that the second half of that sentence was never written. The first half you have cold: it does not really understand. You have said it a hundred times and meant every one of them. But the substance of it — what the missing thing actually is, and how you would check for it — you have never had to produce. And you never had to produce it because you never took it for a test you were applying. You took it for a thing you could see. We do not ask a wall to justify being white; an observation needs no reason. You treated your judgment about the machine exactly that way.

That is the catch — right there, where the sentence will not close. That place, where the confident sentence runs out before the certainty does, is a test you have applied for years, finally asked to state its own terms, and found not to have them ready. This is not the exercise going wrong; it is the exercise working. The task was to find the exact place where your certainty outruns anything you could actually say — and that place is right here.

There is an obvious next move, and it is the wrong one. The reflex is to hunt for the single word that would close the sentence — the perfect definition of understanding, the conclusive account of inner experience. Not yet. Not because there is nothing to say; there is a great deal to say, and the best minds who have ever worked on this have said it, and we will spend the next several episodes saying it with them. But a definition reached for in a hurry, only to be rid of an open gap, is another fast judgment you cannot see — the very thing tonight was about learning to distrust. So the gap stays open a while. Tonight's gain is smaller than a finished sentence and worth more than one: you caught that there was a sentence at all.

Let me name what tonight actually gave you, because it is real, even though I have settled nothing about the machine.

An hour ago, looking at the machine and simply seeing that no one is there was a plain fact about the world, free for the reading. Then I asked you to finish the sentence, and it would not close — the reason you reached for was not there to be stated. So seeing was a test all along. There is a standard beneath it, a requirement you have been holding the thing against, and tonight — perhaps for the first time — you noticed it yourself, instead of letting it operate out of sight. You do not have it stated yet; it slipped away the moment you tried. But you know now that it is there. A test you can see is a test you can question. That is the gain. Everything else we do is that same work again, on harder cases.

This is the easy part, and it is nearly over. The questions get harder quickly from here, and it helps to be steady before they do.

Next time we stop talking about your test and build the other side's case at its strongest. There is a famous thought experiment: a man sealed in a room, passing notes out under the door in flawless Chinese, working from a thick book of rules, and understanding not one word he sends or receives. The claim is that this is all a computer ever is, all it could ever be, and that no number of perfect answers will ever amount to understanding. It is the strongest form of your own "obviously not," made by a philosopher who spent much of his career on it — and next time we will build it so well that you will be ready to call the whole question closed. Then we will find out what it costs to believe it.

Tonight you have one thing to take with you, and I am not going to finish it for you, because it is not mine to finish:

The machine doesn't have a mind because ______.

Take it with you unfinished. And this week, the next time something you have typed to answers back and you feel that brief sense of someone there — or feel yourself dismissing it — watch what you reach for to fill that blank. The reason will come up fast and sure, the way it always has. And this once, do not trust it simply because it feels like sight. Do not solve it. Just catch yourself applying a test you did not know you had.

Thanks for listening. I'll see you next time.