BYTE NEWS — integrity report for the `byte-500` dataset ======================================================================== 16 recorded gap(s) in the last 14 days, totalling 2,846 minutes when this site was not looking. SCOPE The BYTE 500 as it stood at the review of 2026-09-02: 500 assets ranked by reported 24-hour trading volume, reviewed weekly. Membership is a frozen record; this download is the standing list and every earlier review is published beside it unchanged. COVERAGE — when this dataset's producers were not looking ledgers read: prices (18 ledger row(s), merged into 16 window(s)) 2026-08-28T20:47:57.833857+00:00 -> 2026-08-28T23:59:59.999999+00:00 192.0 min The live price tape the reading was taken and could not be written down 2026-08-29T00:00:00+00:00 -> 2026-08-29T23:59:59.999999+00:00 1440.0 min The live price tape the reading was taken and could not be written down 2026-08-30T00:00:00+00:00 -> 2026-08-30T19:04:22+00:00 1144.4 min The live price tape the reading was taken and could not be written down 2026-09-01T00:46:25.911918+00:00 -> 2026-09-01T01:06:38.035196+00:00 20.2 min The price tape — GOLD a source gave us a price too old to use, so we recorded none 2026-09-01T01:11:40.677048+00:00 -> 2026-09-01T01:16:43.077314+00:00 5.0 min The price tape — GOLD a source gave us a price too old to use, so we recorded none 2026-09-02T16:58:10.403633+00:00 -> 2026-09-02T17:02:10.403633+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T01:44:39.370614+00:00 -> 2026-09-03T01:48:39.370614+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T03:26:33.350071+00:00 -> 2026-09-03T03:30:33.350071+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T04:52:50.254052+00:00 -> 2026-09-03T04:56:50.254052+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T05:23:37.895716+00:00 -> 2026-09-03T05:27:37.895716+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T11:20:28.217802+00:00 -> 2026-09-03T11:24:28.217802+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T12:47:08.038613+00:00 -> 2026-09-03T12:51:23.969571+00:00 4.3 min byte500.tail a source we read stopped answering 2026-09-03T14:29:49.973481+00:00 -> 2026-09-03T14:33:49.973481+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T15:00:35.504213+00:00 -> 2026-09-03T15:04:35.504213+00:00 4.0 min byte500.tail a source we read stopped answering 2026-09-03T18:40:08.411432+00:00 -> 2026-09-03T18:44:34.981642+00:00 4.4 min byte500.tail a source we read stopped answering 2026-09-03T18:55:52.496762+00:00 -> 2026-09-03T18:59:52.496762+00:00 4.0 min byte500.tail a source we read stopped answering DENSITY Not a continuous record. A day with no rows on this dataset is a quiet day in the world rather than a gap in ours, so no per-day expectation is stated. CORRECTIONS — what has been revised since publication (none) OUR OWN DOWNTIME — recorded incidents inside this window 2026-09-03 54 min degraded The wire wrote no ledger row for 54 minutes (stage 'budget') [NOT YET WRITTEN UP] 2026-09-01 35 min degraded We published a wrong gold price for 35 minutes 2026-09-01 49 min degraded Publishing ran at half speed for 49 minutes 2026-08-30 33 min degraded Publishing ran at half speed for 33 minutes 2026-08-28 43 min degraded Publishing ran at half speed for 43 minutes 2026-08-28 2,776 min degraded The price record had a 46-hour hole and nothing said so 2026-08-26 78 min degraded Publishing ran at half speed for 78 minutes WHAT THE CHECKS DID NOT CHECK gate of 2026-08-31: 2705/2710 checks passed, 4 skipped, 5 failing, 0 block(s) cut short SKIPPED: digest-2026-08-09-pm: its links resolve to published posts and to pages on disk (3 checks) — published before the wrap became a linked recap — the stored post is the audit trail and is never rewritten SKIPPED: the display rung (44) is asserted on the lead card's figure — the figure is the hero number INSIDE the card graphic — SVG user units in an 800x450 viewBox — so its rendered size is `units x (card width / 800)` and no one value makes it 44px on the front page, an article page and a share kit at once. Measured: 126px before this batch and 68.7px after, at 1440x900, because §6 put the lead in a 1/3 column. Reaching 44 means re-composing the card graphic, which is a batch and not a line — see docs/BATCH-K-REPORT.md FAILING: …and the tape carries PLAIN-TEXT rows as well as linked ones — a row with nothing behind it has no `href` at all, so the two states are distinguishable in the markup and not only in the styling (batch L §9), and a page where every row linked would not be exercising that rule FAILING: every recorded incident carries a written post-mortem FAILING: …and the timeline shows we were first FAILING: …which keeps the permalink, grows the timeline, and records the event that ended it FAILING: …and the measured row is 46px on a phone and 42px above 620 — the heights §1 asked for, read off the rendered page This report is assembled from records this site already keeps; it adds no new collection. The datasets it describes: /api/v1/byte-500.json and .csv