Hour audit: 2026-10-01T07
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-01T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T07:00:00.000250160+00:00 · last event 2026-10-01T07:59:59.999651450+00:00
VOLUME 108,265,298 rows · 1,127,579,646 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 108,159,195 · i: 107,868,639 · h: 102,140,967 · m: 99,723,544 · g: 95,360,607 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 28,849,323 (26.65%) · i: 1,393,727 (1.29%) · h: 9,649,299 (8.91%) · m: 68,297,442 (63.08%) · g: 75,507 (0.07%) (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 108,265,298 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f5c6d827482334c2de5a35b00d0704fa18fd14b789f34b83dcc852f2a1d74ce3
the corpus checksum ledger names this file with the same digest
joined 108,266,910 to merged 108,265,298, minus 1,612 (minus 0.0015%)
boundary drops 1,612 · 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-01T10:06:37Z 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 11,200,304 133,700,767 0-42 401b680a2e4e876bbd13bbd123b406d426e7dc5bbeb129c80a8459c58664621f book 167,700 18,085,652 43-43 55121253dd759de40ea602785226d94aeaccb314d9596b624e2a6bb288f28e25 last_trade_price 47,004 2,772,147 44-44 88887dfffc8429f93d0c3747df0847719275fd25533ea5dec62abca8f603f9aa market_resolved 738 111,423 45-45 ddd76ae4af8a178202e14a8f7f2c3a5f70cc1b9a398c2fa80b974fbae96b64ee new_market 1,236 124,528 46-46 62e766e610bbbbc06abebb08b47a504430199ef1e5d0ab24fc0b1a92d660d046 price_change 96,845,808 971,457,235 47-416 e7440393360048380ad4c6a8c295ccdfd88896c1673f9c97f18b94cb783f6375 tick_size_change 2,508 93,700 417-417 bcd8a85fb04bc4bbddb1788ec288ddf956eaf48324ebefe3e53c096d33c1f55f EVENT MIX count share price_change 96,845,808 89.45% best_bid_ask 11,200,304 10.35% book 167,700 0.15% last_trade_price 47,004 0.04% tick_size_change 2,508 <0.01% new_market 1,236 <0.01% market_resolved 738 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,200,490 11,200,304 186 144 FULL book 167,702 167,700 2 33,529 FULL last_trade_price 47,004 47,004 0 0 FULL market_resolved 738 738 0 0 FULL new_market 1,236 1,236 0 0 FULL price_change 96,847,232 96,845,808 1,424 41,605 FULL tick_size_change 2,508 2,508 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,195,955 2,429 80ms 133ms 376ms 19.3s 0 transport_latency_assumed best_bid_ask h 11,199,244 792,412 18ms 37ms 271ms 53.6s 0 transport_latency_assumed best_bid_ask i 11,199,406 81,313 27ms 79ms 258ms 8.1s 0 transport_latency_assumed best_bid_ask k 11,199,365 2,262,406 14ms 54ms 257ms 56.1s 0 transport_latency_assumed best_bid_ask m 11,199,553 8,061,744 5ms 54ms 226ms 2.0s 0 transport_latency_assumed book g 125,918 31,698 103ms 4.8h 23.9d 105.9d 0 book_staleness book h 106,989 23,210 22ms 9.1s 4.2d 124.4d 0 book_staleness book i 99,797 5,221 29ms 221ms 17.1h 105.8d 0 book_staleness book k 107,636 33,872 18ms 27.8s 4.1d 105.9d 0 book_staleness book m 109,242 73,699 12ms 1.8min 8.5d 102.0d 0 book_staleness last_trade_price g 46,178 25 89ms 207ms 4.5s 19.3s 0 transport_latency_assumed last_trade_price h 46,992 5,942 19ms 38ms 574ms 44.1s 0 transport_latency_assumed last_trade_price i 46,992 236 29ms 139ms 864ms 2.8s 0 transport_latency_assumed last_trade_price k 46,986 11,400 15ms 72ms 420ms 53.7s 0 transport_latency_assumed last_trade_price m 46,995 29,401 7ms 107ms 324ms 904ms 0 transport_latency_assumed market_resolved g 680 not meas. 90ms 22.3s 51.6s 57.3s 0 transport_latency_assumed market_resolved h 680 55 20ms 26.2s 57.7s 57.8s 0 transport_latency_assumed market_resolved i 680 16 49ms 20.8s 55.0s 55.9s 0 transport_latency_assumed market_resolved k 680 182 16ms 138ms 38.0s 43.5s 0 transport_latency_assumed market_resolved m 680 485 9ms 20.3s 54.5s 55.3s 0 transport_latency_assumed new_market g 810 105 260ms 19.6s 28.9s 1.7min 0 transport_latency_assumed new_market h 810 193 215ms 14.4s 30.7s 50.5s 0 transport_latency_assumed new_market i 810 158 173ms 14.8s 24.3s 1.6min 0 transport_latency_assumed new_market k 810 283 108ms 14.1s 44.5s 1.7min 0 transport_latency_assumed new_market m 810 497 91ms 16.8s 46.9s 1.5min 0 transport_latency_assumed price_change g 83,988,558 41,250 83ms 155ms 555ms 19.3s 0 transport_latency_assumed price_change h 90,783,744 8,827,328 18ms 40ms 327ms 53.6s 0 transport_latency_assumed price_change i 96,518,446 1,306,772 27ms 90ms 310ms 8.1s 0 transport_latency_assumed price_change k 96,801,210 26,540,732 15ms 59ms 280ms 56.1s 0 transport_latency_assumed price_change m 88,363,756 60,129,726 5ms 68ms 251ms 2.1s 0 transport_latency_assumed tick_size_change g 2,508 not meas. 87ms 227ms 659ms 814ms 0 transport_latency_assumed tick_size_change h 2,508 159 19ms 66ms 696ms 5.7s 0 transport_latency_assumed tick_size_change i 2,508 11 28ms 110ms 1.3s 1.3s 0 transport_latency_assumed tick_size_change k 2,508 448 15ms 74ms 565ms 905ms 0 transport_latency_assumed tick_size_change m 2,508 1,890 5ms 55ms 248ms 277ms 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-01/07/2026-10-01T07.parquet sha256sum 2026-10-01T07.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.