Hour audit: 2026-09-06T23
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-06T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T23:00:00.000018083+00:00 · last event 2026-09-06T23:59:59.998469204+00:00
VOLUME 112,450,997 rows · 1,165,204,979 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 112,053,044 · g: 111,961,167 · h: 111,881,697 · e: 111,867,088 · c: 107,966,108 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 248,115 (0.22%) · g: 34,451 (0.03%) · h: 8,178,376 (7.27%) · e: 413,525 (0.37%) · c: 103,576,530 (92.11%) (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 112,450,997 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 547e563d3548dfc2dc1f697c043820ffbf35634cbc912361bc78b6c28b8d6828
the corpus checksum ledger names this file with the same digest
joined 112,453,727 to merged 112,450,997, minus 2,730 (minus 0.0024%)
boundary drops 2,730 · 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-07T03:08:56Z 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,855,540 130,811,851 0-45 4343e15d7a3d91e8e99be3234fc1149e26ef1751731c43f40a73bfd8a01a7542 book 468,970 49,192,461 46-47 23df8308a4c1f93a2603f3bc56afbca10f476b6e25450262e8380dec9f79e80e last_trade_price 53,899 3,095,577 48-48 1f3ab8a0bc0eaa6def7071bba6b85bd15dd16716eb9e238abb98cc7bb391e61c market_resolved 2,694 412,815 49-49 b97b2041d037504e75495edf56142d53bad90fac541c6f65f155caa650265f85 new_market 2,536 247,431 50-50 35fc032622530638ef7d0c490069c11d4a1fb2de0f5672e4005d43368884af4c price_change 100,062,550 979,993,502 51-432 e5a906322fd0724db5471f9eb8feabe3288707f7707e9573cd8abfe1ccb15be9 tick_size_change 4,808 171,583 433-433 f96c3378fe8f5162d074581c06946d13eabab5cb16254b9de98f6a53279f8082 EVENT MIX count share price_change 100,062,550 88.98% best_bid_ask 11,855,540 10.54% book 468,970 0.42% last_trade_price 53,899 0.05% tick_size_change 4,808 <0.01% market_resolved 2,694 <0.01% new_market 2,536 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,855,881 11,855,540 341 879 FULL book 468,974 468,970 4 169,339 FULL last_trade_price 53,900 53,899 1 70 FULL market_resolved 2,694 2,694 0 114 FULL new_market 2,536 2,536 0 0 FULL price_change 100,064,934 100,062,550 2,384 1,194 FULL tick_size_change 4,808 4,808 0 113 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,373,897 10,919,411 5ms 10ms 147ms 7.2s 0 transport_latency_assumed best_bid_ask e 11,853,038 42,305 43ms 51ms 241ms 12.2s 0 transport_latency_assumed best_bid_ask f 11,853,132 25,098 48ms 58ms 247ms 14.2s 0 transport_latency_assumed best_bid_ask g 11,850,290 2,777 82ms 105ms 489ms 27.3s 0 transport_latency_assumed best_bid_ask h 11,851,824 865,949 17ms 28ms 249ms 1.0min 0 transport_latency_assumed book c 457,148 447,256 1.6min 16.1h 34.1d 100.1d 0 book_staleness book e 113,668 2,216 45ms 256ms 6.5s 100.0d 0 book_staleness book f 113,784 1,946 51ms 245ms 6.7s 37.6d 0 book_staleness book g 118,227 6,525 91ms 1.1s 10.3h 81.5d 0 book_staleness book h 115,045 11,027 21ms 127ms 22.9min 39.3d 0 book_staleness last_trade_price c 52,023 49,695 10ms 42ms 293ms 7.9s 0 transport_latency_assumed last_trade_price e 53,825 335 49ms 200ms 3.7s 12.3s 0 transport_latency_assumed last_trade_price f 53,756 162 55ms 188ms 3.5s 14.2s 0 transport_latency_assumed last_trade_price g 53,252 29 95ms 290ms 4.3s 27.3s 0 transport_latency_assumed last_trade_price h 53,594 3,678 23ms 84ms 967ms 59.6s 0 transport_latency_assumed market_resolved c 2,480 2,400 5ms 16ms 4.9min 5.2min 0 transport_latency_assumed market_resolved e 2,544 34 81ms 194ms 50.8s 1.1min 0 transport_latency_assumed market_resolved f 2,544 5 87ms 192ms 532ms 59.2s 0 transport_latency_assumed market_resolved g 2,544 10 102ms 264ms 594ms 968ms 0 transport_latency_assumed market_resolved h 2,544 245 33ms 75ms 437ms 1.0min 0 transport_latency_assumed new_market c 1,554 887 154ms 23.1s 45.8s 4.2h 0 transport_latency_assumed new_market e 1,553 493 185ms 22.8s 43.3s 9.9min 0 transport_latency_assumed new_market f 1,553 367 212ms 23.7s 46.0s 1.3h 0 transport_latency_assumed new_market g 1,553 262 342ms 24.9s 51.7s 7.7h 0 transport_latency_assumed new_market h 1,553 527 170ms 23.4s 44.3s 2.6h 0 transport_latency_assumed price_change c 96,074,650 92,152,671 5ms 12ms 154ms 9.3s 0 transport_latency_assumed price_change e 99,837,652 368,134 43ms 57ms 329ms 12.3s 0 transport_latency_assumed price_change f 100,023,467 220,521 48ms 64ms 320ms 14.2s 0 transport_latency_assumed price_change g 99,930,493 24,848 83ms 117ms 610ms 27.3s 0 transport_latency_assumed price_change h 99,852,329 7,296,376 17ms 32ms 283ms 1.0min 0 transport_latency_assumed tick_size_change c 4,356 4,210 5ms 9ms 99ms 247ms 0 transport_latency_assumed tick_size_change e 4,808 8 43ms 52ms 187ms 449ms 0 transport_latency_assumed tick_size_change f 4,808 16 48ms 56ms 217ms 483ms 0 transport_latency_assumed tick_size_change g 4,808 not meas. 82ms 98ms 355ms 929ms 0 transport_latency_assumed tick_size_change h 4,808 574 17ms 24ms 240ms 3.5s 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-06/23/2026-09-06T23.parquet sha256sum 2026-09-06T23.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.