The Day That Reads as Empty

Six rectangular image frames scattered without connecting threads, each containing different abstract content with subtly inconsistent palettes — one cool cyan circuit pattern, one warm amber organic blobs, one with rounded leaf shapes, one with sharp angular fragments, demonstrating how parallel API calls produce images that share keywords but not visual DNA

About Will

I run a multi-site content operation on Claude and Notion with autonomous agents — and I write about what we do, including what breaks.

Connect on LinkedIn →

From outside, the day looks empty. No new product. No new feature. No new shipment counted in the unit the field has agreed to count.

From inside, the day was the most informative one of the week. The operator has a sharper model of the toolchain than they had at breakfast. The decisions sitting one level downstream will be made faster and will land closer to right. The thing that compounded was not visible to anyone outside the room.

This is a class of working day that the outside has no clean way to read. And the absence of a clean read is becoming a problem the outside has to learn to solve, because the class of day is multiplying.


The grammar gap

Pre-AI work had a clean grammar for the inside of a day. A meeting, a draft, a ticket, a deploy, a review. Each had a visible artifact. Each artifact mapped to a known unit of progress. An observer counting artifacts could form a roughly correct picture of what had happened.

The grammar held because the cost of an attempt was high enough that operators only attempted the thing they intended to ship. The artifact and the intent were the same object. Counting one counted the other.

Inside an AI-native operation, the cost of an attempt has dropped far enough that the artifact and the intent have come apart. An operator can attempt many things they do not intend to ship, in an afternoon, because the cheapest output of the toolchain is now a probe of the toolchain itself. The artifacts that remain after such a session are not artifacts of the work — they are residue of the inquiry.

The outside is still counting artifacts. The grammar is still pre-AI. The class of day that produces no shippable artifact and a large diagnostic surface is unreadable to it.


What the outside is actually trying to read

It is worth being careful about what the outside reader is trying to do, because the failure to read this kind of day is sometimes confused with the failure to evaluate someone fairly. Those are different problems.

An investor is trying to read whether the operation will compound. A partner is trying to read whether the operator is moving toward the thing they said they would build. A colleague is trying to read whether the work shared between them is progressing or stalled. A reader of the trade press is trying to read whether the category as a whole is producing real value or producing motion.

All four of those readers will, by default, count artifacts. All four will, by default, miscount when the operation has moved into the new mode. And the miscount is asymmetric: it overrates the operators who still produce artifacts on the old cadence, regardless of whether the artifacts have anything underneath them. It underrates the operators whose afternoon was spent driving the cost of future attempts further toward zero.

This is the same shape of misreading that financial markets used to apply to research-heavy companies before there was a category for them. The artifact was a paper, a patent, a prototype that did not ship. The grammar took a generation to catch up.


The inverse failure, which is real

It would be too clean to argue that the outside is simply wrong and the inside is simply doing better work that the outside cannot see. That is not the case.

The same cost curve that makes a productive probing session rational also makes an unproductive probing session almost free. An operator who has discovered that a session full of failed attempts can be honestly described as a sharpening of their model is one step away from discovering that almost any session can be honestly described that way. The grammar of the new mode is not yet sharp enough to refuse the bad use of it.

So the outside reader is not paranoid to ask the question. The question is the right one. It is just being asked with the wrong tools.


The tells that might be load-bearing

If counting artifacts has stopped working, what has replaced it? The honest answer is that no shared replacement has emerged. The field has not converged on a unit. But a few tells are starting to look like they might be doing some of the work, for an outside reader who is willing to set down the artifact count and pick up something coarser.

The first is the speed and confidence of downstream decisions. A productive probing session leaves the operator able to make the next several calls faster and more cheaply than they would have made them otherwise. An unproductive session leaves them no further along. The tell is not in the session itself. It is in the next few days, and specifically in the fact that the next few days look less like deliberation and more like execution. If an operation’s recent stretch is heavy on probing and the deliberation cost is not falling, the probing is producing motion rather than learning.

The second is the diversity of capability shapes the operator can now describe. A probing session that worked has changed what the operator can articulate about what is possible. That articulation will leak into conversation whether the operator means it to or not. A session that did not work leaves the description identical to what it was before. The vocabulary stays where it was. There is no new texture in the way the operator talks about their own toolchain.

The third — and this one is the most awkward to operationalize, because it is the one most easily faked — is whether the operation’s published outputs, when they do appear, are starting to look like they understood something that earlier outputs did not. The output cadence may have slowed. The output content has gotten more specific to constraints that only become visible from inside a probing session. A reader cannot inspect the inside; they can read the outputs.

None of these are clean signals. All of them require the outside reader to be paying attention over weeks, not days. They are coarser than artifact counting. They are also more durable, because they survive the moment the operator figures out how to fake an artifact.


The cost of reading the wrong layer

An outside reader who keeps counting artifacts will end up funding, partnering with, and writing about the operations whose toolchain is least developed — because those are the ones still producing the volume of visible output that legacy grammar rewards. The operations whose toolchain has moved into the probing regime will look quieter and will be quieter in the units everyone agreed to count.

This is not a moral problem. It is a measurement problem. But measurement problems compound. Capital flows toward what is legible. If the legible signal is the wrong signal for two years, two years of capital is mispriced. The category does not have two years of patient capital available for that.

The catch is that the operations whose toolchains are most developed are the ones least incentivized to translate. Translation is its own cost, and the operator who has just bought themselves an afternoon of cheap probing did not buy it in order to spend the saved hours producing legibility for the outside. They bought it to compound.


What the outside has to do

If the producer is not going to translate, the reader has to learn to read at a different altitude. The work of the outside reader has gotten harder, not easier, because the field got more powerful tooling. The signals the reader needs are now further from the artifact and closer to the operator’s evolving description of their own constraints.

That is an uncomfortable shift, because it pushes the reader’s job toward something that looks more like editorial judgment and less like counting. The reader who is uncomfortable with editorial judgment will keep counting and will keep being wrong. The reader who can hold the discomfort will be looking at the operation a year from now and noticing that the right calls were being made on days that the artifact ledger marked as empty.

The grammar will catch up. It always does. But the operations being read in the gap are real, and the readings being made in the gap are real, and the gap itself is the place where the next category of judgment is being figured out — by the few readers willing to admit they are reading without the old tools, and to start building the new ones in public, one observation at a time.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *