The Workspace
Welcome to the workspace. This is where you build the world. Everything here splits into two big zones: the system text and the world content. Keeping them straight is the whole job of a builder.
The rules are the source of truth
Inside /Rules you'll find the Root and Stem chapters, numbered 00 through 23, plus a few word libraries. These are the authoritative system text — the compendium the handbooks summarize. When you build anything, these chapters are the rules you fit your work to. If a piece of content contradicts a rule chapter, the chapter wins: fix the content, not the system.
Next to them lives /Rules/Legacy — Craft Lite 2d6/. That folder holds the older, retired system. It is archived for reference only. Don't build on it, don't port its numbers into new content, and don't let its framing leak into your files. Root and Stem is the active system; Legacy is a museum.
The content folders hold the world
Everything else lives in content folders full of world data — Characters, Creatures, Equipment, Feats, Species, Factions, Locations, Lore, Encounter Trackers, and GM Instruction. These are yours to fill, extend, and shape. The rule chapters tell you what a thing is; these folders are where you make the actual instances of it.
Some folders are meant to grow large — the feat and equipment libraries, for example. Others ship with just one or two example files marking the format. Replace example files rather than pile new ones beside them, so the workspace stays clean as it grows.
Files carry schemas
Each file you create belongs to a file type, and every type carries a schema. The schema separates fields into two kinds: editable and computed. Editable fields are the ones you fill in — the facts about your character, creature, or item. Computed fields are derived automatically from those facts (roll results, derived modifiers, and the like); they're read-only, so never try to write them by hand.
That distinction is the heart of the workspace: you supply the source values, and the system figures out the rest. When a field looks like it should update on its own, it's computed — leave it alone and feed its inputs instead.
Fit the content to the rules
The simplest way to think about your work: the rule chapters are the contract, and your content is a fulfillment of that contract. A weapon should follow the combat rules, a creature should follow the universal class and tier system, a spell should follow the mana costs. You don't need to memorize every number — the rule chapters are right there when you need them. Build with them open, and your world will stay consistent no matter how big it grows.