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

Policy engine: filter and verdict pipeline #10

New Issue
Closed
opened 2026-08-22 18:22:38 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-22 18:22:38 +01:00
Owner
Copy Link
Copy Source

The core of the app (DESIGN.md §5). Given a policy and a candidate — either a
parsed release name pre-grab, or a probed file post-download — produce a
Verdict that always names the deciding rule.

  • The same engine runs in both phases (§5.6) but sees different evidence. A rule
    that cannot be evaluated pre-grab must return "unknown", never "pass".
  • Post-download, a violation splits into hard fail and soft fail (§5.7). That
    split is engine output, not caller policy.
  • Per-title overrides relax or tighten the root policy, in both directions
    (§5.1).

Language, HDR and scoring rules are separate issues that plug into this. Build
the pipeline and the trivial rules (resolution, source, telesync) here.

Acceptance: exhaustive unit tests. This crate is where correctness is bought.

Depends on: #7, #8

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

The core of the app (`DESIGN.md` §5). Given a policy and a candidate — either a parsed release name pre-grab, or a probed file post-download — produce a `Verdict` that always names the deciding rule. - The same engine runs in both phases (§5.6) but sees different evidence. A rule that cannot be evaluated pre-grab must return "unknown", never "pass". - Post-download, a violation splits into hard fail and soft fail (§5.7). That split is engine output, not caller policy. - Per-title `overrides` relax or tighten the root policy, in both directions (§5.1). Language, HDR and scoring rules are separate issues that plug into this. Build the pipeline and the trivial rules (resolution, source, telesync) here. Acceptance: exhaustive unit tests. This crate is where correctness is bought. --- **Depends on:** #7, #8 Labels: `phase/2-logic`, `area/core`, `difficulty/hard`, `type/feature`
naps62-yolo added the area/coredifficulty/hardphase/2-logictype/feature labels 2026-08-22 18:22:38 +01:00
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/core difficulty/hard phase/2-logic type/feature
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#10
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?