Hour audit: 2026-09-09T13
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-09T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T13:00:00.000009362+00:00 · last event 2026-09-09T13:59:59.999970069+00:00
VOLUME 114,040,869 rows · 1,232,545,095 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 112,059,734 · h: 112,021,247 · e: 111,933,018 · g: 111,828,294 · c: 92,010,241 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 495,526 (0.43%) · h: 25,409,023 (22.28%) · e: 1,902,777 (1.67%) · g: 53,555 (0.05%) · c: 86,179,988 (75.57%) (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 114,040,869 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 58597936e9a160338f4f6c06065a0f184212c28dbb94112d8d9c3654fdbf199a
the corpus checksum ledger names this file with the same digest
joined 114,044,458 to merged 114,040,869, minus 3,589 (minus 0.0031%)
boundary drops 3,589 · 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-09T14:59:08Z 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,433,967 119,723,687 0-39 35e0795f617e15cd252ac9c92fe37b5c4d6a31ed5832f2d0ba6305bb3185f6bb book 1,963,018 92,862,016 40-47 c2c6454201025f94c77a08eba768450f67e95735307fdd00d3c075c3ccd62f34 last_trade_price 75,605 4,249,400 48-48 b0c01aaf8fb13bf50b04a3729be357333317557c780303115996327b63ace835 market_resolved 1,521 161,134 49-49 651561887b63b8553eac98fe7b976af6d6650b92d3333bd19e1f5afbc6533fa0 new_market 4,304 372,927 50-50 5cd3e89e101ce59e8f3da5fa30985902b9f6ac334c3dc4e4fc7f1b78ddd17659 price_change 101,559,178 1,013,756,296 51-438 abc1f9a9bdffcfe1a28a3db64947314ebd89799e7fcd03f19de244bd8b0247f1 tick_size_change 3,276 121,269 439-439 49d7af914124d178416fa3aed629ffa9deca72f75a6cf64786a3de81e6dfee28 EVENT MIX count share price_change 101,559,178 89.06% best_bid_ask 10,433,967 9.15% book 1,963,018 1.72% last_trade_price 75,605 0.07% new_market 4,304 <0.01% tick_size_change 3,276 <0.01% market_resolved 1,521 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,434,147 10,433,967 180 4,098 FULL book 1,963,136 1,963,018 118 190,147 FULL last_trade_price 75,606 75,605 1 386 FULL market_resolved 1,521 1,521 0 57 FULL new_market 4,304 4,304 0 0 FULL price_change 101,562,468 101,559,178 3,290 3,509 FULL tick_size_change 3,276 3,276 0 134 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,385,608 7,856,649 5ms 16ms 168ms 7.1s 0 transport_latency_assumed best_bid_ask e 10,426,996 174,375 38ms 57ms 343ms 20.1s 0 transport_latency_assumed best_bid_ask f 10,429,455 42,519 48ms 70ms 332ms 12.8s 0 transport_latency_assumed best_bid_ask g 10,424,400 4,040 85ms 128ms 678ms 33.8s 0 transport_latency_assumed best_bid_ask h 10,430,989 2,356,384 17ms 33ms 347ms 56.2s 0 transport_latency_assumed book c 1,917,005 1,902,639 19.4min 22.3h 31.8d 102.7d 0 book_staleness book e 161,817 7,176 43ms 988ms 5.5min 83.9d 0 book_staleness book f 161,548 3,816 52ms 542ms 16.8min 84.1d 0 book_staleness book g 166,755 6,499 94ms 4.5s 14.2h 84.1d 0 book_staleness book h 161,836 42,888 22ms 113ms 21.1min 84.0d 0 book_staleness last_trade_price c 57,905 53,673 11ms 49ms 306ms 5.2s 0 transport_latency_assumed last_trade_price e 75,211 1,407 47ms 512ms 5.9s 20.0s 0 transport_latency_assumed last_trade_price f 75,229 641 57ms 333ms 3.4s 12.8s 0 transport_latency_assumed last_trade_price g 73,501 89 98ms 754ms 11.7s 34.2s 0 transport_latency_assumed last_trade_price h 75,349 19,795 23ms 82ms 635ms 40.0s 0 transport_latency_assumed market_resolved c 1,263 1,182 18ms 11.3min 17.2min 17.3min 0 transport_latency_assumed market_resolved e 943 55 39ms 296ms 59.5s 59.5s 0 transport_latency_assumed market_resolved f 943 3 49ms 325ms 59.5s 59.5s 0 transport_latency_assumed market_resolved g 943 28 85ms 360ms 933ms 6.4s 0 transport_latency_assumed market_resolved h 943 253 17ms 132ms 59.5s 59.5s 0 transport_latency_assumed new_market c 3,334 2,054 165ms 10.8min 11.8min 52.0min 0 transport_latency_assumed new_market e 2,325 381 202ms 21.8s 1.5min 2.3min 0 transport_latency_assumed new_market f 2,325 375 199ms 21.3s 1.5min 2.2min 0 transport_latency_assumed new_market g 2,325 411 347ms 23.3s 1.6min 2.1min 0 transport_latency_assumed new_market h 2,325 1,083 140ms 22.2s 1.6min 2.2min 0 transport_latency_assumed price_change c 81,642,386 76,361,171 6ms 17ms 179ms 7.1s 0 transport_latency_assumed price_change e 101,262,450 1,719,355 39ms 73ms 787ms 20.2s 0 transport_latency_assumed price_change f 101,386,958 448,164 48ms 84ms 530ms 12.9s 0 transport_latency_assumed price_change g 101,157,094 42,488 85ms 169ms 1.8s 34.6s 0 transport_latency_assumed price_change h 101,346,529 22,988,000 17ms 37ms 369ms 1.0min 0 transport_latency_assumed tick_size_change c 2,740 2,620 6ms 12ms 68ms 235ms 0 transport_latency_assumed tick_size_change e 3,276 28 38ms 61ms 154ms 486ms 0 transport_latency_assumed tick_size_change f 3,276 8 48ms 65ms 168ms 504ms 0 transport_latency_assumed tick_size_change g 3,276 not meas. 83ms 125ms 478ms 5.7s 0 transport_latency_assumed tick_size_change h 3,276 620 17ms 30ms 751ms 1.4s 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-09/13/2026-09-09T13.parquet sha256sum 2026-09-09T13.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.