Structure Notes

The Core Reference Problem

The information age once relied on physical books. Gaming was no different. Now, apparently, physical books are more for filling shelves and bragging rights. The age of hauling bursting backpacks and milk crates full of books to every game is over. Now we want it all in an easy to reference format like PDF or a spiffy web-based reference site. This means that page numbers and book names are less effective for quick reference. Some OSR systems understood this as they expanded their lines and needed a simple method of reference. We're planning for this from the start to avoid any confusion later.

This is especially important because our core rules are genre neutral, relying on genre catalogs for setting details. The interconnectivity is critical to our intended design.

Our RPG Reference Issues:

• The Core Rules need to be quick and easy to find and reference.
• Genre Catalogs must cleanly connect to the Core Rules without duplicating content.
• Cross-references must survive format changes: print, web, etc.

A page number that works in print breaks the moment you reformat for the web. An HTML anchor that works on the website is meaningless on the printed page.

The Reference Code System

Each mechanical element in AxiomRPG is assigned an alphanumeric notation. These notations don't change unless the content is completely recategorized.

Notation Structure

[Layer].[Domain].[Section]

Examples:
AX.C.02      → Core | Dice Mechanics
AX.GF.07     → Genre: Fantasy | Lineages
AX.GH.09     → Genre: Horror | Perks
AX.C.09      → Core | Perks

Layer Notation

Domain Notation (examples)

Section Notation

The following section numbering is shared across all AxiomRPG documents. Core and Genre Catalogs use the same section numbers for the same topics, so a reader always knows that Section 06 covers Lineages, regardless of which book they're holding.

The Full Catalog message indicates sections where the Core passes control to the Genre Catalogs so authors can create their world. Other sections will usually be supplemental in nature, expanding Core content with new information and rules.

How Notation Appears in Text

In print: Codes appear in a small grey tag in the margin or inline in brackets: [→ AX.C.05] for a cross-reference, [AX.C.05] at the heading of a section to anchor it.

On the web: Codes map directly to URL slugs and HTML anchor IDs. AX.C.05.3 becomes axiomrpg.com/ax-c/05/3 and id="AX-C-05-3" in the page HTML.

In a Genre Catalog referencing Core: (see AX.C.05) — no page number needed. Readers on the web click it; readers in print can find the code on the running header of that section.

Document Architecture

The Hierarchy

TIER 1: CORE RULES                    (AX.C)
        │
        │   Genre-neutral. Never references any catalog.
        │   Defines frameworks; leaves the fill-in points blank.
        │
TIER 2: GENRE CATALOGS               (AX.G*)
        │
        │   Setting-specific. Always references core by code.
        │   Never replicates core text — only cites it.
        │   May override defaults only where core explicitly
        │   permits override.
        │
TIER 3: SUPPLEMENTS & ADVENTURES     (AX.S*)
        │
            References both core and the relevant catalog(s).
            Must declare catalog compatibility in the front matter.

When a writer is unsure whether something belongs in the Core or a Genre Catalog, the simplest test is: does this reference anything setting-specific?

• If yes, it's Genre Catalog material
• If no, there's probably a Core Rule for it

This provides logical direction for what an author needs to build versus simply referencing existing rules.