Hour audit: 2026-09-24T09
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-24T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T09:00:00.000010129+00:00 · last event 2026-09-24T09:59:59.999959642+00:00
VOLUME 139,137,075 rows · 1,528,844,597 bytes (1.42 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 137,047,228 · i: 126,319,603 · g: 124,876,475 · k: 121,035,239 · c: 120,900,339 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,945,122 (4.99%) · i: 2,044,086 (1.47%) · g: 293,957 (0.21%) · k: 20,810,567 (14.96%) · c: 109,043,343 (78.37%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 139,137,075 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5d7e51f9f2e50a5967ec94359220dbc8c1849b8fc6b536d46e85a8dbf77a5018
the corpus checksum ledger names this file with the same digest
joined 139,139,855 to merged 139,137,075, minus 2,780 (minus 0.0020%)
boundary drops 2,780 · 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-24T12:05:09Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 14,618,195 170,493,268 0-55 7522979c04b87f28bbc22039811204dedb16140974f1abcdb289cbda16c3cf20 book 2,423,054 110,583,780 56-65 e5e8f670dc2120f3163296874d65ce523a5863329cc55b78c74b8fb2903f8181 last_trade_price 57,726 3,316,061 66-66 bcd73ea33e18e2dd17cdc0823d41e0123cf8c8a25ea0425cb44eb3d3cd8d148f market_resolved 927 101,229 67-67 9ab41f550756ecddde64040e0be0222c292e606c71451839ad716e16cd83791c new_market 759 70,709 68-68 6fc297ff2382ea382b71bf1edff61f2aa3cbc16511b032c0ce567dd5ffc11673 price_change 122,033,578 1,242,592,583 69-534 eccd78f4ac6f42df81a3a992dba30afbcaf4efd1ce979ef19419b802dbc3fe5f tick_size_change 2,836 105,331 535-535 460ae5b84ed36ebdf0da0d669e0e3e04f6e4135be67cbf56349c49c2b9dbdee6 EVENT MIX count share price_change 122,033,578 87.71% best_bid_ask 14,618,195 10.51% book 2,423,054 1.74% last_trade_price 57,726 0.04% tick_size_change 2,836 <0.01% market_resolved 927 <0.01% new_market 759 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,618,496 14,618,195 301 3,605 FULL book 2,423,112 2,423,054 58 46,747 FULL last_trade_price 57,727 57,726 1 567 FULL market_resolved 927 927 0 21 FULL new_market 759 759 0 0 FULL price_change 122,035,998 122,033,578 2,420 1,895 FULL tick_size_change 2,836 2,836 0 189 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,723,690 11,611,125 5ms 16ms 111ms 3.0s 0 transport_latency_assumed best_bid_ask g 13,288,864 2,001 80ms 106ms 375ms 23.5s 0 transport_latency_assumed best_bid_ask h 14,612,718 748,357 19ms 48ms 148ms 9.9s 0 transport_latency_assumed best_bid_ask i 13,357,130 189,712 22ms 34ms 125ms 3.9s 0 transport_latency_assumed best_bid_ask k 12,707,577 2,067,000 14ms 23ms 93ms 3.4s 0 transport_latency_assumed book c 1,342,808 651,629 9.3min 4.8d 42.8d 117.5d 0 book_staleness book g 987,749 271,488 7.1min 4.0d 42.6d 117.5d 0 book_staleness book h 444,795 131,258 2.5min 2.6d 32.8d 117.5d 0 book_staleness book i 919,080 167,272 6.8min 3.7d 42.6d 117.5d 0 book_staleness book k 1,420,652 1,201,407 9.0min 4.7d 42.8d 117.5d 0 book_staleness last_trade_price c 50,205 44,853 6ms 26ms 170ms 1.3s 0 transport_latency_assumed last_trade_price g 51,393 20 92ms 2.7s 15.0s 22.4s 0 transport_latency_assumed last_trade_price h 57,506 2,871 20ms 78ms 367ms 5.6s 0 transport_latency_assumed last_trade_price i 53,278 762 25ms 130ms 844ms 2.2s 0 transport_latency_assumed last_trade_price k 51,640 9,220 15ms 41ms 202ms 1.3s 0 transport_latency_assumed market_resolved c 648 555 6ms 4.9min 6.2min 6.2min 0 transport_latency_assumed market_resolved g 621 60 90ms 34.5s 5.9min 5.9min 0 transport_latency_assumed market_resolved h 600 80 21ms 16.4s 45.5s 49.2s 0 transport_latency_assumed market_resolved i 629 70 32ms 4.7min 10.4min 10.4min 0 transport_latency_assumed market_resolved k 720 162 22ms 9.3min 14.6min 14.9min 0 transport_latency_assumed new_market c 447 228 54ms 9.5s 31.5s 36.3s 0 transport_latency_assumed new_market g 462 60 254ms 11.9s 6.0min 6.1min 0 transport_latency_assumed new_market h 447 85 144ms 10.2s 27.9s 1.4min 0 transport_latency_assumed new_market i 486 116 99ms 33.6s 6.2min 6.3min 0 transport_latency_assumed new_market k 576 270 97ms 5.8min 10.9min 11.6min 0 transport_latency_assumed price_change c 106,780,041 96,732,685 5ms 19ms 129ms 3.8s 0 transport_latency_assumed price_change g 110,544,770 20,328 81ms 143ms 5.7s 23.7s 0 transport_latency_assumed price_change h 121,928,326 6,062,352 19ms 53ms 191ms 15.7s 0 transport_latency_assumed price_change i 111,986,312 1,686,117 22ms 42ms 215ms 4.1s 0 transport_latency_assumed price_change k 106,851,486 17,532,096 14ms 27ms 113ms 3.4s 0 transport_latency_assumed tick_size_change c 2,500 2,268 5ms 15ms 118ms 430ms 0 transport_latency_assumed tick_size_change g 2,616 not meas. 80ms 100ms 234ms 449ms 0 transport_latency_assumed tick_size_change h 2,836 119 19ms 42ms 92ms 240ms 0 transport_latency_assumed tick_size_change i 2,688 37 22ms 32ms 105ms 311ms 0 transport_latency_assumed tick_size_change k 2,588 412 14ms 22ms 94ms 250ms 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-24/09/2026-09-24T09.parquet sha256sum 2026-09-24T09.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.