CATALOG ARCHITECTURE

Why Catalogs Fail — And How a Platform Should Actually Understand Its Content


Most platforms treat the catalog as a database.

Rows.
Fields.
Metadata.
Filters.

This is the legacy model — a static list of products with tags attached. It works for stores. It does not work for platforms.

A platform needs a catalog that understands:

  • structure
  • relationships
  • identity
  • continuity
  • taxonomy
  • taste
  • play patterns
  • studio identity
  • IP architecture

A database can’t do that.
A catalog can.

The catalog is not a list.
The catalog is a world model.


THE CATALOG PROBLEM

CATALOG PROBLEM
│
├── FLAT STRUCTURE
│     No hierarchy
│     No relationships
│     No identity lanes
│
├── STATIC METADATA
│     Genre tags
│     Store labels
│     Marketing categories
│
└── NO CONTINUITY
        No series logic
        No IP lineage
        No studio identity

Flat catalogs create flat experiences.


THE CATALOG MODEL

A modern platform catalog must be relational, semantic, and structural.

CATALOG MODEL
│
├── IDENTITY LAYER
│     IP identity
│     Studio identity
│     Publisher identity
│
├── TAXONOMY LAYER
│     Loop pattern
│     Tone pattern
│     System pattern
│     Emotional pattern
│
├── CONTINUITY LAYER
│     Series lineage
│     Release cadence
│     Universe mapping
│
├── RELATIONSHIP LAYER
│     Shared systems
│     Shared worlds
│     Shared creators
│
└── SIGNAL LAYER
        Taste Graph inputs
        Play pattern signals
        Social signals

This is how a platform understands content.

Not by tags.
By structure.


WHY THE CATALOG IS A PLATFORM SYSTEM

The catalog is the foundation for:

  • Taste Graph
  • Genre Taxonomy
  • Publisher Architecture
  • Play Architecture
  • Discovery
  • Personalization
  • Continuity
  • Identity
  • Rails
  • Sociality

Every system touches the catalog.
Every system depends on it.


THE CATALOG TREE

PLATFORM CATALOG
│
├── IP
│     Universe
│     Aesthetic identity
│     Narrative identity
│     Mechanical identity
│
├── SERIES
│     Mainline
│     Spin-offs
│     Remasters
│     Reboots
│
├── STUDIO
│     Identity lane
│     Creative signature
│     System mastery
│
├── EXPERIENCE
│     Loop pattern
│     Tone pattern
│     System pattern
│     Emotional pattern
│
└── PRODUCT
        Edition
        Platform
        Release date
        Store metadata

The product is the leaf, not the tree.


THE CATALOG AS A WORLD MODEL

The catalog must understand:

1. IP Worlds

Halo, Fallout, Forza, Minecraft — each is a universe with internal logic.

2. Series Lineage

Mainline → spin-off → reboot → remaster → live service.

3. Studio Identity

Arkane ≠ id Software ≠ Playground ≠ Ninja Theory.

4. Experience Taxonomy

Short-loop, mid-loop, long-loop.
Combat, creation, exploration, sociality.

5. Taste Graph Signals

Tone, intensity, mastery, identity.

6. Continuity

What came before.
What comes next.
What belongs together.

This is how a platform becomes coherent.


THE CATALOG FAILURE TREE

CATALOG FAILURE
│
├── IDENTITY FAILURE
│     IP misunderstood
│     Studio flattened
│     Series misrepresented
│
├── TAXONOMY FAILURE
│     Genre-only metadata
│     No loop/tone/system mapping
│
└── CONTINUITY FAILURE
        No lineage
        No universe logic
        No release cadence

Most catalogs fail in all three.


THE CATALOG AS INFRASTRUCTURE

CATALOG INFRASTRUCTURE
│
├── DISCOVERY
│     Experience rails
│     Identity rails
│     Continuity rails
│
├── PERSONALIZATION
│     Taste Graph integration
│     Emotional arc matching
│     Loop/tone alignment
│
├── SOCIALITY
│     Shared moments
│     Identity signals
│     Community clusters
│
├── CONTINUITY
│     Series mapping
│     Universe mapping
│     Release cadence
│
└── PLATFORM STRATEGY
        Portfolio balance
        Gap analysis
        Identity lanes

The catalog becomes the brain of the platform.


CLOSING

The industry keeps asking:
How do we fix discovery?
How do we fix personalization?
How do we fix continuity?

This is the answer:

The catalog isn’t a list.
The catalog is a world model.

Once you architect the catalog correctly, every other system becomes clearer, smarter, and more personal.

Genre limits.
Taxonomy unlocks.
Taste aligns.
Identity coheres.
Continuity emerges.

The catalog is the spine.

Webb Systems

Essays, architecture, and systems thinking for technology, gaming, and culture.