Runnable products sold as sessions to prepare and run—one-shots, arcs, full campaign books, organized-play style modules—“content you schedule.” Prep/play structure (crawl vs heist vs mystery) belongs on adventure structure tags, not separate product-type rows for each pattern.

Creature- or foe-forward SKUs whose main promise is stat blocks, ecology, factions of monsters, summoning fodder, or encounter-ready enemies as a standalone library. Exclude pure gear books and pure lore gazetteers; exclude full plotted adventures unless the SKU is unmistakably “monster codex first.”

Only if bundles are first-class catalog rows: explicit bundle SKUs with their own IDs and pricing semantics, distinct from listing every component separately. Skip or leave unused if bundles exist only as storefront composites.

Lore-, place-, or culture-forward books—gazetteers, setting bibles, atlases, histories—where imagination of the world sells the SKU. Attached mechanics are fine when they reinforce culture or factions; classify as adventure only when the spine is scripted play, not encyclopedic geography and factions.

Rare escape hatch for odd hybrids, legacy migrations, licensing-only stubs, or one-offs that genuinely don’t fit. Anything here should get a quarterly review—promote it to a real type, split SKUs, or delete—so browse and reporting don’t collect junk.

Treat this as the spine of “the game”: the authoritative rules tomes readers mean when they say they need FateTide’s baseline—core character rules, conflict resolution loops, advancement, equipment and task defaults, plus GM-facing procedures that establish normal assumptions. Typical examples sit in whatever you call your main line (player-facing core, GM guide, primary companion volumes). Reserve it for products that reposition the baseline, not every mechanics-heavy supplement.

Use this for dense mechanical books that broaden or deepen play without redrawing the whole foundation: optional class or build compendia, advanced character modules, big options lists, granular subsystems packaged as references rather than lore books or runnable scenarios. If you merge scopes later, think of this as “rules-heavy but not core-line and not creature/loot/setting-first.”

Utility products optimized for facilitation: generators, printable packs, worksheets, decks of prompts, big table collections—things used at the table more than read cover-to-cover as a core book.

Gear- and loot-forward products: magic item catalogs, equipment libraries, hoard tables, relic lines, crafting tied to possessions, vehicle or base upgrades framed as acquisitions. Separate from spells-only references and from general rules expansions unless the mechanics mainly govern what characters own and wield.