Hour audit: 2026-09-16T07
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-16T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T07:00:00.000018964+00:00 · last event 2026-09-16T07:59:59.999986145+00:00
VOLUME 109,556,214 rows · 1,131,432,041 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 109,167,800 · c: 109,014,253 · h: 108,970,584 · g: 108,898,407 · e: 105,703,212 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 299,100 (0.27%) · c: 104,593,499 (95.47%) · h: 3,968,288 (3.62%) · g: 37,476 (0.03%) · e: 657,851 (0.60%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,556,214 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 45689ebfc2ce4e63bc9377f8337f139e0207b7c2ad4221b2ba3fdcb4123869e9
the corpus checksum ledger names this file with the same digest
joined 109,558,762 to merged 109,556,214, minus 2,548 (minus 0.0023%)
boundary drops 2,548 · 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-16T08:58:31Z 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,430,829 128,978,990 0-43 81e7de9bca26659f7aec970f2a63874618bf3e265949d0a574475fd0e71e573a book 609,773 55,025,314 44-46 1c214869ae2d53a563899918d2cecda03e30483c8107a8d0e0500c63282eed05 last_trade_price 47,482 2,665,523 47-47 5c61dadc4afd0e1019171cdd1251b1e0d306e32a9abb48812ebda8e410858b5e market_resolved 483 79,081 48-48 045ccdd1f984a5b2730bca8bb0420a0071c066bd601df58c50046946aedff9ae new_market 589 68,517 49-49 87f6aec3bb0e910cffa7fedfb076f702d2b608c4f74e73304f5d91361d21ce3f price_change 97,464,786 943,285,403 50-421 22317dec74ebf359af05d10895c47c94b4ea666896b7a51818cc5e76ba6e6fff tick_size_change 2,272 81,247 422-422 d719b18122ce95d68753e93378977e8cb2b68f2fb2cef34d7c13b147819a05ac EVENT MIX count share price_change 97,464,786 88.96% best_bid_ask 11,430,829 10.43% book 609,773 0.56% last_trade_price 47,482 0.04% tick_size_change 2,272 <0.01% new_market 589 <0.01% market_resolved 483 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,431,081 11,430,829 252 396 FULL book 610,341 609,773 568 172,116 FULL last_trade_price 47,484 47,482 2 57 FULL market_resolved 483 483 0 18 FULL new_market 589 589 0 0 FULL price_change 97,466,512 97,464,786 1,726 171 FULL tick_size_change 2,272 2,272 0 5 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,430,157 10,998,180 5ms 10ms 69ms 2.8s 0 transport_latency_assumed best_bid_ask e 11,038,266 29,717 37ms 43ms 120ms 6.1s 0 transport_latency_assumed best_bid_ask f 11,423,920 9,314 46ms 55ms 162ms 5.1s 0 transport_latency_assumed best_bid_ask g 11,426,804 793 81ms 112ms 317ms 23.9s 0 transport_latency_assumed best_bid_ask h 11,428,328 392,825 17ms 24ms 93ms 14.2s 0 transport_latency_assumed book c 101,071 94,766 6ms 32ms 14.0min 109.4d 0 book_staleness book e 448,392 300,661 2.5min 13.7h 35.5d 109.4d 0 book_staleness book f 377,732 183,247 1.9min 11.9h 34.5d 109.4d 0 book_staleness book g 128,854 22,267 98ms 10.6min 10.7d 109.4d 0 book_staleness book h 103,076 8,832 21ms 140ms 25.2min 90.9d 0 book_staleness last_trade_price c 47,308 44,773 10ms 47ms 231ms 5.0s 0 transport_latency_assumed last_trade_price e 45,481 483 45ms 117ms 590ms 6.2s 0 transport_latency_assumed last_trade_price f 47,263 218 54ms 140ms 792ms 5.1s 0 transport_latency_assumed last_trade_price g 47,098 50 96ms 318ms 6.1s 13.9s 0 transport_latency_assumed last_trade_price h 47,105 1,958 24ms 87ms 464ms 12.3s 0 transport_latency_assumed market_resolved c 483 467 5ms 13ms 52ms 111ms 0 transport_latency_assumed market_resolved e 465 3 38ms 170ms 479ms 560ms 0 transport_latency_assumed market_resolved f 483 not meas. 48ms 188ms 439ms 683ms 0 transport_latency_assumed market_resolved g 483 not meas. 88ms 328ms 807ms 1.3s 0 transport_latency_assumed market_resolved h 483 13 18ms 72ms 178ms 297ms 0 transport_latency_assumed new_market c 452 241 58ms 417ms 19.5s 55.4s 0 transport_latency_assumed new_market e 452 43 120ms 398ms 19.9s 54.1s 0 transport_latency_assumed new_market f 452 93 159ms 13.1s 23.2s 54.7s 0 transport_latency_assumed new_market g 452 32 319ms 17.3s 45.5s 1.3min 0 transport_latency_assumed new_market h 452 180 66ms 339ms 19.2s 1.1min 0 transport_latency_assumed price_change c 97,432,510 93,452,968 5ms 11ms 80ms 3.8s 0 transport_latency_assumed price_change e 94,167,904 326,916 37ms 47ms 197ms 7.0s 0 transport_latency_assumed price_change f 97,315,678 106,228 46ms 60ms 261ms 5.2s 0 transport_latency_assumed price_change g 97,292,444 14,334 82ms 136ms 608ms 23.9s 0 transport_latency_assumed price_change h 97,388,868 3,564,340 18ms 28ms 142ms 14.3s 0 transport_latency_assumed tick_size_change c 2,272 2,104 5ms 18ms 68ms 377ms 0 transport_latency_assumed tick_size_change e 2,252 28 37ms 43ms 132ms 217ms 0 transport_latency_assumed tick_size_change f 2,272 not meas. 46ms 62ms 161ms 294ms 0 transport_latency_assumed tick_size_change g 2,272 not meas. 79ms 98ms 355ms 445ms 0 transport_latency_assumed tick_size_change h 2,272 140 18ms 25ms 73ms 113ms 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-16/07/2026-09-16T07.parquet sha256sum 2026-09-16T07.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.