Hour audit: 2026-09-15T00
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-15T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T00:00:00.000019388+00:00 · last event 2026-09-15T00:59:59.999867184+00:00
VOLUME 124,861,253 rows · 1,348,277,509 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 122,303,736 · h: 122,177,880 · f: 117,632,321 · g: 117,392,946 · c: 90,592,777 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,613,737 (1.29%) · h: 36,569,111 (29.29%) · f: 510,015 (0.41%) · g: 250,143 (0.20%) · c: 85,918,247 (68.81%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 124,861,253 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 996643b364568a92620d22b6f1f8672cf3810b33ea00dd0997a7a358572264a8
the corpus checksum ledger names this file with the same digest
joined 124,867,490 to merged 124,861,253, minus 6,237 (minus 0.0050%)
boundary drops 6,237 · 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-15T02:00:47Z 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,841,152 144,334,865 0-48 ff58615c6d5f8f72193e25c0b3f49007f4fc6119e2b515b865584b02a217fdc2 book 2,829,494 111,638,306 49-59 7a1732847258957da84ea4278f500f6f2bd53c9e475f3ffe8b046358d2b9f96f last_trade_price 63,291 3,509,851 60-60 06e801330b6891fc861dc7b3c3fc01f7c7fa4de2d4e6a94fd5ddaa8c5c7d0c2d market_resolved 1,057 108,360 61-61 46e1577220f54f6d662fd758995662822aa0fc2ad94464ae1667e116217e7c16 new_market 903 82,107 62-62 238289fed5f4264e4dc703dc289f9d76fff9f23725e778aaa292b1a6e00f7bf4 price_change 109,122,784 1,087,089,327 63-479 b7b39c8cb795eb9f6dbf1866c5ea77e9941016dee0c06b03783dfd0cdcb6865c tick_size_change 2,572 95,525 480-480 efa6843a4a2f8b4126d1cb7443cab01f8c9704973dfbf7c44e53aff0ff8985a5 EVENT MIX count share price_change 109,122,784 87.40% best_bid_ask 12,841,152 10.28% book 2,829,494 2.27% last_trade_price 63,291 0.05% tick_size_change 2,572 <0.01% market_resolved 1,057 <0.01% new_market 903 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,841,460 12,841,152 308 4,590 FULL book 2,833,150 2,829,494 3,656 136,814 FULL last_trade_price 63,292 63,291 1 574 FULL market_resolved 1,057 1,057 0 94 FULL new_market 903 903 0 6 FULL price_change 109,125,056 109,122,784 2,272 3,557 FULL tick_size_change 2,572 2,572 0 195 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,202,221 8,769,526 5ms 13ms 78ms 1.1s 0 transport_latency_assumed best_bid_ask e 12,837,272 143,160 43ms 52ms 151ms 2.5s 0 transport_latency_assumed best_bid_ask f 12,309,776 35,399 48ms 61ms 181ms 9.8s 0 transport_latency_assumed best_bid_ask g 12,275,777 2,427 83ms 103ms 285ms 13.3s 0 transport_latency_assumed best_bid_ask h 12,835,506 3,890,640 18ms 28ms 109ms 10.2s 0 transport_latency_assumed book c 2,533,441 2,313,366 9.7min 3.3d 37.4d 108.1d 0 book_staleness book e 318,980 92,996 21.4s 10.2h 23.5d 108.1d 0 book_staleness book f 569,720 101,599 3.1min 1.3d 34.0d 108.1d 0 book_staleness book g 636,228 214,363 3.5min 1.4d 34.2d 108.1d 0 book_staleness book h 300,606 107,170 13.3s 8.5h 23.4d 108.1d 0 book_staleness last_trade_price c 44,887 42,190 11ms 47ms 195ms 4.7s 0 transport_latency_assumed last_trade_price e 62,951 1,561 50ms 132ms 569ms 5.0s 0 transport_latency_assumed last_trade_price f 61,041 471 56ms 144ms 713ms 9.7s 0 transport_latency_assumed last_trade_price g 61,061 113 95ms 245ms 2.2s 12.2s 0 transport_latency_assumed last_trade_price h 62,581 18,956 24ms 74ms 286ms 7.5s 0 transport_latency_assumed market_resolved c 842 802 30ms 12.6min 16.6min 17.9min 0 transport_latency_assumed market_resolved e 636 24 44ms 155ms 353ms 594ms 0 transport_latency_assumed market_resolved f 630 not meas. 50ms 160ms 391ms 613ms 0 transport_latency_assumed market_resolved g 615 not meas. 89ms 246ms 639ms 1.2s 0 transport_latency_assumed market_resolved h 636 231 18ms 84ms 59.7s 1.0min 0 transport_latency_assumed new_market c 759 591 110ms 8.9min 15.0min 1.0h 0 transport_latency_assumed new_market e 503 67 138ms 16.1s 1.6min 77.1d 0 transport_latency_assumed new_market f 498 28 142ms 499ms 1.4min 4.2min 0 transport_latency_assumed new_market g 503 44 232ms 11.7s 2.1min 77.1d 0 transport_latency_assumed new_market h 503 173 78ms 18.0s 1.6min 77.1d 0 transport_latency_assumed price_change c 78,808,743 74,789,952 5ms 15ms 94ms 1.3s 0 transport_latency_assumed price_change e 109,080,826 1,375,921 43ms 57ms 206ms 3.8s 0 transport_latency_assumed price_change f 104,688,156 372,518 48ms 67ms 233ms 10.2s 0 transport_latency_assumed price_change g 104,416,326 33,196 83ms 110ms 369ms 13.3s 0 transport_latency_assumed price_change h 108,975,476 32,551,197 18ms 31ms 139ms 10.6s 0 transport_latency_assumed tick_size_change c 1,884 1,820 5ms 10ms 49ms 252ms 0 transport_latency_assumed tick_size_change e 2,568 8 43ms 47ms 117ms 346ms 0 transport_latency_assumed tick_size_change f 2,500 not meas. 48ms 54ms 116ms 204ms 0 transport_latency_assumed tick_size_change g 2,436 not meas. 82ms 102ms 200ms 314ms 0 transport_latency_assumed tick_size_change h 2,572 744 18ms 22ms 50ms 2.1s 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-15/00/2026-09-15T00.parquet sha256sum 2026-09-15T00.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.