ADR-0007: Progressive disclosure for logging

Status: Accepted
Date: 2026-07-30
Supersedes: —
Superseded by: —

Context

BoardGameGeek’s play logger captures everything and is barely used — precisely because it shows the whole form at once. The richness of ADR-0006’s session model creates exactly the same risk here.

Decision

Schema depth ≠ form depth. Everything on a session is nullable except game_id and played_at.

Tap once: “Played.” Date defaults to today.
Expand: who was there (recent players as chips), who won.
Expand again: scores, expansions, duration, location, variant.

Remember the last table and offer it as a one-tap default — the same people play the same games on the same night.

Consequences

Logging must be possible in one tap. Any change that adds a required session field breaks this ADR and needs a superseding decision.
Session logging ships tier-one only (WI-032); tiers two and three come later. The schema supports all three from the start.
Session logging and stats stay deliberately understated in the UI — lists, collection and the social feed are the headline features.