Hour audit: 2026-09-22T14
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-22T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T14:00:00.000066896+00:00 · last event 2026-09-22T14:59:59.999838772+00:00
VOLUME 123,686,241 rows · 1,429,723,130 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES cefhij — 6 machines contributed rows
captured h: 118,762,381 · e: 118,211,854 · i: 116,199,672 · f: 113,936,940 · c: 113,588,981 · j: 60,025,026 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,483,490 (6.05%) · e: 187,722 (0.15%) · i: 2,762,092 (2.23%) · f: 235,127 (0.19%) · c: 97,287,432 (78.66%) · j: 15,730,378 (12.72%) (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 123,686,241 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 4fe9ed9aaa516f4b9695e1d35476f6c6080372a8465f8e4f9529582246f67c20
the corpus checksum ledger names this file with the same digest
joined 123,697,809 to merged 123,686,241, minus 11,568 (minus 0.0094%)
boundary drops 11,568 · 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-22T17:29:16Z as cefhij
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,811,424 133,092,339 0-41 22b364a8522f67eb36a294c73de8868bf218d40a94181609e3264ad4579a59be book 4,981,476 131,001,841 42-61 9bf8ec8604f334c1aa6c0efb52a662ec8d01462b971143d524f1e1ed0fbb650e last_trade_price 68,526 3,963,785 62-62 778c6e4327f596fb988e77c0310a9b0e4b97e2ccc482c2e4ad4850f08199c113 market_resolved 15,420 333,623 63-63 d6f9e74e3c93ff614954e3531f4ce4e43d7b855dd7a985bc51bb8e4915ab8a22 new_market 19,383 557,156 64-64 deff169b94a2a57464dd4bc9686fca4912207e74efdae08cc339636043d927e4 price_change 107,787,076 1,159,252,803 65-476 636a2e1caa9d1e24e867867a5f381c6b4762e80eb332f2351b5db95494f8a407 tick_size_change 2,936 109,971 477-477 296968c6301ff6d42e73dd9f8a182a4a17a51e6aa823ed1c55ea464dca304d3a EVENT MIX count share price_change 107,787,076 87.15% best_bid_ask 10,811,424 8.74% book 4,981,476 4.03% last_trade_price 68,526 0.06% new_market 19,383 0.02% market_resolved 15,420 0.01% tick_size_change 2,936 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,811,553 10,811,424 129 12,327 FULL book 4,991,787 4,981,476 10,311 175,197 FULL last_trade_price 68,526 68,526 0 1,288 FULL market_resolved 15,426 15,420 6 981 FULL new_market 19,453 19,383 70 787 FULL price_change 107,788,128 107,787,076 1,052 10,422 FULL tick_size_change 2,936 2,936 0 377 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,296,495 8,893,798 6ms 20ms 205ms 7.5s 0 transport_latency_assumed best_bid_ask e 10,801,214 12,993 45ms 71ms 452ms 27.0s 0 transport_latency_assumed best_bid_ask f 10,384,457 9,083 49ms 74ms 442ms 25.4s 0 transport_latency_assumed best_bid_ask h 10,809,466 655,386 19ms 35ms 387ms 1.1min 0 transport_latency_assumed best_bid_ask i 10,711,505 265,382 22ms 47ms 850ms 17.4s 0 transport_latency_assumed best_bid_ask j 5,040,236 974,782 10ms 18ms 96ms 2.9s 0 transport_latency_assumed book c 517,840 253,849 2.3min 2.0d 38.0d 115.7d 0 book_staleness book e 153,730 7,609 60ms 16.4s 5.9d 115.7d 0 book_staleness book f 499,814 121,523 3.1min 1.9d 38.0d 115.7d 0 book_staleness book h 141,864 10,324 23ms 108ms 3.7s 97.2d 0 book_staleness book i 201,224 49,326 153ms 27.3min 13.8d 114.1d 0 book_staleness book j 4,707,019 4,538,845 10.0min 3.9d 44.8d 115.7d 0 book_staleness last_trade_price c 64,688 54,793 7ms 32ms 276ms 4.0s 0 transport_latency_assumed last_trade_price e 66,108 187 54ms 1.7s 11.4s 26.8s 0 transport_latency_assumed last_trade_price f 63,383 92 58ms 1.3s 10.6s 25.5s 0 transport_latency_assumed last_trade_price h 68,423 4,905 20ms 70ms 666ms 55.3s 0 transport_latency_assumed last_trade_price i 62,541 1,305 25ms 841ms 7.0s 17.3s 0 transport_latency_assumed last_trade_price j 31,355 7,244 11ms 27ms 167ms 1.2s 0 transport_latency_assumed market_resolved c 798 632 6ms 44.4s 6.1min 6.2min 0 transport_latency_assumed market_resolved e 789 19 47ms 13.1s 39.9s 56.8s 0 transport_latency_assumed market_resolved f 770 23 51ms 37.4s 4.6min 5.9min 0 transport_latency_assumed market_resolved h 789 133 20ms 12.9s 37.8s 57.1s 0 transport_latency_assumed market_resolved i 781 20 22ms 26.1s 49.8s 1.4min 0 transport_latency_assumed market_resolved j 14,985 14,593 55.9min 1.7h 2.1h 2.2h 0 transport_latency_assumed new_market c 2,170 610 119ms 36.5s 2.5min 51.6min 0 transport_latency_assumed new_market e 2,167 222 225ms 29.4s 2.2min 3.0min 0 transport_latency_assumed new_market f 2,179 316 220ms 32.8s 2.8min 4.6min 0 transport_latency_assumed new_market h 2,167 347 186ms 31.8s 2.2min 3.0min 0 transport_latency_assumed new_market i 2,167 339 149ms 27.6s 2.6min 2.8min 0 transport_latency_assumed new_market j 19,109 17,549 23.0min 1.5h 2.0h 2.2h 0 transport_latency_assumed price_change c 102,704,126 88,081,235 6ms 23ms 218ms 7.7s 0 transport_latency_assumed price_change e 107,184,910 166,688 46ms 109ms 3.8s 27.0s 0 transport_latency_assumed price_change f 102,983,509 104,090 50ms 110ms 3.3s 25.7s 0 transport_latency_assumed price_change h 107,736,736 6,812,276 19ms 40ms 433ms 1.1min 0 transport_latency_assumed price_change i 105,218,566 2,445,670 23ms 78ms 2.7s 17.4s 0 transport_latency_assumed price_change j 50,210,762 10,177,117 10ms 20ms 108ms 3.1s 0 transport_latency_assumed tick_size_change c 2,864 2,515 6ms 17ms 180ms 309ms 0 transport_latency_assumed tick_size_change e 2,936 4 45ms 69ms 273ms 545ms 0 transport_latency_assumed tick_size_change f 2,828 not meas. 49ms 66ms 303ms 635ms 0 transport_latency_assumed tick_size_change h 2,936 119 19ms 34ms 242ms 5.5s 0 transport_latency_assumed tick_size_change i 2,888 50 22ms 50ms 1.2s 4.0s 0 transport_latency_assumed tick_size_change j 1,560 248 10ms 16ms 39ms 119ms 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-22/14/2026-09-22T14.parquet sha256sum 2026-09-22T14.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.