Evidence record
Transcript intelligence
Every published claim on this page was checked by running the command shown. Claims that did not pass were withdrawn before publication; their count is stated below and the full record is available on request.
Measured 2026-08-23 · figures expire with the next publish run; the site is rebuilt from one figures ledger.
Research artifact · published claims
| Claim | How it was checked | Status |
|---|---|---|
| The corpus is 12,171 deduplicated calls across 3,652 tickers, spanning 2021-03-10 to 2026-08-21 — 9,376 from the archive provider and 2,795 from the live provider. | sqlite3 'file:<derived>?mode=ro' "SELECT COUNT(*) FROM calls" -> 12,171 ; "SELECT COUNT(DISTINCT ticker) FROM calls" -> 3,652 ; "SELECT MIN(call_date), MAX(call_date) FROM calls" -> 2021-03-10 | 2026-08-21 ; "SELECT source_db, COUNT(*) FROM calls GROUP BY source_db" -> 9,376 | 2,795 | published |
| 12,712 raw captures became 12,171 calls: 541 rows (4.3%) removed by two deduplication passes. The live provider loses 153 of its own rows not to the archive but to a fuller sibling capture in its own store — the second pass keeps the capture with the most speaker turns, and it is source-blind. | COUNT(*) on the documents table of each upstream store -> 9,764 + 2,948 = 12,712 ; 12,712 - 12,171 = 541. Pass 1 drops an archive capture colliding with a live capture on (ticker, fiscal quarter, fiscal year, call date); pass 2 keeps the fullest capture within a (ticker, fiscal quarter, fiscal year) group. | published |
| The corpus is concentrated in 2024 to 2026, with a thin 2021 tail and no 2022 to 2023 coverage at all: 2 calls in 2021, 780 in 2024, 3,310 in 2025 and 7,773 in 2026. | sqlite3 'file:<derived>?mode=ro' "SELECT substr(call_date,1,4), COUNT(*) FROM calls WHERE call_date<>'' GROUP BY 1 ORDER BY 1" -> 2021:2 | 2024:780 | 2025:3,310 | 2026:7,773. The 2022 and 2023 buckets are absent, not zero-filled. | published |
| The derived read model holds 146,579 question-and-answer pairs, 128,976 speaker rows with 1,878 analyst firms parsed out of free-text role labels, 35,825 linguistic-vitals rows and 230,925 extracted guidance sentences. The measured non-answer rate across all pairs is 6.54%. | COUNT(*) per table on <derived> opened mode=ro -> qa_pairs 146,579 | speakers 128,976 | vitals 35,825 | guidance_sents 230,925 | memos 43 ; "SELECT COUNT(DISTINCT firm) FROM qa_pairs WHERE firm<>''" -> 1,878 ; "SELECT ROUND(100.0*SUM(non_answer)/COUNT(*),2) FROM qa_pairs" -> 6.54 | published |
| The round-one loss was diagnosed as a bias in the evaluation, not a defect in the index: the candidate surfaced 92 to 101 top-10 hits per 300 that had never been graded, against 26 at the setting the incumbent won with, and the harness scores an ungraded hit as zero. All 111 ungraded items across the four gated configurations were then graded against each query's written intent — distribution 20 zeros, 54 ones, 37 twos, 33% top grade, checked against the earlier passes for leniency drift. | the ungraded-hit ledger the runner writes on every evaluation ; judgment pool grew 695 -> 806 with the prior state kept — three retained snapshots of the pool read 300, 454 and 695 grades, and the pool stands at 897 today. | published |
| Re-running the identical gate with zero unjudged hits on both sides promoted the candidate: nDCG@10 0.606 to 0.701 (+15.7% relative), P@5 with at least one relevant result 0.813 to 0.900, hit@5-strong 0.867 to 0.900, MRR@10 0.629 to 0.773. Warm query latency measured 0.52 to 0.92 s at the development flip and 0.56 to 0.92 s after the container deploy, against a 2 s bar. | same runner, same 30 queries, same two-metric rule, judgment pool at 806 ; unjudged@10 = 0 for both arms. Latency from the two flip verifications: three mandated queries re-run at the development flip (0.52 to 0.92 s) and again after the container deploy (0.56 to 0.92 s), the post-deploy result sets byte-identical to the development ones. | published |
| One of the six query categories regressed under the promoted backend and was published as such rather than averaged into the headline: macro_chain fell 0.657 to 0.621. The five gaining categories moved as the earlier failure analysis had predicted, the largest being incident_impact at 0.682 to 0.892. | per-category nDCG@10 table from the round-two evaluation run. The write-up also records 0.701 as a floor rather than a ceiling, because the fusion parameters beyond one knob were tuned against the previous backend's score distribution and never retuned. | published |
| A one-line date fallback corrupted at least 330 calls, and the damage was split by failure mode rather than reported as a total: 179 joined to a real earnings surprise and price reaction from an unrelated quarter with no signal in the interface, 150 joined to nothing and rendered blank, 1 had no ticker in the outcome feed. The archive provider leaves the call date NULL on 3,500 of 9,603 documents (36.4%). | the integrity investigation of 2026-08-03, run read-only against production data (the archive store held 9,603 documents at that date): a fiscal quarter-and-year cross-check with a 150-day plausibility cutoff, quantified explicitly as a floor and not a total, with ten worked examples and every downstream consumer of the join traced (three call sites plus the feed sort and the company timeline). The 3,500-of-9,603 NULL rate is recorded in that investigation rather than produced by a standing command. | published |
| After the four-tier repair every call records which tier resolved its date: 5,925 (48.7%) from an explicit provider call date, 5,649 (46.4%) matched by fiscal period to a report date in the outcome feed, 291 (2.4%) from a page date within a plausible reporting lag, and 306 (2.5%) left NULL by design. | sqlite3 'file:<derived>?mode=ro' "SELECT date_src, COUNT(*) FROM calls GROUP BY date_src" -> 5,925 | 5,649 | 291 | 306. The 306 NULLs are the rule working as specified, not a gap. | published |
12 claims tested · 9 published · 3 withdrawn before publication. Full evidence record available on request — king.hippopotamus@yahoo.com.
Author approval — 2026-08-23, hash 926a2097