Hour audit: 2026-09-27T22
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-27T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T22:00:00.000030566+00:00 · last event 2026-09-27T22:59:59.999947940+00:00
VOLUME 117,813,697 rows · 1,333,542,281 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 116,922,498 · k: 116,909,094 · h: 116,875,244 · g: 116,555,854 · c: 107,115,823 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 19,634,073 (16.67%) · k: 6,162,779 (5.23%) · h: 1,832,558 (1.56%) · g: 11,697 (0.01%) · c: 90,172,590 (76.54%) (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 117,813,697 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 93e7a94f2297dd1933910b889bbe740114e95b3089585e85f7d6ddf880931abd
the corpus checksum ledger names this file with the same digest
joined 117,816,052 to merged 117,813,697, minus 2,355 (minus 0.0020%)
boundary drops 2,355 · 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-28T01:09:17Z 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 12,812,367 149,240,706 0-48 a25e39f0529e0b74cce4f364c46144e20a118656a5f3c38050541514b4680cc7 book 951,326 60,627,868 49-52 cc3568d003c5230d31028b4e45ad369102a7dc2142b0170519833f4de1d7573d last_trade_price 50,191 2,885,095 53-53 9e0f213a9a06900340e57bd9874c6f59230025e4c80784946b15083008e75a38 market_resolved 6,560 763,506 54-54 50d2be86e5d5293b18f2e7f411101b367abf01fde7ac9f7c33366a01e1ec8cb0 new_market 2,397 227,345 55-55 67225f048280f933f353df6e6ea8b8f447d3e5fd4c0c18aa7fb65be31b4be6d2 price_change 103,986,020 1,118,280,944 56-452 7961e75c4405dd1f1af1858cbfae370d2846b0a09d9ac1e1b2f19f4bdfdf43af tick_size_change 4,836 177,802 453-453 ac1ace17340b86d32af4517e443d55610d9c9bc4976ac4570e4732cd354c315e EVENT MIX count share price_change 103,986,020 88.26% best_bid_ask 12,812,367 10.88% book 951,326 0.81% last_trade_price 50,191 0.04% market_resolved 6,560 <0.01% tick_size_change 4,836 <0.01% new_market 2,397 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,812,630 12,812,367 263 1,598 FULL book 951,668 951,326 342 206,282 FULL last_trade_price 50,191 50,191 0 191 FULL market_resolved 6,560 6,560 0 15 FULL new_market 2,397 2,397 0 10 FULL price_change 103,987,770 103,986,020 1,750 1,201 FULL tick_size_change 4,836 4,836 0 90 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,655,808 9,855,592 5ms 17ms 204ms 6.8s 0 transport_latency_assumed best_bid_ask g 12,803,154 881 82ms 122ms 703ms 27.6s 0 transport_latency_assumed best_bid_ask h 12,809,195 178,049 17ms 28ms 309ms 54.9s 0 transport_latency_assumed best_bid_ask i 12,809,404 2,149,203 15ms 23ms 117ms 12.9s 0 transport_latency_assumed best_bid_ask k 12,809,767 628,642 12ms 25ms 231ms 1.0min 0 transport_latency_assumed book c 932,317 907,777 47.0min 3.0d 43.3d 121.0d 0 book_staleness book g 106,754 3,777 94ms 4.1s 18.7h 102.4d 0 book_staleness book h 106,165 4,643 22ms 125ms 13.9h 102.4d 0 book_staleness book i 118,033 25,930 19ms 3.3min 9.3d 102.5d 0 book_staleness book k 110,535 9,199 17ms 286ms 1.3d 102.5d 0 book_staleness last_trade_price c 45,156 37,103 6ms 32ms 333ms 1.8s 0 transport_latency_assumed last_trade_price g 48,428 14 94ms 761ms 14.9s 26.2s 0 transport_latency_assumed last_trade_price h 50,061 1,259 19ms 57ms 512ms 33.3s 0 transport_latency_assumed last_trade_price i 49,957 8,596 16ms 60ms 509ms 2.8s 0 transport_latency_assumed last_trade_price k 50,048 3,219 14ms 53ms 383ms 8.5s 0 transport_latency_assumed market_resolved c 5,774 4,583 8ms 9.9min 16.4min 16.9min 0 transport_latency_assumed market_resolved g 4,659 280 83ms 402ms 50.9s 58.7s 0 transport_latency_assumed market_resolved h 4,659 637 18ms 23.5s 50.8s 56.2s 0 transport_latency_assumed market_resolved i 4,659 857 16ms 22.8s 50.8s 53.8s 0 transport_latency_assumed market_resolved k 4,659 203 13ms 25.1s 51.4s 56.2s 0 transport_latency_assumed new_market c 1,697 830 214ms 6.6min 9.8min 11.3min 0 transport_latency_assumed new_market g 1,420 169 378ms 22.4s 48.6s 1.6min 0 transport_latency_assumed new_market h 1,410 379 197ms 24.0s 48.7s 1.6min 0 transport_latency_assumed new_market i 1,410 733 89ms 20.6s 42.2s 1.5min 0 transport_latency_assumed new_market k 1,410 286 226ms 22.3s 53.1s 1.5min 0 transport_latency_assumed price_change c 94,470,595 79,363,019 5ms 19ms 219ms 7.1s 0 transport_latency_assumed price_change g 103,586,603 6,576 83ms 170ms 2.6s 28.0s 0 transport_latency_assumed price_change h 103,898,918 1,647,565 18ms 33ms 368ms 55.6s 0 transport_latency_assumed price_change i 103,934,199 17,447,912 15ms 27ms 185ms 12.9s 0 transport_latency_assumed price_change k 103,927,839 5,520,948 13ms 28ms 257ms 1.7min 0 transport_latency_assumed tick_size_change c 4,476 3,686 5ms 19ms 131ms 325ms 0 transport_latency_assumed tick_size_change g 4,836 not meas. 81ms 100ms 306ms 664ms 0 transport_latency_assumed tick_size_change h 4,836 26 18ms 25ms 74ms 4.0s 0 transport_latency_assumed tick_size_change i 4,836 842 14ms 21ms 58ms 296ms 0 transport_latency_assumed tick_size_change k 4,836 282 13ms 20ms 60ms 406ms 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-27/22/2026-09-27T22.parquet sha256sum 2026-09-27T22.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.