Hour audit: 2026-09-14T04
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-14T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T04:00:00.000061921+00:00 · last event 2026-09-14T04:59:59.999998765+00:00
VOLUME 96,277,296 rows · 928,279,115 bytes (885.28 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 96,203,659 · f: 96,200,749 · h: 96,177,748 · e: 96,160,334 · g: 96,119,088 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 92,749,259 (96.34%) · f: 192,700 (0.20%) · h: 2,888,436 (3.00%) · e: 401,796 (0.42%) · g: 45,105 (0.05%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,277,296 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1ad6423874ccc71d7e67210223a53243ecafc8e328140db4d98c1f9ac8019d4d
the corpus checksum ledger names this file with the same digest
joined 96,279,446 to merged 96,277,296, minus 2,150 (minus 0.0022%)
boundary drops 2,150 · 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-14T05:55:17Z 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 10,817,938 114,153,189 0-41 929666e373b33497a55980098dc0a2986c4d5d54e2fc6b4e42622564e72a5803 book 140,824 14,318,397 42-42 8c5eeee4e2a8b5eba08040edbb2fd04ba3c56ea70eaf9ac462124ad93931a2ff last_trade_price 48,272 2,684,041 43-43 a709bdd168137c0966fe9a7e60ea70e3ff95367c3dd49d4ad7ea2a7fb8991deb market_resolved 613 99,054 44-44 37dc7ac3b28ece3b57800eacc01be8c27524dbb0069bcf5d845b6ff4d33454b2 new_market 2,477 255,499 45-45 b2e6d25edc88389b923f4571294414de08375a6391f56d8de1fe7774b7fd9008 price_change 85,265,448 795,606,581 46-371 e649fbaea1b330ed0747f4b1a445c0c28e31e412943f345609d9b067bb2e6595 tick_size_change 1,724 62,521 372-372 205a42ba39b54bc0a829b712b915add9fb222473d4dbbe101c3fdaa6425733c5 EVENT MIX count share price_change 85,265,448 88.56% best_bid_ask 10,817,938 11.24% book 140,824 0.15% last_trade_price 48,272 0.05% new_market 2,477 <0.01% tick_size_change 1,724 <0.01% market_resolved 613 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,818,191 10,817,938 253 232 FULL book 140,824 140,824 0 16,224 FULL last_trade_price 48,273 48,272 1 1 FULL market_resolved 613 613 0 0 FULL new_market 2,477 2,477 0 0 FULL price_change 85,267,344 85,265,448 1,896 183 FULL tick_size_change 1,724 1,724 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,817,292 10,458,089 4ms 8ms 143ms 4.4s 0 transport_latency_assumed best_bid_ask e 10,814,819 43,043 40ms 45ms 229ms 16.5s 0 transport_latency_assumed best_bid_ask f 10,815,494 19,973 47ms 53ms 249ms 7.8s 0 transport_latency_assumed best_bid_ask g 10,812,125 1,939 81ms 100ms 532ms 19.1s 0 transport_latency_assumed best_bid_ask h 10,816,800 294,894 17ms 22ms 304ms 27.9s 0 transport_latency_assumed book c 105,523 98,696 6ms 40ms 2.8h 88.8d 0 book_staleness book e 105,140 3,539 42ms 245ms 3.1h 88.7d 0 book_staleness book f 105,914 3,662 49ms 342ms 4.5h 88.7d 0 book_staleness book g 130,405 28,243 95ms 1.7h 6.8d 88.8d 0 book_staleness book h 104,420 6,684 20ms 71ms 22.7s 88.6d 0 book_staleness last_trade_price c 48,103 45,762 10ms 44ms 257ms 4.8s 0 transport_latency_assumed last_trade_price e 47,896 270 47ms 136ms 2.5s 16.3s 0 transport_latency_assumed last_trade_price f 48,112 173 53ms 151ms 5.5s 7.8s 0 transport_latency_assumed last_trade_price g 47,713 15 96ms 270ms 10.4s 18.5s 0 transport_latency_assumed last_trade_price h 48,219 2,052 23ms 68ms 472ms 11.8s 0 transport_latency_assumed market_resolved c 611 599 5ms 9ms 226ms 1.0min 0 transport_latency_assumed market_resolved e 611 not meas. 43ms 194ms 656ms 59.3s 0 transport_latency_assumed market_resolved f 611 not meas. 49ms 199ms 667ms 59.7s 0 transport_latency_assumed market_resolved g 611 not meas. 91ms 343ms 1.0s 57.9s 0 transport_latency_assumed market_resolved h 611 14 22ms 73ms 704ms 59.5s 0 transport_latency_assumed new_market c 1,658 989 117ms 19.5s 32.5s 33.3min 0 transport_latency_assumed new_market e 1,658 322 209ms 19.9s 28.4s 1.2min 0 transport_latency_assumed new_market f 1,658 240 216ms 19.8s 27.7s 1.0min 0 transport_latency_assumed new_market g 1,658 206 360ms 20.4s 31.2s 59.7min 0 transport_latency_assumed new_market h 1,658 720 176ms 19.8s 30.3s 42.7min 0 transport_latency_assumed price_change c 85,228,748 82,143,404 5ms 9ms 158ms 5.8s 0 transport_latency_assumed price_change e 85,188,486 354,622 40ms 50ms 356ms 16.5s 0 transport_latency_assumed price_change f 85,227,236 168,652 47ms 59ms 366ms 7.8s 0 transport_latency_assumed price_change g 85,124,852 14,702 82ms 111ms 740ms 19.3s 0 transport_latency_assumed price_change h 85,204,316 2,584,068 17ms 26ms 313ms 27.9s 0 transport_latency_assumed tick_size_change c 1,724 1,720 5ms 6ms 15ms 420ms 0 transport_latency_assumed tick_size_change e 1,724 not meas. 40ms 43ms 53ms 523ms 0 transport_latency_assumed tick_size_change f 1,724 not meas. 46ms 49ms 67ms 847ms 0 transport_latency_assumed tick_size_change g 1,724 not meas. 81ms 95ms 161ms 1.3s 0 transport_latency_assumed tick_size_change h 1,724 4 17ms 20ms 62ms 570ms 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-14/04/2026-09-14T04.parquet sha256sum 2026-09-14T04.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.