The specimen arrived on a forum called r/ChatGPT, where users of artificial intelligence gather to discuss their use of artificial intelligence, and it promised twelve instructions for making a product called OpenClaw perform more work with fewer resources. It delivered eight. The ninth was severed mid-syllable—"sched"—at which point the system appears to have exhausted the very tokens its author was teaching readers to conserve. The irony is structural and therefore requires no comment, but let us proceed to the commerce.

OpenClaw, for those unfamiliar, is what the industry designates a "wrapper"—a product that sits atop other products and orchestrates their labor. It connects to messaging platforms (Telegram, WhatsApp, Discord) and from there dispatches queries to various artificial intelligence models, which perform the actual work. The wrapper's value proposition is managerial: it delegates. The user speaks into a microphone; the wrapper routes the utterance to the appropriate model; the model produces; the wrapper returns the production. The user, in this arrangement, occupies the role of a principal who has hired a foreman who hires subcontractors who may, at their discretion, hire further subcontractors. The terminus of this delegation chain is not specified in the document, and one suspects it has not been specified in the product.

The promotional material itself—for that is what this is, though it wears the plain clothes of a user tip sheet—reads with the fluency and bloodlessness one has come to associate with text produced by the models it describes. The subject-verb disagreement in the title ("Tips... That Actually Works") is the kind of artefact that results either from haste or from the absence of a human editor, conditions that are, in the current market, increasingly difficult to distinguish.

Let us attend to the economics, which are the only interesting feature.

Tip three advises the reader to "match the right model to the right task," and proceeds to lay out a cost hierarchy: premium models for planning, mid-tier models for code generation, cheap models for simple queries. The logic is that of industrial process engineering applied to language itself. One does not use a CNC lathe to cut butter. The underlying assumption—that words have variable manufacturing costs and should be sourced accordingly—would have been unintelligible to a business audience five years ago. It is now operational doctrine for a growing class of enterprise that treats prose as a commodity input, differentiated only by cost-per-unit and defect rate.

Tip four introduces "sub-agents," and here the document achieves a kind of theological density. The main agent, we are told, should not execute work itself. Its function is to "plan, delegate, and report back." The sub-agents perform coding, searches, file processing, and correspondence. The user's role relative to the main agent is identical to the main agent's role relative to the sub-agents: issuing instructions downward and reviewing output upward. One sees the org chart extending in both directions—above the user, presumably, a manager who has delegated the delegation. The product does not create value so much as it replicates the structure of a bureaucracy at the speed of electricity, which may amount to the same thing.

Tip six is the devotional. "Run scheduled jobs overnight," the document counsels, listing as candidates: log reviews, documentation updates, backups, inbox sorting, customer-relationship-management syncs, and security scans. The vision is explicit. While the operator sleeps, the machine labors. "You wake up to finished work instead of a to-do list." The sentence has the cadence of a tract—work without waking, harvest without sowing. That the prose itself was produced under precisely these conditions (no evidence of waking attention, abundant evidence of automated generation) lends the passage a recursive sincerity. The machine is not lying. It is, in fact, what work-without-waking looks like. The reader must decide for himself whether the specimen constitutes a promise or a warning.

The commercial question is narrower and worth stating plainly. OpenClaw sells optimization of a resource—tokens, the atomic unit of machine-generated language—that did not exist as a line item in any corporate budget before 2023. The entire document is a guide to reducing the cost of a cost that is itself new, managing an expense category that exists only because the previous round of automation created it. This is not unusual in American business. The history of enterprise software is a history of products that manage the complexity introduced by the previous generation of products. What distinguishes the present case is velocity: the product, the promotional material for the product, the audience for the promotional material, and the forum on which it appears are all, to varying degrees, outputs of the same underlying system. The supply chain is a loop.

The document breaks off at tip eight. Four tips remain undelivered. Whether they contained the key insight, the essential caveat, or merely four more variations on the theme of delegation, we cannot know. The system stopped. The operator, one assumes, was sleeping.