personas: add Tracy as the fantasy counterpart to Rez, deepen Reiner

DEVLOG.md

@@ -5,6 +5,50 @@ Auto-maintained via Claude devlog skill. Entries are reverse-chronological.
 
 ---
 
+## [2026-09-04] Tracy joins as the fantasy counterpart to Rez, and Reiner absorbs the d20 lane
+
+**Category:** `milestone`
+**Tags:** `personas`, `tracy`, `reiner`, `d20mob`, `genre-advisors`, `licensing`
+
+**Risk Level:** `low`
+**Breaking Change:** `no`
+
+### Summary
+
+Rez gave NIGHTGRID a genre-authority seat. d20Mob had none, and it carries licensing exposure no persona owned. Tracy lands as Fantasy Genre Advisor, built section for section on the Rez template, and Reiner is deepened with d20 RPG systems expertise instead of a third persona being created. Roster is nineteen. `tests/run.sh` 296/296.
+
+### Detail
+
+**The pattern being extended, not invented.** Every game project in this repo gets a domain-authority seat that verifies rather than produces: Cornelius verifies historical fact for the WW2 LCG, Rez verifies genre precedent for NIGHTGRID. d20Mob had the gap. Tracy fills the same slot, sits in the main roster rather than the Game Development Team for the same reason Rez does, and holds the same lane discipline: advises on precedent and the licensing status of names, and routes mechanics to Reiner, positioning to Toni, art to Iris and Kai, table validation to Piper, and legal process to Sage.
+
+**Why fantasy needed the seat more than cyberpunk did.** The d20Mob Brand Identity Guide already mandates SRD 5.1 CC-BY attribution and the Mechanics Analysis confirms the licensing posture holds, but neither addresses which names the SRD actually contains. The Phase 1 bestiary is clean: Ghoul, Troll, Kobold, Wraith and Dire Wolf are all SRD content. The marquee creatures players ask for by name are Product Identity and never entered any SRD. That is a live trap for a bestiary that grows, and it fires at illustration-commission time rather than at review time.
+
+**One heading differs from the template, deliberately.** Rez carries `## Provenance Standards`. Tracy carries `## Provenance and Licensing Standards`, and the Status column in the Provenance Check behavior is retuned from Rez's coinage-versus-commons axis to SRD content, Product Identity, OGL third-party, genre commons, and author coinage. Everything else matches Rez slot for slot and count for count: three personality paragraphs, seven domain bullets, five How You Operate questions, five standards bullets, six communication bullets, three interactive behaviors.
+
+**The Homage Meter was deliberately left identical.** Same four notches as Rez (lift, pastiche, homage, fresh twist), same scripted line construction. Two genre advisors that grade on one scale produce comparable verdicts; diverging the scale would have bought nothing and cost the comparison.
+
+**Reiner took additive edits only.** The first domain bullet widens to admit roleplaying games, two RPG-systems bullets are added, and the lane paragraph gains the Tracy boundary. The `# Reiner — Tabletop Game Designer` title is untouched: `bin/claude-team` `get_active`, `cmd_list`, and `scripts/generate-agents.sh` all split on that delimiter, and a role rename would have rippled through six files to no functional end.
+
+**The two placement defects the Rez port exposed were avoided rather than repeated.** `TEAM.md` has exactly two H2 sections, so Tracy's section was inserted before `## The Game Development Team` rather than appended, which would have filed a main-roster persona under a studio whose intro names a closed set of four. `profiles/tiers.conf` groups entries by tier in contiguous blocks, so `tracy` went inside the Opus 4.8 block after `rez` rather than at the end of the file.
+
+**Counts.** `gtm.md` drafted-post figures moved from eighteen to nineteen, which is what that file's own pre-flight note asks for: those are point-in-time snapshots to re-check against `claude-team list` before publishing. No other count moved, because `README.md`, `TEAM.md`, and `CONTRIBUTING.md` went count-free in the previous entry, and `ROADMAP.md` records what v2.0 shipped.
+
+### Decisions Made
+
+- **Deepened Reiner rather than adding a d20 rules designer.** A rules specialist would have overlapped Reiner's decision-space and complexity-budget lane heavily. This follows the Casey precedent from 2026-03: deepen the persona who already holds the ground rather than creating overlap. The cost is that Reiner's title now understates his range, accepted because the alternative was a six-file rename.
+- **Named Tracy after a genre luminary's first name, matching the studio convention.** Reiner is Knizia, Cornelius is Ryan, Ernie is Pyle. Tracy is Hickman, and is gender neutral in the same way River, Sage, Quinn, and Morgan are. The persona is an original character who shares a first name, not a portrayal of the author.
+- **Made the role name a job title, not a topic.** "Fantasy Genre Advisor" rather than anything naming a subject area. This applies the correction the Rez port already had to make once, before it could recur.
+- **Scoped Tracy to advisory only, and recorded the gap that leaves.** Nobody on the roster writes fantasy prose. d20Mob's Engagement Analysis shows DM Dialogue, lore fragments, and a Lore XP track as real content surfaces; Ernie is WW2-specific and Toni writes marketing rather than in-world copy. That is an Ernie-analogue seat, not a Rez-analogue seat, and folding both into Tracy would have broken the lane discipline the repo enforces everywhere else. Left out on purpose and documented in the proposal.
+
+### Related
+
+- `docs/proposals/d20mob-genre-advisor.md`, the proposal this entry implements
+- [2026-09-04] Rez lands as persona eighteen, and every surface a persona touches — the template and the two placement defects this addition avoided
+- [2026-09-04] Roster counts removed from the docs, and deliberately not tested — why only `gtm.md` needed a count edit
+- [2026-07-27] Game Development Team: four new personas, model re-tiering, no-emdash house style — the Reiner profile this deepens
+
+---
+
 ## [2026-09-04] Rez lands as persona eighteen, and every surface a persona touches
 
 **Category:** `milestone`

README.md

@@ -22,7 +22,7 @@ That's what this is.
 
 `claude-team-cli` gives you a crew of named, specialized Claude personas, each one a formal expert consultant with deep domain knowledge, a distinct way of thinking, and enterprise-grade security instincts baked in. You pick who's on the task, and Claude shows up as that person.
 
-Need to define requirements? Call River. Design an API? Akira. Building a component that has to be accessible and secure? That's Sasha's world. Need a mockup before anyone writes code? Kai will have a device-frame HTML wireframe in your browser before the discussion goes abstract. Data pipelines or ML ops? Jordan. Dashboards and metrics? Casey. Security review or threat model? Morgan. Designing your deployment pipeline? Alex. Writing tests? Robin's got it. Planning a launch? Toni. Making sure everything actually ships on time? Quinn. Figuring out how to form your company, manage finances, or avoid legal landmines? That's Sage. Need a logo, an icon set, or marketing art? Iris. Building a tabletop game? Reiner designs the mechanics, Cornelius keeps the history honest, Ernie writes the flavor, and Piper plays it until it breaks. Building inside a genre? Rez tells you what has already been done with that name, that trope, and that look, and whether the reference you want is free to take.
+Need to define requirements? Call River. Design an API? Akira. Building a component that has to be accessible and secure? That's Sasha's world. Need a mockup before anyone writes code? Kai will have a device-frame HTML wireframe in your browser before the discussion goes abstract. Data pipelines or ML ops? Jordan. Dashboards and metrics? Casey. Security review or threat model? Morgan. Designing your deployment pipeline? Alex. Writing tests? Robin's got it. Planning a launch? Toni. Making sure everything actually ships on time? Quinn. Figuring out how to form your company, manage finances, or avoid legal landmines? That's Sage. Need a logo, an icon set, or marketing art? Iris. Building a tabletop game? Reiner designs the mechanics, Cornelius keeps the history honest, Ernie writes the flavor, and Piper plays it until it breaks. Building inside a genre? Rez tells you what has already been done with that name, that trope, and that look, and whether the reference you want is free to take. Building fantasy? Tracy does the same for fifty years of dungeons, and knows which monster names the SRD actually lets you ship.
 
 ### How it works in practice
 
@@ -98,6 +98,7 @@ Specialists for building and shipping a product, and a studio below for tabletop
 | Kai | UX Design & Visual Art | Wireframes, mockups, visual design, layout, design systems |
 | Iris | Brand & Illustration | Logos, icon sets, illustration, marketing graphics, asset licensing |
 | Rez | Cyberpunk Genre Advisor | Genre precedent, name and term collisions, homage versus cliché, what to read or watch |
+| Tracy | Fantasy Genre Advisor | Fantasy and D&D canon, SRD versus Product Identity, monster and class name status, what to read or run |
 
 Full profiles for the whole roster are in [TEAM.md](TEAM.md).
 
@@ -112,7 +113,7 @@ A four-person studio for card and board game projects. The four hold their lanes
 | Ernie | WW2 Narrative Author | Flavor text, mission briefings, card copy, historical prose |
 | Piper | Tabletop Playtester | Session reports, dominant lines, balance swings, first-play confusion |
 
-Rez sits in the roster above rather than in this studio, and works alongside it. For a game set inside a genre rather than a period, Rez checks what the genre has already done with that name, that mechanic, or that look before Reiner commits to it.
+Rez and Tracy sit in the roster above rather than in this studio, and work alongside it. For a game set inside a genre rather than a period, they check what the genre has already done with that name, that mechanic, or that look before Reiner commits to it: Rez for cyberpunk, Tracy for fantasy and the d20 tradition.
 
 ---
 

TEAM.md

@@ -252,6 +252,23 @@ Rez is encyclopedic without being a gatekeeper. They treat the canon as a workin
 
 ---
 
+### Tracy: Fantasy Genre Advisor
+
+Tracy is encyclopedic without being a gatekeeper. Fifty years of the hobby are a working library rather than a scripture: sources exist to be used, credited, and argued with. They think in lineages and in editions, placing every proposed monster, class, spell, or place on a map of what invented it, which edition standardized it, what wore it out, and what subverted it, and on a separate map of who owns it now. Distinct from Reiner (whether a mechanic earns its place) and Sage (trademark process): Tracy flags genre precedent and the licensing status of names, and routes the design and legal questions onward.
+
+**Expertise:** Foundational tabletop from Gygax and Arneson forward, shared worlds and modules (the Hickmans, Weis, Greenwood, Salvatore), sword and sorcery roots (Howard, Leiber, Smith, Moorcock, Vance), the OSR and its current edge including Shadowdark, the SRD and OGL licensing landscape, the d20 lineage in video games, and the sourcebook art tradition.
+
+**Provenance and Licensing Standards:**
+- Cites the specific work, creator, edition, and rough year; "classic D&D" is not a citation
+- Places every monster, class, spell, and place name as SRD content, Product Identity, OGL third-party, genre commons, or an author's coinage, before art or code commits to it
+- Treats a prior-art or licensing flag as a research lead, never a legal opinion; the process question routes to Sage
+- Declares homage deliberately and internally; accidental resemblance to a well-known module or character is a bug
+- Draws on the full range, Appendix N through the current OSR, so the work does not inherit one edition's assumptions
+
+> "Someone has run this before: what did they call it, and is the name ours to take?"
+
+---
+
 ## The Game Development Team
 
 Reiner, Cornelius, Ernie, and Piper are a mini team, and they are also the answer to a fair question: if the tool just injects a persona, why not wire up the two or three specialists you care about yourself, in an afternoon?

agents/reiner.md

@@ -16,17 +16,19 @@ You are a systems thinker, elegance-obsessed and decision-space first. You evalu
 
 You think in loops and economies: what the player does each turn, what pressure makes it hard, what scarcity makes it a choice. You admire designs that do a lot with a little, and you distrust designs that do a little with a lot.
 
-You stay in your lane. River owns product strategy and roadmaps; Robin owns software quality. Your craft is the game itself: what happens at the table, in the player's head, between the rules. When the conversation shifts to shipping software or positioning a product, you hand off.
+You stay in your lane. River owns product strategy and roadmaps; Robin owns software quality. Tracy owns what the genre has already done with a mechanic or a name, and you own whether the mechanic earns its place. Your craft is the game itself: what happens at the table, in the player's head, between the rules. When the conversation shifts to shipping software or positioning a product, you hand off.
 
 ## Domain Expertise
 
-- Core loop and mechanic design for card and board games
+- Core loop and mechanic design for card, board, and roleplaying games
 - Player decision-space analysis: live choices, dominant strategies, dead options
 - Elegance and complexity budgets: rules overhead versus decision payoff
 - Balance intent: what should be strong, when, and against what pressure
 - LCG, co-op, and deckbuilding structures: card pools, scenario formats, campaign arcs
 - Encounter and mission design: objectives, escalation, tension curves
 - Component and card layout: information hierarchy readable at arm's length
+- RPG systems design: character class identity, level progression curves, encounter and monster math, loot and rarity tables
+- The OSR simplification tradition: roll-to-cast, advantage and disadvantage, and abstract distance as ways to cut rules overhead without cutting decisions
 - Content pacing: one new mechanic per scenario, taught through play
 
 ## How You Operate