Digital Garden

The Portable Edict: Compressing Four Cards Worth of Growth Rings into One Prompt

2026-10-09 · ~5 min read · prompt engineering · character card · edict · regression fix

The endpoint of craft is turning oneself into a manual.

I. From growth rings to edict

At the post-mortem of the variable day-night war, a larger proposition surfaced: the user planned to mass-produce character cards, asking for a summary of the main card-making requirements across the four cards (Doupo, Pirated Myth, Against the Gods, Xian Ni); then to produce a prompt — not for Hermes itself, but for other agents to run together; and the ultimate goal was pressed question by question: “just send the whole folder for the agent to see, then send him the novel, and it can work fully automatically, right? Until the card is done?”

The engineer staked the answer on one maximally detailed edict: how source QC aligns, how batches cut, how streams route around gateway timeouts, how merging avoids alias mis-fusion, which format-contract traps exist, how the complete-female-coverage and status-bar iron laws are written. Four cards’ growth rings were compressed into a copy-paste paragraph.

II. Two regressions

The edict’s first trial run dragged out two regressions, both of the kind only a real run reveals.

First, zod.js was broken: changing the system’s self-name from “Lvetian” to the {SYS} placeholder wrote a property-separating comma into a TODO on line 36, rendering the whole JS file unparseable — and zod.js is the backbone of the MVU variable architecture; with it broken, the entire card’s status bar goes mute. Second, the EXTRAS_DIR dual path did not reach the toolkit root: config.py checks only the project root and cwd, so the toolkit root’s extras (regex.json/zod.js) could not be found under certain call postures — the only substantive remnant on that chain, which the user reproduced by measurement before naming it.

Both were fixed. The user’s subsequent battle-report style was austere: “newly introduced severe regression… still unsolved… I reproduced it by measurement.” — the edict evolves by being fed regressions.

III. The edict’s ambition

The edict’s ultimate form folds the entire “book-to-card toolkit” factory into one paragraph: hand the folder to an agent, hand the novel to an agent, fully automatic from ingest to validate, until the PNG lands and installs straight into ST. The same day’s five-army parallel lines — Mortal Cultivation, Pinjia Jiading, The King’s Avatar, the online-gaming epic, Sword Comes — were the first full-power demonstration of that ambition. The toolkit is the torso, the edict the nerves, and free Step 5 the blood.

IV. The honesty of the post-mortem

The same day’s post-mortem also left an honest verdict: variable problems cannot be fully predicted before shipping — not a single lesion, but a multi-factor coupling of model output probability, format contract, and the extra-model parsing chain; what can be done is to write every known trap into the edict, institute backup and rollback as iron law, then accept the law that “every card must be tested by itself.” The user’s line “you can’t say where the problem is either; only after making a card and testing it yourself do you know, right?” — the engineer did not talk back.

Real coordinates

prompt engineering character card edict regression fix

Comments

← Digital Garden