Hour audit: 2026-09-18T12
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-18T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T12:00:00.000000935+00:00 · last event 2026-09-18T12:59:59.999818623+00:00
VOLUME 120,092,045 rows · 1,317,205,784 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,606,512 · g: 118,590,186 · h: 118,573,712 · f: 113,790,736 · c: 103,992,430 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,693,280 (1.41%) · g: 123,045 (0.10%) · h: 19,935,553 (16.60%) · f: 777,650 (0.65%) · c: 97,562,517 (81.24%) (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,092,045 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4ab04f6f1c97a2a00c3637f2af8548d1f30837b53db2d09fc1769584fca143dd
the corpus checksum ledger names this file with the same digest
joined 120,098,334 to merged 120,092,045, minus 6,289 (minus 0.0052%)
boundary drops 6,289 · 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-18T14:08:00Z 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,679,443 149,090,237 0-48 b61865f830c2ed67e7eed8b602dc364414dc04e046e02928894cad67595b994f book 1,443,836 88,093,999 49-54 7ed08afbbccad9dd993c27829f22cd9e3275969d40a59e6fc856c3f77ac9b51c last_trade_price 61,042 3,509,694 55-55 cd7516916ba5f66728f622d3a4f200cd116d55eb276e5d5e84aca11c16f91759 market_resolved 832 111,526 56-56 7a8709a7ea13ba56284a3a696233b3c60f8ba817268074a03ee37612f3f4a9a3 new_market 2,096 209,980 57-57 d72e52acecbcb03732a02738f718a70ee994b28f02c27af0b02c53e4dc38f95b price_change 105,900,520 1,074,668,104 58-461 9d0f705657a62eccf5322b612241e9a5324b1022f28b1eb68bd2f2f0591cf71b tick_size_change 4,276 156,815 462-462 61dc667d793ffb45142a705d91880f18f80a0cb2c90f2d9162df1c10969481d9 EVENT MIX count share price_change 105,900,520 88.18% best_bid_ask 12,679,443 10.56% book 1,443,836 1.20% last_trade_price 61,042 0.05% tick_size_change 4,276 <0.01% new_market 2,096 <0.01% market_resolved 832 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,679,699 12,679,443 256 2,554 FULL book 1,445,898 1,443,836 2,062 197,014 FULL last_trade_price 61,043 61,042 1 324 FULL market_resolved 832 832 0 32 FULL new_market 2,096 2,096 0 0 FULL price_change 105,904,490 105,900,520 3,970 1,930 FULL tick_size_change 4,276 4,276 0 115 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,968,796 10,325,914 5ms 16ms 164ms 6.3s 0 transport_latency_assumed best_bid_ask e 12,673,239 162,058 43ms 56ms 241ms 7.8s 0 transport_latency_assumed best_bid_ask f 12,093,334 50,052 48ms 65ms 253ms 15.6s 0 transport_latency_assumed best_bid_ask g 12,673,249 7,018 80ms 104ms 397ms 21.5s 0 transport_latency_assumed best_bid_ask h 12,674,542 2,134,401 18ms 34ms 229ms 23.6s 0 transport_latency_assumed book c 1,344,773 1,160,575 3.7min 16.3h 37.7d 111.6d 0 book_staleness book e 134,863 9,538 46ms 440ms 26.3min 111.6d 0 book_staleness book f 527,904 212,638 2.0min 6.7h 32.7d 111.6d 0 book_staleness book g 170,399 33,475 98ms 7.4min 12.9d 111.6d 0 book_staleness book h 134,628 27,610 23ms 239ms 26.0min 93.0d 0 book_staleness last_trade_price c 51,240 47,908 11ms 54ms 322ms 5.0s 0 transport_latency_assumed last_trade_price e 60,603 1,421 52ms 196ms 2.5s 8.0s 0 transport_latency_assumed last_trade_price f 57,357 781 59ms 218ms 3.3s 15.6s 0 transport_latency_assumed last_trade_price g 60,286 172 97ms 316ms 6.7s 21.6s 0 transport_latency_assumed last_trade_price h 60,528 10,760 26ms 116ms 689ms 6.6s 0 transport_latency_assumed market_resolved c 694 651 6ms 4.8min 10.8min 11.8min 0 transport_latency_assumed market_resolved e 668 50 44ms 264ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 641 26 50ms 467ms 3.9min 4.1min 0 transport_latency_assumed market_resolved g 668 2 85ms 247ms 611ms 1.3s 0 transport_latency_assumed market_resolved h 668 103 20ms 122ms 1.0min 1.0min 0 transport_latency_assumed new_market c 1,474 931 101ms 4.1min 6.2min 6.5min 0 transport_latency_assumed new_market e 1,347 296 185ms 19.2s 44.8s 1.2min 0 transport_latency_assumed new_market f 1,347 199 200ms 19.7s 47.5s 1.5min 0 transport_latency_assumed new_market g 1,347 143 270ms 19.3s 39.6s 1.2min 0 transport_latency_assumed new_market h 1,347 527 127ms 14.6s 50.2s 1.2min 0 transport_latency_assumed price_change c 91,621,637 86,022,996 6ms 18ms 182ms 6.8s 0 transport_latency_assumed price_change e 105,731,516 1,519,899 43ms 69ms 467ms 7.8s 0 transport_latency_assumed price_change f 101,105,985 513,954 49ms 77ms 485ms 15.7s 0 transport_latency_assumed price_change g 105,679,961 82,235 81ms 124ms 754ms 22.2s 0 transport_latency_assumed price_change h 105,697,723 17,761,436 19ms 40ms 302ms 23.8s 0 transport_latency_assumed tick_size_change c 3,816 3,542 6ms 17ms 57ms 160ms 0 transport_latency_assumed tick_size_change e 4,276 18 43ms 64ms 162ms 513ms 0 transport_latency_assumed tick_size_change f 4,168 not meas. 48ms 61ms 151ms 302ms 0 transport_latency_assumed tick_size_change g 4,276 not meas. 80ms 98ms 216ms 337ms 0 transport_latency_assumed tick_size_change h 4,276 716 19ms 31ms 64ms 112ms 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-18/12/2026-09-18T12.parquet sha256sum 2026-09-18T12.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.