Hour audit: 2026-09-18T03
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-18T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T03:00:00.000003982+00:00 · last event 2026-09-18T03:59:59.999746747+00:00
VOLUME 113,133,812 rows · 1,172,901,828 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 112,663,402 · h: 112,648,019 · g: 112,608,660 · e: 112,385,114 · f: 108,365,575 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,583,774 (95.09%) · h: 4,752,507 (4.20%) · g: 14,118 (0.01%) · e: 233,273 (0.21%) · f: 550,140 (0.49%) (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 113,133,812 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a6db4f237f68789cc4027f2d85079d83ef45df2fa76a02e96427068982923793
the corpus checksum ledger names this file with the same digest
joined 113,136,799 to merged 113,133,812, minus 2,987 (minus 0.0026%)
boundary drops 2,987 · 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-18T04:59:06Z 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,907,375 120,566,723 0-41 716c62716098a76806d79ebfb89be90ac389eff18502382255d806d225ee47ff book 535,116 55,835,758 42-44 d10f18532f61eaa57d14c59fed2158bb9e419880d8cf38c5e9d3eead22991ab2 last_trade_price 52,476 2,934,475 45-45 9500f7e0cedc8de3d48b02c67b1c0c32900f2b371cb2156ac32a81514cb9a27c market_resolved 1,017 156,422 46-46 fc1af154a7180ffd7f51c5439ea25ffc29093498af4bd31d23b3797a8b05902b new_market 600 63,876 47-47 b0adb635b702418ccfb73b03bdc2e4869e6dc6a6804c4ca0f721330372c6fb97 price_change 101,633,724 991,927,711 48-435 d7649ac6e50e8ea5839d583593c05045d639d937b1f85fedb0eefe1dad98bec5 tick_size_change 3,504 127,343 436-436 8c539b8090439f0b758b1a8b755df8c97004db073e63255880a086b3e40a8527 EVENT MIX count share price_change 101,633,724 89.83% best_bid_ask 10,907,375 9.64% book 535,116 0.47% last_trade_price 52,476 0.05% tick_size_change 3,504 <0.01% market_resolved 1,017 <0.01% new_market 600 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,907,617 10,907,375 242 389 FULL book 535,132 535,116 16 185,302 FULL last_trade_price 52,477 52,476 1 73 FULL market_resolved 1,017 1,017 0 40 FULL new_market 600 600 0 0 FULL price_change 101,636,452 101,633,724 2,728 327 FULL tick_size_change 3,504 3,504 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,906,053 10,465,090 5ms 10ms 69ms 6.5s 0 transport_latency_assumed best_bid_ask e 10,893,347 16,789 44ms 50ms 121ms 8.5s 0 transport_latency_assumed best_bid_ask f 10,448,606 10,602 47ms 55ms 135ms 4.3s 0 transport_latency_assumed best_bid_ask g 10,905,216 858 81ms 98ms 187ms 7.8s 0 transport_latency_assumed best_bid_ask h 10,906,392 414,036 18ms 25ms 83ms 13.7s 0 transport_latency_assumed book c 117,585 108,565 6ms 93ms 8.3h 92.7d 0 book_staleness book e 116,740 10,482 46ms 424ms 32.1min 89.7d 0 book_staleness book f 511,800 404,567 2.3min 7.5h 36.3d 111.2d 0 book_staleness book g 112,498 2,640 84ms 206ms 27.6min 61.7d 0 book_staleness book h 111,344 8,862 20ms 52ms 6.9min 92.6d 0 book_staleness last_trade_price c 52,037 48,740 10ms 44ms 235ms 5.0s 0 transport_latency_assumed last_trade_price e 51,280 271 50ms 103ms 761ms 8.1s 0 transport_latency_assumed last_trade_price f 50,785 221 54ms 108ms 410ms 5.0s 0 transport_latency_assumed last_trade_price g 52,093 34 91ms 185ms 942ms 7.9s 0 transport_latency_assumed last_trade_price h 52,318 3,210 23ms 63ms 241ms 5.0s 0 transport_latency_assumed market_resolved c 976 920 5ms 15ms 54.5s 57.3s 0 transport_latency_assumed market_resolved e 976 1 47ms 184ms 45.4s 1.0min 0 transport_latency_assumed market_resolved f 937 28 69ms 167ms 351ms 6.3min 0 transport_latency_assumed market_resolved g 976 not meas. 99ms 329ms 52.9s 55.7s 0 transport_latency_assumed market_resolved h 976 68 30ms 72ms 1.0min 1.0min 0 transport_latency_assumed new_market c 413 263 62ms 13.3s 56.4s 1.1min 0 transport_latency_assumed new_market e 413 80 97ms 13.9s 57.1s 1.0min 0 transport_latency_assumed new_market f 413 68 106ms 19.3s 60.0s 2.2min 0 transport_latency_assumed new_market g 413 32 129ms 13.1s 46.2s 58.2s 0 transport_latency_assumed new_market h 413 157 70ms 26.2s 50.9s 1.9min 0 transport_latency_assumed price_change c 101,582,834 96,956,824 5ms 11ms 84ms 6.5s 0 transport_latency_assumed price_change e 101,318,854 205,634 44ms 53ms 166ms 8.5s 0 transport_latency_assumed price_change f 97,349,634 134,650 48ms 58ms 182ms 4.5s 0 transport_latency_assumed price_change g 101,533,960 10,554 82ms 101ms 263ms 8.7s 0 transport_latency_assumed price_change h 101,573,072 4,326,062 18ms 28ms 102ms 14.7s 0 transport_latency_assumed tick_size_change c 3,504 3,372 5ms 9ms 86ms 331ms 0 transport_latency_assumed tick_size_change e 3,504 16 44ms 49ms 191ms 449ms 0 transport_latency_assumed tick_size_change f 3,400 4 48ms 62ms 443ms 693ms 0 transport_latency_assumed tick_size_change g 3,504 not meas. 81ms 99ms 330ms 538ms 0 transport_latency_assumed tick_size_change h 3,504 112 18ms 27ms 114ms 1.3s 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-18/03/2026-09-18T03.parquet sha256sum 2026-09-18T03.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.