Hour audit: 2026-09-27T03
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-27T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T03:00:00.000081652+00:00 · last event 2026-09-27T03:59:59.999953601+00:00
VOLUME 122,889,255 rows · 1,356,705,675 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 120,949,022 · h: 116,312,759 · g: 115,962,923 · k: 111,022,286 · c: 102,089,671 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,066,623 (1.68%) · h: 1,952,982 (1.59%) · g: 109,829 (0.09%) · k: 22,825,946 (18.57%) · c: 95,933,875 (78.07%) (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 122,889,255 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 512061c949de03ee11aa6f05f9b270d7f642fb3f4cc718bafa58b0b29cb51bc5
the corpus checksum ledger names this file with the same digest
joined 122,897,532 to merged 122,889,255, minus 8,277 (minus 0.0067%)
boundary drops 8,277 · 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-27T13:32:38Z 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,009,332 157,245,165 0-53 56a442f780cd41d48a103d4588ea9daf14fe3f48da2043b59497c2bb7fb4968b book 2,015,424 84,654,372 54-61 4401ea8c6955e1d18092988e9949eaf35721633ef69fcb9b16e4eba997bf1cf7 last_trade_price 38,354 2,272,350 62-62 062dbaa7be5c0a32765d7cbb60c2cf08cf712a67069a606e2ddd45f6d46dcd77 market_resolved 6,807 733,311 63-63 c4fb9b3e360a8533aef89ba0f28c04d38f00b9c4ae5bd04bb980d6bbd9657653 new_market 1,964 161,369 64-64 8d074d5348b958563655b2f14b79076959b5bf5b380ac2e8998df6a920280923 price_change 106,808,554 1,109,917,093 65-472 38d16c2ab7fe8db33a911d38ace08a1fdac4c656f9d342b29bef540466d544b3 tick_size_change 8,820 323,789 473-473 821725ca485c776b4e2bad1172da7ac20a96839248e9956f981c2ded188e6fcc EVENT MIX count share price_change 106,808,554 86.91% best_bid_ask 14,009,332 11.40% book 2,015,424 1.64% last_trade_price 38,354 0.03% tick_size_change 8,820 <0.01% market_resolved 6,807 <0.01% new_market 1,964 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,009,880 14,009,332 548 3,385 FULL book 2,018,901 2,015,424 3,477 181,232 FULL last_trade_price 38,356 38,354 2 387 FULL market_resolved 6,809 6,807 2 779 FULL new_market 1,964 1,964 0 8 FULL price_change 106,812,802 106,808,554 4,248 2,060 FULL tick_size_change 8,820 8,820 0 654 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,691,636 11,014,106 4ms 10ms 111ms 4.3s 0 transport_latency_assumed best_bid_ask g 13,390,194 1,138 79ms 96ms 297ms 8.4s 0 transport_latency_assumed best_bid_ask h 13,454,689 197,187 19ms 64ms 229ms 38.2s 0 transport_latency_assumed best_bid_ask i 14,007,126 221,389 21ms 26ms 87ms 7.9s 0 transport_latency_assumed best_bid_ask k 12,787,833 2,575,512 12ms 16ms 80ms 4.5s 0 transport_latency_assumed book c 1,649,011 1,497,505 1.6h 6.4d 46.3d 120.2d 0 book_staleness book g 495,363 99,108 46.4min 5.3d 42.6d 120.2d 0 book_staleness book h 471,302 139,857 39.6min 5.3d 42.6d 120.2d 0 book_staleness book i 111,401 10,683 25ms 7.1h 21.6d 101.7d 0 book_staleness book k 889,124 268,271 1.3h 5.3d 45.4d 120.2d 0 book_staleness last_trade_price c 30,957 28,380 5ms 17ms 202ms 1.2s 0 transport_latency_assumed last_trade_price g 36,833 6 81ms 164ms 585ms 5.8s 0 transport_latency_assumed last_trade_price h 36,320 924 21ms 66ms 344ms 6.1s 0 transport_latency_assumed last_trade_price i 38,228 1,046 22ms 35ms 207ms 6.5s 0 transport_latency_assumed last_trade_price k 34,354 7,998 13ms 24ms 186ms 1.3s 0 transport_latency_assumed market_resolved c 5,226 4,010 7ms 7.9min 13.2min 14.5min 0 transport_latency_assumed market_resolved g 5,349 1,049 86ms 11.9min 18.2min 18.7min 0 transport_latency_assumed market_resolved h 4,374 629 27ms 26.4s 9.5min 10.4min 0 transport_latency_assumed market_resolved i 4,231 139 22ms 52ms 53.1s 56.0s 0 transport_latency_assumed market_resolved k 3,962 980 13ms 16.2s 5.0min 5.5min 0 transport_latency_assumed new_market c 1,571 776 306ms 4.0min 7.4min 10.6min 0 transport_latency_assumed new_market g 1,080 170 287ms 53.4s 11.8min 14.8min 0 transport_latency_assumed new_market h 1,074 266 173ms 59.3s 6.2min 6.2min 0 transport_latency_assumed new_market i 998 384 95ms 25.1s 1.1min 1.7min 0 transport_latency_assumed new_market k 1,002 368 90ms 11.8s 1.6min 2.0min 0 transport_latency_assumed price_change c 88,703,450 83,381,945 5ms 10ms 117ms 4.5s 0 transport_latency_assumed price_change g 102,025,700 8,358 79ms 99ms 367ms 8.4s 0 transport_latency_assumed price_change h 102,336,252 1,613,916 19ms 65ms 247ms 38.2s 0 transport_latency_assumed price_change i 106,778,218 1,832,654 21ms 27ms 110ms 8.0s 0 transport_latency_assumed price_change k 97,298,615 19,971,681 12ms 17ms 89ms 5.1s 0 transport_latency_assumed tick_size_change c 7,820 7,153 4ms 14ms 165ms 312ms 0 transport_latency_assumed tick_size_change g 8,404 not meas. 80ms 104ms 394ms 648ms 0 transport_latency_assumed tick_size_change h 8,748 203 19ms 62ms 326ms 14.8s 0 transport_latency_assumed tick_size_change i 8,820 328 21ms 32ms 157ms 779ms 0 transport_latency_assumed tick_size_change k 7,396 1,136 12ms 30ms 214ms 585ms 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/03/2026-09-27T03.parquet sha256sum 2026-09-27T03.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.