Hour audit: 2026-09-05T16
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-05T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T16:00:00.065272430+00:00 · last event 2026-09-05T16:59:59.999998206+00:00
VOLUME 118,991,001 rows · 1,275,394,491 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 117,404,112 · h: 117,388,973 · f: 117,241,297 · g: 117,009,283 · c: 99,518,751 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 138,744 (0.12%) · h: 9,714 (0.01%) · f: 311,267 (0.26%) · g: 117,006,314 (98.33%) · c: 1,524,962 (1.28%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 118,991,001 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f5a89397f8fc07dc6ac8a69c66195bd71cfb81be59348fd621b6957571ed6fc7
the corpus checksum ledger names this file with the same digest
joined 118,993,983 to merged 118,991,001, minus 2,982 (minus 0.0025%)
boundary drops 2,982 · 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-05T21:19:46Z 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,094,682 117,233,259 0-38 45101904449aaaff068abadeecede81955d2487ad48e810025230974b3d56706 book 1,681,603 85,125,018 39-45 8489af3b09cd09834626c15ac122625c8c7279f794c754ee37c05f4a82edcfc8 last_trade_price 69,700 4,006,043 46-46 5771d6df1b02a19a338cfcabd6ab36bab7773b232b435c896263c0db56d715ad market_resolved 3,038 434,747 47-47 5cd1d7306846ef93eb5cb0d02e627ee27190690fbb13dc96c78073d04c2d9440 new_market 1,906 200,215 48-48 0c54939135e7c5d99bfd0aaeb9a1dafb585198e4dea763f021f98732485ad471 price_change 107,122,460 1,066,394,517 49-457 2da3dec478ed54f53bbeb51e1cf522230c8ef4d74d78f2fd4882f36c0e613a45 tick_size_change 17,612 646,959 458-458 9f623ffdcda1645a3091cddd0b3abb6a8ac50257c97cf6b36b98bec5e1265246 EVENT MIX count share price_change 107,122,460 90.03% best_bid_ask 10,094,682 8.48% book 1,681,603 1.41% last_trade_price 69,700 0.06% tick_size_change 17,612 0.01% market_resolved 3,038 <0.01% new_market 1,906 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,094,947 10,094,682 265 3,463 FULL book 1,681,623 1,681,603 20 186,273 FULL last_trade_price 69,703 69,700 3 402 FULL market_resolved 3,038 3,038 0 177 FULL new_market 1,906 1,906 0 0 FULL price_change 107,125,154 107,122,460 2,694 1,933 FULL tick_size_change 17,612 17,612 0 1,163 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,481,488 692 5ms 10ms 121ms 8.9s 0 transport_latency_assumed best_bid_ask e 10,091,846 7,522 41ms 48ms 196ms 4.6s 0 transport_latency_assumed best_bid_ask f 10,081,717 15,892 47ms 67ms 362ms 16.0s 0 transport_latency_assumed best_bid_ask g 10,069,600 10,069,336 81ms 132ms 980ms 28.5s 0 transport_latency_assumed best_bid_ask h 10,093,256 1,240 18ms 26ms 206ms 46.3s 0 transport_latency_assumed book c 1,644,328 1,515,126 3.2min 13.3h 34.2d 98.8d 0 book_staleness book e 144,944 2,433 43ms 118ms 2.0s 24.9d 0 book_staleness book f 147,258 5,394 49ms 243ms 1.2h 1.5d 0 book_staleness book g 157,913 157,899 87ms 10.7s 23.4h 80.3d 0 book_staleness book h 145,059 751 21ms 52ms 1.9s 4.7h 0 book_staleness last_trade_price c 57,934 3 10ms 40ms 246ms 9.0s 0 transport_latency_assumed last_trade_price e 69,611 866 47ms 100ms 980ms 5.0s 0 transport_latency_assumed last_trade_price f 68,340 1,569 53ms 144ms 5.0s 15.1s 0 transport_latency_assumed last_trade_price g 67,260 67,257 91ms 213ms 6.7s 26.8s 0 transport_latency_assumed last_trade_price h 69,668 5 23ms 61ms 383ms 8.9s 0 transport_latency_assumed market_resolved c 2,623 364 5ms 3.7min 8.4min 9.7min 0 transport_latency_assumed market_resolved e 2,674 not meas. 43ms 187ms 443ms 916ms 0 transport_latency_assumed market_resolved f 2,674 not meas. 48ms 170ms 675ms 1.5s 0 transport_latency_assumed market_resolved g 2,674 2,674 86ms 311ms 1.6s 2.5s 0 transport_latency_assumed market_resolved h 2,674 not meas. 19ms 63ms 226ms 2.1s 0 transport_latency_assumed new_market c 1,320 71 75ms 15.4s 9.7min 24.1min 0 transport_latency_assumed new_market e 1,301 166 171ms 13.9s 23.2s 8.6min 0 transport_latency_assumed new_market f 1,301 304 189ms 16.2s 31.3s 15.3min 0 transport_latency_assumed new_market g 1,301 1,301 295ms 16.0s 49.2s 15.4min 0 transport_latency_assumed new_market h 1,301 64 143ms 14.1s 24.7s 2.5min 0 transport_latency_assumed price_change c 89,318,046 8,706 5ms 11ms 142ms 9.1s 0 transport_latency_assumed price_change e 107,076,124 127,725 41ms 52ms 254ms 4.7s 0 transport_latency_assumed price_change f 106,922,427 288,068 47ms 79ms 467ms 16.0s 0 transport_latency_assumed price_change g 106,692,995 106,690,307 83ms 161ms 1.2s 29.0s 0 transport_latency_assumed price_change h 107,059,403 7,654 18ms 29ms 231ms 46.9s 0 transport_latency_assumed tick_size_change c 13,012 not meas. 6ms 13ms 234ms 1.4s 0 transport_latency_assumed tick_size_change e 17,612 32 40ms 49ms 255ms 941ms 0 transport_latency_assumed tick_size_change f 17,580 40 73ms 183ms 356ms 1.5s 0 transport_latency_assumed tick_size_change g 17,540 17,540 127ms 383ms 727ms 1.7s 0 transport_latency_assumed tick_size_change h 17,612 not meas. 18ms 33ms 280ms 3.7s 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-05/16/2026-09-05T16.parquet sha256sum 2026-09-05T16.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.