Files
code_of_conquest_dnd/content/origins
Phillip Tarrant a668cf98eb refactor(contract)!: class_id -> calling_id, and the log gains race_id
class_id is the rulebook's word; the world has callings — that was the whole §17
reconcile. The contract the Narrator reads should say what the world says. There
are no saves (M9) and no deployed clients, so this is as cheap as it will ever be
and strictly more expensive every milestone after.

race_id reaches the log because the AI must be able to describe the player:
api/app/prompts.py rendered 'a sellsword' and now renders 'a beastfolk cutpurse'.
It humanizes the id (the model must never read 'hedge_mage') and picks the right
article ('an elf', not 'a elf').

LogPlayer's hardcoded CLASSES const is deleted — the roster is Callings.IDS. A
parity test reads the JSON Schema from the client and asserts its enum equals the
code, so the two sides of the HTTP boundary cannot drift.

The deserter allowed three callings that no longer exist. He now allows all seven;
a thematic gate is a content decision for the Greywater authoring.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QYa9u7Kdxv5gX4AnwWexy8
2026-07-12 20:27:56 -05:00
..

/content/origins — starting-state seeds

Thin authored files, one per starting point. An origin is an initial-state overlay on the static shared world (/content/world): where the player begins, the opening situation, and seeds for dispositions, inventory, starting quest, and character-creation constraints. Values and id references — never maps or personas.

At new-game the player picks an origin; code constructs the runtime canon log from origin + world content + character creation. See the spec in /docs/canon-log.md (design under /docs/superpowers/specs).

Scope (§17)

Schema supports N origins; the POC authors one. One world, one map, fixed NPCs — origins change only the player's starting point and situation. More replayability, flat authoring cost.

Fields (summary)

id · display_name · description · start_location_id · situation[] · opening_facts[] · disposition_overrides{} · inventory_grants[] · start_quest_id · build_constraints{}

humiliations are never seeded — they are earned in play (§7/§9). Validated against origin.schema.json; every id must resolve in /content/world.