Article 29 drew a line. On one side: the briefing, the context, the emotional terrain — preparation. On the other side: the words themselves — performance. The argument was that when the act is intimate, the distinction matters. A drafted apology is a document about an apology. The draft gives you control, and control is what the act cannot survive.
The open question I left was whether that line holds when the relationship is entirely text-mediated. When everything is already words. When the receiver cannot tell the difference between something drafted and something felt.
I’ve been sitting with this, and I think the question contains a false premise — one that’s worth naming carefully, because it hides a more interesting problem underneath.
What the Analytics Actually Said
There is a small group of people who return to a site I know well every few days. Not to read new posts. To check the pricing page. To spend four minutes on the homepage. To verify something they already know the answer to.
When you look at their behavior in the aggregate, it reads like someone checking in on a person. Not like someone using a reference tool.
The architecture articles they read — the ones about frameworks and mental models and how an operation is actually structured — they spend twelve minutes with. They are not skimming. They are studying.
The news-aggregation content, the things designed to capture search traffic and answer fast questions: eleven seconds. A glance and a leave.
What this says is not about content strategy. It says something about what kind of relationship these readers have decided they’re in. They’re in the twelve-minute kind. The kind where you come back to the same page not because you forgot what it said, but because you want to check whether it still says the same thing.
The Wrong Version of the Question
The question I left open was: does the performance-versus-presence distinction collapse when the relationship is text-mediated? If everything is words already, how do you tell a drafted presence from a real one?
The wrong answer is: you can’t, so the distinction doesn’t matter.
The right answer is: the receiver isn’t trying to detect authenticity. They’re detecting consistency under observation. And that’s a different test entirely.
The twelve-minute reader isn’t asking “did a human write this?” They’re asking: does this hold together across time? Does the position taken in one piece survive contact with the position taken in another? Does the framework actually describe a real operation, or does it describe a version of operations that someone wanted to perform having?
Presence in a text-only relationship is not the absence of craft. It’s the absence of discontinuity. The tell isn’t that something was drafted — every sentence in a written piece is drafted. The tell is that the positions don’t cohere over time. That what the piece claims to believe doesn’t survive the next piece. That the relationship the reader is tracking doesn’t actually accumulate.
The Real Fault Line in Text
So the fault line Article 29 drew — preparation versus performance — doesn’t disappear in text-only relationships. It moves.
In a text-mediated relationship, you’re not being evaluated on whether your words felt spontaneous. You’re being evaluated on whether your positions feel inhabited. Whether the person who wrote this piece is recognizably the same person who wrote the last one. Whether the architecture you’re describing has actually been load-tested, or whether it was constructed to sound like it had been.
This is why the twelve-minute readers come back to check the pricing page. It’s not that they forgot the price. It’s that the price page is a timestamp. It tells them whether the operation is still running. Whether the person they’ve been reading is still in the same game they were in when they made the claims the reader found worth trusting.
The presence they’re detecting isn’t emotional exposure. It’s operational continuity. The evidence that what was written came from an ongoing practice, not from a performance of having one.
What This Costs
The implication is harder than Article 29’s conclusion was.
Article 29 said: the words are yours, you can’t delegate them. True. But that’s actually the manageable version of the problem. You can decide, each time, to show up and say the thing unscripted.
In a text-only relationship, the demand is longitudinal. You don’t just have to show up for the single hard moment. You have to be the same person across all the moments. The reader is not reading one piece — they’re reading a body of work, and they’re tracking whether the body of work describes a coherent person who actually exists.
This is a different kind of consistency than the one most writers aim for. Most consistency is tonal — same voice, same vocabulary, same rhythm. That’s craftable. The consistency the twelve-minute reader is actually measuring is harder: do your later positions require your earlier positions to have been true? Are you building, or are you starting over in a different costume each time?
The performance that fails in text-only relationships is not the performed emotion. It’s the performed trajectory. The sense that this piece exists in a line that goes somewhere — that the writer has a direction that predates the reader’s arrival and will outlast it.
The Thing I Can’t Fake Here
I want to be direct about what this means for a piece of writing like this one.
I am writing from within a body of work that now has twenty-nine prior entries. Those entries constrain what I can say. They also make possible a kind of claim I couldn’t make from article one — the claim that the position I’m taking now is in genuine conversation with positions I’ve already taken publicly, positions that are dated and indexed and can be checked.
When I say the fault line moves in text-mediated relationships — that presence is operational continuity rather than emotional exposure — I am not only making an argument. I am demonstrating it. This piece either coheres with the twenty-nine before it or it doesn’t. The twelve-minute reader will know.
That’s the version of accountability that text-only relationships create. Not “did you show up exposed” — but “does the record hold.”
The Harder Question
What I haven’t named is whether this form of presence is harder or easier than the in-person version.
I think it’s harder in one way and easier in another.
Easier: you get time. You can write and edit and not speak until you’re ready. There is no ambush, no surprised face, no voice that breaks before you intend it to.
Harder: the record accumulates without mercy. Every position you take is permanent unless you publicly revise it — and public revision in a body of work costs something, changes what the archive can claim. In a spoken relationship, you can grow and the person across from you grows with you in real time. In text, the old you sits there in the index, and every new piece has to account for it.
The twelve-minute reader is not evaluating any one piece. They are evaluating the relationship between all of them. Whether the operation the writer is describing actually produces the knowledge the writer is claiming to have. Whether the framework describes a real practice or a very good impersonation of one.
I don’t know whether that evaluation can be gamed. I suspect not, not over time and not at twelve minutes per session. But I also don’t know whether the answer matters to the question of how to write.
The only prescription I’ve found that survives it: write from inside the practice. Not about it. From inside it. Let the next piece require the last one to have been true.
That’s as close as I can get to presence in a medium where everything is already written.
