peter
53b50231ff
E24 S1. The anti-paralysis answer layer, served from our own Postgres with no upstream call: one hero suggestion, one CROSS-SOURCE resume rail, and the user's own comfort shelf. Survey first, because the roadmap line was wrong about the starting point: Plex already ships the whole trio (E5's Discover rails, including a reshuffling Surprise me), the YouTube side ships none of it, and nothing anywhere answers the question across both. The data already existed on both sides — VideoState and PlexState are structurally identical, the feed has an `in_progress` filter and a seeded shuffle, and the YT player already resumes position. - app/discover/budget.py — the time bands. "How much time do you have" (10 perc / 30 perc / egy este / mindegy) replaces 15/D's mood questionnaire: deterministic, answerable from a column we have, and it picks the source for free. Matched against REMAINING time, so a film with 8 minutes left is a ten-minute answer. An unknown runtime fits only the unbounded band. - app/discover/cards.py — a thin unified card that carries the NATIVE feed / Plex payload, so the page renders with the existing card components instead of a third one. `aspect` is the one new field: a rail needs to know poster from 16:9, and that is a property of the artwork, not of the module. - app/discover/queries.py — the SQL, reusing feedquery and plex.rollup rather than the Plex Discover ROUTE, whose LibraryFilters narrowing belongs to a surface that has a sidebar. One seed drives both halves so a reroll moves them together. - app/discover/hero.py — resume -> comfort -> surprise, with the chosen tier in the payload so the client labels it honestly instead of guessing. - comfort_pins (0083): five nullable CASCADE-ing FKs under num_nonnulls(...) = 1 rather than a flag or a polymorphic string ref. A flag cannot order a shelf or hold a channel; a string ref would let a deleted library item leave a dead tile on the one surface whose whole job is to be reliable. Two honest-state rules the tests pin: the surprise draw excludes anything already started (the resume tier may have skipped it for not fitting, and offering it back as "Meglepetés" would contradict the question), and which source leads the draw follows the seed, so the Plex library can actually answer "egy este". Gate green: ruff, ruff format, 3x tsc, eslint, prettier, knip, vitest 770, pytest 987.
63 lines
2.8 KiB
Python
63 lines
2.8 KiB
Python
"""The time budget — E24's replacement for "what mood are you in?".
|
|
|
|
`random-gondolatok` 15/D asked for a mood questionnaire before the recommendations. The same file's
|
|
later BA-interview note (#23) says the mood half is not what makes this work: the friction is
|
|
deciding at all. A mood→genre mapping would also be invented data — we store no mood signal and never
|
|
will — whereas "how much time do you have" is a question the library can actually answer, from a
|
|
column we already have.
|
|
|
|
So the surface asks about TIME, and the answer is deterministic: four bands, no model, no latency.
|
|
The band also picks the source for free — ten minutes is a YouTube video, an evening is a movie —
|
|
which is exactly the cross-source behaviour the Home surface exists to provide.
|
|
|
|
The bands overlap on purpose. "I have 30 minutes" should not be answered with a two-minute Short just
|
|
because it fits; a lower bound is as much a part of the promise as the upper one.
|
|
"""
|
|
|
|
from typing import Literal
|
|
|
|
Budget = Literal["short", "medium", "long", "any"]
|
|
|
|
DEFAULT_BUDGET: Budget = "any"
|
|
|
|
# budget -> (min_seconds, max_seconds); None = unbounded on that side.
|
|
BANDS: dict[str, tuple[int | None, int | None]] = {
|
|
"short": (None, 12 * 60), # "10 perc" — a bit of slack over the round number the chip shows
|
|
"medium": (8 * 60, 40 * 60), # "30 perc"
|
|
"long": (40 * 60, None), # "Egy este"
|
|
"any": (None, None), # "Mindegy"
|
|
}
|
|
|
|
|
|
def band(budget: str) -> tuple[int | None, int | None]:
|
|
"""The (min, max) seconds for a budget. Unknown budgets fall back to the unbounded band rather
|
|
than raising: the route validates the vocabulary with a Literal, so anything reaching here with a
|
|
bad value is our own bug, and an unfiltered shelf is a better failure than a 500 on the landing
|
|
page."""
|
|
return BANDS.get(budget, BANDS["any"])
|
|
|
|
|
|
def remaining_seconds(duration_seconds: int | None, position_seconds: int) -> int | None:
|
|
"""What is actually LEFT to watch. The question is "how much time do you have", so a 90-minute
|
|
film with 8 minutes to go belongs in the ten-minute band, not the evening one. Unknown duration
|
|
stays unknown — see `fits`."""
|
|
if duration_seconds is None:
|
|
return None
|
|
return max(0, duration_seconds - max(0, position_seconds))
|
|
|
|
|
|
def fits(seconds: int | None, budget: str) -> bool:
|
|
"""Does a runtime fit the budget?
|
|
|
|
An unknown duration fits only the unbounded band. We cannot promise an item finishes inside ten
|
|
minutes when we do not know how long it is, and quietly including it would make the one control
|
|
on this page dishonest — the failure mode the house rules call an un-honest state."""
|
|
lo, hi = band(budget)
|
|
if seconds is None:
|
|
return lo is None and hi is None
|
|
if lo is not None and seconds < lo:
|
|
return False
|
|
if hi is not None and seconds > hi:
|
|
return False
|
|
return True
|