Hour audit: 2026-10-08T09
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-10-08T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T09:00:00.000124277+00:00 · last event 2026-10-08T09:59:59.999639666+00:00
VOLUME 120,144,807 rows · 1,402,183,009 bytes (1.31 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 119,342,025 · o: 119,279,076 · m: 119,258,452 · i: 118,912,332 · n: 116,050,229 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,325,347 (1.10%) · o: 56,462,099 (47.00%) · m: 61,460,825 (51.16%) · i: 551,239 (0.46%) · n: 345,297 (0.29%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 120,144,807 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4dfefa9fa9735cea75359be6be0e57f12b8a2b80f1e24051d567e268fbdd4ebd
the corpus checksum ledger names this file with the same digest
joined 120,146,508 to merged 120,144,807, minus 1,701 (minus 0.0014%)
boundary drops 1,701 · 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-10-08T11:14:00Z as himno
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 10,746,960 134,812,283 0-40 9af047687d20d7cbf0cf8b5eaaad22499104c1afcdd86b407b84fd79da3b9ed5 book 1,344,328 94,144,495 41-46 07123cc11ad11577e6a23d67bafffd92dd8b203a220b3a8f916b25b007f51a3b last_trade_price 54,877 3,148,986 47-47 7e715765eef114db75c05b948ecb7d1443a73b0785a4eaa5b5e035edc9e4cbc9 market_resolved 359 59,689 48-48 32898e0d26c6bb9ad5a5cc25a7aa3ea2a4ac209523b55010d4836f6182ae675f new_market 383 41,485 49-49 b0365e8ad28a92e605bd222454bb7a51eef054e52464da25117e027f349c3cbf price_change 107,995,644 1,168,523,212 50-461 b6546fd9a60ec2e08f9ccfd1a3acbb0084e8833cf6bd305903d6c1143e20f1ea tick_size_change 2,256 84,785 462-462 ffce1ac90b4871d3e34aaa4ef43b8062bfc50f222174be65c66118e42c78862e EVENT MIX count share price_change 107,995,644 89.89% best_bid_ask 10,746,960 8.95% book 1,344,328 1.12% last_trade_price 54,877 0.05% tick_size_change 2,256 <0.01% new_market 383 <0.01% market_resolved 359 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,747,114 10,746,960 154 64 FULL book 1,344,832 1,344,328 504 249,286 FULL last_trade_price 54,878 54,877 1 0 FULL market_resolved 359 359 0 16 FULL new_market 383 383 0 0 FULL price_change 107,996,686 107,995,644 1,042 40 FULL tick_size_change 2,256 2,256 0 25 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,744,115 79,920 18ms 28ms 113ms 6.6s 0 transport_latency_assumed best_bid_ask i 10,741,095 43,227 21ms 31ms 129ms 6.8s 0 transport_latency_assumed best_bid_ask m 10,743,450 5,579,690 5ms 15ms 78ms 5.6s 0 transport_latency_assumed best_bid_ask n 10,648,296 1,632 44ms 62ms 394ms 24.4s 0 transport_latency_assumed best_bid_ask o 10,744,673 5,042,491 6ms 15ms 76ms 2.8s 0 transport_latency_assumed book h 631,117 344,558 10.8min 5.7h 46.8d 131.5d 0 book_staleness book i 228,291 47,826 5.2s 5.8h 38.7d 131.5d 0 book_staleness book m 543,478 310,343 8.3min 5.7h 46.8d 131.5d 0 book_staleness book n 581,693 321,907 10.9min 5.6h 46.8d 131.5d 0 book_staleness book o 548,883 319,694 8.4min 5.7h 46.8d 131.5d 0 book_staleness last_trade_price h 54,782 591 20ms 85ms 469ms 3.8s 0 transport_latency_assumed last_trade_price i 54,557 226 24ms 181ms 1.1s 6.1s 0 transport_latency_assumed last_trade_price m 54,679 26,070 7ms 27ms 214ms 5.6s 0 transport_latency_assumed last_trade_price n 47,715 31 48ms 1.1s 8.3s 24.4s 0 transport_latency_assumed last_trade_price o 54,801 27,959 7ms 23ms 147ms 1.6s 0 transport_latency_assumed market_resolved h 358 2 22ms 88ms 44.0s 44.1s 0 transport_latency_assumed market_resolved i 358 34 25ms 120ms 33.8s 56.3s 0 transport_latency_assumed market_resolved m 358 165 6ms 58ms 35.9s 56.9s 0 transport_latency_assumed market_resolved n 342 not meas. 45ms 3.6s 51.7s 51.7s 0 transport_latency_assumed market_resolved o 358 158 6ms 47ms 34.7s 56.9s 0 transport_latency_assumed new_market h 263 42 42ms 325ms 1.4min 1.8min 0 transport_latency_assumed new_market i 263 61 39ms 12.9s 1.4min 1.6min 0 transport_latency_assumed new_market m 263 147 28ms 16.3s 50.9s 1.7min 0 transport_latency_assumed new_market n 263 21 82ms 8.8s 49.4s 1.6min 0 transport_latency_assumed new_market o 263 112 34ms 7.6s 36.8s 1.4min 0 transport_latency_assumed price_change h 107,909,134 900,194 18ms 33ms 196ms 6.7s 0 transport_latency_assumed price_change i 107,885,512 459,840 21ms 37ms 433ms 6.9s 0 transport_latency_assumed price_change m 107,913,968 55,543,276 6ms 16ms 93ms 6.8s 0 transport_latency_assumed price_change n 104,769,764 21,706 44ms 81ms 4.8s 24.5s 0 transport_latency_assumed price_change o 107,927,842 51,070,628 6ms 16ms 86ms 3.2s 0 transport_latency_assumed tick_size_change h 2,256 40 19ms 34ms 97ms 467ms 0 transport_latency_assumed tick_size_change i 2,256 25 21ms 38ms 88ms 210ms 0 transport_latency_assumed tick_size_change m 2,256 1,134 6ms 23ms 115ms 346ms 0 transport_latency_assumed tick_size_change n 2,156 not meas. 45ms 85ms 1.6s 2.0s 0 transport_latency_assumed tick_size_change o 2,256 1,057 6ms 19ms 67ms 244ms 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-10-08/09/2026-10-08T09.parquet sha256sum 2026-10-08T09.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.