Hour audit: 2026-10-03T20
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-03T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T20:00:00.000059883+00:00 · last event 2026-10-03T20:59:59.999832900+00:00
VOLUME 155,441,122 rows · 1,829,404,061 bytes (1.70 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 144,701,152 · m: 143,936,028 · i: 118,926,157 · g: 110,316,954 · k: 100,700,532 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,586,281 (6.17%) · m: 129,893,349 (83.56%) · i: 4,001,966 (2.57%) · g: 2,061,058 (1.33%) · k: 9,898,468 (6.37%) (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 155,441,122 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 99f22f33a797a5f235a8bee495f656fedf4fea5e4a0addc5356b81aac8ce8d85
the corpus checksum ledger names this file with the same digest
joined 155,504,511 to merged 155,441,122, minus 63,389 (minus 0.0408%)
boundary drops 63,389 · 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-03T22:54:22Z as ghikm
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 13,983,538 170,370,974 0-53 7bc634e98f1df6e00eab675e5c39cf384677fb36548c54a80760321146eff75e book 4,686,455 155,814,104 54-71 5a904d0d0febf89ad4dec4692cbdf267b1ec20ec792454e12a221eac6082b9ff last_trade_price 62,152 3,622,756 72-72 f069b80cf24fd9a0a41f2aeb31e43ba898b61f4f043b7a0795439a266b31887b market_resolved 19,876 1,101,677 73-73 4a20118c1301178adb74c0a29b395163cb5aa6fade93ffec08fc57989461ba96 new_market 17,581 1,029,908 74-74 d551b7be76c60fe4b5f33a624fff3c3f836a31091de15b31f49a891c81550654 price_change 136,658,444 1,495,224,504 75-596 df04b503e4da3690c75b27cc8b63907e9fe1c31698d687a1710de3c60d8ea42e tick_size_change 13,076 474,825 597-597 5bdb6e13d895dd981f90842bbcd689aee87eb2396635574f46c4f36e695fe416 EVENT MIX count share price_change 136,658,444 87.92% best_bid_ask 13,983,538 9.00% book 4,686,455 3.01% last_trade_price 62,152 0.04% market_resolved 19,876 0.01% new_market 17,581 0.01% tick_size_change 13,076 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,988,150 13,983,538 4,612 16,237 FULL book 4,686,713 4,686,455 258 3,301 FULL last_trade_price 62,222 62,152 70 1,439 FULL market_resolved 19,900 19,876 24 735 FULL new_market 17,896 17,581 315 354 FULL price_change 136,716,554 136,658,444 58,110 12,516 FULL tick_size_change 13,076 13,076 0 1,933 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,158,924 7,417 82ms 178ms 1.9s 1.1min 0 transport_latency_assumed best_bid_ask h 13,398,037 851,336 20ms 61ms 5.2s 2.2min 0 transport_latency_assumed best_bid_ask i 10,847,577 304,716 22ms 46ms 401ms 28.3s 0 transport_latency_assumed best_bid_ask k 9,217,558 740,645 15ms 39ms 383ms 1.2min 0 transport_latency_assumed best_bid_ask m 13,318,742 12,079,424 6ms 22ms 228ms 8.8s 0 transport_latency_assumed book g 2,889,171 1,965,061 38.0min 2.0d 42.5d 126.9d 0 book_staleness book h 621,613 95,027 8.1min 1.8d 42.3d 126.9d 0 book_staleness book i 2,474,070 523,407 35.8min 2.0d 42.3d 126.9d 0 book_staleness book k 3,476,039 1,947,245 39.4min 2.2d 45.8d 126.9d 0 book_staleness book m 606,919 155,715 6.7min 1.8d 42.3d 126.9d 0 book_staleness last_trade_price g 43,105 251 89ms 817ms 18.6s 1.1min 0 transport_latency_assumed last_trade_price h 58,664 5,260 21ms 201ms 9.2s 1.4min 0 transport_latency_assumed last_trade_price i 45,897 1,659 24ms 116ms 1.3s 7.2s 0 transport_latency_assumed last_trade_price k 37,561 3,462 16ms 69ms 644ms 53.3s 0 transport_latency_assumed last_trade_price m 57,945 51,520 7ms 34ms 365ms 6.2s 0 transport_latency_assumed market_resolved g 7,334 1,453 340ms 14.6min 20.9min 21.6min 0 transport_latency_assumed market_resolved h 5,790 454 22ms 36.2s 5.6min 6.2min 0 transport_latency_assumed market_resolved i 9,580 1,374 4.3min 19.0min 27.8min 28.8min 0 transport_latency_assumed market_resolved k 16,813 11,413 11.6min 30.3min 39.8min 41.7min 0 transport_latency_assumed market_resolved m 6,037 5,182 7ms 49.7s 9.1min 9.8min 0 transport_latency_assumed new_market g 11,154 1,770 5.2min 11.5min 16.3min 16.7min 0 transport_latency_assumed new_market h 5,543 1,545 50.2s 1.5min 2.0min 4.9min 0 transport_latency_assumed new_market i 10,044 4,075 1.5min 11.4min 23.7min 23.8min 0 transport_latency_assumed new_market k 11,525 7,538 4.9min 28.2min 35.7min 37.3min 0 transport_latency_assumed new_market m 5,609 2,653 49.9s 1.5min 5.1min 6.9min 0 transport_latency_assumed price_change g 97,198,010 85,106 83ms 227ms 3.4s 1.1min 0 transport_latency_assumed price_change h 130,598,849 8,632,025 20ms 80ms 6.6s 2.2min 0 transport_latency_assumed price_change i 105,528,357 3,166,541 23ms 54ms 545ms 30.2s 0 transport_latency_assumed price_change k 87,933,444 7,187,694 15ms 42ms 404ms 1.2min 0 transport_latency_assumed price_change m 129,928,112 117,587,078 6ms 23ms 248ms 8.8s 0 transport_latency_assumed tick_size_change g 9,256 not meas. 82ms 113ms 834ms 34.2s 0 transport_latency_assumed tick_size_change h 12,656 634 19ms 111ms 2.4s 1.1min 0 transport_latency_assumed tick_size_change i 10,632 194 22ms 66ms 452ms 2.1s 0 transport_latency_assumed tick_size_change k 7,592 471 14ms 32ms 423ms 2.5s 0 transport_latency_assumed tick_size_change m 12,664 11,777 6ms 19ms 219ms 611ms 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-03/20/2026-10-03T20.parquet sha256sum 2026-10-03T20.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.