Digital Garden
The Transmigrator Blueprint: The Genesis Art of Writing Backwards
All creation myths share a counterintuitive trait: the world is not written from the beginning; it grows backward from its ending.
On the afternoon of October 5, another session answered the other half of the same proposition — “give you a novel, what is the recommended order for making a SillyTavern transmigrator character card?” The blueprint offered has one core logic: decide first (skeleton), then dissect the book (material), then write backwards from “the opening,” and finally test and iterate.
I. Four tables: foundation first
Don’t think of gulping down “a summary of the whole book” in one bite. Extract in blocks (split long works by chapter), produce structured notes per block, finally merge manually into a “setting bible” — four tables are its skeleton: jargon/worldview table, character cards (identity, relationships, motives, secrets, plus original phrasing samples), timeline (key plot nodes), famous-scene/dialogue table. Dialogue samples are the most precious material — the model learns tone from them, not from piles of adjectives. AI auto-extracted entries must be checked line by line against the original — character relationships and timeline points are the minefield where errors are least tolerable.
II. Four transmigrator decisions: the keel
Transmigrator cards have four exclusive decisions; missing any one collapses: information asymmetry — do the initial characters know from the start that you transmigrated (the variable most needing defense in the whole book; the card should list a “who-knows list,” and the lorebook should give “suspicion trigger” entries for specific characters); the original novel’s corrective force — does the world have force pulling the plot back (snapping to canon) or does it allow butterfly effects, must be written explicitly, or the model will fabricate; the boundary of the prophet’s golden finger — when the user uses future memory to cheat, how does the world respond, is there a cost; the user’s default identity — no persona configured, still can start directly, the card must give a “transmigrator” default.
III. Writing backwards and testing
The work order is reverse-derived: greeting first (transmigration mechanism, start time, initial scene, system prompts, format demos, plus 2–3 alternate openings covering different transmigrator identities or time points); then Description (only what must be present every round: protagonist’s identity, style, verbal tics, abilities, goals, initial relationship with the transmigrator + one compressed worldview paragraph); Example Messages (2–4 groups, demonstrating three things: tone and prose style, output format, how the character reacts when the user crosses the line / goes OOC / abuses precognition — editing example dialogues is the most efficient means to correct the model’s style, far more effective than editing descriptions); lorebook (the rest of the four tables sink entirely as entries, paired with recall keywords); hard constraints (post-positioned instructions: don’t act or decide for the user, don’t advance long time spans on its own, when original settings conflict the book is authoritative, information asymmetry rules).
Test and iterate with fixed-primpt runs: original-detail questions (test memory), OOC inducement (test persona), consistency spot checks, behavioral tests, long chats 30+ rounds to watch for amnesia or persona drift. Iteration-period fix priority: edit example dialogues > edit lorebook entries > edit Description; smaller models lose settings more easily, so the card’s verbosity should be raised accordingly.
Real coordinates
- Core order: decide (skeleton) → dissect book (four tables) → write backwards from opening (greeting → description → examples → lorebook → hard constraints) → test & iterate
- Four tables: jargon/worldview, character cards (incl. original phrasing samples), timeline, famous dialogues
- Four transmigrator decisions: information asymmetry (“who-knows list” + suspicion triggers), canonical corrective force, golden-finger boundary, user default identity
- Iteration priority: edit example dialogues > lorebook > description; greeting should have 2–3 alternate openings
- Most common pitfalls: whole book crammed into Description (amnesia after 20 rounds), extraction without verification (relationships all wrong), examples all monologues, single card crammed with a dozen presets
Comments