Skip to content

DOMAIN.md

Latest commit

 

History

History
44 lines (30 loc) · 1.81 KB

DOMAIN.md

File metadata and controls

44 lines (30 loc) · 1.81 KB

Domain Model

Source of truth: the Drizzle schema in src/lib/server/db/schema.ts and the tier logic in src/lib/tier.ts. If this document conflicts with those files, the code wins.

For the reasoning behind key decisions, see ADR-0004.

Entities

  • Category — groups tier list items under a topic (e.g. Games, Books, Movies). Has a slug, name, optional description, display order, and optional per-category tier cutoff overrides.
  • TierListItem — a rated item within a category. Carries a numeric score that maps to a tier, a display order, and optional Markdown description.
  • Props — an ordered list of key-value pairs stored as JSON on each item. Used for category-specific metadata (e.g. Platform for games, Year/ISBN for books). Max 10 per item, keys ≤ 64 chars, values ≤ 128 chars.
  • Page — a CMS-managed static page (e.g. Home, About). Standalone, no relationships to other entities.

All entities carry createdAt and updatedAt timestamps.

Tiers and scoring

Tiers are a hardcoded enum: S → A → B → C → D → E → F.

Each item's numeric score is mapped to a tier using cutoff thresholds. Categories can override the defaults per-tier; null values fall back to the global defaults defined in src/lib/tier.ts.

Default cutoffs: S ≥ 90, A ≥ 75, B ≥ 60, C ≥ 45, D ≥ 30, E ≥ 15, F ≥ 0.

Relationships

erDiagram
    Category ||--o{ TierListItem : "has many"
    Page
Loading

Props are stored as a JSON column on TierListItem, not as a separate entity.

Ordering

The order field on both Category and TierListItem is an explicit integer. Within a tier list, items are sorted first by tier (S → F), then by order within each tier — not by score.