From b7c96641a9eecd1e84727c66959149671c15ba4c Mon Sep 17 00:00:00 2001 From: Duncan Tourolle Date: Fri, 31 Jul 2026 09:55:50 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20no=20exact=20tier=20=E2=80=94=20the=20f?= =?UTF-8?q?ile-hash=20tier=20was=20withdrawn?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A stale reference to 'the runtime/exact tiers' as the fallback for media too short to carry an audio signature. The exact tier keyed on a file hash and was withdrawn on legal grounds: it fingerprinted the individual copy a user holds rather than the cut the timings describe. The pipeline never emitted a video_hash, so nothing in the code changes — but a spec that still names a withdrawn tier is what makes the withdrawal look like an oversight to the next reader, which is exactly how it nearly got re-added. Co-Authored-By: Claude Opus 5 --- docs/SPEC.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/SPEC.md b/docs/SPEC.md index 5123d6b..8a6da1b 100644 --- a/docs/SPEC.md +++ b/docs/SPEC.md @@ -997,8 +997,10 @@ rewritten. **Media shorter than 120 s.** The window `runtime/2 ± 60 s` underflows, so no signature is emitted and **no sync offset is applied**. Such items fall back to -the runtime/exact tiers, which is adequate: a 90-second extra or trailer is not -the content whose cut alignment matters. Both producers must apply the identical +the runtime tier, which is adequate: a 90-second extra or trailer is not the +content whose cut alignment matters. (There is no `exact` tier: the file-hash +tier was withdrawn on legal grounds — it fingerprinted an individual copy rather +than the cut the timings describe. See the server spec §3.) Both producers must apply the identical rule, or they diverge on exactly the short items most likely to be mis-identified.