Hour audit: 2026-09-23T11
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-23T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T11:00:00.000472354+00:00 · last event 2026-09-23T11:59:59.999917124+00:00
VOLUME 120,472,831 rows · 1,296,314,939 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cfghik — 6 machines contributed rows
captured i: 119,942,758 · f: 119,541,517 · h: 119,516,452 · g: 117,848,240 · k: 115,260,895 · c: 114,900,154 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,018,120 (0.85%) · f: 59,580 (0.05%) · h: 5,679,221 (4.71%) · g: 31,411 (0.03%) · k: 8,948,200 (7.43%) · c: 104,736,299 (86.94%) (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 120,472,831 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 5e7c233d65934fdba5a26fae6ad0ccf07beb105a89ef5ff1e54843810cd4e98f
the corpus checksum ledger names this file with the same digest
joined 120,475,836 to merged 120,472,831, minus 3,005 (minus 0.0025%)
boundary drops 3,005 · 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-23T14:59:10Z as cfghik
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,154,393 130,861,953 0-42 044f4323487e5900e647bdb8d7affb625bf0897b4a5a519491211c794656a3e2 book 806,938 63,886,729 43-46 714a1ff5c33cc3d004f5cf41cc53be181286dafdf55e10b567bba8d408bd30d3 last_trade_price 53,970 3,146,245 47-47 1da64ed406d1af3da461d23e8cae053ad96bda35a7c58387cba34ac349640e85 market_resolved 1,002 149,123 48-48 dbd5676e96754b20d773eb1697ff67b9947d7fb9a679be3cb3c5612751fddf4e new_market 762 84,914 49-49 dc17c666e19ac986c09dd010db7e226253118cfd8f8eb14daf5756a8cc7a11e5 price_change 108,452,122 1,096,677,287 50-463 66aaeb0bb5eb1ff204f457bd14393f028667e36a4c49fc3244be0aaf51a25525 tick_size_change 3,644 134,473 464-464 621ae86ef91b4406446ae82ec13ecad204b2b41d6da50259648b0eb27ba33af4 EVENT MIX count share price_change 108,452,122 90.02% best_bid_ask 11,154,393 9.26% book 806,938 0.67% last_trade_price 53,970 0.04% tick_size_change 3,644 <0.01% market_resolved 1,002 <0.01% new_market 762 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,154,577 11,154,393 184 430 FULL book 808,148 806,938 1,210 192,125 FULL last_trade_price 53,971 53,970 1 85 FULL market_resolved 1,002 1,002 0 43 FULL new_market 762 762 0 0 FULL price_change 108,453,732 108,452,122 1,610 205 FULL tick_size_change 3,644 3,644 0 91 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,621,694 9,771,585 5ms 13ms 101ms 9.3s 0 transport_latency_assumed best_bid_ask f 11,152,120 2,825 50ms 62ms 191ms 14.9s 0 transport_latency_assumed best_bid_ask g 11,091,176 317 79ms 102ms 581ms 22.5s 0 transport_latency_assumed best_bid_ask h 11,152,742 544,029 18ms 28ms 127ms 44.8s 0 transport_latency_assumed best_bid_ask i 11,151,434 69,231 24ms 33ms 115ms 3.9s 0 transport_latency_assumed best_bid_ask k 10,661,837 766,406 13ms 20ms 82ms 1.6s 0 transport_latency_assumed book c 564,135 246,803 7.2min 2.8d 38.9d 116.5d 0 book_staleness book f 140,407 14,114 58ms 20.1min 16.0d 116.5d 0 book_staleness book g 129,643 25,751 119ms 4.5min 4.8d 116.5d 0 book_staleness book h 114,206 8,836 23ms 177ms 8.4h 98.5d 0 book_staleness book i 391,483 215,812 2.6min 1.7d 31.9d 116.5d 0 book_staleness book k 516,690 295,622 6.1min 2.6d 38.7d 116.5d 0 book_staleness last_trade_price c 51,123 46,000 6ms 24ms 186ms 1.4s 0 transport_latency_assumed last_trade_price f 53,658 46 53ms 293ms 3.3s 15.0s 0 transport_latency_assumed last_trade_price g 49,412 15 96ms 1.7s 12.3s 22.5s 0 transport_latency_assumed last_trade_price h 53,770 2,613 20ms 76ms 488ms 8.0s 0 transport_latency_assumed last_trade_price i 53,859 380 27ms 168ms 957ms 2.0s 0 transport_latency_assumed last_trade_price k 51,672 4,916 14ms 38ms 192ms 959ms 0 transport_latency_assumed market_resolved c 903 802 5ms 14.0s 5.4min 5.4min 0 transport_latency_assumed market_resolved f 903 not meas. 51ms 355ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 902 1 78ms 199ms 34.2s 57.7s 0 transport_latency_assumed market_resolved h 903 96 19ms 127ms 53.5s 53.5s 0 transport_latency_assumed market_resolved i 903 35 25ms 184ms 53.5s 53.5s 0 transport_latency_assumed market_resolved k 861 68 13ms 44ms 27.8s 2.4min 0 transport_latency_assumed new_market c 527 210 86ms 8.3s 46.7s 3.9min 0 transport_latency_assumed new_market f 527 67 171ms 9.2s 18.3s 1.8min 0 transport_latency_assumed new_market g 527 55 285ms 11.9s 17.1s 1.8min 0 transport_latency_assumed new_market h 527 125 112ms 12.3s 30.5s 1.8min 0 transport_latency_assumed new_market i 527 94 136ms 10.9s 19.6s 1.7min 0 transport_latency_assumed new_market k 527 211 77ms 10.1s 17.7s 1.4min 0 transport_latency_assumed price_change c 103,658,240 94,667,616 5ms 16ms 117ms 9.4s 0 transport_latency_assumed price_change f 108,190,258 42,528 50ms 75ms 461ms 15.0s 0 transport_latency_assumed price_change g 106,572,956 5,272 79ms 154ms 4.2s 27.3s 0 transport_latency_assumed price_change h 108,190,660 5,123,428 18ms 34ms 193ms 45.0s 0 transport_latency_assumed price_change i 108,340,908 732,554 25ms 41ms 248ms 4.7s 0 transport_latency_assumed price_change k 104,025,960 7,880,724 13ms 23ms 109ms 2.4s 0 transport_latency_assumed tick_size_change c 3,532 3,283 5ms 12ms 64ms 236ms 0 transport_latency_assumed tick_size_change f 3,644 not meas. 50ms 55ms 118ms 190ms 0 transport_latency_assumed tick_size_change g 3,624 not meas. 79ms 191ms 358ms 2.0s 0 transport_latency_assumed tick_size_change h 3,644 94 18ms 34ms 90ms 180ms 0 transport_latency_assumed tick_size_change i 3,644 14 24ms 38ms 72ms 306ms 0 transport_latency_assumed tick_size_change k 3,348 253 13ms 18ms 59ms 361ms 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-23/11/2026-09-23T11.parquet sha256sum 2026-09-23T11.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.