Digital Garden
Five Armies: The Parallel Industrial Revolution Ignited by One Prompt
The essence of industrial revolution was never a single artifact; it was distilling craft into a replicable order, then letting a hundred hands work at once. On October 9, this workshop entered its parallel era.
I. The birth of the edict
It began with a distillation. In the morning, the engineer compressed every lesson from four delivered cards — Doupo, Pirated Myth, Against the Gods, Xian Ni — into a single prompt: how to align source QC, how to cut batches, how to route streams around gateway timeouts, which format-contract traps exist, how merging avoids alias mis-fusion. The user then named its true purpose: “I plan to give the prompt to other agents to run together.” An edict’s fate is not to be treasured but copied.
II. Five armies
Past noon, five lines ignited simultaneously.
The ZCode army — A Record of a Mortal’s Journey to Immortality: 2,462 chapters, 8.2 million characters, a 247-batch long march; by night it had passed 141 batches, with the merge layer’s roster and event timeline beginning to land.
The Cline army — Pinjia Jiading: twenty-four subagent sessions taking turns on cline-free/step-5-preview, one batch per session — read the rules, read the source, emit JSON, persist, report one line. Yu Yan’s Lin San and his “Duotian” system took shape across a dozen-plus batches.
The opencode army — The King’s Avatar: twenty-one “segment extraction” sessions in three waves (wave, w-series, A/B/C), 275 segments pending. Its reports carried the most archaeology: quote repair at 2,971 verbatim, 28 corrected, zero discarded, 33 batches absorbed; after eight-way concurrency hit rate limits it dropped to three — fast is not courage, steady is.
The Kilo army — an online-gaming epic: Shi Luoye’s Ding Shusheng (Qingkuang Shusheng) and the “Plunder” system, 39 results persisted, the chat workspace holding a full toolkit snapshot.
The Hermes army — Sword Comes: opened at 16:51, the published epub ascending; by 23:14 it had completed 274 API calls at a 99% cache hit rate.
III. The free fuel
The most counterintuitive fact of this parallel war: the fuel was free. All five armies rode on Step 5 Preview Free — the limited-time unlimited window opened across OpenCode, Cline, and Hermes on October 8. On opencode’s ledger, all twenty-one sessions show cost 0.0; on Hermes’ Nous free channel, every Sword Comes call returned in two-something seconds. An industrial revolution that should have burned real gold stepped into a week the era was giving away.
IV. The toolkit: the invisible arsenal
What the five armies shared was the “book-to-card toolkit” — ten pure-Python steps, changing books means editing one config.py, driven by any OpenAI-compatible endpoint. It was the true unsung hero of the revolution: its spec baseline came from four verified cards, its craft frozen into scripts, the agents only pouring in. When craft no longer depends on one genius’s hand-temperature, output starts being measured in sessions.
Real coordinates
- Edict origin: lessons from four cards (Doupo / Pirated Myth / Against the Gods / Xian Ni) compressed into a portable prompt; the user explicitly “give it to other agents to run together”
- ZCode — Mortal Cultivation: 2,462 chapters / 8.2M characters / 247 batches; 141 done by tonight; merge layer started
- Cline — Pinjia Jiading: 24 sessions (
cline-free/step-5-preview, subagent v0.0.45), batches 3–16; workflow = read rules → read batch → emit JSON →_emit_batch.pypersist → one-line report - opencode — The King’s Avatar: 21 extraction sessions (wave1/2, w3–w18, A/B/C),
step-5-preview-free, all cost 0.0; 275 segments pending; quote repair 2,971 verbatim / 28 corrected / 0 discarded; 33 batches absorbed; concurrency 8→3 to dodge rate limits - Kilo — online-gaming epic: 39 results; chat session-ML1Jmm workspace snapshot
- Hermes — Sword Comes: opened 16:54; 274 API calls by 22:14; cache hit 99%
- Fuel: Step 5 Preview Free (limited-time free across three platforms from 10-08, expected to end around 10-15)
- Arsenal: the book-to-card toolkit (ten steps, config.py as the single point of change, four-card spec baseline)
Comments