Repository navigation
00_Pipeline_Overview
Welcome to the World Forge, an agentic pipeline designed to create high-fidelity, highly consistent roleplay worlds for SillyTavern. This page explains how the agentic workflow operates and how to launch it, using the "Lucifer" project as a practical case study.
This pipeline is optimized for use within agentic environments like Antigravity or Visual Studio Code (VS Code) using extensions like Roo Code or Cline.
When starting a new world project, your repository must follow this exact folder structure:
[project-name]/
├── World_Seed.md ← The starting document (produced by Phase 0)
├── Notes_On_functionality.md ← SillyTavern mechanics reference
├── Drafts/ ← Where the Architect and Editor agents build the world
├── templates/ ← Required structural templates
├── workflows/
│ └── world-forge.md ← The master agent instructions
└── Export/ ← The final compiled SillyTavern JSON package
The World Forge operates sequentially. Each phase represents a different agentic persona that hands its work off to the next.
-
Phase 0: The Interviewer – An interactive agent that asks you questions to help build your
World_Seed.md. -
Phase 1: The Refiner – Classifies your seed into world (Tier 1), character (Tier 2), and arc (Tier 3) knowledge, producing a
Drafts/Master_Design.md. - Phase 2 & 2.5: The Architect (and Intimacy Architect) – Drafts the actual lorebook entries and character cards based on the design. The conditional Intimacy Architect runs only if your world includes intimate scenes.
- Phase 3, 3.5, 3.6, 3.7: The Editor & Auditors – Iteratively edits the prose and tests the world in simulated roleplay to ensure voice, continuity, and intimacy fidelity.
- Phase 4: The Compiler – Translates the approved Markdown drafts into SillyTavern JSON.
- Phase 5: The Prompt Engineer – Audits the final JSONs and authors a custom Chat Completion Preset for the world.
You can launch the orchestrator from your AI agent by telling it to read the master instructions.
In Antigravity:
Use the @ mention system to inject the file directly into your prompt.
Run the pipeline @[workflows/world-forge.md] start
In VS Code (Roo Code / Cline):
Use the @ file mention or the custom slash command (if configured in your workspace):
@workflows/world-forge.md start
Other useful commands include:
-
resume phase[N]— Resumes the pipeline if it was paused for human input (e.g.,@workflows/world-forge.md resume phase1). -
skip phase0— Skips the Interviewer if you have already written yourWorld_Seed.mdmanually.
The foundation of the entire pipeline is the World Seed. Let's look at how the Lucifer World Seed was constructed.
The World Seed strictly divides knowledge into three tiers:
- Tier 1 (The World): Permanent truths. In Lucifer, this includes the setting (LA and the Penthouse), the Factions (Black Hand, Heavenly Host), and the Rules of Reality.
- Tier 2 (The Characters): Permanent biological and psychological facts. Anna's baseline physical description and core wound.
-
Tier 3 (The Arcs): Modular, changing states. The Lucifer project spans 4 arcs. Anna has a different
ANNA_STATEentry for each arc, moving from withdrawal to healing.
Crucial Rule: Never put arc-specific information (like Anna's withdrawal sickness) into a Tier 2 physical baseline. If it changes, it belongs in Tier 3.
The Auditors require specific, user-defined roleplay scenarios to test the drafted content. We added scenarios like:
- Anna's arrival at the penthouse in Arc 1 in the throes of withdrawal.
- An intimate scene in Arc 2 where Anna experiences a trauma flinch.
- Anna standing between Archangel Michael and Andrei in Arc 3.
For Lucifer, intimacy is a core thematic pillar.
- The Substrate: Anna's trauma map (freezing when pinned, dissociation during silence).
- The World & Arc Specification: The purpose of intimacy. Arc 1 is Transaction and Survival. Arc 2 is Communion and Comfort.
Once the World_Seed_Lucifer.md is complete, here is a high-level summary of exactly what the agents do with it:
-
Phase 1 (The Refiner): Reads the seed and maps out the architecture. It officially assigns the Penthouse to Tier 1, Anna's baseline psychology to Tier 2, and her withdrawal state to Tier 3 (Arc 1). It creates the locked
Drafts/Master_Design.md. -
Phase 2 (The Architect): Drafts the actual Markdown files (
Card_Anna.md,Card_WorldDirector.md, Tier 1 rules, 4 Arc Lorebooks). - Phase 2.5 (The Intimacy Architect): Authors Anna's permanent trauma map and the Arc 1-4 Intimacy Registers.
- Phase 3 (The Editor): Reviews the Architect's drafts, ensuring structural compliance.
- Phase 3.5, 3.6, 3.7 (The Auditors): Runs simulated text-generation tests against the drafts, testing voice, transitions, and intimacy hard-rules.
- Phase 4 & 5 (Compiler & Prompt Engineer): Packages the Markdown into ready-to-use SillyTavern JSONs and builds the Chat Preset.
Proceed to 01 Phase 1: The Refiner for a deep dive into the first step of this journey!