Hour audit: 2026-09-20T11
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-20T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T11:00:00.000653862+00:00 · last event 2026-09-20T11:59:59.999679232+00:00
VOLUME 115,438,941 rows · 1,224,040,567 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 115,003,669 · f: 114,950,386 · e: 114,895,355 · g: 114,784,485 · c: 110,696,127 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,205,989 (7.97%) · f: 320,939 (0.28%) · e: 777,323 (0.67%) · g: 46,129 (0.04%) · c: 105,088,561 (91.03%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 115,438,941 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5a3b8e685002fcf1a9d7a6bcc0d94b73251fcad7df8c81eb390a0b7b1c5acfcb
the corpus checksum ledger names this file with the same digest
joined 115,441,563 to merged 115,438,941, minus 2,622 (minus 0.0023%)
boundary drops 2,622 · 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-20T13:37:03Z 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,268,499 128,591,792 0-42 5042d590aaebee4d0026ed97c72992a6decfd7350afb2e7c1c6b5e1e750afe5d book 496,501 52,331,153 43-44 f50319332d08e16f5b8b37fad679c55adfbcf9cc392c93971d0000553ad877f1 last_trade_price 58,846 3,430,972 45-45 e68b35968bc4c12e2c37c46c50e1ebc4b297c57e0b1ef2fc5d8ee14d981e49b7 market_resolved 1,483 232,918 46-46 71935e84637d11111ab5788899fe656bf90eb10c45c62d75c00c74fd78025a18 new_market 2,626 260,158 47-47 d7174ee3a2c15b621ff43f47ef4cca64987f39d2af52fd75676ecd305e422373 price_change 103,606,038 1,037,703,242 48-443 329f5a7406e02a45989db645aeb04ebb5bc1a2e64fc5d2a3b2e9707ea59027a3 tick_size_change 4,948 178,149 444-444 106bd99565283e7f5fb8367298e7fcea964adee0ec3309a56fb64791db1e565d EVENT MIX count share price_change 103,606,038 89.75% best_bid_ask 11,268,499 9.76% book 496,501 0.43% last_trade_price 58,846 0.05% tick_size_change 4,948 <0.01% new_market 2,626 <0.01% market_resolved 1,483 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,268,719 11,268,499 220 797 FULL book 496,671 496,501 170 168,398 FULL last_trade_price 58,848 58,846 2 120 FULL market_resolved 1,483 1,483 0 40 FULL new_market 2,626 2,626 0 0 FULL price_change 103,608,268 103,606,038 2,230 393 FULL tick_size_change 4,948 4,948 0 57 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,842,516 10,319,828 5ms 13ms 122ms 7.8s 0 transport_latency_assumed best_bid_ask e 11,263,270 71,036 40ms 52ms 269ms 26.9s 0 transport_latency_assumed best_bid_ask f 11,263,480 27,200 47ms 62ms 305ms 19.1s 0 transport_latency_assumed best_bid_ask g 11,260,917 3,374 78ms 103ms 575ms 30.3s 0 transport_latency_assumed best_bid_ask h 11,265,061 847,061 18ms 31ms 241ms 45.7s 0 transport_latency_assumed book c 469,878 456,690 2.8min 1.7d 38.7d 113.5d 0 book_staleness book e 128,518 8,388 42ms 834ms 17.1h 95.1d 0 book_staleness book f 131,476 9,103 51ms 3.1s 1.8d 95.0d 0 book_staleness book g 130,175 9,102 89ms 3.7s 1.8d 95.1d 0 book_staleness book h 123,156 13,218 23ms 112ms 8.3min 95.1d 0 book_staleness last_trade_price c 56,182 52,513 6ms 24ms 249ms 1.1s 0 transport_latency_assumed last_trade_price e 58,276 608 42ms 174ms 2.7s 26.7s 0 transport_latency_assumed last_trade_price f 58,369 332 50ms 205ms 4.1s 19.2s 0 transport_latency_assumed last_trade_price g 57,744 41 86ms 404ms 5.0s 30.3s 0 transport_latency_assumed last_trade_price h 58,651 5,352 20ms 62ms 521ms 15.5s 0 transport_latency_assumed market_resolved c 1,373 1,306 5ms 20ms 5.4min 5.9min 0 transport_latency_assumed market_resolved e 1,386 48 41ms 121ms 52.1s 57.6s 0 transport_latency_assumed market_resolved f 1,386 27 47ms 125ms 370ms 843ms 0 transport_latency_assumed market_resolved g 1,386 not meas. 79ms 217ms 587ms 2.1s 0 transport_latency_assumed market_resolved h 1,386 102 19ms 59ms 54.8s 1.0min 0 transport_latency_assumed new_market c 1,734 984 108ms 3.8min 4.5min 6.9h 0 transport_latency_assumed new_market e 1,687 418 212ms 16.7s 1.1min 13.5h 0 transport_latency_assumed new_market f 1,687 359 218ms 21.1s 39.8s 5.5h 0 transport_latency_assumed new_market g 1,687 220 288ms 21.0s 48.0s 7.3h 0 transport_latency_assumed new_market h 1,687 645 148ms 19.7s 42.0s 4.1h 0 transport_latency_assumed price_change c 99,319,724 94,252,698 5ms 15ms 137ms 7.9s 0 transport_latency_assumed price_change e 103,437,270 696,792 40ms 63ms 443ms 27.0s 0 transport_latency_assumed price_change f 103,489,040 283,918 47ms 75ms 528ms 19.2s 0 transport_latency_assumed price_change g 103,327,628 33,392 78ms 133ms 1.3s 30.8s 0 transport_latency_assumed price_change h 103,548,780 8,339,238 18ms 36ms 279ms 47.5s 0 transport_latency_assumed tick_size_change c 4,720 4,542 5ms 10ms 41ms 224ms 0 transport_latency_assumed tick_size_change e 4,948 33 39ms 44ms 96ms 221ms 0 transport_latency_assumed tick_size_change f 4,948 not meas. 46ms 53ms 103ms 335ms 0 transport_latency_assumed tick_size_change g 4,948 not meas. 78ms 93ms 269ms 607ms 0 transport_latency_assumed tick_size_change h 4,948 373 18ms 26ms 84ms 5.0s 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-20/11/2026-09-20T11.parquet sha256sum 2026-09-20T11.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.