Hour audit: 2026-09-28T13
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-28T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T13:00:00.000022091+00:00 · last event 2026-09-28T13:59:59.999877054+00:00
VOLUME 105,675,355 rows · 1,157,451,388 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 105,202,387 · k: 105,161,292 · h: 105,147,135 · g: 103,801,480 · i: 101,358,617 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 93,177,335 (88.17%) · k: 8,298,222 (7.85%) · h: 1,668,636 (1.58%) · g: 29,702 (0.03%) · i: 2,501,460 (2.37%) (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 105,675,355 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b7cbdb0202bebe7190c623d903eb1d8422c32d9b6fb6d64bbfe5df694c2bd83a
the corpus checksum ledger names this file with the same digest
joined 105,677,403 to merged 105,675,355, minus 2,048 (minus 0.0019%)
boundary drops 2,048 · 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-28T15:37:12Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,073,960 118,734,449 0-38 1939ae6773dcdef1f1dfbb692bc7fec3412b84f2a49dd14d4389494f57383cde book 550,881 54,985,667 39-41 b511d898dbeea15e7eed9bfe61f6dda96f314540523217dfc9d07d51c0c63f39 last_trade_price 62,626 3,594,484 42-42 469fa369aa901ba938c09c1dbf8ba5c3c251b139366a5c50b95360978d355a0f market_resolved 791 114,287 43-43 b293da6127f48ad47aa99fd0814af61f514862c004e2826bf5773d8cd40ba3e2 new_market 1,537 153,390 44-44 31df9f1d98de29faecbe32ca7f1db6c7cc7259692988e600cbc3f3be5ca2da16 price_change 94,982,668 978,555,279 45-407 19b05892a2eb9214fda70e532a135491cdadae8ba4d61cb92d11937eeccfe5bc tick_size_change 2,892 106,686 408-408 15b407a8e077958aabf0b3a3d64f9237d81792aec750eda48543dfe3aa75edb8 EVENT MIX count share price_change 94,982,668 89.88% best_bid_ask 10,073,960 9.53% book 550,881 0.52% last_trade_price 62,626 0.06% tick_size_change 2,892 <0.01% new_market 1,537 <0.01% market_resolved 791 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,074,142 10,073,960 182 397 FULL book 550,885 550,881 4 198,628 FULL last_trade_price 62,626 62,626 0 61 FULL market_resolved 791 791 0 19 FULL new_market 1,537 1,537 0 0 FULL price_change 94,984,530 94,982,668 1,862 426 FULL tick_size_change 2,892 2,892 0 20 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,072,562 8,971,742 6ms 17ms 132ms 4.4s 0 transport_latency_assumed best_bid_ask g 10,052,560 1,327 80ms 112ms 679ms 36.1s 0 transport_latency_assumed best_bid_ask h 10,071,361 150,797 18ms 33ms 202ms 45.3s 0 transport_latency_assumed best_bid_ask i 9,712,382 194,849 20ms 30ms 154ms 20.6s 0 transport_latency_assumed best_bid_ask k 10,072,004 755,245 13ms 26ms 146ms 57.6s 0 transport_latency_assumed book c 130,142 113,032 8ms 44ms 2.9h 103.0d 0 book_staleness book g 131,082 12,240 99ms 26.3s 1.9d 103.1d 0 book_staleness book h 131,384 5,375 23ms 279ms 13.8h 103.1d 0 book_staleness book i 527,896 406,905 29.9min 1.4d 37.0d 121.6d 0 book_staleness book k 132,904 13,329 17ms 128ms 22.0h 103.1d 0 book_staleness last_trade_price c 62,434 55,029 7ms 27ms 224ms 2.7s 0 transport_latency_assumed last_trade_price g 57,319 42 95ms 3.6s 16.2s 36.4s 0 transport_latency_assumed last_trade_price h 62,175 1,069 20ms 130ms 2.3s 13.6s 0 transport_latency_assumed last_trade_price i 58,082 1,084 22ms 242ms 2.3s 6.7s 0 transport_latency_assumed last_trade_price k 62,343 5,402 14ms 59ms 361ms 5.3s 0 transport_latency_assumed market_resolved c 686 613 6ms 27ms 54.1s 56.8s 0 transport_latency_assumed market_resolved g 686 94 87ms 33.6s 41.1s 58.2s 0 transport_latency_assumed market_resolved h 686 11 19ms 74ms 52.6s 56.3s 0 transport_latency_assumed market_resolved i 667 43 23ms 34.9s 4.2min 4.2min 0 transport_latency_assumed market_resolved k 686 30 15ms 41.5s 48.7s 51.4s 0 transport_latency_assumed new_market c 979 430 124ms 10.8s 9.9min 12.4min 0 transport_latency_assumed new_market g 979 135 338ms 25.7s 10.1min 16.5min 0 transport_latency_assumed new_market h 979 262 157ms 21.9s 11.8min 12.3min 0 transport_latency_assumed new_market i 979 423 121ms 17.3s 11.8min 12.3min 0 transport_latency_assumed new_market k 979 287 179ms 19.6s 10.1min 12.4min 0 transport_latency_assumed price_change c 94,932,692 84,033,827 6ms 20ms 147ms 4.4s 0 transport_latency_assumed price_change g 93,555,962 15,864 82ms 193ms 8.6s 36.4s 0 transport_latency_assumed price_change h 94,877,658 1,511,102 19ms 42ms 338ms 47.6s 0 transport_latency_assumed price_change i 91,055,799 1,898,132 20ms 43ms 495ms 20.6s 0 transport_latency_assumed price_change k 94,889,484 7,523,743 13ms 31ms 175ms 58.3s 0 transport_latency_assumed tick_size_change c 2,892 2,662 6ms 13ms 50ms 162ms 0 transport_latency_assumed tick_size_change g 2,892 not meas. 79ms 99ms 239ms 1.3s 0 transport_latency_assumed tick_size_change h 2,892 20 18ms 27ms 61ms 1.7s 0 transport_latency_assumed tick_size_change i 2,812 24 19ms 27ms 88ms 253ms 0 transport_latency_assumed tick_size_change k 2,892 186 13ms 21ms 63ms 122ms 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-28/13/2026-09-28T13.parquet sha256sum 2026-09-28T13.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.