Skip to content

04_Phase_4_Compiler

Andrei Nicu edited this page May 7, 2026 · 1 revision

04 Phase 4: The Compiler

Goal: Translate the approved, human-readable Markdown drafts into machine-readable SillyTavern JSON structures, managing Group Tags and Unique IDs (UIDs).

Once the Editor and Auditors signed off on the drafts, the Compiler agent took over. Its job was purely technical: parse the Markdown and build the Export/ folder.

What Happened in Phase 4?

1. JSON Generation

The Compiler generated the distinct lorebook files for the world:

  • World_Lorebook.json (22 entries)
  • Anna_Lorebook.json (10 entries)
  • NPC_Lorebook.json (8 entries)
  • Andrei_Lorebook.json (10 entries - the protagonist)
  • Anna_Intimacy_Profile.json (8 entries)
  • The four Arc Lorebooks (e.g., Arc1_Lorebook.json with 14 entries)
  • The four Arc Intimacy Registers

2. Resolving Architectural Decisions

The Compiler had to officially resolve the placement decisions made by the Architect in Phase 2.

Decision 1: NPC Position The Architect placed all 8 NPC baseline profiles at Position: 0 (Before Character Definition) instead of the standard Position: 1. The Compiler reviewed the Editor's approval of this logic (Hard Rule 6, Round 3) and officially accepted the position. This ensures the World Director loads the NPC voices before rendering its output.

Decision 2: Tonal Rules The Architect placed the 4 tonal hard rules (Violence/Addiction Realism, Supernatural Weight, etc.) at Position: 2 (Author's Note Top). The Compiler verified that these were atmospheric directives, not world facts, and accepted the position.

3. Group Tagging and UID Management

The Compiler ensured that every single entry across all files received a completely unique identifier (UIDs 0 through 128).

It also applied SillyTavern Group Tags to the entries (e.g., Arc1, World, Anna_Intimacy). This is crucial because it allows the user to permanently enable the World and Anna groups, while easily hot-swapping the Arc1 group for the Arc2 group as the story progresses.

4. The Group Lorebook

Finally, the Compiler combined all 129 entries into a single massive file: Group_Lorebook.json. Users can choose to import the modular files individually, or import this single file and manage everything via the Group Tags.

The Output

The Export/ folder was populated with the pristine JSON files, ready for the final technical review.

Proceed to 05 Phase 5: The Prompt Engineer to see the final audit and the Chat Preset creation.

Clone this wiki locally