Each binder below was generated from a short brief by a deterministic expert system. Campaign arc, NPCs, relationships, plot facts, contingencies, per-session encounters, handouts, and a coherence audit — every page traceable to a specific rule firing, fully reproducible from the seed.
A short brief — or a structured feature set — runs through ten orchestrated factories, each operating on typed inputs and contributing to a growing campaign state:
CampaignFactory — arc type, session count, tone, setting, themesNPCFactory + RelationshipsFactory — signed social graph with motivesPlotFactsFactory — canonical facts the DM can and cannot contradictContingencyFactory — plan-B branches for player deviationPCHooksFactory — hooks that tie player characters to the arcHandoutFactory — letters, journals, wills, ciphers, sermonsEncounterFactory — per-session tuned encounters from an 80-creature poolMapsFactory — location graphsCoherenceFactory — post-audit that cross-checks everythingThe 205 rules propagate through MYCIN-style certainty factors and leave JTMS-style justifications behind — every fact in the binder can be traced back through the chain that produced it, which is shipped in trace.json alongside the output.
Every run is seeded. Given the same features and seed, the factory produces byte-identical output. Change one seed and every name, handout, and encounter shifts while the structural beats stay intact.
This is one of seven systems built alongside the Return of the Coder essay to demonstrate the same method: use AI to extract the rules, then run the rule-based system without AI.