Hour audit: 2026-09-20T19
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-20T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T19:00:00.000009955+00:00 · last event 2026-09-20T19:59:59.999888728+00:00
VOLUME 141,731,654 rows · 1,630,770,640 bytes (1.52 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 138,233,526 · e: 132,981,821 · f: 116,976,315 · c: 96,606,642 · g: 10,263,046 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 43,821,058 (30.92%) · e: 4,496,483 (3.17%) · f: 1,774,575 (1.25%) · c: 90,811,050 (64.07%) · g: 828,488 (0.58%) (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 141,731,654 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ab4887524240c59ac7bf5c9e6e4b34f5e8763a747da64710cf54b9fdbf4c0da0
the corpus checksum ledger names this file with the same digest
joined 141,760,078 to merged 141,731,654, minus 28,424 (minus 0.0201%)
boundary drops 28,424 · 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-23T09:33:32Z 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 13,880,535 163,408,506 0-52 06724a073b0d7d58b21c89fe5586c570055ac73694cb49af094530e52f9bfc55 book 3,603,372 121,914,633 53-66 c801538413d2fb853e7d1458e0099cb65f355914fa411de05b7158e5704f90ec last_trade_price 65,586 3,801,572 67-67 8298f17b2605f61ddedbfe7d6538cc9f7fbe414f806a867fb6669ca685b57f76 market_resolved 9,123 689,080 68-68 8187bb68adb2fbaa8335bc31f49c418c0598466b7cef60f8a92f02ce93e4e146 new_market 8,930 450,509 69-69 aab95c764e0c660d94f9340f0ece5c0782c9081c7582ed03429aacc7d85c9303 price_change 124,154,188 1,338,534,391 70-543 2cc3ea67e2f5b10e30a9a67bdd629d2e6b7ebffe37ed837639bd28640b0f2857 tick_size_change 9,920 364,932 544-544 367daff463e01e5f5d15790fecccbb513028d290273b3b308d5e15e6a0567c41 EVENT MIX count share price_change 124,154,188 87.60% best_bid_ask 13,880,535 9.79% book 3,603,372 2.54% last_trade_price 65,586 0.05% tick_size_change 9,920 <0.01% market_resolved 9,123 <0.01% new_market 8,930 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,880,692 13,880,535 157 56,159 FULL book 3,630,476 3,603,372 27,104 157,864 FULL last_trade_price 65,586 65,586 0 3,608 FULL market_resolved 9,123 9,123 0 3,858 FULL new_market 8,931 8,930 1 1,113 FULL price_change 124,155,350 124,154,188 1,162 65,539 FULL tick_size_change 9,920 9,920 0 2,396 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,450,796 8,940,937 6ms 17ms 141ms 4.0s 0 transport_latency_assumed best_bid_ask e 13,309,559 425,075 42ms 67ms 326ms 28.8s 0 transport_latency_assumed best_bid_ask f 11,668,255 142,803 45ms 75ms 362ms 29.4s 0 transport_latency_assumed best_bid_ask g 940,484 4,978 83ms 405ms 1.6s 30.4s 0 transport_latency_assumed best_bid_ask h 13,878,054 4,366,742 19ms 47ms 304ms 51.8s 0 transport_latency_assumed book c 2,883,338 2,307,449 7.0min 2.2d 43.2d 113.9d 0 book_staleness book e 490,937 104,824 1.5min 1.6d 39.0d 113.9d 0 book_staleness book f 1,630,045 363,932 5.6min 2.1d 43.2d 113.9d 0 book_staleness book g 1,093,687 778,051 6.7min 2.1d 43.2d 113.9d 0 book_staleness book h 149,213 49,116 26ms 1.8s 2.2d 106.2d 0 book_staleness last_trade_price c 44,396 41,742 7ms 26ms 220ms 1.8s 0 transport_latency_assumed last_trade_price e 62,583 2,050 47ms 315ms 5.2s 28.7s 0 transport_latency_assumed last_trade_price f 55,095 543 52ms 525ms 11.1s 29.4s 0 transport_latency_assumed last_trade_price g 3,980 25 149ms 1.9s 16.6s 30.1s 0 transport_latency_assumed last_trade_price h 65,513 21,226 21ms 82ms 479ms 7.5s 0 transport_latency_assumed market_resolved c 5,368 5,011 4.4min 17.6min 23.4min 25.2min 0 transport_latency_assumed market_resolved e 3,284 93 88ms 236ms 4.4min 4.8min 0 transport_latency_assumed market_resolved f 7,300 3,060 7.9min 22.7min 28.3min 29.1min 0 transport_latency_assumed market_resolved g 188 6 227ms 597ms 1.2s 1.7s 0 transport_latency_assumed market_resolved h 3,263 953 36ms 90ms 27.2s 58.7s 0 transport_latency_assumed new_market c 7,713 4,500 6.5min 17.4min 54.1min 16.5h 0 transport_latency_assumed new_market e 2,536 450 222ms 4.1min 5.2min 3.5h 0 transport_latency_assumed new_market f 6,737 1,670 5.2min 13.7min 2.0h 16.4h 0 transport_latency_assumed new_market g 4,487 1,456 3.9min 9.7min 10.5min 55.5min 0 transport_latency_assumed new_market h 2,433 854 136ms 28.4s 1.4min 3.4h 0 transport_latency_assumed price_change c 84,207,979 79,504,655 6ms 19ms 166ms 4.1s 0 transport_latency_assumed price_change e 119,103,586 3,963,734 42ms 82ms 636ms 28.9s 0 transport_latency_assumed price_change f 103,600,507 1,262,497 45ms 95ms 849ms 29.4s 0 transport_latency_assumed price_change g 8,219,732 43,972 85ms 478ms 4.3s 30.6s 0 transport_latency_assumed price_change h 124,125,130 39,379,330 19ms 52ms 350ms 52.2s 0 transport_latency_assumed tick_size_change c 7,052 6,756 6ms 14ms 220ms 247ms 0 transport_latency_assumed tick_size_change e 9,336 257 42ms 60ms 296ms 2.2s 0 transport_latency_assumed tick_size_change f 8,376 70 45ms 77ms 293ms 669ms 0 transport_latency_assumed tick_size_change g 488 not meas. 80ms 129ms 568ms 579ms 0 transport_latency_assumed tick_size_change h 9,920 2,837 19ms 52ms 148ms 3.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-20/19/2026-09-20T19.parquet sha256sum 2026-09-20T19.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.