The traditional way of sharing or customizing tabletop RPG rules—printing PDFs, manually cutting and pasting content, or maintaining separate homebrew documents—is too slow, too clumsy, and too isolated for today’s creators and players.

Our goal is to build a flexible, creator-friendly system that makes it easy to curate, remix, and share not only rules, but also lore, maps, worlds, and modular content. Whether a user wants to create a complete player’s handbook with custom Domains and cultures, or simply download someone else's streamlined hack of the rules, the system should support it natively.

This is about more than software—it’s about supporting a creative economy around RPG content, one that’s non-custodial, permissionless, decentralized, and ultimately player-controlled.

The system must support all of the following:

• ✅ Let individuals curate the exact set of rules they want to use
• ✅ Add and organize private rules and lore content
• ✅ Share rules, lore, and curated handbooks publicly or with specific groups
• ✅ Enable full world-building packages, including:
  • Lore
  • Maps
  • Custom rulesets
  • NPCs, factions, and world history
• ✅ Share, trade, or publish curated content bundles
• ✅ Allow creators to:
  • Charge for access (with low friction)
  • Receive donations or tips
  • Retain full ownership and control over their content or allow it to be freely shared

Every rule or lore element—be it a single spell, Domain feature card, or an entire campaign setting—is stored as a modular data object, ideally using a consistent, parseable format.

We support and encourage:

• Markdown for readable and editable content
• XML for structured data with validation via DTD
• Custom DSLs (Domain-Specific Languages) as optional simplified syntaxes for highly specific content types (e.g., feature cards or map metadata)

The system must support low-friction payments, including:

• Microtransactions (as low as $0.01)
• Optional donations or tips
• Pay-what-you-want pricing models

Requirements:

• Non-custodial: we do not store private keys or handle funds directly
• Low/no transaction fees: favor cryptos with fast and cheap transfers
• Privacy-preserving: no personal info collected, and no tracking

Preferred Options:

• 🧊 Dash – Human-friendly usernames, InstantSend, zero-fee transactions, and Evolution-based features
• 🐶 Dogecoin – Fast, low-cost, and fun
• 🌩️ Lightning Network – Supported if users opt-in, but custodial usage is discouraged

The goal is to avoid centralized dependencies. This includes:

• Hosting and sync: Use distributed systems like IPFS, Hypercore, or BitTorrent to host rule packages and world lore
• Discovery and search: Implement a distributed registry or index so users can find content without relying on a single website
• Offline-first design: Users should be able to browse and use their curated handbooks even when not connected to the internet

Support both:

• A core system for “official” base rules and formats
• Plug-in-like extensions for alternate mechanics, UI modes, or content types

Build or support tools for:

• Creating and testing rule/lore cards
• Integrating with map editors or visual storytelling tools
• Writing lore and content in Markdown or XML with embedded rule objects
• Allowing creators to package entire campaigns or settings as downloadable modules.

• Non-custodial = no liability for payments or content ownership
• Clear licenses (e.g. Creative Commons) for user-generated content
• No DRM: creators are encouraged to charge, but not to impose artificial restrictions on redistribution

• A GM creates a Norse-themed world with 12 Domains, 6 custom species, and a full calendar system. They offer it for $1 or free with donations.
• A group of players recreates the mechanics and setting of a favorite video game using only the relevant rules and lore, shared as a curated handbook.
• A teacher-friendly creator publishes a series of modular cards to teach core rules to kids, earning income through micro-payments and tips.

This is the high-level vision. Technical specifications (schemas, formats, protocols) will be developed and documented in dedicated sub-pages.