Hour audit: 2026-09-29T15
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-29T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T15:00:00.000028528+00:00 · last event 2026-09-29T15:59:59.999967205+00:00
VOLUME 103,043,905 rows · 1,166,253,673 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 102,515,434 · h: 102,416,916 · i: 101,047,225 · g: 99,974,779 · c: 98,000,787 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 11,597,299 (11.25%) · h: 2,417,099 (2.35%) · i: 1,278,827 (1.24%) · g: 34,473 (0.03%) · c: 87,716,207 (85.13%) (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 103,043,905 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a12612facf7cb44faeb95c2aebedde51327553bb5ffbdb71333307ddb2692b15
the corpus checksum ledger names this file with the same digest
joined 103,045,894 to merged 103,043,905, minus 1,989 (minus 0.0019%)
boundary drops 1,989 · 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-29T17:53:28Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 8,425,717 105,138,856 0-32 f245ec2c061f08b35678db815182b20ad18182082c1c5f0433a147e21e69506a book 632,446 61,582,814 33-35 c8957234b3870196892cd523b09619cac846056861f4080403e6216df543eca4 last_trade_price 65,817 3,769,112 36-36 93f3c653ea9e5e5f41bf32e6bed01b57fd964a9c3102541ea10184f57ba85180 market_resolved 897 130,307 37-37 bfbec886ab8dfed493146df64e6e300764e72ce322bb91db4191eeb8df3f38e7 new_market 1,782 170,131 38-38 20edf2f7907384d6d973dec94dc0724014bbbe01a308f44c0a83fb080e693834 price_change 93,913,842 994,158,053 39-397 f37c66211a6c253fa3125238c11244866da3809e0affb205282c6d8b877ec618 tick_size_change 3,404 126,285 398-398 8741ed633e154518c03910605b2808d18c568866dbfcf8aabce91ef64705d4ea EVENT MIX count share price_change 93,913,842 91.14% best_bid_ask 8,425,717 8.18% book 632,446 0.61% last_trade_price 65,817 0.06% tick_size_change 3,404 <0.01% new_market 1,782 <0.01% market_resolved 897 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,425,867 8,425,717 150 1,644 FULL book 632,492 632,446 46 224,633 FULL last_trade_price 65,818 65,817 1 165 FULL market_resolved 897 897 0 42 FULL new_market 1,782 1,782 0 0 FULL price_change 93,915,634 93,913,842 1,792 2,091 FULL tick_size_change 3,404 3,404 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,976,859 7,147,432 6ms 19ms 177ms 3.1s 0 transport_latency_assumed best_bid_ask g 8,366,410 1,234 79ms 147ms 3.3s 35.0s 0 transport_latency_assumed best_bid_ask h 8,421,778 205,764 21ms 46ms 433ms 1.7min 0 transport_latency_assumed best_bid_ask i 8,316,383 106,748 28ms 39ms 208ms 6.5s 0 transport_latency_assumed best_bid_ask k 8,424,835 964,539 14ms 27ms 152ms 3.8s 0 transport_latency_assumed book c 587,755 571,249 15.9min 2.1d 38.1d 122.7d 0 book_staleness book g 145,059 18,751 105ms 15.8min 6.9d 104.2d 0 book_staleness book h 168,503 17,197 40ms 3.1h 20.3d 104.2d 0 book_staleness book i 135,998 5,573 32ms 274ms 8.3h 104.2d 0 book_staleness book k 142,576 19,676 19ms 137ms 1.3d 104.7d 0 book_staleness last_trade_price c 62,122 55,359 7ms 25ms 223ms 2.7s 0 transport_latency_assumed last_trade_price g 60,090 10 95ms 2.2s 14.6s 35.1s 0 transport_latency_assumed last_trade_price h 65,451 1,346 23ms 138ms 1.1s 54.2s 0 transport_latency_assumed last_trade_price i 64,736 732 30ms 150ms 2.8s 6.2s 0 transport_latency_assumed last_trade_price k 65,679 8,370 16ms 42ms 244ms 1.3s 0 transport_latency_assumed market_resolved c 823 715 6ms 36.3s 10.4min 10.5min 0 transport_latency_assumed market_resolved g 807 1 80ms 6.2s 53.8s 1.9min 0 transport_latency_assumed market_resolved h 807 97 23ms 10.7s 46.2s 52.9s 0 transport_latency_assumed market_resolved i 799 7 29ms 19.4s 52.6s 1.3min 0 transport_latency_assumed market_resolved k 807 77 17ms 17.0s 51.0s 58.2s 0 transport_latency_assumed new_market c 1,389 817 137ms 8.9min 9.2min 151.8d 0 transport_latency_assumed new_market g 1,099 97 246ms 1.2min 3.9min 151.9d 0 transport_latency_assumed new_market h 1,099 258 128ms 22.7s 4.0min 151.9d 0 transport_latency_assumed new_market i 1,099 391 93ms 47.9s 3.6min 151.9d 0 transport_latency_assumed new_market k 1,099 219 126ms 1.1min 3.8min 151.8d 0 transport_latency_assumed price_change c 89,368,607 79,937,648 6ms 20ms 180ms 3.4s 0 transport_latency_assumed price_change g 91,397,910 14,380 79ms 271ms 11.5s 35.2s 0 transport_latency_assumed price_change h 93,755,874 2,192,352 21ms 61ms 623ms 1.8min 0 transport_latency_assumed price_change i 92,524,838 1,165,344 28ms 53ms 573ms 6.5s 0 transport_latency_assumed price_change k 93,877,034 10,604,118 15ms 30ms 168ms 5.3s 0 transport_latency_assumed tick_size_change c 3,232 2,987 6ms 14ms 71ms 405ms 0 transport_latency_assumed tick_size_change g 3,404 not meas. 79ms 212ms 619ms 3.9s 0 transport_latency_assumed tick_size_change h 3,404 85 21ms 50ms 175ms 526ms 0 transport_latency_assumed tick_size_change i 3,372 32 27ms 56ms 173ms 360ms 0 transport_latency_assumed tick_size_change k 3,404 300 14ms 25ms 87ms 354ms 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-29/15/2026-09-29T15.parquet sha256sum 2026-09-29T15.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.