docs: Recently Played (frecency) design + US-PLAY-10 + S10.6#56
Merged
Conversation
Reworks the S10.2 History tab into an all-time, per-track, frecency-ranked 'Recently Played' view. Design vetted by architect-reviewer + swiftui-pro; founder brainstorm locked the four knobs (half-life 7d; ≥60%-heard capped at ~4min; cumulative heard-time; rename to 'Recently Played'). - docs/sprints/recently-played-frecency-design.md (new): the full design + QA plan. Data model = a decayed-score accumulator column (frecency_score, schema v4) — chosen over both a naive count×decay (violates recency>count) and a per-play events table (unbounded); mathematically equal to summing per-play decays at O(1). ≥60% rule extracted into a pure PlayThroughTracker (unit-testable). Full delete of the in-memory session log (kills the dup-row bug by construction). - backlog.md: new US-PLAY-10 (Recently Played). - sprint-plan.md + s10 plan: add S10.6 (5 SP, enhancement — NOT an R1 gate); §Status now 'S10.6 in design → then S10.4'. - roadmap.md: S10 line notes recently-played (frecency). D8 flagged: the v3→v4 bump resets current play counts ONCE (eraseOnSchemaChange); 'preserve play-state columns across schema change' logged as an R1 durability req. No code yet — design + docs only; implementation follows the architect/the-fool gate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design + doc updates for reworking the S10.2 History tab into an all-time, per-track, frecency-ranked "Recently Played" view (fixes the duplicate-row-on-replay complaint by construction). No code yet — implementation follows the architect/the-fool gate.
Founder-locked knobs (brainstorm 2026-07-14)
Design highlights (architect-reviewer + swiftui-pro)
frecency_score(schema v4) — chosen over a naivecount×decay(violates recency>count) and a per-play events table (unbounded); O(1) and mathematically equal to summing per-play decays.play_count/last_playedunchanged. One registered GRDB decay function drives write + read.PlayThroughTrackerfor unit tests.RecentlyPlayedRow(LibraryTrackDisplay), "N plays · 2h ago" legibility cue, tap = play-now. Deletes the in-memory session log.PlayThroughTrackerswift-testing.⚠ Flagged (D8)
eraseDatabaseOnSchemaChange→ the v3→v4 bump resets current play counts once, and counts persist only until the next schema bump pre-R1. Accepted (matches the no-migration posture); "preserve play-state columns across schema change" logged as an R1 durability requirement.Files
New: recently-played-frecency-design.md. Edits: backlog (US-PLAY-10), sprint-plan (S10.6 + §Status), s10 plan, roadmap.
🤖 Generated with Claude Code