Hour audit: 2026-09-12T01
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-12T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T01:00:00.000019016+00:00 · last event 2026-09-12T01:59:59.999415988+00:00
VOLUME 123,593,475 rows · 1,325,981,884 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 120,428,053 · h: 120,368,951 · g: 115,440,439 · f: 105,848,185 · c: 86,501,175 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,412,869 (1.95%) · h: 36,772,335 (29.75%) · g: 158,974 (0.13%) · f: 349,311 (0.28%) · c: 83,899,986 (67.88%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 13924da9c455dd9373a934711648b8ee520b9014e7d33d4d3d4433b3917be7d4
the corpus checksum ledger names this file with the same digest
joined 123,601,954 to merged 123,593,475, minus 8,479 (minus 0.0069%)
boundary drops 8,479 · 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-12T03:49:48Z 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 11,414,306 126,758,910 0-43 752089840233afa008f231efe3d02f5584d55d525ca530cea6c5fb69c6730f7f book 3,224,013 116,303,905 44-56 6959ab8debc5855afefee465f319efb1ac3c3169cb3ac9a8ce32fab74f27b68e last_trade_price 41,654 2,414,721 57-57 8bfa5f623a6101b1570067486a87b8d625a6ffddb4dbf6d0769fc48bd1a97428 market_resolved 11,842 1,694,257 58-58 7f9b85882ce1ff0307af3fb6638ffeafe32c4eee55b8a03af4c6c79c3d3eb23b new_market 15,596 2,138,879 59-59 dadc009b03912ab164e53b268fbb2ff7b7311c7af22ff29786d962f298891f61 price_change 108,881,972 1,075,114,917 60-475 4cd801d75b5bed0116047844321e8c3236677380595243a94bff6c4728e521b3 tick_size_change 4,092 148,607 476-476 71cf1b63b75aeb9bfbc405693102b473d777ad2c528aec6b0e874b1782863d4c EVENT MIX count share price_change 108,881,972 88.10% best_bid_ask 11,414,306 9.24% book 3,224,013 2.61% last_trade_price 41,654 0.03% new_market 15,596 0.01% market_resolved 11,842 <0.01% tick_size_change 4,092 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,415,130 11,414,306 824 8,030 FULL book 3,224,108 3,224,013 95 211,472 FULL last_trade_price 41,657 41,654 3 690 FULL market_resolved 11,842 11,842 0 9,232 FULL new_market 15,655 15,596 59 14,958 FULL price_change 108,889,470 108,881,972 7,498 12,819 FULL tick_size_change 4,092 4,092 0 395 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,072,088 7,837,881 5ms 9ms 53ms 8.0s 0 transport_latency_assumed best_bid_ask e 11,412,847 217,187 39ms 43ms 98ms 5.5s 0 transport_latency_assumed best_bid_ask f 10,023,543 20,994 45ms 50ms 109ms 6.0s 0 transport_latency_assumed best_bid_ask g 10,926,312 836 82ms 98ms 245ms 11.7s 0 transport_latency_assumed best_bid_ask h 11,413,360 3,337,408 17ms 24ms 81ms 13.5s 0 transport_latency_assumed book c 3,004,261 2,944,284 15.7min 7.9h 31.3d 105.1d 0 book_staleness book e 113,905 11,727 42ms 26.2min 4.6d 105.1d 0 book_staleness book f 537,952 89,897 6.4min 7.5h 27.6d 105.1d 0 book_staleness book g 563,902 148,183 7.7min 7.6h 27.6d 105.1d 0 book_staleness book h 88,589 29,922 20ms 51ms 21.8min 86.6d 0 book_staleness last_trade_price c 27,512 26,124 10ms 40ms 206ms 5.0s 0 transport_latency_assumed last_trade_price e 41,573 1,184 45ms 95ms 426ms 5.0s 0 transport_latency_assumed last_trade_price f 36,281 203 51ms 102ms 542ms 5.0s 0 transport_latency_assumed last_trade_price g 39,486 14 93ms 203ms 1.1s 9.7s 0 transport_latency_assumed last_trade_price h 41,446 14,129 22ms 58ms 225ms 6.6s 0 transport_latency_assumed market_resolved c 1,977 1,912 6ms 5.8min 11.3min 18.3min 0 transport_latency_assumed market_resolved e 1,849 31 44ms 120ms 263ms 631ms 0 transport_latency_assumed market_resolved f 10,996 9,186 3.1h 5.4h 6.8h 6.9h 0 transport_latency_assumed market_resolved g 1,849 23 94ms 246ms 3.5min 4.8min 0 transport_latency_assumed market_resolved h 1,849 690 21ms 47ms 583ms 1.0min 0 transport_latency_assumed new_market c 568 350 177ms 10.6min 11.2min 13.3min 0 transport_latency_assumed new_market e 397 72 69ms 10.2s 21.5s 1.6min 0 transport_latency_assumed new_market f 15,355 14,976 4.3h 6.0h 6.8h 6.9h 0 transport_latency_assumed new_market g 397 38 126ms 12.5s 30.8s 2.1min 0 transport_latency_assumed new_market h 397 160 63ms 304ms 20.2s 1.0min 0 transport_latency_assumed price_change c 75,391,901 73,086,615 5ms 9ms 58ms 8.4s 0 transport_latency_assumed price_change e 108,853,390 2,182,602 39ms 44ms 118ms 5.5s 0 transport_latency_assumed price_change f 95,220,386 214,048 45ms 51ms 125ms 6.0s 0 transport_latency_assumed price_change g 103,904,537 9,876 82ms 100ms 288ms 11.7s 0 transport_latency_assumed price_change h 108,819,218 33,388,831 17ms 25ms 87ms 19.4s 0 transport_latency_assumed tick_size_change c 2,868 2,820 5ms 8ms 37ms 174ms 0 transport_latency_assumed tick_size_change e 4,092 66 39ms 43ms 91ms 199ms 0 transport_latency_assumed tick_size_change f 3,672 7 46ms 52ms 122ms 187ms 0 transport_latency_assumed tick_size_change g 3,956 4 82ms 96ms 187ms 351ms 0 transport_latency_assumed tick_size_change h 4,092 1,195 17ms 24ms 254ms 1.6s 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-12/01/2026-09-12T01.parquet sha256sum 2026-09-12T01.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.