Hour audit: 2026-09-19T03
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-19T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T03:00:00.000008772+00:00 · last event 2026-09-19T03:59:59.999893383+00:00
VOLUME 112,874,772 rows · 1,159,726,916 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 112,390,618 · c: 112,378,144 · e: 112,338,587 · g: 112,226,689 · f: 107,297,507 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,374,252 (3.88%) · c: 107,461,483 (95.20%) · e: 426,548 (0.38%) · g: 18,652 (0.02%) · f: 593,837 (0.53%) (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 112,874,772 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8ef3272c068c3f97fd98150b55e37d624129092b567ce7f7ebf28197b75ea0c2
the corpus checksum ledger names this file with the same digest
joined 112,877,942 to merged 112,874,772, minus 3,170 (minus 0.0028%)
boundary drops 3,170 · 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-19T05:08:08Z 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,243,974 131,901,156 0-46 f69585f5985a307ce57dfe1a61b1a813c84b29ab7146c96d505b4dc1074ef313 book 531,041 53,527,893 47-49 d13605fc6994b53fbd28b0b7bf451c3392443608f389699e8a613d7e04a1420a last_trade_price 46,326 2,660,659 50-50 d388fcf185bd6273ad153eb02cf753d6e4f87c77a3428d087c42f186facd6ba4 market_resolved 3,001 464,265 51-51 405878ad9b55ba3891d019d1797b650c89017892c58b4446f15912326028e634 new_market 987 106,282 52-52 11e8f57ac69537512ed682b48f347287b35471158baf21e5d060cbb883f8e217 price_change 100,044,823 969,614,822 53-434 fb600d879e9059efa6d20251eb7efe7a0f9f57b7821717f08a508d5b255eaefe tick_size_change 4,620 165,988 435-435 2eaf3f602b6f22ab1e7d5e410bac15dc562294ea8cda1dc02a1e05b46ccc3ca4 EVENT MIX count share price_change 100,044,823 88.63% best_bid_ask 12,243,974 10.85% book 531,041 0.47% last_trade_price 46,326 0.04% tick_size_change 4,620 <0.01% market_resolved 3,001 <0.01% new_market 987 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,244,259 12,243,974 285 507 FULL book 531,055 531,041 14 206,326 FULL last_trade_price 46,327 46,326 1 106 FULL market_resolved 3,001 3,001 0 0 FULL new_market 987 987 0 0 FULL price_change 100,047,693 100,044,823 2,870 293 FULL tick_size_change 4,620 4,620 0 20 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,243,160 11,759,758 4ms 9ms 86ms 3.2s 0 transport_latency_assumed best_bid_ask e 12,242,139 41,874 39ms 45ms 136ms 13.6s 0 transport_latency_assumed best_bid_ask f 11,682,151 14,869 47ms 55ms 164ms 11.6s 0 transport_latency_assumed best_bid_ask g 12,240,434 1,350 80ms 95ms 264ms 46.5s 0 transport_latency_assumed best_bid_ask h 12,242,649 426,123 17ms 30ms 119ms 9.6s 0 transport_latency_assumed book c 101,050 92,322 6ms 48ms 11.7h 93.6d 0 book_staleness book e 101,387 3,502 41ms 239ms 11.6h 93.7d 0 book_staleness book f 518,189 422,794 11.4min 11.6h 34.4d 112.2d 0 book_staleness book g 102,964 4,092 83ms 998ms 12.0h 93.6d 0 book_staleness book h 100,357 8,331 20ms 76ms 7.0h 93.7d 0 book_staleness last_trade_price c 46,120 43,204 10ms 48ms 254ms 5.0s 0 transport_latency_assumed last_trade_price e 46,083 303 46ms 121ms 3.0s 13.6s 0 transport_latency_assumed last_trade_price f 44,118 155 54ms 137ms 3.4s 11.6s 0 transport_latency_assumed last_trade_price g 45,763 12 91ms 206ms 7.4s 36.6s 0 transport_latency_assumed last_trade_price h 46,172 2,652 23ms 70ms 352ms 5.0s 0 transport_latency_assumed market_resolved c 2,807 2,720 4ms 11ms 81ms 306ms 0 transport_latency_assumed market_resolved e 2,807 11 61ms 142ms 359ms 59.5s 0 transport_latency_assumed market_resolved f 2,832 191 99ms 214ms 5.5min 5.8min 0 transport_latency_assumed market_resolved g 2,807 not meas. 94ms 240ms 558ms 1.3s 0 transport_latency_assumed market_resolved h 2,807 79 32ms 63ms 184ms 1.0min 0 transport_latency_assumed new_market c 705 481 61ms 43.5s 1.7min 4.9min 0 transport_latency_assumed new_market e 705 86 138ms 22.3s 1.5min 1.8min 0 transport_latency_assumed new_market f 705 84 137ms 17.1s 1.4min 1.8min 0 transport_latency_assumed new_market g 705 52 212ms 17.1s 1.5min 1.8min 0 transport_latency_assumed new_market h 705 284 102ms 33.5s 1.6min 1.8min 0 transport_latency_assumed price_change c 99,979,682 95,558,540 4ms 11ms 102ms 5.2s 0 transport_latency_assumed price_change e 99,940,846 380,749 39ms 49ms 226ms 13.6s 0 transport_latency_assumed price_change f 95,044,972 155,732 47ms 60ms 250ms 11.6s 0 transport_latency_assumed price_change g 99,829,396 13,146 80ms 100ms 400ms 46.5s 0 transport_latency_assumed price_change h 99,993,308 3,936,656 17ms 33ms 152ms 9.6s 0 transport_latency_assumed tick_size_change c 4,620 4,458 4ms 9ms 69ms 117ms 0 transport_latency_assumed tick_size_change e 4,620 23 39ms 45ms 114ms 333ms 0 transport_latency_assumed tick_size_change f 4,540 12 47ms 54ms 144ms 252ms 0 transport_latency_assumed tick_size_change g 4,620 not meas. 80ms 96ms 251ms 1.5s 0 transport_latency_assumed tick_size_change h 4,620 127 17ms 40ms 89ms 234ms 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/03/2026-09-19T03.parquet sha256sum 2026-09-19T03.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.