Hour audit: 2026-09-19T02
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-19T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T02:00:00.000156463+00:00 · last event 2026-09-19T02:59:59.999875886+00:00
VOLUME 118,058,585 rows · 1,230,141,855 bytes (1.15 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,588,537 · c: 117,585,434 · e: 117,535,974 · g: 117,466,709 · f: 112,166,181 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,844,600 (4.10%) · c: 112,090,627 (94.94%) · e: 434,458 (0.37%) · g: 30,624 (0.03%) · f: 658,276 (0.56%) (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 118,058,585 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 64aaf8691837101924e4e411cf6b3fb38af691a55f966a291102814c00292e7a
the corpus checksum ledger names this file with the same digest
joined 118,069,478 to merged 118,058,585, minus 10,893 (minus 0.0092%)
boundary drops 10,893 · 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-19T04:42:25Z 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 12,783,828 139,042,056 0-48 8dc0a6bb4a8520c86e18a4ba8eaf5787f948c1153e735e66c52f4477ef207078 book 533,695 53,887,198 49-51 c3783f6dac38af5969945d43c6bf50a3f05c48c602ec49bd8dd1312255acc093 last_trade_price 48,117 2,767,952 52-52 41a699970f43ae52a1b6e6eac4c7fb863b3516810c37f78bdb56dbaa60d942bb market_resolved 1,914 274,061 53-53 57f43c1e99a8bfd7fefda4d06e2f45b6bf007d199f03aa320e7d2505197c2628 new_market 1,041 110,808 54-54 09e2809ed879057e20fa37762958300234b0b8c6019ec8c85e651ee4cf287451 price_change 104,685,950 1,032,570,591 55-454 85a6f03d31232da5baf3cc57184e9b6d23b744dced973aa5718eb0ec84d38713 tick_size_change 4,040 144,466 455-455 fd15983ff03330778a4e69e458389f37016d0b13bdf5b628c3a348ce58f71800 EVENT MIX count share price_change 104,685,950 88.67% best_bid_ask 12,783,828 10.83% book 533,695 0.45% last_trade_price 48,117 0.04% tick_size_change 4,040 <0.01% market_resolved 1,914 <0.01% new_market 1,041 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,785,038 12,783,828 1,210 629 FULL book 533,846 533,695 151 207,211 FULL last_trade_price 48,119 48,117 2 77 FULL market_resolved 1,914 1,914 0 3 FULL new_market 1,043 1,041 2 2 FULL price_change 104,695,478 104,685,950 9,528 323 FULL tick_size_change 4,040 4,040 0 27 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,782,612 12,237,247 4ms 11ms 95ms 11.7s 0 transport_latency_assumed best_bid_ask e 12,781,612 41,078 42ms 50ms 164ms 8.8s 0 transport_latency_assumed best_bid_ask f 12,146,049 21,398 47ms 58ms 183ms 7.8s 0 transport_latency_assumed best_bid_ask g 12,780,795 2,185 80ms 97ms 298ms 16.1s 0 transport_latency_assumed best_bid_ask h 12,782,910 481,920 18ms 33ms 139ms 13.2s 0 transport_latency_assumed book c 104,832 94,821 6ms 62ms 10.8h 93.7d 0 book_staleness book e 104,598 2,739 44ms 199ms 10.4h 112.2d 0 book_staleness book f 520,850 423,442 11.0min 10.7h 32.8d 112.2d 0 book_staleness book g 107,255 4,366 84ms 544ms 11.0h 93.7d 0 book_staleness book h 102,810 8,327 21ms 77ms 1.6h 93.6d 0 book_staleness last_trade_price c 47,779 44,482 10ms 53ms 305ms 4.9s 0 transport_latency_assumed last_trade_price e 47,809 261 49ms 133ms 1.6s 8.8s 0 transport_latency_assumed last_trade_price f 45,606 287 55ms 143ms 1.1s 7.8s 0 transport_latency_assumed last_trade_price g 47,566 42 90ms 204ms 1.7s 16.1s 0 transport_latency_assumed last_trade_price h 47,856 3,045 24ms 78ms 380ms 6.9s 0 transport_latency_assumed market_resolved c 1,698 1,632 5ms 14ms 137ms 6.5s 0 transport_latency_assumed market_resolved e 1,698 10 53ms 132ms 400ms 51.1s 0 transport_latency_assumed market_resolved f 1,733 217 101ms 4.3min 6.3min 6.3min 0 transport_latency_assumed market_resolved g 1,698 not meas. 93ms 246ms 594ms 1.0min 0 transport_latency_assumed market_resolved h 1,698 55 31ms 70ms 206ms 50.9s 0 transport_latency_assumed new_market c 719 505 60ms 13.0s 1.1min 3.8min 0 transport_latency_assumed new_market e 721 138 138ms 26.7s 1.0min 4.6min 0 transport_latency_assumed new_market f 723 116 147ms 13.6s 2.3min 6.2min 0 transport_latency_assumed new_market g 721 49 216ms 17.8s 1.1min 1.7min 0 transport_latency_assumed new_market h 721 233 109ms 19.9s 1.1min 4.3min 0 transport_latency_assumed price_change c 104,643,754 99,708,042 5ms 13ms 112ms 18.8s 0 transport_latency_assumed price_change e 104,595,496 390,232 42ms 56ms 242ms 8.8s 0 transport_latency_assumed price_change f 99,447,288 212,812 47ms 64ms 271ms 7.9s 0 transport_latency_assumed price_change g 104,524,634 23,982 80ms 103ms 409ms 16.1s 0 transport_latency_assumed price_change h 104,648,502 4,350,882 18ms 36ms 171ms 13.3s 0 transport_latency_assumed tick_size_change c 4,040 3,898 5ms 9ms 54ms 157ms 0 transport_latency_assumed tick_size_change e 4,040 not meas. 41ms 46ms 90ms 411ms 0 transport_latency_assumed tick_size_change f 3,932 4 47ms 52ms 100ms 183ms 0 transport_latency_assumed tick_size_change g 4,040 not meas. 80ms 93ms 176ms 302ms 0 transport_latency_assumed tick_size_change h 4,040 138 18ms 30ms 64ms 333ms 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-19/02/2026-09-19T02.parquet sha256sum 2026-09-19T02.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.