Skip to content

bivex/loreSystem

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

424 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Python 3.11+ DDD 200+ entities MCP Server Agent Teams 100% repo coverage

🧢 MythWeave Chronicles

Complete lore management system for AAA game development β€” 200+ entity types, AI-powered extraction, and multi-agent team coordination.

MythWeave turns raw narrative text into structured, validated game lore. Feed it a chapter of your game's story, and a team of specialized AI agents will extract characters, locations, quests, factions, items, cinematics β€” everything β€” into a clean JSON knowledge base.

πŸ”€ How this differs from MiroFish technically

This repository is the canonical lore / world-model layer. The embedded MiroFish/ project is a simulation runtime + interactive report UI.

Current recommendation: for new lore generation, extraction, and structured entity write-back workflows, prefer CAMEL.Bridge/ in this repo first. Use MiroFish/ only when you specifically need the simulation runtime, social-agent behavior, or the interactive report UI.

Aspect loreSystem (this repo) MiroFish/ subproject
Primary role Structured lore extraction, validation, storage Multi-agent social simulation, report generation, graph exploration
Backend style Python-first DDD / repository architecture Flask API orchestrating simulation and report workflows
Frontend Optional local GUI (PyQt6) + CLI + MCP Web frontend with Vue 3 + Vite + D3
Core AI pattern Claude Code agent teams + domain extraction skills OASIS/CAMEL agent simulation + ReportAgent tool calling
Data layer SQLite / SQLAlchemy / in-memory repositories / Elasticsearch Zep Cloud + Cognee-style graph memory + runtime action logs
Package/runtime tooling Poetry/pip-style Python workflow Mixed npm + uv + Python backend workflow

In short: loreSystem compiles the world canon, while MiroFish simulates how actors behave inside that world. They are complementary systems, not the same stack in different folders β€” and right now the preferred default path is CAMEL.Bridge/ inside loreSystem, not the MiroFish/ subproject.

πŸ—ΊοΈ CAMEL.Bridge continuity architecture

This C4 diagram shows the preferred current generation path: CAMEL.Bridge CLI β†’ RumorBridgeService β†’ canonical SQLite persistence, optional Qdrant semantic memory, and canon-control via CanonicalPersistEngine.

CAMEL.Bridge continuity architecture


✨ Key Features

Feature Description
200+ Entity Types 34 categories covering every aspect of AAA game design
Agent Teams 5 specialist AI teams extract lore in parallel
33 Domain Skills Claude Code skills for entity extraction from text
MCP Server Model Context Protocol server with 22 CRUD tools
DDD Architecture Clean Domain β†’ Application β†’ Infrastructure layers
Multi-tenant Run multiple game projects simultaneously
Dual Storage In-Memory and SQLite backends, 100% repository coverage
Validation Invariant checks, UUID tracking, version control

πŸš€ Quick Start

Prerequisites

Installation

git clone https://github.com/bivex/loreSystem && cd loreSystem
python -m venv venv && source venv/bin/activate
pip install -r requirements.txt
make hooks-install

The repository ships its git hooks in .githooks/ so they survive fresh clones. Run make hooks-install once per clone to activate them.

Run

# Main application
python main.py

# Preferred current AI bridge path
python CAMEL.Bridge/run_rumor_pipeline.py --help

# MCP server (standalone)
python lore_mcp_server/run_server.py

# CLI
python -m src --help

# Tests
python -m pytest tests/ -v

πŸ€– LM Studio & Local Models

CAMEL.Bridge now works with local models via LM Studio! No API keys required, fully offline generation.

Setup LM Studio

  1. Install LM Studio
  2. Load a model (tested with L3-8B-Stheno-v3.2-MLX)
  3. Start the server (default: http://127.0.0.1:1234)

Run with Local Model

# Set environment for LM Studio
export CAMEL_MODEL_PLATFORM="OPENAI"
export CAMEL_MODEL_BASE_URL="http://127.0.0.1:1234"
export CAMEL_MODEL_TYPE="l3-8b-stheno-v3.2-mlx"
export CAMEL_MODEL_TEMPERATURE="0.8"

# Run CAMEL Bridge
python CAMEL.Bridge/run_rumor_pipeline.py \
  --tenant-id 1 \
  --world-id 1 \
  --theme "Dark Fantasy" \
  --output-language ru \
  --count 2 \
  --db-path "lore_local.db"

Quick Test Scripts

# Test LM Studio connection
python3 scripts/test_lm_studio.py

# Generate quests with local model
python3 scripts/run_lm_studio.py --type quest --limit 3

Note: Local models are slower than cloud APIs (~8-10s per request) but offer:

  • Zero API costs
  • Full privacy (data never leaves your machine)
  • Custom model fine-tuning
  • Offline operation

πŸ€– Agent Team System

The core power of MythWeave is AI-powered lore extraction. You give it narrative text β€” it gives you structured entities.

Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                  extraction-lead                     β”‚
β”‚            (orchestrator, delegate mode)             β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ narrative β”‚   world   β”‚  society  β”‚systems β”‚  tech  β”‚
β”‚   team    β”‚   team    β”‚   team    β”‚  team  β”‚  team  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Stories   β”‚ Geography β”‚ Factions  β”‚ Skills β”‚ Cinema β”‚
β”‚ Charactersβ”‚ Climate   β”‚ Politics  β”‚ Economyβ”‚ Audio  β”‚
β”‚ Quests    β”‚ Cities    β”‚ Religion  β”‚ Items  β”‚ VFX    β”‚
β”‚ Lore      β”‚ Dungeons  β”‚ History   β”‚ Combat β”‚ Travel β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”˜
        ↓           ↓           ↓          ↓         ↓
  narrative.json world.json society.json systems.json technical.json
        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                          ↓
                   merged_lore.json

Teams & Skills

Team Role Skills Output
extraction-lead Orchestrate, merge, validate lore-extraction, entity-validator, json-formatter entities/merged_lore.json
narrative-team Stories, characters, quests narrative-writing, character-design, quest-design, lore-writing entities/narrative.json
world-team Geography, environments, cities world-building, environmental-design, urban-design entities/world.json
society-team Factions, politics, religion, history faction-design, political-analysis, social-culture, religious-lore, historical-research entities/society.json
systems-team Progression, economy, items, combat progression-design, economic-modeling, legendary-items, + 6 more entities/systems.json
technical-team Cinematics, audio, VFX, transport cinematic-direction, audio-direction, vfx-design, + 6 more entities/technical.json

How to Use

Full team extraction (recommended for chapters / long text):

Create an agent team to extract lore from chapter_1.txt.
Use the extraction-lead agent for coordination.
Spawn all 5 domain teammates.
Use delegate mode so the lead only coordinates.

Selective team (for focused text):

Create an agent team for chapter_1.txt.
Use extraction-lead. Spawn only narrative-team and world-team.

Single skill (quick extraction, no team overhead):

/character-design chapter_1.txt
/world-building chapter_1.txt

When to Use What

Scenario Approach
Full chapter (5+ pages) Agent team with all 5 specialists
Character-focused scene /character-design or narrative-team only
Battle description narrative-team + systems-team
World/map description world-team only
Quick entity check Single skill (/faction-design, /quest-design, etc.)

Cross-Reference Protocol

When a teammate finds an entity belonging to another domain, they log a cross-reference:

{
  "cross_references": [
    {
      "domain": "world-team",
      "entity_type": "location",
      "name": "Eldoria Village",
      "note": "Referenced as protagonist's hometown"
    }
  ]
}

The lead resolves all cross-references during the merge phase, connecting entities across domains.


πŸ“‚ Project Structure

loreSystem/
β”œβ”€β”€ src/                          # Main application (DDD)
β”‚   β”œβ”€β”€ domain/                   #   Entities, value objects, repo interfaces
β”‚   β”œβ”€β”€ application/              #   Use cases, services
β”‚   β”œβ”€β”€ infrastructure/           #   SQLite, InMemory implementations
β”‚   └── presentation/             #   CLI, API
β”‚
β”œβ”€β”€ lore_mcp_server/              # Standalone MCP server
β”‚   β”œβ”€β”€ mcp_server/server.py      #   22 MCP tools
β”‚   └── lore_data/                #   Persistent JSON storage
β”‚
β”œβ”€β”€ CAMEL.Bridge/                 # Preferred current AI bridge for lore generation/write-back
β”‚   └── run_rumor_pipeline.py     #   Live rumor -> narrative -> quest bridge CLI
β”‚
β”œβ”€β”€ .claude/
β”‚   β”œβ”€β”€ agents/                   # 6 team agent definitions
β”‚   β”‚   β”œβ”€β”€ extraction-lead.md    #   Orchestrator
β”‚   β”‚   β”œβ”€β”€ narrative-team.md     #   Stories, characters, quests
β”‚   β”‚   β”œβ”€β”€ world-team.md         #   Geography, environments
β”‚   β”‚   β”œβ”€β”€ society-team.md       #   Factions, politics, religion
β”‚   β”‚   β”œβ”€β”€ systems-team.md       #   Progression, economy, items
β”‚   β”‚   └── technical-team.md     #   Cinema, audio, VFX
β”‚   β”œβ”€β”€ skills/                   # 33 domain extraction skills
β”‚   └── settings.json             # Agent teams + permissions
β”‚
β”œβ”€β”€ entities/                     # Extracted entity output (JSON)
β”œβ”€β”€ examples/                     # Sample lore JSON files
β”œβ”€β”€ tests/                        # Test suite (unit, integration, e2e)
β”œβ”€β”€ docs/                         # Full documentation
β”œβ”€β”€ CLAUDE.md                     # Project context for AI agents
└── AGENTS.md                     # Agent workflow documentation

πŸ›οΈ Architecture

Domain-Driven Design

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚              Presentation                β”‚
β”‚          (CLI, API, MCP Server)          β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚              Application                 β”‚
β”‚        (Services, Use Cases, DTOs)       β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                Domain                    β”‚
β”‚  (Entities, Value Objects, Repo Interfaces)β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚             Infrastructure               β”‚
β”‚    (SQLite, InMemory, Elasticsearch)     β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Repository Status β€” 100% Coverage (18/18)

All repository interfaces are fully implemented with In-Memory + SQLite backends.

Core Lore System (4)
  • WorldRepository β€” Create/list/delete worlds
  • CharacterRepository β€” Manage characters within worlds
  • StoryRepository β€” Create and organize stories
  • PageRepository β€” Manage content pages
World Building (3)
  • ItemRepository β€” Items and inventory
  • LocationRepository β€” World locations and areas
  • EnvironmentRepository β€” Time, weather, lighting
Game Mechanics (8)
  • SessionRepository β€” Active game sessions
  • ChoiceRepository β€” Interactive story choices
  • FlowchartRepository β€” Story branching
  • HandoutRepository β€” Player documents
  • ImageRepository β€” Asset management
  • InspirationRepository β€” Creative prompts
  • MapRepository β€” Game maps
  • TokenboardRepository β€” Combat boards
Content Organization (3)
  • TagRepository β€” Tag-based organization
  • NoteRepository β€” GM notes and annotations
  • TemplateRepository β€” Reusable templates

Note: Only these 18 entities have repository interfaces and are accessible via the MCP server. The remaining 200+ domain entities exist in the domain model β€” their business logic is handled within other entities.


🌍 Domain Model β€” 200+ Entities across 34 Categories

Core Game Systems (50 entities)
Category Count Entities
Campaign & Story 17 Act, Chapter, Episode, Prologue, Epilogue, PlotBranch, Consequence, Ending, AlternateReality
Characters 9 CharacterEvolution, CharacterVariant, CharacterProfileEntry, MotionCapture, VoiceActor
Quests 7 QuestChain, QuestNode, QuestPrerequisite, QuestObjective, QuestTracker, QuestGiver
Skills & Progression 8 Skill, Perk, Trait, Attribute, Experience, LevelUp, TalentTree, Mastery
Inventory & Crafting 9 Inventory, CraftingRecipe, Material, Component, Blueprint, Enchantment, Socket, Rune, Glyph
World Building (39 entities)
Category Count Entities
Locations 10 HubArea, Instance, Dungeon, Raid, Arena, OpenWorldZone, Underground, Skybox, Dimension, PocketDimension
Politics & History 14 Era, EraTransition, Timeline, Calendar, Holiday, Season, TimePeriod, Treaty, Constitution, Law, LegalSystem, Nation, Kingdom, Empire
Economy 8 Trade, Barter, Tax, Tariff, Supply, Demand, Price, Inflation
Military 7 Army, Fleet, WeaponSystem, Defense, Fortification, SiegeEngine, Battalion
Social Systems (22 entities)
Category Count Entities
Social Relations 7 Reputation, Affinity, Disposition, Honor, Karma, SocialClass, SocialMobility
Factions 5 FactionHierarchy, FactionIdeology, FactionLeader, FactionResource, FactionTerritory
Religion & Mysticism 10 Cult, Sect, HolySite, Scripture, Ritual, Oath, Summon, Pact, Curse, Blessing
Content & Creativity (25 entities)
Category Count Entities
Lore System 8 LoreFragment, CodexEntry, JournalPage, BestiaryEntry, Memory, Dream, Nightmare, SecretArea
Music & Audio 8 Theme, Motif, Score, Soundtrack, VoiceLine, SoundEffect, Ambient, Silence
Visual Effects 5 VisualEffect, Particle, Shader, Lighting, ColorPalette
Cinematography 6 Cutscene, Cinematic, CameraPath, Transition, Fade, Flashback
Advanced Systems (29 entities)
Category Count Entities
Architecture 8 District, Ward, Quarter, Plaza, MarketSquare, Slums, NobleDistrict, PortDistrict
Biology & Ecology 6 FoodChain, Migration, Hibernation, Reproduction, Extinction, Evolution
Astronomy 10 Galaxy, Nebula, BlackHole, Wormhole, StarSystem, Moon, Eclipse, Solstice
Weather & Climate 5 WeatherPattern, Cataclysm, Disaster, Miracle, Atmosphere
Gameplay, UGC & Analytics (50+ entities)
Category Count Entities
Narrative Devices 6 PlotDevice, DeusExMachina, ChekhovsGun, Foreshadowing, FlashForward, RedHerring
Global Events 7 WorldEvent, SeasonalEvent, Invasion, Plague, Famine, War, Revolution
Travel 6 FastTravelPoint, Waypoint, SavePoint, Checkpoint, Autosave, SpawnPoint
Achievements 6 Achievement, Trophy, Badge, Title, Rank, Leaderboard
Legendary Items 6 LegendaryWeapon, MythicalArmor, DivineItem, CursedItem, ArtifactSet, RelicCollection
Transport 9 Pet, Mount, Familiar, MountEquipment, Vehicle, Spaceship, Airship, Portal, Teleporter
UGC 5 Mod, CustomMap, UserScenario, ShareCode, WorkshopEntry
Localization 5 Localization, Translation, VoiceOver, Subtitle, Dubbing
Analytics 8 PlayerMetric, SessionData, Heatmap, DropRate, ConversionRate, DifficultyCurve, LootTableWeight, BalanceEntities
Institutions 7 Academy, University, School, Library, ResearchCenter, Archive, Museum
Media 7 Newspaper, Radio, Television, Internet, SocialMedia, Propaganda, Rumor
Secrets 8 SecretArea, HiddenPath, EasterEgg, Mystery, Enigma, Riddle, Puzzle, Trap

πŸ”§ 33 Extraction Skills

All skills live in .claude/skills/ with YAML frontmatter for auto-discovery by Claude Code.

Domain Skills (30) β€” auto-invoked by Claude when relevant
Skill Entities Team
narrative-writing Story, Chapter, Act, Episode, PlotBranch narrative
character-design Character, Relationships, Evolution, Variants narrative
quest-design Quest, QuestChain, Objectives, MoralChoice narrative
lore-writing LoreFragment, Codex, Bestiary, Dreams narrative
world-building Location, Dungeon, Arena, Dimension world
environmental-design Weather, Atmosphere, Lighting, Disasters world
urban-design District, Ward, Market, Plaza world
faction-design Faction, Hierarchy, Territory, Ideology society
political-analysis Government, Law, Court, Treaty society
social-culture SocialClass, Honor, Karma, Festival society
religious-lore Cult, Ritual, Blessing, Curse, Scripture society
historical-research Era, Timeline, Calendar, Ceremony society
progression-design Skill, Perk, Trait, TalentTree, XP systems
economic-modeling Trade, Currency, Shop, Supply/Demand systems
legendary-items Artifacts, Runes, Enchantments, Relics systems
achievement-design Trophy, Badge, Rank, Leaderboard systems
puzzle-design Puzzle, Riddle, Trap, EasterEgg systems
military-strategy Army, Fleet, Fortification, War systems
biology-design Ecosystem, FoodChain, Evolution systems
celestial-science Galaxy, Star, BlackHole, Eclipse systems
analytics-balance DropRate, DifficultyCurve, LootTable systems
cinematic-direction Cutscene, CameraPath, Flashback technical
audio-direction Music, SoundEffect, Motif, Ambient technical
vfx-design Particle, Shader, Lighting, ColorPalette technical
transport-design Mount, Vehicle, Portal, Airship technical
content-management Mod, Localization, UGC, Workshop technical
media-analysis Newspaper, Radio, Propaganda, Rumor technical
research-design Academy, Library, Archive, Museum technical
ui-design Choice, Flowchart, Handout, Tag technical
technical-systems 193 catch-all entity types (safety net) technical
Base Skills (3) β€” background knowledge, auto-loaded
Skill Purpose
lore-extraction Base extraction rules for all agents
entity-validator Type checking, required fields, deduplication
json-formatter Strict JSON output, UUID generation, schema compliance

πŸ”Œ MCP Server

The MCP server exposes 22 tools for lore CRUD operations:

python lore_mcp_server/run_server.py

Connect from Claude Code, Claude Desktop, or any MCP client. See MCP Server docs for the full API reference.


πŸ“– Documentation

Document Description
User Guide Installation and usage
Documentation Index Full docs navigation
Design & Implementation Architecture decisions, ADRs
Validation & Verification Test reports, edge cases
Feature Guides Detailed feature docs
CLI Quick Reference Command-line usage
MCP Server Docs MCP API reference
Gacha Mechanics Gacha system design

οΏ½ Community Standards

This project follows recommended community standards for open-source development:

Standard Status Description
README βœ… Comprehensive project documentation
Code of Conduct βœ… πŸ“„ Community guidelines and expectations
Contributing βœ… πŸ“ How to contribute to the project
License βœ… πŸ“œ Project licensing information
Security Policy βœ… πŸ”’ Security vulnerability reporting
Issue Templates βœ… πŸ“‹ Standardized issue reporting
Pull Request Template βœ… πŸ”„ Standardized PR submissions

οΏ½πŸ§ͺ Testing

# Full test suite with coverage
python -m pytest tests/ -v --cov=src --cov-report=html

# By marker
python -m pytest tests/ -m unit          # Fast, no I/O
python -m pytest tests/ -m integration   # Database tests
python -m pytest tests/ -m e2e           # Full system

πŸ› οΈ Tech Stack

Layer Technologies
Language Python 3.11+
Architecture DDD, Hexagonal, Repository Pattern
Storage SQLite, SQLAlchemy, In-Memory
Validation Pydantic 2.x
CLI Click, Rich
GUI PyQt6
Search Elasticsearch
Config PyYAML, python-dotenv
DI dependency-injector
AI Claude Code Agent Teams, CAMEL Bridge, 33 Skills, MCP Server
Testing pytest, pytest-cov

🧭 Which path should I use right now?

Prefer CAMEL.Bridge/ when you want

  • structured lore generation directly into SQLite
  • deterministic bridge-owned persistence and smoke testing
  • fast iteration on rumor / event / character / quest / story entity generation
  • the current actively preferred workflow in this repository

Use MiroFish/ when you specifically need

  • social simulation runs
  • report generation over runtime/simulation evidence
  • the web UI / graph exploration flow
  • experimentation with the simulation subproject itself

Practical rule of thumb

If you're deciding where to start today, start with:

python CAMEL.Bridge/run_rumor_pipeline.py --help

Reach for MiroFish/ only if the task is explicitly about simulation or report UX rather than canonical lore generation.


MythWeave Chronicles β€” built for game developers who take their lore seriously.

About

🌍 WORLDBUILDING SOFTWARE. Create universes. Design civilizations. The ultimate storytelling toolkit. πŸ“–

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors