Hour audit: 2026-09-16T19
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-16T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T19:00:00.000069451+00:00 · last event 2026-09-16T19:59:59.999908540+00:00
VOLUME 139,326,963 rows · 1,562,374,329 bytes (1.46 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 136,585,928 · e: 135,977,919 · g: 124,922,540 · f: 116,002,379 · c: 106,721,510 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 34,945,658 (25.08%) · e: 2,707,246 (1.94%) · g: 262,325 (0.19%) · f: 988,949 (0.71%) · c: 100,422,785 (72.08%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 139,326,963 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 434f004c464130b89360f793100f1275c21666afaa69a4502d487f48143d525a
the corpus checksum ledger names this file with the same digest
joined 139,329,146 to merged 139,326,963, minus 2,183 (minus 0.0016%)
boundary drops 2,183 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-16T21:03:26Z as cefgh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 12,672,218 151,487,104 0-48 b490da4d3f7db72ede34169f23ad068bfdd5052086aa632070c24e0fe6e48ad4 book 2,837,935 120,138,758 49-59 1266b331a8504fa3f752b325e170db18ec7b1c9be320e7a7e92b6f2f95429acc last_trade_price 70,614 4,023,220 60-60 68dfc18262460ae813924fc37a703f055b5aff12954ef017f626a58b3406d17d market_resolved 2,063 209,819 61-61 0a0b0d639fab728899e9792ec0de20025a96a4e553d46dd20d829ad74f177926 new_market 2,479 218,328 62-62 f9eeee92b9d347d18e440b0b81e55be36582d47cffcf851a1ab7f66190c1c581 price_change 123,735,634 1,284,491,025 63-535 798d285c7b0396b9eae9d4ffc939d1bd3f64b7ccddebc83c1673c5218c961162 tick_size_change 6,020 221,615 536-536 0f7bd1350d74e1c2a1e4bcb3192f43ddc84bf0ce036113ba3f4f81c876686409 EVENT MIX count share price_change 123,735,634 88.81% best_bid_ask 12,672,218 9.10% book 2,837,935 2.04% last_trade_price 70,614 0.05% tick_size_change 6,020 <0.01% new_market 2,479 <0.01% market_resolved 2,063 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,672,458 12,672,218 240 5,068 FULL book 2,838,147 2,837,935 212 175,448 FULL last_trade_price 70,615 70,614 1 707 FULL market_resolved 2,063 2,063 0 105 FULL new_market 2,479 2,479 0 11 FULL price_change 123,737,364 123,735,634 1,730 1,713 FULL tick_size_change 6,020 6,020 0 532 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,642,270 9,070,806 5ms 15ms 107ms 13.2s 0 transport_latency_assumed best_bid_ask e 12,662,439 258,311 42ms 61ms 281ms 23.2s 0 transport_latency_assumed best_bid_ask f 10,629,728 52,581 46ms 66ms 267ms 27.9s 0 transport_latency_assumed best_bid_ask g 11,630,644 2,828 82ms 114ms 485ms 31.9s 0 transport_latency_assumed best_bid_ask h 12,670,807 3,287,692 18ms 38ms 167ms 14.6s 0 transport_latency_assumed book c 2,264,272 2,165,827 4.8min 3.0d 38.9d 109.9d 0 book_staleness book e 172,740 17,794 62ms 2.9min 9.4d 109.9d 0 book_staleness book f 1,562,799 395,674 3.8min 2.2d 38.2d 109.9d 0 book_staleness book g 861,966 216,665 2.5min 1.1d 36.0d 109.9d 0 book_staleness book h 158,073 41,975 24ms 196ms 36.1min 91.4d 0 book_staleness last_trade_price c 53,630 50,597 11ms 51ms 237ms 5.0s 0 transport_latency_assumed last_trade_price e 68,403 1,177 68ms 2.4s 17.5s 23.2s 0 transport_latency_assumed last_trade_price f 59,167 400 75ms 2.5s 15.3s 28.0s 0 transport_latency_assumed last_trade_price g 60,795 87 111ms 3.4s 16.3s 31.9s 0 transport_latency_assumed last_trade_price h 70,534 18,353 27ms 99ms 471ms 13.9s 0 transport_latency_assumed market_resolved c 1,219 1,147 7ms 4.8min 9.5min 9.8min 0 transport_latency_assumed market_resolved e 1,184 31 45ms 203ms 28.3s 1.0min 0 transport_latency_assumed market_resolved f 1,534 442 127ms 10.6min 16.4min 16.7min 0 transport_latency_assumed market_resolved g 1,440 119 107ms 5.8min 11.9min 12.1min 0 transport_latency_assumed market_resolved h 1,185 324 21ms 92ms 28.1s 1.0min 0 transport_latency_assumed new_market c 1,611 1,058 92ms 5.2min 6.1min 6.2min 0 transport_latency_assumed new_market e 1,297 229 202ms 15.1s 50.2s 1.2min 0 transport_latency_assumed new_market f 1,752 445 321ms 6.3min 7.2min 13.1min 0 transport_latency_assumed new_market g 1,625 232 356ms 7.5min 8.3min 8.7min 0 transport_latency_assumed new_market h 1,297 515 121ms 13.6s 42.0s 1.3min 0 transport_latency_assumed price_change c 94,753,840 89,128,932 6ms 16ms 116ms 13.8s 0 transport_latency_assumed price_change e 123,065,840 2,429,624 43ms 86ms 4.2s 23.3s 0 transport_latency_assumed price_change f 103,742,631 539,390 47ms 92ms 4.6s 27.9s 0 transport_latency_assumed price_change g 112,360,458 42,394 83ms 162ms 6.6s 31.9s 0 transport_latency_assumed price_change h 123,678,012 31,595,294 19ms 42ms 226ms 15.2s 0 transport_latency_assumed tick_size_change c 4,668 4,418 5ms 12ms 103ms 358ms 0 transport_latency_assumed tick_size_change e 6,016 80 42ms 56ms 200ms 712ms 0 transport_latency_assumed tick_size_change f 4,768 17 46ms 60ms 279ms 11.5s 0 transport_latency_assumed tick_size_change g 5,612 not meas. 82ms 106ms 385ms 2.1s 0 transport_latency_assumed tick_size_change h 6,020 1,505 18ms 30ms 90ms 460ms 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-16/19/2026-09-16T19.parquet sha256sum 2026-09-16T19.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.