THE post arrives without capitals, which is to say it arrives in the contemporary uniform of candor. Its author, writing to the r/ChatGPT forum on Reddit, describes a livelihood built on a single repeating task: clients send documents, the author instructs an artificial intelligence system to condense them, and the condensed versions go back to the clients. The work, as described, is not writing. It is not editing. It is the issuance of instructions to a machine that performs both.

What the author has discovered—and what prompted the post—is that the instruction itself has become the labor. Eleven times in a single workday, by the author's own tally, the same prompt was retyped or retrieved from the archive of prior conversations. "Summarize this, keep it under a certain length, use this tone, pull out action items if there are any." The sentence has the character of a form letter, which is precisely what it is. The author's occupation is to fill out the same form, repeatedly, and to send it to a machine that does the rest.

The arithmetic is worth examining. If eleven prompts were issued in one day, and each required between thirty seconds and "a couple minutes" to retype or locate, the daily overhead ranges from five and a half minutes to twenty-two. Annualized across a five-day workweek, the lower bound is twenty-four hours per year spent remembering how to phrase a request the author has already phrased. The upper bound is ninety-five hours, or nearly two and a half working weeks devoted exclusively to the reconstruction of a sentence that does not change. This is not an estimate of the time spent summarizing. It is the time spent asking for summarization to begin.

The condition has a name in industrial engineering, though no one in the forum thread uses it. It is setup time—the interval between productive cycles consumed by the reconfiguration of tooling. In manufacturing, setup time is the enemy of throughput, the target of every efficiency methodology from SMED to lean production. Frederick Taylor would have recognized the problem instantly: a worker performing the same preparatory motion eleven times per day because the jig has not been fixed to the bench. The solution, Taylor would have noted, is not to type faster. It is to type once.

What is novel is not the inefficiency but the layer at which it occurs. The artificial intelligence system was adopted, presumably, to eliminate the manual labor of summarization. It succeeded. The author no longer reads the documents, no longer composes the summaries, no longer exercises editorial judgment. The machine does this. What remains is a thin membrane of human effort—the prompt—and it is this membrane that has become the site of all friction. The automation did not eliminate labor. It moved labor to the boundary between the worker and the automation, which is exactly where one would expect to find it if one had been paying attention.

The post's closing question—"did you actually build a system for it?"—is, in the language of the market, a request for capital expenditure advice from workers in the same trade. The answers, should they arrive, will describe templates, text expanders, clipboard managers, and saved prompt libraries. Each of these is a tool for managing the tool. The stack deepens: a client produces a document, which is sent to a worker, who sends an instruction to a machine, which produces a summary, which is returned to the client. If the worker now adopts a prompt management system, the chain gains another link. At no point in this sequence does anyone write anything.

There is a further question embedded in the specimen, though the author does not raise it. If the prompt is the same every time—if eleven instances of it were issued in a day with only cosmetic variation—then the author's role in the transaction is not compositional but mechanical. The value added is not judgment, not taste, not the selection of what matters from what does not. It is the accurate reproduction of a known string of text. This is work that a scheduled script could perform without supervision, and the author appears to be arriving at this conclusion by degrees.

One notes, finally, the prose itself. The post is organized into six paragraphs of escalating narrative consequence, each advancing the argument by exactly one increment, arriving at a closing solicitation calibrated to maximize engagement. The planted specificity of "11 times"—not ten, not twelve, but the prime number that sounds counted rather than estimated—performs authenticity with the precision of a machine trained on ten thousand confessional posts. Whether the author or the author's tool composed the lament is, at this point, a distinction without economic difference. The output is the same. The prompt is the product, and the product is the prompt, and the new clerical class is typing as fast as it can to stay in exactly the same place.