Size-band scoring #13

Closed
opened 2026-08-22 18:22:38 +01:00 by naps62-yolo · 1 comment
Owner

DESIGN.md §5.5. Score by distance from a target size, not by source tier — a
remux must win only when nothing smaller exists.

  • Per resolution: floor, target, growing penalty above target. Below the floor
    is a hard filter, not a low score.
  • Source tier survives as a small tiebreaker.
  • Seeders log-scaled and small.
  • Telesync, CAM and screener are hard filters.

The numbers in §5.5 are placeholders pending the remux streaming test in §14, so
they live in the Policy row and are trivially changed. Do not hard-code them.

Acceptance: given a realistic candidate set, a 20 GB WEB-DL beats a 60 GB remux,
and the remux still wins when it is the only candidate.


Depends on: #10

Labels: phase/2-logic, area/core, difficulty/moderate, type/feature

`DESIGN.md` §5.5. Score by distance from a target size, not by source tier — a remux must win only when nothing smaller exists. - Per resolution: floor, target, growing penalty above target. Below the floor is a hard filter, not a low score. - Source tier survives as a small tiebreaker. - Seeders log-scaled and small. - Telesync, CAM and screener are hard filters. The numbers in §5.5 are placeholders pending the remux streaming test in §14, so they live in the `Policy` row and are trivially changed. Do not hard-code them. Acceptance: given a realistic candidate set, a 20 GB WEB-DL beats a 60 GB remux, and the remux still wins when it is the only candidate. --- **Depends on:** #10 Labels: `phase/2-logic`, `area/core`, `difficulty/moderate`, `type/feature`
naps62-yolo added the difficulty/moderatearea/corephase/2-logictype/feature labels 2026-08-22 18:22:38 +01:00
Author
Owner

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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#13