Builder's Manual · Chapter 1

The Content Map

The whole universe is a set of packages — a small number of folders that hold everything that matters. Knowing which folder something belongs in is the first half of building well.

The three package roots

SPAECIMH is modular, and that modularity is physical: content installs into one of three roots, and nothing crosses them.

/                                  — the package structure
├── S.P.A.E.C.I.M.H. CORE/         — the system core itself
│     GM Instructions/             —   the master's private operating manuals
│     Characters/ Equipment/ Locations/ Game Starts/ Lore/ Services/
│     Trade & services/ Transport/ Storage/ Craft productions/ Artifact/ …
│      (each subfolder = the FILE TEMPLATE of one file type)
│
├── PACKS PARTS_1 SETTINGS/        — install folder for SETTING packages (worlds)
│     <SettingAbbrev>_…/           —   one folder per world, named by abbreviation
│       Game Starts · Characters · Locations · Monsters · Lore · Services …
│
└── PARTS_2 GENRE PACKS/           — install folder for standalone GENRE modules
      <Genre>/                     —   one folder per genre (Framework + Tech Level)
        <genrecode>_EQUIPMENT/ · <genrecode>_SERVICES/
  • S.P.A.E.C.I.M.H. CORE/ is the system. Its GM Instructions/ hold the operational manuals. Every other subfolder is the template of one file type — when you build a new Character, Location, or piece of Equipment, you clone the CORE template for that type; you do not improvise its shape.
  • PACKS PARTS_1 SETTINGS/ is where whole worlds install. A setting is a self-contained package: game starts, cast, places, monsters, lore, venues. Everything belonging to that world lives inside its setting folder.
  • PARTS_2 GENRE PACKS/ is where standalone genre modules install — genre framework + tech level, delivered as self-contained equipment and services sets usable in any setting at the matching tech level.

The prefix system — the rule that keeps names honest

The same names recur in every package — Tavern, Armor, Market appear in every world and every genre. An AI that encounters a bare Tavern cannot tell which one you mean, so collisions are prevented by prefixing, wherever a collision is possible:

  • SETTINGS — folders and files are prefixed with the setting's abbreviation, in capitals. DREAM BOX → DB_ → DB Characters/, DB Locations/, DB Lore/, DB Trade and services/.
  • GENRE PACKS — prefixed with the genre's 3-letter abbreviation, lower-case. MODERN → mod_ → mod_EQUIPMENT/, mod_SERVICES/.

The prefix is not decoration. It is the disambiguation mechanism of the whole build — it turns two identically named files in different packages into two unambiguously addressable entries. Establish the prefix the moment you create a package folder, and apply it to every folder and file you add inside it.

Multi-Package settings

A setting is not locked to one genre. One SETTINGS package may mount any number of GENRE PACKS on top of it — that is how CraftRPGS packages combine. The setting supplies places and people; each mounted genre pack supplies equipment and services at its tech level. This is how a single world runs Western, Fantasy, and Cyberpunk together.

A sheriff with a cybernetic arm fires a revolver loaded with magic bullets at a dragon guarding a corporate server. SETTING = the world · GENRE 1 = Western (revolver) · GENRE 2 = Fantasy (magic bullets, dragon) · GENRE 3 = Cyberpunk (cybernetic arm, corporate server).

Why filenames carry a slug

Every filename also ends in its file type's slug: .character.json, .equipment.json, .location.json, .game-start.json, .lore.json, .gm-instructions.md, and so on. This is not decoration. It is what lets one file point at another unambiguously — an inventory entry knows it references an equipment file, a map knows its pins are location files — without any shared database. The slug is the address; the folder locates it inside its package; the prefix disambiguates it across packages. Address + folder + prefix together resolve any reference to exactly one file.

Files point at each other, by reference

The schema stores references as strings: readable target names, not invented IDs. When you write a character's inventory, you put the equipment's name, and the sheet resolves it to the actual file at render time.

Two rules make references safe:

  1. Reference an existing file. A reference to a name that resolves to nothing renders as a broken chip and — worse — a computed field that depends on it silently returns nothing. Create the target before you point at it, or leave the field empty.
  2. Reference one thing, fully. An inventory row names one item. A character's origin names one derived category. Avoid inventing compound references like sword-and-shield; build real entries and link to them.
  3. Reference by prefixed path when packages collide. If the target's bare name is shared by another package, name it with its setting/genre prefix so the AI resolves the right one.

The cross-cutting rule: categories are enumerated

Almost every value that the machine reasons over is an enumerated choice, not free text. Equipment must be one of Weapon, Armor, Gear, Consumable, Treasure. A character's attributes come from a fixed set. This is what lets the AI sort, weigh and compare cleanly. Where a schema offers an enum, use a value from the enum — it is a contract, not a suggestion.

When you add a new thing

Match the package and the folder. Is it a rule or master guidance? → a GM Instruction in S.P.A.E.C.I.M.H. CORE/GM Instructions/. Is it a blade? → an Equipment file. A village? → a Location file. Is it part of a specific world? → that world's folder under PACKS PARTS_1 SETTINGS/, carrying its prefix. Is it genre gear or a genre service, meant to plug into any world at that tech level? → PARTS_2 GENRE PACKS/<Genre>/, carrying the genre prefix.

The system reasons over files, and text buried inside another file's notes is invisible to that reasoning. A real, typed entry in the right prefixed folder is the difference between a world the AI can run and a wall of words it can only recite.

If what you want to add fits none of the existing homes — a faction, a spell, a monster with no sheet — see Extending the System before you improvise.

Manual updated Nov 7, 2026.