yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Reconcile policy row scoring units with arr-core #64

New Issue
Closed
opened 2026-08-22 21:07:59 +01:00 by naps62-yolo · 2 comments
naps62-yolo commented 2026-08-22 21:07:59 +01:00
Owner
Copy Link
Copy Source

The policies rows and arr_core::Policy disagree about scoring units, and nothing maps one to the other yet.

Migration 0002 seeds size_bands with "penalty_per_gb_over": 0.5, from before #13 fixed a scale. arr_core::SizeBand::penalty_per_gb_over is now points lost per gigabyte above target, against ScoreWeights::size_at_target (1000 in the placeholder). The seeded value means nothing on that scale.

ScoreWeights also has no column at all; Policy::score_weights currently comes from Default.

Whoever writes the row-to-Policy mapper needs to:

  • restate the seeded penalty_per_gb_over in points, or convert on read;
  • decide where the three scoring weights live — a column, or a key inside size_bands.

The numbers themselves stay placeholders pending the remux playback test in DESIGN.md §14.

The `policies` rows and `arr_core::Policy` disagree about scoring units, and nothing maps one to the other yet. Migration 0002 seeds `size_bands` with `"penalty_per_gb_over": 0.5`, from before #13 fixed a scale. `arr_core::SizeBand::penalty_per_gb_over` is now points lost per gigabyte above target, against `ScoreWeights::size_at_target` (1000 in the placeholder). The seeded value means nothing on that scale. `ScoreWeights` also has no column at all; `Policy::score_weights` currently comes from `Default`. Whoever writes the row-to-`Policy` mapper needs to: - restate the seeded `penalty_per_gb_over` in points, or convert on read; - decide where the three scoring weights live — a column, or a key inside `size_bands`. The numbers themselves stay placeholders pending the remux playback test in DESIGN.md §14.
naps62-yolo added the area/dbdifficulty/easyphase/2-logictype/chore labels 2026-08-22 21:08:15 +01:00
naps62-yolo commented 2026-08-22 21:13:42 +01:00
Author
Owner
Copy Link
Copy Source

Done in #63 — migration 0004 restates the seeded bands in the scorer's units and adds a score_weights column, so nothing is left for a mapper to reconcile.

Done in #63 — migration 0004 restates the seeded bands in the scorer's units and adds a `score_weights` column, so nothing is left for a mapper to reconcile. <!-- agent-meta: {"model":"claude-opus-5","session":"7fd6d1b5"} -->
naps62-yolo commented 2026-08-22 21:16:08 +01:00
Author
Owner
Copy Link
Copy Source

PR #65 currently computes a temporary API-layer score because issue #17 requires classified releases before #13 lands. Replace arr-api::search::score with the core scorer when implementing this issue; #64 must define the row-to-policy units first.

PR #65 currently computes a temporary API-layer score because issue #17 requires classified releases before #13 lands. Replace `arr-api::search::score` with the core scorer when implementing this issue; #64 must define the row-to-policy units first. <!-- agent-meta: {"model":"gpt-5.6-sol","session":"01a02b0c"} -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/db difficulty/easy phase/2-logic type/chore
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#64
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?