Hour audit: 2026-09-13T02
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-13T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T02:00:00.000026157+00:00 · last event 2026-09-13T02:59:59.999601562+00:00
VOLUME 114,561,915 rows · 1,228,385,717 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 112,922,581 · h: 112,918,754 · f: 112,915,878 · e: 112,885,035 · c: 95,178,344 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 40,135 (0.04%) · h: 20,499,360 (17.89%) · f: 262,850 (0.23%) · e: 998,778 (0.87%) · c: 92,760,792 (80.97%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,561,915 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7f769651c2891ac5c76a4fb73b23023a15910b68d7be422a998f78268276b7be
the corpus checksum ledger names this file with the same digest
joined 114,569,817 to merged 114,561,915, minus 7,902 (minus 0.0069%)
boundary drops 7,902 · 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-13T04:05:01Z 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,906,380 129,013,996 0-45 e6def38072183f2c947fe78937aefcd666878c9c8b8c5fae000a8406a182fc74 book 1,727,967 80,558,436 46-52 1adfaefd2891ab203e8809bd7694564bf8ba3cdacc9be30373343cbe7084f67a last_trade_price 39,438 2,339,695 53-53 3b551d65d6fa28f8c47f25416d584270013499d63f17d70042fd40ec70710347 market_resolved 4,815 628,372 54-54 29234dadcd7a4783ffc262ca4b41417caeb2a6b6949270e530d538fc42fb3d75 new_market 1,241 122,634 55-55 c797f029fb390a29bcaaf34467c79d45238f0abf0d36debd9662b549723d18ee price_change 100,873,326 1,014,101,125 56-440 f2d2611b5bb05440f482cbc30a4583209154993a6c3d1f430f9d5258ae17fd8a tick_size_change 8,748 317,945 441-441 87e8d7b9cbe97549793ba5924a10c0c164a2dff700838728dd395147f4f65432 EVENT MIX count share price_change 100,873,326 88.05% best_bid_ask 11,906,380 10.39% book 1,727,967 1.51% last_trade_price 39,438 0.03% tick_size_change 8,748 <0.01% market_resolved 4,815 <0.01% new_market 1,241 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,906,612 11,906,380 232 2,696 FULL book 1,731,945 1,727,967 3,978 182,771 FULL last_trade_price 39,440 39,438 2 314 FULL market_resolved 4,815 4,815 0 338 FULL new_market 1,267 1,241 26 32 FULL price_change 100,876,990 100,873,326 3,664 1,703 FULL tick_size_change 8,748 8,748 0 242 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,917,572 9,671,048 4ms 8ms 57ms 10.0s 0 transport_latency_assumed best_bid_ask e 11,903,681 100,444 40ms 45ms 120ms 19.1s 0 transport_latency_assumed best_bid_ask f 11,904,207 24,203 46ms 50ms 137ms 19.0s 0 transport_latency_assumed best_bid_ask g 11,902,277 2,374 77ms 91ms 288ms 10.0s 0 transport_latency_assumed best_bid_ask h 11,905,114 2,108,311 18ms 21ms 124ms 42.5s 0 transport_latency_assumed book c 1,684,515 1,673,287 33.3min 1.4d 35.3d 106.2d 0 book_staleness book e 90,291 4,384 43ms 831ms 1.4d 87.7d 0 book_staleness book f 107,383 8,139 49ms 1.8h 7.5d 106.2d 0 book_staleness book g 134,335 18,104 103ms 5.2h 21.1d 106.2d 0 book_staleness book h 106,001 24,053 22ms 1.3h 5.7d 98.4d 0 book_staleness last_trade_price c 31,561 30,351 10ms 41ms 183ms 5.0s 0 transport_latency_assumed last_trade_price e 39,115 541 47ms 98ms 537ms 5.0s 0 transport_latency_assumed last_trade_price f 39,237 213 52ms 103ms 364ms 5.1s 0 transport_latency_assumed last_trade_price g 39,256 7 89ms 207ms 1.4s 5.4s 0 transport_latency_assumed last_trade_price h 39,413 8,326 23ms 62ms 312ms 9.5s 0 transport_latency_assumed market_resolved c 4,155 4,103 5ms 5.3min 9.9min 11.6min 0 transport_latency_assumed market_resolved e 3,714 23 108ms 170ms 428ms 1.1min 0 transport_latency_assumed market_resolved f 3,714 21 111ms 162ms 364ms 50.2s 0 transport_latency_assumed market_resolved g 3,712 1 182ms 261ms 742ms 38.0s 0 transport_latency_assumed market_resolved h 3,714 667 36ms 64ms 405ms 1.1min 0 transport_latency_assumed new_market c 860 548 93ms 4.3min 3.8h 6.4h 0 transport_latency_assumed new_market e 782 196 155ms 18.6s 34.9s 3.2h 0 transport_latency_assumed new_market f 783 117 147ms 15.3s 28.7s 1.2h 0 transport_latency_assumed new_market g 783 97 287ms 17.7s 34.5s 35.0s 0 transport_latency_assumed new_market h 783 283 132ms 14.2s 29.3s 5.2min 0 transport_latency_assumed price_change c 83,531,901 81,373,838 5ms 9ms 62ms 14.1s 0 transport_latency_assumed price_change e 100,838,704 893,166 40ms 45ms 143ms 19.3s 0 transport_latency_assumed price_change f 100,851,806 230,157 46ms 52ms 161ms 21.9s 0 transport_latency_assumed price_change g 100,833,470 19,552 77ms 93ms 339ms 14.4s 0 transport_latency_assumed price_change h 100,854,981 18,356,613 18ms 23ms 136ms 42.5s 0 transport_latency_assumed tick_size_change c 7,780 7,617 4ms 8ms 38ms 410ms 0 transport_latency_assumed tick_size_change e 8,748 24 40ms 44ms 111ms 458ms 0 transport_latency_assumed tick_size_change f 8,748 not meas. 46ms 49ms 81ms 396ms 0 transport_latency_assumed tick_size_change g 8,748 not meas. 77ms 91ms 129ms 525ms 0 transport_latency_assumed tick_size_change h 8,748 1,107 18ms 21ms 63ms 277ms 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-13/02/2026-09-13T02.parquet sha256sum 2026-09-13T02.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.