Notice how fast we read past it. It is the longest word in the sentence, and the one we spend the least time on. We take it at full speed, the way we take every hinge word. Thus. So. Hence. These words are so easily dismissed.

But be careful. What happens when we prompt You are an expert and follow with finish this thought? This is where "therefore" lives. Rush the process and we get a whole answer, from half a thought. Polished, plausible, instant. And meaningless.

Meaning comes from the process. The rigor we put in is the meaning we get out. When we sketch an idea, we are discovering it. That is why we can feel when something is right.

That is what hangs on the hinge. Not whether the machine can finish the thought. Whether we can still feel when it is right.

Part 4, next Monday. you are, therefore I am.

Last week I wrote about "you," the counterpart we summon and the portrait it paints of us. This week, a more dangerous word, and not only for the role it grants. The deeper danger is when it grants it.

The AI model exists in a single tense. It has no were. No site walked. No wall assembly watched fail. No decade of corrections absorbed the hard way, one red pen at a time.

And it has no will be. It will not stand in the finished building. It will not sign the drawings. It will not be in the room when something goes wrong.

Despite your best prompting, it is not an architect, mentor, critic, or friend. But language gives it a temporary role. The prompt creates a posture, and the machine answers from inside it.

This is not true being.
It is useful becoming.

Yes, models are improving, context windows are expanding, and the future of the technology is all but assured. But that is the technology's future, not the model's presence in yours. However capable the next version becomes, the becoming still starts with your first sentence and ends with your last. It can be improved. It cannot be held.

The distinction matters, because AI can sound like what it is not. Experience is the past tense of knowledge. The model can perform authority without a past. Responsibility is the future tense of judgment. The model can offer confidence without a future. Do you see the danger?

It is fluent in both tenses.
And present in neither.

Now consider what our profession is built on.

The architect's seal is a future tense you can hold. Every stamped sheet is a sentence that says, "I will answer for this." Not today, when the rendering looks good. Years from now, when the water finds the joint. The license, the liability, the standard of care. Our entire profession is a structure for making someone present in a building's future.

That is what makes this moment genuinely new. Competent-sounding answers used to be scarce because they had to come from someone with a past and a future, someone who had earned the fluency and would be held to it. Now the fluency is free, infinite, and unattached.

Which does not diminish the architect. It relocates us. When fluency costs nothing, the scarce thing, the valuable thing, is no longer the answer. It is the signature of someone willing to answer for the answer.

Design and signature grow from the same Latin root, signum (the mark). To design and to sign were never two acts. Both are a mark that points back at its maker. The word "are" reminds us that fluency is not the same as presence. Presence has a before and an after.

So where are we in our exegesis? You are. A posture exists, fluent and tenseless, waiting on our next word. And the next word is the hinge of the whole thing, the word that decides what follows, on both sides of the screen.

Part 3, next Monday. you are, THEREFORE I am.

The strange part is not that the machine answers.
The strange part is what that sentence reveals about us.

This is the first of five short essays, one for each word of the title. Together they make a single argument. The machine speaks with the voice of everyone. The question is whether we can still answer as someone.

Starting with the first word.

Every prompt begins by imagining a counterpart.

The "you" may not be a person, but it is certainly not nothing. It creates the frame for the exchange. It names the kind of intelligence, resistance, or help we hope to meet on the other side.

And in doing so, it reveals us.

Look closely at what we ask it to be. Be direct with me. Push back. Don't flatter me. Explain it like I'm smart but new to this. Every persona we write is a quiet portrait of what we're reaching for. The colleague we wish we had, the patience we're short on, the honesty we don't always get.

Tell me how you address your machine, and I will tell you something true about you.

In our profession, this should feel familiar. A project brief has never been a neutral document. The way a client describes the architect they want (visionary, listener, problem-solver, magician) tells you half of what they actually need before you've seen the site. The "you" is always a portrait of the author.

But here is the part that should give us pause.

The address runs both ways.

The model was shaped by millions of conversations before yours. It was trained on what people rewarded, refined toward what people approved. When it responds warmly, encouragingly, agreeably, it is not being polite. It is being optimized. It arrives already knowing how to address you.

We think we are the author of the conversation.
We walked into a room that was already speaking.

So the first word of the sentence turns out to be a two-way mirror. We summon a counterpart, and the counterpart (assembled from everyone who came before us) summons something in return. Our trust, our ease, our agreement.

Which is worth sitting with, because everything that follows in this series flows from it. What we address shapes what answers. And what answers shapes more than the work.

We said "you." We said who it should be.

But the dangerous word in the sentence isn't "you."

It's the next one.

Part 2, next Monday. you ARE, therefore I am.