Separate the System’s Rules from the Panel Display
System rules are the complete boundaries the author must know: capability range, failure conditions, cost, and information reliability. Panel display is the portion the character and reader can see now. They may be disclosed at different times and must remain consistent.
This separation preserves mystery without allowing rules to change after the fact. A system may lie, but the conditions under which it misleads should already exist in the design. Otherwise every contradiction can be dismissed as “the system deceived the protagonist,” and readers lose any basis for judging risk.
The Author’s System-Rules Card
What the system provides: Information, an ability, tasks, or exchange opportunities?
What it explicitly cannot do: Which decisions or actions can it never perform for the protagonist?
Trigger: Which concrete behavior activates a function?
Failure condition: When is it unavailable or unreliable?
Visible cost: How does use affect the protagonist’s time, body, relationships, reputation, opportunities, or future access?
Reliability: Accurate, limited, or misleading according to an established rule?
Disclosed so far: Which rules do the character and reader already know?
When use costs supply the story’s pressure, they should affect something the character values and readers can observe. Gentle daily-life or light wish-fulfillment stories can use low-cost systems and draw choices from availability, relationships, or everyday goals rather than compulsory harm on every query. “Consumes energy” creates no pressure if it never changes action. The system may offer options and deadlines, but the character must make the crucial choice and bear its consequences.
A System-Panel Template for the Prose
Display only fields that affect the present choice:
Current task: {An objective the character can perform}
Completion condition: {An observable standard}
Remaining limit: {Time, uses, or a condition currently preventing use}
Reward: {Something connected to the protagonist’s goal}
Cost of use: {A consequence understandable now}
Locked information: Keep this only when the unknown itself changes strategy; otherwise remove it.
Use this test: after reading the panel, must the protagonist choose again? If it merely repeats attributes readers already know, replace the full list with one character reaction.
Original Example: The Lost-and-Found System
Original rules card: Touching a lost object shows Gu Lin where its owner last set it down voluntarily. It does not show later movers or directly supply a name or motive. Each query randomly erases one segment of his route memory from that day. An image appears only after voluntary placement. Memory loss supplies pressure in this example rather than a requirement for all system fiction.
Present scene: Gu finds a worn school badge in a library and promises to try to find its owner before closing, then take his sister home. She does not know the route; visitor street maps are already available in the lobby. The badge belongs to an old choir design. He checks the former membership list, but several batches shared the design, so the list cannot identify this badge’s owner. Earlier material also establishes that readers sometimes place belongings beside their book piles.
Chapter panel:
Available clue: Last voluntary placement.
Cost: Lose one segment of today’s route memory; which segment is unknown.
Not established: Later movers, the owner’s name, or motive.
After ordinary checking fails, Gu queries. He sees a book pile at a window table and asks A-Yao, who is gathering books there. She says she is looking for her badge, describes an old crack on its back, and shows a previous photograph of it on her bag. Gu compares these before returning it. The system supplies none of that confirmation and does not identify anyone nearby merely by showing a table corner.
Leaving, Gu cannot remember the shortcut he took that day. His sister waits for him to lead. He takes the established lobby map and follows a longer route; they arrive later than planned. The map was already available and using it still costs time, rather than restoring erased memory for free.
Revision check: Voluntary placement triggers a location image; asking produces a candidate; responses and comparison support return; lost memory actually affects the journey. To show names directly, change the ability card and earlier prose first rather than quietly add that function mid-example.
Common System-Panel Failures and Fixes
| Failure | Correction |
|---|---|
| A perfect function unlocks during the crisis | Establish its source earlier and give it a new limit or cost |
| The announced number of uses changes arbitrarily | Publish only values and conditions you can maintain |
| A clue-only system suddenly gives the complete answer | Preserve its established scope; an explicitly answer-giving system can put choices in actions and consequences |
| The only cost is abstract “mental energy” | Show the missed event, relationship misunderstanding, or lost opportunity caused by dizziness |
| Every chapter repeats the full attribute table | Display only what changes the current choice |
| The panel and prose invent rules independently | Update one rules card first, then decide when to disclose it |
A system notification may create expectation at chapter end, but it should point to a real next choice rather than sounding once in isolation.
FAQ
Does a fictional system panel need many numerical values?
No. Once disclosed, a number becomes a rule readers can check. Keep only values that affect strategy. Use qualitative conditions for anything you cannot maintain consistently or that never changes a choice.
Can the system deliberately deceive the protagonist?
Yes, provided unreliability is itself a stable rule with a discernible boundary or cost. Do not wait for a contradiction and then use “the system lied” to explain every problem.
Do it with the skill
In Claude Code, say: “Use /story-long-write to design the fictional system. Define capability limits, failure conditions, visible costs, and reliability first, then provide a panel for this chapter that displays only necessary information. Do not draft the prose.” In Codex, write $story-long-write.
Read the method: Method used in this article · Rules expressed through action and consequences · Author choices and method defaults