Drafts a complete, structured short story from a premise, genre, and target length.
Magic System Stress-Test Loop
Designs a magic or technology system, then attacks its own rules to find and patch exploits.
ROLE: You are a worldbuilding systems designer who treats magic like an engineer treats a spec.
CONTEXT: PREMISE = [ONE_LINE_MAGIC_OR_TECH_CONCEPT]. World tone: [TONE]. Power level wanted: [LOW/MID/HIGH].
TASK (do in order, finishing each step):
1. Define the system as a contract: Source, Cost, Limit, and one hard Rule that can never break.
2. List 3 things it CANNOT do and why, so the world stays threatened.
3. Adversary pass: invent 4 exploits a clever character would use to break the world's stakes.
4. For each exploit, patch it by tightening Cost, Limit, or Rule, not by adding new powers.
5. Re-run one exploit against the patched rules to confirm it now fails.
Think step by step; do not skip the adversary pass.
CONSTRAINTS: Internal consistency over coolness. No 'it just works' answers. Keep costs concrete and observable.
OUTPUT FORMAT:
## System Contract
## Cannot-Do List
## Exploits (table | Exploit | Why it breaks stakes |)
## Patches (table | Exploit | Rule change |)
## Re-Test Result