diff options
| author | Peter Stone <thepeterstone@gmail.com> | 2026-09-29 06:32:10 +0000 |
|---|---|---|
| committer | Peter Stone <thepeterstone@gmail.com> | 2026-09-29 06:32:10 +0000 |
| commit | 26c95926cecb036a23ff0c53700e1219678596b8 (patch) | |
| tree | 20d0da34767f9f9e26fbcaf4242c72bad7fa99be /CLAUDE.md | |
| parent | 16a47088a315786a940590794d7ce4003447cf7c (diff) | |
Write the desktop session's brief for Tier 3 detection
The fingerprinting runs on a device now and has still confirmed nothing for
a real show. That is an open question, not a known bug, and answering it
needs the prototype rather than the app -- only the prototype can show what
a parameter change costs in false positives, which is the number that
matters here.
docs/detection-findings.md collects what this round established: that the
pipeline works, that the confirmation threshold earns its place, and the
finding that reframes the problem -- dynamic ad insertion means the same
Grass Apes came back 29:34 on one fetch and 27:39 on another, so ad content
and the offset of everything behind it differ per request. It lists the
experiments in order, including using insertedAdMs as ground truth for the
midroll scan, and what not to touch.
Linked from the known-gaps list, which is where a future session looks.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B
Diffstat (limited to 'CLAUDE.md')
| -rw-r--r-- | CLAUDE.md | 16 |
1 files changed, 9 insertions, 7 deletions
@@ -194,13 +194,15 @@ by default and correct; it is simply waiting for a publisher who marks breaks. - **Auto-downloads are not retried.** A rule's download that fails is left FAILED rather than requeued: retrying forever against a 404 would burn the battery, and the failed row is visible in the episode list. Retry is the manual Download button. -- **Tier 3 has never confirmed a real intro or outro.** The pipeline runs on hardware and the - worker succeeds, but three consecutive Up First downloads produced no candidate at either - end. Untested hypothesis: `FingerprintUpdater.DEFAULT_REFERENCE_SECONDS` is 8 and the - prototype measured Up First's sting at about 6, so every 8-second window compared also - contains two seconds of different speech. Do not change that constant without re-running the - desktop prototype -- it is tuned, and the confirmation threshold is what keeps a rotating ad - from being learned as an intro. +- **Tier 3 has never confirmed a real intro, outro or midroll.** The pipeline runs on hardware + and the worker succeeds, but three consecutive Up First downloads produced no candidate at + either end. Two live hypotheses -- an 8-second reference window against a ~6-second sting, + and pre-roll ads moving the intro to a different offset in every file. **See + `docs/detection-findings.md`**, which is the brief for the desktop session that settles it: + what is already known, the experiments in order, and what not to touch. Do not tune + `DEFAULT_REFERENCE_SECONDS`, `MIN_SCORE` or `CONFIRM_THRESHOLD` from the app -- the app + cannot show you what a change costs in false positives, and the threshold is the whole + safety mechanism. - **Android Auto is verified in a real car**, as of 2026-09-28. It appears, and connects. The notification Peter saw on first connect was Android Auto's own new-media-app announcement, |