Hour audit: 2026-09-27T20
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-27T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T20:00:00.001302047+00:00 · last event 2026-09-27T20:59:59.999439431+00:00
VOLUME 126,759,806 rows · 1,443,041,399 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 123,573,168 · i: 120,047,955 · k: 118,147,321 · g: 117,447,114 · c: 86,108,549 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,053,305 (7.14%) · i: 4,002,889 (3.16%) · k: 37,330,280 (29.45%) · g: 133,933 (0.11%) · c: 76,239,399 (60.14%) (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 126,759,806 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 970d71d447460f0fcc1f1f3a4776b015b3ec2e0cfb16090ad475eb771385216b
the corpus checksum ledger names this file with the same digest
joined 126,779,881 to merged 126,759,806, minus 20,075 (minus 0.0158%)
boundary drops 20,075 · 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-27T22:50:30Z as cghik
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,501,598 156,999,316 0-51 ab364cc8f093cb0c8cf32e78f914788866de0cef248c3c3c9688df21aa4f7b53 book 3,232,266 99,000,567 52-64 5ce7c68f31e06a9eeddb1e4bed4ac14d566408449934bec3d3236509d403e47a last_trade_price 71,017 4,105,073 65-65 e6059160b5507d655157fb0392185466f4e43c96d1de9abaaf803544a2f308df market_resolved 11,337 1,009,335 66-66 fcca550b097335c1a0d4dd502cbcaea00d42d9f0144b328232e2d8e6f0a00260 new_market 15,442 978,293 67-67 abb20761bd151ea9686b1c34d199777e5ae00a8df3610b601b09ae15062f93b5 price_change 109,918,046 1,179,136,909 68-487 8976efbba282c2f44982c85c3f7d74d2ca564fdd88a67655bd84a214acde4aea tick_size_change 10,100 368,777 488-488 76db3bae30ae03045d8f0dbdc1c610b56d1efcbd0ad9197a252391cf3db894a2 EVENT MIX count share price_change 109,918,046 86.71% best_bid_ask 13,501,598 10.65% book 3,232,266 2.55% last_trade_price 71,017 0.06% new_market 15,442 0.01% market_resolved 11,337 <0.01% tick_size_change 10,100 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,502,230 13,501,598 632 7,305 FULL book 3,238,663 3,232,266 6,397 210,341 FULL last_trade_price 71,041 71,017 24 958 FULL market_resolved 11,433 11,337 96 1,434 FULL new_market 15,502 15,442 60 1,605 FULL price_change 109,930,912 109,918,046 12,866 7,350 FULL tick_size_change 10,100 10,100 0 836 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,124,300 8,064,618 5ms 20ms 354ms 12.0s 0 transport_latency_assumed best_bid_ask g 12,837,180 3,527 82ms 205ms 1.8s 40.9s 0 transport_latency_assumed best_bid_ask h 13,497,616 961,803 18ms 42ms 1.4s 1.5min 0 transport_latency_assumed best_bid_ask i 13,119,672 412,384 38ms 49ms 247ms 5.7s 0 transport_latency_assumed best_bid_ask k 12,878,565 4,059,266 13ms 28ms 335ms 1.1min 0 transport_latency_assumed book c 3,058,938 3,000,885 1.8h 3.0d 46.1d 120.9d 0 book_staleness book g 587,016 94,784 19.2min 1.1d 36.3d 120.9d 0 book_staleness book h 156,834 16,344 24ms 965ms 16.1h 102.4d 0 book_staleness book i 161,452 12,445 44ms 4.6s 2.4d 113.2d 0 book_staleness book k 597,012 107,808 18.1min 1.1d 36.3d 120.9d 0 book_staleness last_trade_price c 46,386 40,901 6ms 31ms 425ms 4.9s 0 transport_latency_assumed last_trade_price g 63,950 39 93ms 760ms 10.9s 40.9s 0 transport_latency_assumed last_trade_price h 70,855 5,896 20ms 137ms 2.6s 1.1min 0 transport_latency_assumed last_trade_price i 69,141 2,543 40ms 114ms 1.2s 4.3s 0 transport_latency_assumed last_trade_price k 66,163 21,638 14ms 58ms 549ms 48.7s 0 transport_latency_assumed market_resolved c 9,523 8,537 7.3min 34.2min 48.6min 51.6min 0 transport_latency_assumed market_resolved g 4,743 95 83ms 792ms 4.8min 5.6min 0 transport_latency_assumed market_resolved h 4,875 1,047 19ms 26.7s 50.8s 56.4s 0 transport_latency_assumed market_resolved i 4,797 204 40ms 32.7s 57.2s 2.5min 0 transport_latency_assumed market_resolved k 4,931 1,454 14ms 38.2s 5.4min 5.8min 0 transport_latency_assumed new_market c 13,122 10,591 7.0min 31.9min 49.4min 49.8min 0 transport_latency_assumed new_market g 4,527 662 442ms 2.1min 4.6min 5.4min 0 transport_latency_assumed new_market h 4,495 1,007 228ms 1.9min 2.4min 2.7min 0 transport_latency_assumed new_market i 4,495 1,532 186ms 2.0min 2.6min 2.8min 0 transport_latency_assumed new_market k 4,653 1,650 209ms 2.2min 5.2min 6.1min 0 transport_latency_assumed price_change c 73,849,228 65,107,537 6ms 22ms 362ms 15.2s 0 transport_latency_assumed price_change g 103,939,838 34,826 83ms 281ms 4.5s 40.9s 0 transport_latency_assumed price_change h 109,828,393 8,066,641 18ms 53ms 1.9s 1.5min 0 transport_latency_assumed price_change i 106,678,574 3,573,484 38ms 55ms 310ms 5.7s 0 transport_latency_assumed price_change k 104,586,225 33,135,558 13ms 32ms 353ms 1.2min 0 transport_latency_assumed tick_size_change c 7,052 6,330 5ms 14ms 360ms 1.4s 0 transport_latency_assumed tick_size_change g 9,860 not meas. 81ms 105ms 1.3s 7.0s 0 transport_latency_assumed tick_size_change h 10,100 567 18ms 26ms 544ms 16.9s 0 transport_latency_assumed tick_size_change i 9,824 297 36ms 46ms 231ms 435ms 0 transport_latency_assumed tick_size_change k 9,772 2,906 12ms 20ms 357ms 3.0s 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-27/20/2026-09-27T20.parquet sha256sum 2026-09-27T20.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.