Hour audit: 2026-09-16T05
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-16T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T05:00:00.000008915+00:00 · last event 2026-09-16T05:59:59.999990727+00:00
VOLUME 107,577,276 rows · 1,093,155,604 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 107,211,742 · e: 107,142,476 · f: 107,134,905 · h: 107,125,473 · g: 107,116,170 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,053,846 (95.80%) · e: 490,308 (0.46%) · f: 206,437 (0.19%) · h: 3,684,883 (3.43%) · g: 141,802 (0.13%) (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 107,577,276 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9d1504d84da420879aaf8bc9114fd4238e018693a8042c3bd57add0f701ac179
the corpus checksum ledger names this file with the same digest
joined 107,615,395 to merged 107,577,276, minus 38,119 (minus 0.0354%)
boundary drops 38,119 · 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-16T06:57:45Z 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,198,450 135,408,855 0-46 d23ea210ca8a340caa06b8c8c7804e5b8490503339fdff4476c58fb80a470256 book 498,802 46,356,372 47-48 75f26b6ef8c87473f723c0354660b154679ecc56d6d6e2badd3f2dbcc56ac3b0 last_trade_price 44,216 2,515,406 49-49 73ab0d5b65b2e4bbbd01c748bf687c458f659fa13a337e07ce932fed3be1eeb1 market_resolved 1,051 166,438 50-50 f260b5ed0d2d964ad1e926af07e80a80cd3134c5fc356c057ae8404d91474eaa new_market 1,819 179,030 51-51 4584d1dc7705c8bcd9413d32979893316aea5cd057b2ba9d51cf6ea50af9fa4c price_change 94,829,638 907,189,074 52-413 f4c72df9828cd0fce10fe86c4a969b9a6b84ba0cf090a01ddc90d0d0c330aed0 tick_size_change 3,300 116,761 414-414 4877445657f73b5e42513d437d2a51ab1b4c04a7555b0fae2f1513172e1ad8fc EVENT MIX count share price_change 94,829,638 88.15% best_bid_ask 12,198,450 11.34% book 498,802 0.46% last_trade_price 44,216 0.04% tick_size_change 3,300 <0.01% new_market 1,819 <0.01% market_resolved 1,051 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,199,524 12,198,450 1,074 150 FULL book 499,251 498,802 449 132,764 FULL last_trade_price 44,226 44,216 10 0 FULL market_resolved 1,051 1,051 0 1 FULL new_market 1,819 1,819 0 0 FULL price_change 94,866,224 94,829,638 36,586 117 FULL tick_size_change 3,300 3,300 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,196,946 11,755,222 4ms 9ms 90ms 4.7s 0 transport_latency_assumed best_bid_ask e 12,195,198 43,509 37ms 44ms 169ms 15.5s 0 transport_latency_assumed best_bid_ask f 12,194,829 13,794 47ms 55ms 184ms 8.1s 0 transport_latency_assumed best_bid_ask g 12,191,731 1,406 79ms 107ms 381ms 24.2s 0 transport_latency_assumed best_bid_ask h 12,193,476 384,519 18ms 24ms 137ms 38.5s 0 transport_latency_assumed book c 178,170 158,500 92ms 28.9min 24.7d 109.3d 0 book_staleness book e 167,437 66,477 189ms 25.8min 24.6d 109.3d 0 book_staleness book f 171,549 69,309 186ms 28.0min 24.6d 90.8d 0 book_staleness book g 240,948 125,922 32.8s 1.5h 24.7d 109.3d 0 book_staleness book h 175,684 78,594 156ms 27.3min 24.6d 109.3d 0 book_staleness last_trade_price c 44,045 41,685 10ms 48ms 217ms 4.9s 0 transport_latency_assumed last_trade_price e 43,812 365 45ms 154ms 4.5s 15.6s 0 transport_latency_assumed last_trade_price f 43,732 142 55ms 130ms 798ms 8.1s 0 transport_latency_assumed last_trade_price g 43,334 39 93ms 265ms 2.4s 23.7s 0 transport_latency_assumed last_trade_price h 43,681 1,985 24ms 76ms 398ms 8.1s 0 transport_latency_assumed market_resolved c 1,026 983 5ms 21ms 48.5s 51.5s 0 transport_latency_assumed market_resolved e 1,026 8 79ms 186ms 420ms 803ms 0 transport_latency_assumed market_resolved f 1,026 3 97ms 196ms 429ms 946ms 0 transport_latency_assumed market_resolved g 1,026 not meas. 143ms 351ms 1.3s 1.0min 0 transport_latency_assumed market_resolved h 1,025 57 27ms 74ms 314ms 1.1s 0 transport_latency_assumed new_market c 1,157 685 90ms 32.0s 1.3min 1.5min 0 transport_latency_assumed new_market e 1,157 218 171ms 30.6s 1.3min 1.8min 0 transport_latency_assumed new_market f 1,157 285 179ms 36.7s 1.2min 1.4min 0 transport_latency_assumed new_market g 1,157 155 285ms 27.6s 1.2min 1.5min 0 transport_latency_assumed new_market h 1,157 476 132ms 29.8s 1.2min 1.4min 0 transport_latency_assumed price_change c 94,787,098 91,093,562 5ms 11ms 100ms 5.7s 0 transport_latency_assumed price_change e 94,730,550 379,730 37ms 50ms 286ms 15.6s 0 transport_latency_assumed price_change f 94,719,312 122,904 47ms 61ms 274ms 8.2s 0 transport_latency_assumed price_change g 94,634,678 14,280 80ms 125ms 565ms 24.2s 0 transport_latency_assumed price_change h 94,707,150 3,219,162 18ms 28ms 169ms 43.0s 0 transport_latency_assumed tick_size_change c 3,300 3,209 4ms 8ms 36ms 115ms 0 transport_latency_assumed tick_size_change e 3,296 1 37ms 42ms 118ms 201ms 0 transport_latency_assumed tick_size_change f 3,300 not meas. 47ms 53ms 126ms 354ms 0 transport_latency_assumed tick_size_change g 3,296 not meas. 78ms 136ms 670ms 16.4s 0 transport_latency_assumed tick_size_change h 3,300 90 18ms 20ms 47ms 1.0s 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/05/2026-09-16T05.parquet sha256sum 2026-09-16T05.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.