1 files changed, 18 insertions, 5 deletions
diff --git a/server/internal/transcript/publish.go b/server/internal/transcript/publish.go
index 670a8d5..b9856c3 100644
--- a/server/internal/transcript/publish.go
+++ b/server/internal/transcript/publish.go
@@ -10,17 +10,30 @@ decides what the phone will seek past, so it is deliberately narrow.
 
 Two detectors produce candidates and they are not close in quality. Subtraction -- comparing an
 episode's words against a second description of the same programme -- measured 92% to 104% of
-what the declared-versus-served length gap implies across eighteen episodes, finding every pod,
-with its edges pulled back off the programme. Reading the ad copy measured 0%, 0%, 15% and 29%
-on the same kind of episode. Only the first is acted on.
+what the declared-versus-served length gap implies, finding every pod, with its edges pulled back
+off the programme. Reading the ad copy measured 0%, 0%, 15% and 29% on the same kind of episode.
+Only the first is acted on.
+
+**That 92-104% is the figure for a publisher's transcript**, which is a second description of the
+programme written once. Against a refetch -- a second download of the same dynamically-assembled
+file, carrying its own advertising at its own positions -- the same code recovers a median of 33%
+across fifteen episodes, with a range of 20% to 146%. Measured on the live corpus 2026-11-02; see
+docs/detection-findings.md. Nothing below distinguishes the two, which is a known gap, not a
+decision.
 
 The length gap is both the measure and the guard. It comes from the feed and the file rather
 than from any detector, which makes it the one number able to contradict one.
 */
 
 // overshootLimit is how much more than the lengths imply a candidate set may claim and still be
-// published, as a percentage. The measured spread runs to 104%; 150 leaves room for a music
-// sting at the edge of a pod without leaving room for having found the wrong thing entirely.
+// published, as a percentage. 150 leaves room for a music sting at the edge of a pod without
+// leaving room for having found the wrong thing entirely.
+//
+// It was set against the publisher-transcript spread, which runs to 104%, so it sat well clear of
+// the distribution. Where it actually binds is the shows whose length gap is noise rather than a
+// measurement -- Reply All's gaps run from -0.48 to +1.02 minutes across eight episodes, so a
+// percentage of one of them means little either way. Raising this limit would not help and
+// lowering it would not either; see docs/detection-findings.md for what would.
 const overshootLimit = 150
 
 // Publishable returns the candidates fit to skip, or nothing and the reason.