The Quillverse Knowledge Engine

Obsidian + Zotero + rpgcast-xyz Integration Architecture

Version 1.0 — February 2026

Co-authors: Cody Lestelle + Claude Opus 4.6

Abstract

This document proposes an architecture for the Quillverse Knowledge Engine — a system where Obsidian, Zotero group libraries, and the rpgcast-xyz platform (including its MUD, character generators, and web properties) work together as a single living knowledge organism. The core innovation is a feedback loop between fiction and fact: gameplay exploration generates real-world knowledge queries, sourced material enriches the game world, and the distinction between visionary fiction and scholarly citation is structurally maintained at every level.

The architecture draws on Eleanor Konik’s Claude + Obsidian workflow patterns, the Zotero Integration plugin ecosystem, and the existing 150+ document Quillverse corpus spread across four repositories.

The Vision: Forests of Heart-Knowledge-Wisdom
Vault Architecture: The Quillverse Garden
Fiction vs. Fact: The Membrane System
Zotero Integration: The Root System
Claude Code Integration: The Gardener
MUD ↔ Knowledge Base: The Feedback Loop
Git Workflow: The Mycelium Network
Plugin Stack: Recommended Installation
CLAUDE.md: Vault Instructions
Custom Slash Commands
Implementation Roadmap
Appendix A: Existing Corpus Inventory
Appendix B: Template Designs

1. The Vision: Forests of Heart-Knowledge-Wisdom {#1-the-vision}

The Quillverse is not a game with a wiki attached. It is a knowledge garden where play IS research.

When a player roleplays as a mermaid in the MUD, their exploration should surface real folklore, marine biology, and indigenous ocean knowledge. When they encounter a CryptoFae species like Labradorite, the game world connects them to actual mineralogy, Inuit labradorite origin stories, and optical physics. When they follow the Crystal Cycle’s QUEST step (D20 Water/Empathy), they might discover Winona LaDuke’s writings on water sovereignty — not because the game lectures them, but because the knowledge forest is structured so that every fictional path leads to real roots.

The feedback loop:

┌─────────────────────────────────────────────────────┐
│  PLAY → WONDER → QUERY → SOURCE → ENRICH → PLAY    │
│                                                     │
│  MUD exploration    "What are mermaids    Zotero    │
│  Character creation   really based on?"   library   │
│  CrySword sessions   "Is labradorite     adds the   │
│  Rainbow Roads map    actually from       source     │
│                       Labrador?"                     │
│                                           ↓         │
│                                    Obsidian note     │
│                                    with citation     │
│                                           ↓         │
│                                    MUD lore enriched │
│                                    NPC dialogue      │
│                                    Item descriptions │
│                                    Quest hooks       │
└─────────────────────────────────────────────────────┘

This is the TimeKnot — where play and knowledge braid together into something richer than either alone.

2. Vault Architecture: The Quillverse Garden {#2-vault-architecture}

Root Structure

quillverse-vault/
├── CLAUDE.md                          ← Vault instructions for Claude Code
├── .obsidian/                         ← Obsidian config, plugins, themes
│
├── 00-INBOX/                          ← Unprocessed captures (Telegram, quick notes)
│   └── ...
│
├── 01-ATLAS/                          ← Maps of Content (MOCs), indexes, navigation
│   ├── Quillverse MOC.md
│   ├── TEK8 MOC.md
│   ├── Dice Godz MOC.md
│   ├── CrySword SAGA MOC.md
│   ├── CryptoFae MOC.md
│   ├── Rainbow Roads MOC.md
│   └── 7ABCs MOC.md
│
├── 10-LORE/                           ← FICTION — Game world, narrative, worldbuilding
│   ├── campaigns/                     ← Road to Redemption, Fugitive Seas, etc.
│   ├── characters/                    ← JaiRuviel, Ko'a, NPCs, character builds
│   ├── species/                       ← 64 Gemstone Species + boundary species
│   ├── locations/                     ← 13 Zodiac Worlds, 40 Territories, dungeons
│   ├── items/                         ← CrySwords, sacred instruments, artifacts
│   ├── factions/                      ← 8 Guilds, 3 Factions, Pirate Democracy
│   └── sessions/                      ← Play session logs and outcomes
│
├── 20-SYSTEMS/                        ← MECHANICS — Game rules, engines, code docs
│   ├── dice-godz/                     ← GWE, attainment, combat, character creation
│   ├── crysword-saga/                 ← Crystal Cycle, Musician Bond, zine content
│   ├── tek8/                          ← Learning Lotus, 8 petals, 8 capitals
│   ├── cryptofae/                     ← Species system, birth hexagram, discovery
│   ├── mud/                           ← MUD architecture, commands, rooms, items
│   └── generators/                    ← Character sheet generators, Quilltangle docs
│
├── 30-SOURCES/                        ← FACT — Scholarly citations, real-world knowledge
│   ├── literature-notes/              ← One note per Zotero item (auto-generated)
│   ├── indigenous-knowledge/          ← TEK, LaDuke, Cajete, Kimmerer, etc.
│   ├── education/                     ← NSLOtC, garden education, IB framework
│   ├── ecology/                       ← Nature-health, environmental science
│   ├── economics/                     ← Capital flow, cooperative economics, CRA
│   ├── mythology/                     ← Cross-cultural folklore, I Ching, Vedic
│   ├── mineralogy/                    ← Gemstone science, crystal structures
│   ├── music/                         ← Ethnomusicology, instrument traditions
│   ├── policy/                        ← WA state law, UNDRIP, education policy
│   └── game-studies/                  ← RPG design theory, play research
│
├── 40-PROJECTS/                       ← Active work streams
│   ├── zine-quest-2026/               ← Dice Godz Core Rulebook production
│   ├── kickstarter-gazetteer/         ← CrySword SAGA Gazetteer fulfillment
│   ├── eccc-2026/                     ← Emerald City Comic Con planning
│   ├── game-jam/                      ← Rainbow Roads Game Jam
│   ├── peoples-arcade/                ← Afterschool program development
│   └── rpgcast-xyz/                   ← Platform development tasks
│
├── 50-DAILY/                          ← Daily notes, journal, session logs
│   └── 2026/
│       └── 02/
│           └── 2026-02-09.md
│
├── 60-TEMPLATES/                      ← Note templates
│   ├── literature-note.md
│   ├── species-entry.md
│   ├── character-build.md
│   ├── session-log.md
│   ├── lore-entry.md
│   ├── source-annotation.md
│   └── project-brief.md
│
├── 70-ARCHIVES/                       ← Completed projects, old versions
│   └── ...
│
└── 80-META/                           ← Vault maintenance, tag taxonomy, conventions
    ├── tag-taxonomy.md
    ├── conventions.md
    └── fiction-fact-guide.md

Design Principles

Numbered prefixes for folder sort order (Obsidian displays alphabetically)
ATLAS at the top — the “canopy” that lets you navigate the forest
LORE (fiction) and SOURCES (fact) are sibling directories at the same level — equally valued, structurally separated
SYSTEMS bridges both — game mechanics reference both lore and sources
PROJECTS are time-bound; completed work moves to ARCHIVES
DAILY captures temporal flow; everything else is evergreen

3. Fiction vs. Fact: The Membrane System {#3-fiction-vs-fact}

“Distinguishing from gameplay fiction and allegedly real facts and sources will be a crucial part of the archive’s structure(s).”

This is the hardest and most important design challenge. The Quillverse deliberately blurs boundaries — TEK8 is both a game mechanic AND an educational framework. A CryptoFae species is both a fictional character type AND a real mineral with real properties. The Crystal Cycle is both a game session structure AND a pedagogical circuit.

The Membrane Approach

Rather than a hard wall between fiction and fact, we use a semi-permeable membrane — a tagging and metadata system that makes the nature of every claim transparent:

YAML Frontmatter Tags

Every note gets a knowledge_type field:

---
knowledge_type: lore          # Pure fiction / game world
knowledge_type: source        # Scholarly/verified citation
knowledge_type: bridge        # Game mechanic grounded in real knowledge
knowledge_type: synthesis     # Original analysis connecting multiple sources
knowledge_type: speculation   # Hypothesis, unverified claim, creative extrapolation
---

Visual Callout Convention

Within notes, use Obsidian callouts to flag transitions:

> [!lore] In-World Knowledge
> The Labradorite CryptoFae are said to be fragments of the Northern Lights
> trapped in stone by the Ether Guild during the First Crystallization.

> [!source] Real-World Connection
> Labradorite is a feldspar mineral first identified in 1770 on Paul's Island,
> Labrador, Canada. Inuit legend holds that the Northern Lights were once
> trapped in rocks along the coast until a warrior freed them with his spear.
> — Source: [[laduke_traditional_1994]]

> [!bridge] TEK8 Integration
> The Labradorite species occupies the Chaos/D10 petal because its optical
> phenomenon (labradorescence) emerges unpredictably from internal crystal
> structure — order creating apparent chaos. This maps to the D10 Mind/Willpower
> attribute: consciousness emerging from material substrate.

Tag Taxonomy for Knowledge Types

#fact/verified        — Peer-reviewed, multiply sourced
#fact/reported        — Single source, journalistic
#fact/indigenous      — Traditional knowledge (cite tradition, not "verify")
#fact/scientific      — Empirical/experimental
#lore/canon           — Established game world truth
#lore/player-created  — Player-contributed narrative
#lore/evolving        — Subject to change via gameplay
#bridge/tek8          — TEK8 educational mapping
#bridge/mechanic      — Game mechanic with real-world basis
#bridge/metaphor      — Deliberate fictional metaphor for real concept
#speculation/hypothesis — Untested claim
#speculation/creative  — Imaginative extrapolation

The “Source Trail” Convention

Any factual claim in a LORE note must include a source trail:

The D20 is mapped to Water in TEK8 because water is the element of empathy
and taste. ^[bridge/tek8 — See [[TEK8_Learning_Lotus]] for mapping rationale]
^[fact/indigenous — Ayurvedic tradition associates water with rasa (taste/juice).
See [[charaka_samhita_water_element]]]

This way, a reader exploring lore can always trace backward to the real-world knowledge that inspired it. The MUD can surface these trails as “lore depth” — hover over a description and see the scholarly roots.

4. Zotero Integration: The Root System {#4-zotero-integration}

The 7ABCs Zotero group library (group 6420794, 208 items) is the root system of the knowledge forest. Every scholarly source lives there with structured metadata and annotations.

Recommended Plugin Stack

Tool	Purpose
Better BibTeX (Zotero)	Generates stable citation keys (e.g., `laduke_traditional_1994`)
Zotero Integration (Obsidian, by mgmeyers)	Live connection to Zotero desktop; imports citations, annotations, literature notes

Setup Steps

Install Better BibTeX in Zotero 7
- Preferences → Better BibTeX → Citation key format: auth.lower + '_' + shorttitle(3,3) + '_' + year
- This produces keys like laduke_traditional_1994, kimmerer_braiding_2013
Sync group library locally
- Zotero desktop → Groups → 7abcs should appear
- All 208 items + annotations sync to local Zotero
Install Zotero Integration in Obsidian
- Settings → Zotero Integration → Database: “Zotero”
- Literature note folder: 30-SOURCES/literature-notes/
- Configure Nunjucks template (see Appendix B)
Set up BBT auto-export (optional but recommended)
- Right-click 7abcs library → Export → Better CSL JSON → Save to quillverse-vault/80-META/7abcs-library.json
- Check “Keep updated” for auto-sync

Workflow: Adding a New Source

1. Find source (paper, book, article, traditional knowledge record)
2. Add to Zotero → 7abcs group library → appropriate collection
3. Annotate PDF in Zotero's reader (color-coded: yellow=key, red=concept, green=resource)
4. In Obsidian: Cmd+Shift+I → "Create Literature Note" → select item
5. Template auto-generates note in 30-SOURCES/literature-notes/
6. Manually add [[wikilinks]] connecting to relevant LORE and SYSTEMS notes
7. Update relevant MOC in 01-ATLAS/

Workflow: Citing in a Lore Note

In the Road to Redemption campaign, the concept of "cultural continuity as
protective factor" manifests through the Crying Depths — a dungeon where
ancestral memory is literally under siege.

> [!source] Scholarly Basis
> Chandler & Lalonde (1998) found that First Nations communities with markers
> of cultural continuity had youth suicide rates 102.8/100,000 LOWER than
> those without. [[@chandler_cultural_1998]]

The [[@citekey]] syntax is recognized by Zotero Integration and creates a live link back to the Zotero item.

5. Claude Code Integration: The Gardener {#5-claude-code-integration}

Claude Code operates as the gardener of the knowledge forest — planting new notes, pruning connections, grafting sources onto lore, and reporting on the health of the ecosystem.

Recommended Approach: polyipseity Terminal + Claudian

Two complementary plugins:

Plugin	Use Case
Terminal (polyipseity)	Full shell access inside Obsidian; for `git`, `npm`, running scripts, Claude Code CLI with full tool access
Claudian (YishenTu)	Sidebar chat with `@file` references, inline editing with diff preview, plan mode toggle

Why both? Terminal gives you the full Claude Code CLI experience (tools, plan mode, task spawning, MCP). Claudian gives you quick inline edits and conversational file references without leaving the editor.

Alternative: MCP Bridge

The obsidian-claude-code-mcp plugin (by iansinnott) exposes the vault as a structured API via Model Context Protocol. This means Claude Code running in any terminal (not just inside Obsidian) can access the vault’s structure, active files, and create/edit notes through the MCP tool interface. Setup: install the plugin, then in Claude Code run /ide → select “Obsidian”.

Knowledge Gardening Tasks

Claude Code can perform these vault maintenance operations:

Orphan detection — Find notes with no incoming links (isolated knowledge)
Bridge building — Identify lore notes that reference real concepts but lack source links
Source gap analysis — Scan SOURCES for topics with only 1-2 items; suggest acquisitions
Tag consistency — Ensure all notes have knowledge_type frontmatter
MOC updating — Regenerate Maps of Content when new notes are added
Species enrichment — For each of the 64 Gemstone Species, check whether the corresponding mineral has a literature note with real mineralogical data
Session processing — After a MUD or TTRPG session, process the log into structured notes (characters encountered, lore revealed, knowledge queries generated)

Plan Mode for Vault Work

Always use Plan Mode (Shift+Tab twice) before:

Reorganizing folder structures
Bulk-updating frontmatter across many files
Creating new MOCs or indexes
Any operation touching 5+ files

Plan Mode lets Claude read everything, map relationships, and present a plan before modifying anything. Review the plan with Ctrl+G (opens in editor) before executing.

6. MUD ↔ Knowledge Base: The Feedback Loop {#6-mud-knowledge-base-feedback-loop}

This is the most novel and ambitious part of the architecture: connecting the MUD (and future Quillverse virtual environments at paladinking.com, rpgcast.xyz, quillverse.org) directly to the knowledge forest.

Architecture: Three Layers

┌─────────────────────────────────────────┐
│  LAYER 3: EXPERIENCE                    │
│  MUD / Web UI / Character Generators    │
│  Player sees: room descriptions, NPC    │
│  dialogue, item lore, quest text        │
│  ↕ (API / content pipeline)             │
├─────────────────────────────────────────┤
│  LAYER 2: KNOWLEDGE BASE                │
│  Obsidian Vault                         │
│  Structured notes with fiction/fact     │
│  membrane, wikilinks, citations         │
│  ↕ (Zotero Integration + git sync)     │
├─────────────────────────────────────────┤
│  LAYER 1: SOURCE LIBRARY                │
│  Zotero 7ABCs Group Library             │
│  208+ items with annotations            │
│  PDFs, DOIs, structured metadata        │
└─────────────────────────────────────────┘

Content Pipeline: Vault → MUD

The MUD’s room descriptions, NPC dialogue, and item text can be authored in Obsidian and deployed to the MUD:

10-LORE/locations/crying-depths/
├── entrance.md          ← Room description + source annotations
├── crystal-chamber.md   ← Description + mineralogy sources
└── hag-kings-throne.md  ← Description + folklore sources

Each location note contains:

description field in YAML frontmatter (the text players see)
Body of the note contains deeper lore, source citations, and design notes
A build script extracts description fields and generates MUD content files

Knowledge Queries: MUD → Vault

When a player encounters something in the MUD that piques curiosity, the system should make it easy to explore deeper:

“Examine” command in MUD — examine crystal shows the room description PLUS a “Learn More” link/tag indicating real-world connections exist
Knowledge depth levels:
- Surface: “This crystal shimmers with internal fire” (lore)
- Curious: “Labradorite exhibits labradorescence, an optical effect caused by light diffracting between layers of feldspar” (bridge)
- Scholar: “First described by Moravian missionaries in Labrador, 1770. See: [Zotero link]” (source)
Query logging — When players ask questions the MUD can’t answer, those queries are captured in 00-INBOX/ as knowledge gaps to be filled

The Enrichment Cycle

Player roleplays as mermaid character
  → MUD room: "Coral gardens stretch before you..."
    → Player types: EXAMINE CORAL
      → "Precious Coral (Corallium rubrum) has been harvested in the
         Mediterranean for 5,000 years. The Ko'a CryptoFae species embodies
         coral's patience — growing 1mm per year."
        → [LEARN MORE] links to literature note
          → Literature note cites actual marine biology sources
            → Player's curiosity becomes real knowledge
              → Player's next roleplay action is richer
                → GM/system adds new coral-related content
                  → New sources discovered, added to Zotero
                    → Cycle continues...

Implementation: Neon Database as Bridge

The rpgcast-xyz platform already uses Neon PostgreSQL (project: sweet-heart-33815315). The knowledge bridge can work through:

Content table: Stores MUD-ready text extracted from Obsidian vault
Source links table: Maps game objects → Zotero citation keys
Knowledge gaps table: Captures player questions for inbox processing
Sync script: Runs on git push, extracts frontmatter from vault, updates Neon

-- Example schema additions
CREATE TABLE knowledge_content (
  id SERIAL PRIMARY KEY,
  vault_path TEXT UNIQUE,        -- '10-LORE/species/labradorite.md'
  knowledge_type TEXT,           -- 'lore', 'source', 'bridge'
  game_text TEXT,                -- Player-visible description
  deep_text TEXT,                -- Extended lore for EXAMINE
  updated_at TIMESTAMPTZ DEFAULT NOW()
);

CREATE TABLE source_links (
  id SERIAL PRIMARY KEY,
  content_id INT REFERENCES knowledge_content(id),
  zotero_citekey TEXT,           -- 'laduke_traditional_1994'
  relevance_note TEXT,           -- Why this source matters here
  depth_level TEXT               -- 'curious' or 'scholar'
);

CREATE TABLE knowledge_gaps (
  id SERIAL PRIMARY KEY,
  player_query TEXT,             -- "what are mermaids based on"
  context TEXT,                  -- Where in the game this came up
  status TEXT DEFAULT 'open',    -- 'open', 'researching', 'resolved'
  resolved_note TEXT,            -- Vault path of the note that answered it
  created_at TIMESTAMPTZ DEFAULT NOW()
);

7. Git Workflow: The Mycelium Network {#7-git-workflow}

The vault needs version control for collaboration, backup, and Claude Code’s change tracking.

Recommended: obsidian-git Plugin

Plugin: Vinzent03/obsidian-git

Configuration:

Auto-commit interval: 10 minutes
Auto-pull on startup: enabled
Commit message format: vault: {{date}} {{numFiles}} files

.gitignore:

.obsidian/workspace.json
.obsidian/workspace-mobile.json
.obsidian/plugins/*/data.json
.trash/

Repository Strategy

Option A: Vault as its own repo (Recommended for now)

quillverse-vault/          ← Its own git repo
├── .git/
├── CLAUDE.md
└── ... (vault contents)

Option B: Vault as workspace member (Future, when rpgcast-xyz moves to monorepo)

rpgcast-xyz/
├── package.json           ← workspaces: ["mud", "vault"]
├── mud/
├── vault/                 ← Obsidian vault, workspace member
│   └── ... (vault contents)
└── src/                   ← Astro app

Start with Option A. The vault’s git history will be primarily documentation changes, which have different commit patterns than code. Keep them separate until there’s a clear reason to merge.

Syncing Content Between Repos

For content that needs to exist in both the vault AND rpgcast-xyz (e.g., the 35 markdown docs currently in /home/z/rpgcast-xyz/):

Move originals into vault — The vault becomes the source of truth for all documentation
Symlink or copy script — A script copies relevant files from vault to rpgcast-xyz when needed
CI/CD pipeline (future) — GitHub Actions on vault push extracts MUD content, updates Neon DB

8. Plugin Stack: Recommended Installation {#8-plugin-stack}

Essential (Install First)

Plugin	Purpose	Source
Terminal (polyipseity)	Shell access inside Obsidian	Community Plugins
Zotero Integration (mgmeyers)	Zotero ↔ Obsidian bridge	Community Plugins
obsidian-git (Vinzent03)	Version control	Community Plugins
Dataview (blacksmithgu)	Query notes as data	Community Plugins
Templater (SilentVoid)	Advanced note templates	Community Plugins

Recommended (Install Second)

Plugin	Purpose	Source
Claudian (YishenTu)	Claude Code sidebar + inline edit	Community Plugins / BRAT
Calendar	Daily note navigation	Community Plugins
Tag Wrangler	Manage tag taxonomy	Community Plugins
Excalidraw	Visual diagrams (TEK8 Lotus, maps)	Community Plugins

Optional (Install When Needed)

Plugin	Purpose	Source
obsidian-claude-code-mcp	MCP bridge for remote Claude access	GitHub
Kanban	Project task boards	Community Plugins
Graph Analysis	Enhanced graph view metrics	Community Plugins
Breadcrumbs	Hierarchical navigation	Community Plugins

9. CLAUDE.md: Vault Instructions {#9-claude-md}

The following CLAUDE.md should be placed at the vault root:

# Quillverse Knowledge Engine — Claude Code Instructions

## Identity
This is the Quillverse Knowledge Engine vault. It serves as the central
knowledge base for the Quillverse ecosystem: RPGCast.xyz, TimeKnot Games,
CrySword SAGA, Dice Godz, TEK8, and all related projects.

## File Versioning Policy (CRITICAL)
NEVER overwrite existing files. Always create new versions:
- document_v1.0.md → document_v1.1.md → document_v2.0.md
- Major changes = first number. Minor changes = second number.
- Never delete iterations. All drafts have historical value.

## Folder Structure
- 00-INBOX/ — Unprocessed captures. Process into appropriate folders.
- 01-ATLAS/ — Maps of Content. Index and navigation notes only.
- 10-LORE/ — FICTION. Game world, narrative, characters, worldbuilding.
- 20-SYSTEMS/ — MECHANICS. Rules, engines, educational frameworks.
- 30-SOURCES/ — FACT. Scholarly sources, citations, literature notes.
- 40-PROJECTS/ — Active work streams with deadlines.
- 50-DAILY/ — Daily notes in YYYY/MM/YYYY-MM-DD.md format.
- 60-TEMPLATES/ — Note templates. NEVER modify directly.
- 70-ARCHIVES/ — Completed work. Move here, don't delete.
- 80-META/ — Vault maintenance, conventions, tag taxonomy.

## Knowledge Type System
Every note MUST have knowledge_type in YAML frontmatter:
- lore: Pure fiction / game world content
- source: Scholarly/verified citation with Zotero citekey
- bridge: Game mechanic grounded in real knowledge
- synthesis: Original analysis connecting multiple sources
- speculation: Hypothesis or creative extrapolation

## Linking Conventions
- Use [[wikilinks]] for internal vault links
- Use [[@citekey]] for Zotero citations (e.g., [[@laduke_traditional_1994]])
- Every lore note making factual claims MUST include a source trail
- Use callouts for knowledge type transitions:
  > [!lore], > [!source], > [!bridge], > [!speculation]

## What NOT To Do
- Never delete any file (move to 70-ARCHIVES/ instead)
- Never modify files in 60-TEMPLATES/ (create new versions)
- Never create notes without knowledge_type frontmatter
- Never mix lore claims with source claims without callout markers
- Never add a source without a corresponding Zotero entry
- Never overwrite — always version

## Key Systems Reference
- TEK8: 8 guilds (D2-D100), elements, senses, abilities, capitals
- Crystal Cycle: 10-step session structure (Coin→Music→...→Close)
- CryptoFae: 64 Gemstone Species via Birth Hexagram (I Ching mapping)
- GWE: Great Wheel of Elements — 6 dice rolled, 2 emergent
- Attainment: roll/max percentage system (equalizes all dice)
- 7ABCs: Educational initiative and Zotero group library

## Zotero Group Library
- Group: 7abcs (ID: 6420794)
- Items: 208+ with annotations
- Integration: Zotero Integration plugin (mgmeyers)
- Literature notes generated in 30-SOURCES/literature-notes/

10. Custom Slash Commands {#10-custom-slash-commands}

Create these as markdown files in .claude/commands/ within the vault:

`/digest-session`

Process a play session log into structured notes.

Read the session log provided and create:
1. A session summary note in 50-DAILY/ with key events
2. New or updated character notes in 10-LORE/characters/
3. New lore entries for any locations, items, or factions encountered
4. A list of knowledge gaps — real-world questions raised by the fiction
5. Put knowledge gaps in 00-INBOX/ for later research

Tag all new notes with appropriate knowledge_type frontmatter.
Follow the file versioning policy — never overwrite existing notes.

`/enrich-species`

Add real-world knowledge to a CryptoFae species entry.

For the species note at $ARGUMENTS:
1. Read the current lore content
2. Research the real-world mineral: geological properties, cultural
   significance across traditions, metaphysical associations, locations
3. Check if a Zotero source exists for this mineral. If not, note the gap.
4. Add > [!source] callouts with real-world connections
5. Add > [!bridge] callouts explaining the TEK8 mapping rationale
6. Update the species MOC in 01-ATLAS/

`/audit-sources`

Check vault health for source integrity.

Scan all notes in 10-LORE/ and 20-SYSTEMS/ for:
1. Factual claims without source trails
2. [[@citekey]] references that don't match any literature note
3. Literature notes in 30-SOURCES/ with no incoming links (orphans)
4. Notes missing knowledge_type frontmatter

Report findings as a checklist. Do not modify any files.

`/bridge-build`

Connect a lore concept to real-world knowledge.

For the concept described in $ARGUMENTS:
1. Identify the real-world domains it touches (ecology, folklore, science, etc.)
2. Search existing 30-SOURCES/ for relevant literature notes
3. Search Zotero library for relevant items not yet in the vault
4. Propose new > [!bridge] callouts connecting fiction to fact
5. List any knowledge gaps that need new sources

Present as a plan — do not modify files until approved.

11. Implementation Roadmap {#11-implementation-roadmap}

Phase 1: Foundation (Week 1)

Create the vault directory and folder structure
Install Obsidian and essential plugins (Terminal, Zotero Integration, obsidian-git, Dataview, Templater)
Initialize git repo in vault
Place CLAUDE.md at vault root
Install Better BibTeX in Zotero and configure citation key format
Configure Zotero Integration plugin to connect to local Zotero
Create note templates in 60-TEMPLATES/

Phase 2: Migration (Week 2)

Copy existing 35 markdown files from rpgcast-xyz into appropriate vault folders
Copy 16 docs from quilltangle_v8/docs/ into vault
Copy relevant docs from 8xM/AgileXPS/ into vault
Copy TimeKnot event docs into 40-PROJECTS/
Copy r2r/ campaign files into 10-LORE/campaigns/
Add knowledge_type frontmatter to all migrated files
Create initial MOCs in 01-ATLAS/

Phase 3: Literature Note Generation (Week 2-3)

Run Zotero Integration’s “Create Literature Note” for top 50 most-cited items
Configure Nunjucks template for annotation import
Begin linking literature notes to lore and systems notes
Establish the first source trails in lore notes

Phase 4: Claude Code Integration (Week 3)

Install Claudian plugin
Create custom slash commands
Run /audit-sources to identify gaps
Run /enrich-species on first 8 species (one per petal)
Refine CLAUDE.md based on what works and what doesn’t

Phase 5: MUD Content Pipeline (Week 4+)

Design the content extraction script (vault → MUD)
Create knowledge_content and source_links tables in Neon
Implement EXAMINE command depth levels in MUD
Create knowledge_gaps capture system
Test the full feedback loop with one location (e.g., Crying Depths entrance)

Phase 6: Ongoing Cultivation

Weekly: Process 00-INBOX/ items
Weekly: Update MOCs
After each session: Run /digest-session
Monthly: Run /audit-sources
Continuously: Add sources to Zotero as gameplay generates questions

Appendix A: Existing Corpus Inventory {#appendix-a}

rpgcast-xyz/ (35 markdown files)

Core game design, species systems, character builds, educational frameworks, campaign content, research papers. These form the nucleus of the vault.

quilltangle_v8/docs/ (16 files)

Architecture guides, governance docs, implementation strategies, Garu lifecycle, family education. These belong in 20-SYSTEMS/ and 40-PROJECTS/.

8xM/AgileXPS/ (20+ files)

Educational deployment, Peoples Arcade program, curriculum guides, consolidated TEK8 data. These split between 20-SYSTEMS/tek8/ and 40-PROJECTS/peoples-arcade/.

TimeKnot/ (50+ files)

Event planning, game jam docs, CJSR integration, deployment guides. These belong in 40-PROJECTS/ with completed events moving to 70-ARCHIVES/.

8xM/DiceGodz.Core64/ (5 files + assets)

Species database, digital dharma manifesto, zine content. These belong in 20-SYSTEMS/dice-godz/ and 10-LORE/.

r2r/ (6 files)

Campaign archives — Road to Redemption narrative, character builds, session transcripts. These belong in 10-LORE/campaigns/road-to-redemption/.

Total: ~150 documents to migrate + 208 Zotero items to generate literature notes for

Appendix B: Template Designs {#appendix-b}

Literature Note Template (Nunjucks for Zotero Integration)

---
knowledge_type: source
zotero_citekey: "{{citekey}}"
title: "{{title}}"
authors: [{% for creator in creators %}{% if creator.firstName %}"{{creator.firstName}} {{creator.lastName}}"{% endif %}{% if not loop.last %}, {% endif %}{% endfor %}]
year: {{date | format("YYYY")}}
item_type: "{{itemType}}"
tags: [{% for tag in tags %}"{{tag.tag}}"{% if not loop.last %}, {% endif %}{% endfor %}]
zotero_link: "{{desktopURI}}"
created: "{{importDate | format('YYYY-MM-DD')}}"
---

# {{title}}

> [!info] Citation
> {{bibliography}}
> [Open in Zotero]({{desktopURI}})

## Abstract
{{abstractNote}}

## Annotations
{% for annotation in annotations %}
{% if annotation.annotatedText %}

> [!quote{% if annotation.colorCategory == "Red" %}+ Concept{% elif annotation.colorCategory == "Green" %}+ Resource{% elif annotation.colorCategory == "Orange" %}+ Action{% endif %}] Page {{annotation.page}}
> {{annotation.annotatedText}}
{% if annotation.comment %}
> **Note**: {{annotation.comment}}
{% endif %}

{% endif %}
{% endfor %}

## Relevance to Quillverse
<!-- How does this source connect to TEK8, CrySword SAGA, the 7ABCs initiative? -->

## Connected Notes
<!-- Add [[wikilinks]] to related lore, systems, and bridge notes -->

Species Entry Template

---
knowledge_type: bridge
species_name: ""
petal: ""
die: ""
element: ""
hexagram_number:
hexagram_name: ""
trigram_lower: ""
trigram_upper: ""
mineral_real: true
mohs_hardness:
crystal_system: ""
created: "{{date}}"
---

# {{species_name}}

## In-World Lore
> [!lore]
> <!-- Game world description of this CryptoFae species -->

## Real-World Mineral
> [!source]
> <!-- Geological properties, locations, cultural significance -->
> <!-- Cite Zotero sources with [[@citekey]] -->

## TEK8 Mapping
> [!bridge]
> <!-- Why this species is on this petal -->
> <!-- Connection between mineral properties and die/element/sense -->

## Birth Hexagram
- **Number**: {{hexagram_number}} — {{hexagram_name}}
- **Lower trigram**: {{trigram_lower}} (material nature: D4+D6+D8)
- **Upper trigram**: {{trigram_upper}} (subtle nature: D10+D12+D20)

## Connected Notes
- Petal: [[]]
- Related species: [[]]
- Sources: [[]]

Session Log Template

---
knowledge_type: lore
session_type: ""  # mud, ttrpg, game-jam, playtest
date: "{{date}}"
players: []
characters: []
location_start: ""
location_end: ""
crystal_cycle_step: ""
---

# Session: {{date}}

## Summary
<!-- What happened this session -->

## Characters Encountered
<!-- New or notable characters -->

## Lore Revealed
<!-- New world information discovered -->

## Knowledge Queries Generated
> [!speculation]
> <!-- Questions that came up during play that deserve real-world research -->
> - [ ] Query:
> - [ ] Query:

## Outcomes
<!-- Mechanical outcomes: XP, items, relationships, territory changes -->

## Notes for Next Session
<!-- Loose threads, pending decisions -->

Closing Note

The Quillverse Knowledge Engine is not a content management system — it is a living curriculum. Every note planted in this vault is a seed. Every source added to Zotero is a root. Every game session is sunlight. The feedback loop between fiction and fact is photosynthesis: the process by which imagination and scholarship together create something neither could alone.

The Crystal Cycle says it best:

Coin Music Gather Craft Quest Rest Play Map Yield Close

This vault follows the same cycle. We insert the coin of intention (creating the vault). Music begins (Claude Code and Zotero sing together). We gather (migrating 150 documents). We craft (building templates and structure). We quest (researching and enriching). We rest (archiving completed work). We play (exploring through the MUD). We map (the graph view reveals connections). It yields (knowledge grows). And we close — only to begin again.

Aloha ke akua. Plant the forest.

Document created February 2026. This is v1.0 — the seed. Versions to come as the garden grows.