RPGPT Sovereign RPG Engine

Status: Architecture validated — exp045 validates ruleset control systems (49 checks: PF2e, FATE, Cairn), exp046 validates text adventure DAG (33 checks), exp047 validates MTG card provenance (23 checks). exp053 proves anti-cheat = chain-of-custody thesis with 12 fraud types across 3 tiers. 🎮♨️ ludoSpring V23: session decomposition, typed TransitionIssue enum, pluggable ValidationSink, toadStool direct dispatch, zero-panic validation ( ⛰️♨️ groundSpring V109), #[expect(reason)] dictionary, deny.toml, 9 RPGPT dialogue plane experiments (321 checks). Date: March 16, 2026 Literature Anchor: Gygax & Arneson (1974, tabletop RPG structure), Cook (Pathfinder 2e, 3-action economy), Csikszentmihalyi (1990, Flow), Yannakakis & Togelius (2018, computational game science) Springs: 🎮♨️ ludoSpring (game science + HCI metrics), 🌱🔐 rhizoCrypt (ephemeral DAG — game state), 🍯🌾 sweetGrass (creative attribution), 🪨📖 loamSpine (permanence — rulesets, characters, world lore), 🐿️🧠 Squirrel (AI/MCP — narration), 🌿🖥️ biomeOS (orchestration), 🐻🐕 BearDog (anti-cheat signing) Open Systems: Pathfinder 2e (ORC License), FATE Core (CC-BY), Powered by the Apocalypse (CC-BY), Cypher System (Open License), Cairn (CC-BY-SA) License: ORC License for game mechanics; 🔧🦎 ecoPrimals code AGPL-3.0-or-later

The Question

Can the 🔧🦎 ecoPrimals data layer — 🌱🔐 rhizoCrypt (ephemeral DAG), 🍯🌾 sweetGrass (semantic attribution), 🪨📖 loamSpine (immutable certificates) — serve as the state engine for a tabletop RPG system where:

1. Any open ruleset (Pathfinder 2e, FATE, PbtA, Cypher) can be ingested as a 🪨📖 loamSpine certificate
2. Any world (original or existing fantasy series) can be loaded as world-lore certificates
3. The player is their own DM — setting up the quest, the world, the NPCs — then AI assists with storytelling from that foundation
4. Every game action is a DAG vertex — provable, auditable, branchable — using the same code path that tracks biological samples from field to freezer
5. 🎮♨️ ludoSpring’s validated HCI metrics measure session quality in real-time (Flow, DDA, engagement, fun classification)

Specifically: Is the anti-cheat/chain-of-custody isomorphism — the same DAG operation for item lineage in an extraction shooter, sample lineage in field genomics, and loot lineage in a tabletop RPG — sufficient to build a mechanically rigorous RPG engine?

The Isomorphism

The provenance trio applies the same code path across domains. Only the vocabulary changes:

🌱🔐 rhizoCrypt’s SessionType::Gaming { game_id } handles all four columns. The ItemLoot vertex in a Tarkov raid is the same DAG operation as a SampleCollect vertex in 💧♨️ wetSpring. Anti-cheat is chain-of-custody. Chain-of-custody is anti-cheat. Same primal, same Merkle integrity, different application.

Ingestible Rulesets: The Key Architectural Decision

The system does not hard-code Pathfinder or any other system. Instead, rulesets are 🪨📖 loamSpine certificates — immutable, machine-readable constraint documents that the AI must respect.

What This Means

Hand the system:

• Lord of the Rings (world lore certs) + Pathfinder 2e (ruleset cert) → play a d20 campaign in Middle-earth
• Dune (world lore certs) + FATE Core (ruleset cert) → play an Aspect-driven campaign on Arrakis
• Original world (player-authored lore certs) + Cypher System (ruleset cert) → play a GM-intrusion-driven campaign in a custom setting
• Any fantasy novel (world lore extraction) + any open ruleset → playable RPG

The ruleset certificate constrains the AI absolutely: if the PF2e cert says “3 actions per turn” or “Resist Fire 5 halves fire damage”, the AI cannot hallucinate around it because the constraint is provably anchored in 🪨📖 loamSpine.

Open Rulesets Available Under ORC / CC-BY

Ruleset-to-Certificate Mapping (Pathfinder 2e Example)

FATE Aspects as sweetGrass Entities

FATE’s Aspects are particularly interesting: they’re freeform narrative tags (“Haunted by the Ghost of My Mentor”, “Last of the Iron Legion”) that mechanically affect rolls via invocations and compels. This maps directly to 🍯🌾 sweetGrass semantic entities with derivation tracking — the Aspect is an entity whose origin is attributed (player created it during character creation), and whose evolution is tracked (the ghost was confronted in session 4, the Aspect changed to “Made Peace with My Mentor’s Ghost”).

Primal Roles

rhizoCrypt — Game State Engine

The DAG holds the living game world. Every action is a vertex:

Session: "campaign-northwatch-s4"
├── v0: SessionStart { phase: Exploration, ruleset: "pf2e-v1.2" }
├── v1: PlayerAction { agent: "did:key:alice", action: "search the ruins" }
├── v2: AINarration { agent: "did:key:squirrel", text: "You find a locked door..." }
├── v3: PlayerChoice { agent: "did:key:alice", choice: "pick the lock" }
│   ├── v4a: SkillCheck { skill: "Thievery", dc: 20, roll: 18, degree: Failure }
│   │   └── v5a: Consequence { condition: Condition::new("Detected", 1), scope: "encounter" }
│   └── v4b: [BRANCH — "what if I break it down?"]
│       └── v5b: SkillCheck { skill: "Athletics", dc: 15, roll: 22, degree: Success }
├── v6: PhaseTransition { from: Exploration, to: Encounter }
├── v7: InitiativeRoll { participants: [...], order: [...] }
└── ...

Key properties:

• Branching is native — “what if?” is a DAG fork, not a save file
• Every roll is a vertex — provable, auditable, no phantom crits
• NPC memory accumulates — the guard remembers being alerted
• Conditions have temporal scope — Frightened 2 decays structurally across turn vertices

Evolution goals (from RPGPT → benefits all domains):

loamSpine — Permanent Record and Constraint Engine

🪨📖 loamSpine anchors things that survive beyond a session AND constrains the AI:

Evolution goals:

sweetGrass — Creative Attribution

Tracks who built the world:

The player who designs the quest gets higher attribution than the AI that narrates it. If the AI generates a compelling NPC from the player’s template, 🍯🌾 sweetGrass tracks: Player designed template (Creation) → AI implemented dialogue (Implementation) → Player’s choices evolved personality (Extension).

FATE Aspects as 🍯🌾 sweetGrass entities: An Aspect like “Haunted by the Ghost of My Mentor” becomes a semantic entity with a derivation chain — created during character creation (player, Creation), invoked during session 2 combat (player, Extension), compelled during session 3 negotiation (AI, Implementation), evolved to “Made Peace with My Mentor’s Ghost” in session 4 (player, Extension). Full provenance.

Squirrel (AI/MCP) — Constrained Storytelling Engine

🐿️🧠 Squirrel reads the DAG, references the ruleset cert, and generates constrained narration:

The AI is not a freeform chatbot. It operates within provably anchored constraints. If the ruleset says “Resist Fire 5 halves fire damage”, the AI must apply that. The ruleset cert is the contract.

ludoSpring — Session Quality Measurement

🎮♨️ ludoSpring’s 13 validated HCI models evaluate whether the session is actually fun:

BearDog — Anti-Cheat Signing

Every game action is 🐻🐕 BearDog-signed. The anti-cheat isomorphism:

The Player-as-DM Model

Traditional RPGs have a DM (Dungeon Master) who builds the world and the AI narrates within it. RPGPT inverts the common “AI is the DM” pattern:

1. Player designs: World setting, quest hooks, NPC templates, tone, stakes (Creation attribution)
2. Player sets the stage: Opening scene, initial situation, available paths (Design attribution)
3. AI assists: Narrates consequences, voices NPCs within their templates, interprets rules (Implementation attribution)
4. Player choices evolve: Decisions create new DAG branches, NPC personalities shift, world state changes (Extension attribution)
5. AI follows: Maintains internal consistency, applies rules, tracks conditions (Maintenance attribution)

The player is the creative director. The AI is the execution engine. 🍯🌾 sweetGrass tracks this distinction precisely.

This is not a chatbot — the 🌱🔐 rhizoCrypt DAG gives it structure. You can:

• Fork a branch to explore “what if I’d negotiated instead of fighting?”
• Return to any vertex and take a different path
• View the full DAG of your campaign as a tree of decisions
• Compare branches (the negotiation path was higher-Flow than the combat path)
• Merge worlds (two players’ campaigns share a world — their DAGs are separate sessions in the same world-state)

Connection to Existing Papers

Experimental Validation (ludoSpring V3)

The architecture described above is no longer theoretical — three experiments validate the core claims:

Additionally, exp053 (Extraction Shooter Provenance, 65 checks) proves the core thesis of this paper — anti-cheat is chain-of-custody — with 12 concrete fraud types detected purely through DAG provenance analysis. The same orphan-item detector that catches duped extraction shooter loot catches phantom swords in an RPG.

What We Build

Phase 1: Ruleset-as-Certificate Format

Define machine-readable subsets of open rulesets as 🪨📖 loamSpine certificates:

• PF2e ability scores, proficiency, action economy, degrees of success, conditions
• FATE Aspects, Fate Points, invocations, compels
• Generic interfaces that any ORC/CC-BY system can implement
• This is the constraint document the AI must respect — the contract

Phase 2: Session DAG (rhizoCrypt Gaming Mode Evolution)

Build on existing SessionType::Gaming to add:

• Turn structure (round → turn → N actions per ruleset)
• Dice roll vertices with ruleset-specific outcome evaluation
• Condition application and decay (temporal vertex metadata)
• Phase transitions (encounter ↔ exploration ↔ downtime state machine)
• NPC memory accumulation across sessions

Phase 3: AI Narration Loop (Squirrel + ludoSpring)

• 🐿️🧠 Squirrel reads DAG context + ruleset cert + NPC templates
• Generates narration constrained by anchored rules
• 🎮♨️ ludoSpring measures engagement/flow/fun per session
• DDA adjusts encounter difficulty based on metrics

Phase 4: Attribution + Economics (sweetGrass + sunCloud)

• Player world-building gets Creation attribution
• AI narration gets Implementation attribution
• NPC personality evolution tracked as Derivation
• If the world becomes shareable, sunCloud radiates value to creators

Provenance Trio Evolution Goals (Scaffolded by RPGPT)

These evolution goals apply across all springs — RPGPT is the proving ground:

rhizoCrypt

• Turn-based session mode with configurable action economy
• Condition tracking with temporal decay across turn vertices
• Branch diff and merge for “what if?” exploration
• NPC-scoped vertex queries across sessions
• Phase transition state machine (configurable per ruleset)

loamSpine

• Ruleset certificate type (machine-readable, queryable)
• CharacterSheet certificate type (system-agnostic base + system-specific extensions)
• NpcTemplate certificate type (personality, knowledge bounds, voice)
• WorldEntry certificate type (canon level, authorship, derivation)
• Lending via Loan slice mode (“play my character for a session”)

sweetGrass

• Multi-agent creative attribution (player + AI + NPC derivation chains)
• Narrative entity extraction (quest, NPC, location as semantic entities)
• Session contribution rollup (“who built tonight’s session?”)
• Personality evolution tracking (NPC drift attributed to player interactions)
• FATE Aspect lifecycle as derivation chain

License Note

All game mechanics referenced from ORC-licensed material (Pathfinder 2e) are used under the ORC License. The ORC License is irrevocable and system-agnostic. Reserved Material (Pathfinder trademarks, Golarion setting, named characters) is NOT used. Only open mechanical structures are referenced.

FATE Core mechanics are used under CC-BY 3.0 (Evil Hat Productions).

🔧🦎 ecoPrimals code remains AGPL-3.0-or-later.