Hour audit: 2026-09-18T00
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-18T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T00:00:00.000000536+00:00 · last event 2026-09-18T00:59:59.999947597+00:00
VOLUME 116,500,646 rows · 1,177,869,487 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 116,469,970 · h: 116,434,860 · f: 116,415,849 · e: 116,390,430 · g: 116,327,779 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 111,487,708 (95.70%) · h: 4,314,389 (3.70%) · f: 170,290 (0.15%) · e: 483,175 (0.41%) · g: 45,084 (0.04%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,500,646 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f6d43dedc04d9ef779c4b34561dad040d559daa15fcef9dc2199ce55b86c87c9
the corpus checksum ledger names this file with the same digest
joined 116,503,226 to merged 116,500,646, minus 2,580 (minus 0.0022%)
boundary drops 2,580 · 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-18T02:04:04Z 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,847,427 122,231,280 0-41 34296c1c69fe93ec4115dc76a65629f32babc66828cd98bb7ae32a2823020d8c book 119,415 12,188,792 42-42 cc155e84d17dae2a4bee6548d8cdc28a57b12af83199de7e3364d0df5ea14ae3 last_trade_price 49,861 2,903,619 43-43 41aa13113e316d8d558093b5bff206920c14b577c8d2c8fd868cbac78ab584db market_resolved 501 83,039 44-44 d110450c17d9d122f8a31f8a6e822c9cf7ba30d2ca63a883d90316e554d9e5e5 new_market 1,086 117,267 45-45 4c9a1fc0da40aff69d86a2407e3d5b63c74e2cfeb6591dc1dfcbe8ae0c0ca439 price_change 105,479,472 1,038,914,449 46-448 13600ea6399f2a604870ed77962fcdf2b5b882a996ed4feb91f91cb0da2a1521 tick_size_change 2,884 103,554 449-449 167c85ead3436742221d3a17e9758ae96f6a96082f594feaffd245289ce56e21 EVENT MIX count share price_change 105,479,472 90.54% best_bid_ask 10,847,427 9.31% book 119,415 0.10% last_trade_price 49,861 0.04% tick_size_change 2,884 <0.01% new_market 1,086 <0.01% market_resolved 501 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,847,609 10,847,427 182 108 FULL book 119,415 119,415 0 4,575 FULL last_trade_price 49,861 49,861 0 0 FULL market_resolved 501 501 0 0 FULL new_market 1,086 1,086 0 0 FULL price_change 105,481,870 105,479,472 2,398 314 FULL tick_size_change 2,884 2,884 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,846,785 10,427,024 5ms 9ms 103ms 8.4s 0 transport_latency_assumed best_bid_ask e 10,844,879 38,786 40ms 46ms 152ms 5.0s 0 transport_latency_assumed best_bid_ask f 10,845,250 11,877 48ms 56ms 198ms 3.6s 0 transport_latency_assumed best_bid_ask g 10,842,756 2,742 82ms 100ms 275ms 9.6s 0 transport_latency_assumed best_bid_ask h 10,846,182 366,998 18ms 24ms 130ms 15.8s 0 transport_latency_assumed book c 108,428 101,305 7ms 35ms 19.4min 92.5d 0 book_staleness book e 108,014 4,525 42ms 124ms 15.6min 92.6d 0 book_staleness book f 106,923 2,611 50ms 173ms 4.1min 92.6d 0 book_staleness book g 107,498 4,237 87ms 293ms 25.8min 92.5d 0 book_staleness book h 106,170 6,737 21ms 54ms 7.2s 47.1d 0 book_staleness last_trade_price c 49,725 46,802 10ms 46ms 255ms 4.7s 0 transport_latency_assumed last_trade_price e 49,657 386 46ms 108ms 588ms 4.7s 0 transport_latency_assumed last_trade_price f 49,742 125 55ms 151ms 1.3s 4.7s 0 transport_latency_assumed last_trade_price g 49,063 81 95ms 204ms 2.6s 7.5s 0 transport_latency_assumed last_trade_price h 49,706 2,467 24ms 67ms 360ms 7.1s 0 transport_latency_assumed market_resolved c 496 489 5ms 9ms 38ms 214ms 0 transport_latency_assumed market_resolved e 496 not meas. 41ms 123ms 1.9s 57.3s 0 transport_latency_assumed market_resolved f 496 1 49ms 143ms 307ms 468ms 0 transport_latency_assumed market_resolved g 496 not meas. 86ms 241ms 465ms 953ms 0 transport_latency_assumed market_resolved h 496 11 19ms 52ms 4.0s 56.0s 0 transport_latency_assumed new_market c 754 426 118ms 57.5s 1.1min 1.3min 0 transport_latency_assumed new_market e 754 154 170ms 56.1s 1.2min 1.3min 0 transport_latency_assumed new_market f 754 148 206ms 1.0min 1.2min 1.2min 0 transport_latency_assumed new_market g 754 78 353ms 27.9s 1.2min 1.2min 0 transport_latency_assumed new_market h 754 280 147ms 58.2s 1.3min 1.3min 0 transport_latency_assumed price_change c 105,460,898 100,908,870 5ms 11ms 132ms 10.6s 0 transport_latency_assumed price_change e 105,383,746 439,320 40ms 50ms 231ms 6.3s 0 transport_latency_assumed price_change f 105,409,800 155,528 48ms 61ms 298ms 5.9s 0 transport_latency_assumed price_change g 105,324,328 37,946 82ms 102ms 367ms 10.1s 0 transport_latency_assumed price_change h 105,428,668 3,937,808 18ms 27ms 185ms 18.6s 0 transport_latency_assumed tick_size_change c 2,884 2,792 5ms 8ms 49ms 268ms 0 transport_latency_assumed tick_size_change e 2,884 4 40ms 78ms 450ms 629ms 0 transport_latency_assumed tick_size_change f 2,884 not meas. 48ms 52ms 87ms 119ms 0 transport_latency_assumed tick_size_change g 2,884 not meas. 81ms 95ms 127ms 214ms 0 transport_latency_assumed tick_size_change h 2,884 88 18ms 23ms 48ms 179ms 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-18/00/2026-09-18T00.parquet sha256sum 2026-09-18T00.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.