Hour audit: 2026-09-27T16
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-27T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T16:00:00.000030655+00:00 · last event 2026-09-27T16:59:59.999954278+00:00
VOLUME 97,618,373 rows · 1,100,296,212 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 96,295,669 · k: 96,292,979 · h: 96,259,704 · g: 95,623,122 · c: 84,845,446 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,532,426 (2.59%) · k: 18,770,667 (19.23%) · h: 3,030,072 (3.10%) · g: 41,868 (0.04%) · c: 73,243,340 (75.03%) (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 97,618,373 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 35b279f55f15c5469c5c97e9bf51d088df35603fc0b7651c0ab507024da3937a
the corpus checksum ledger names this file with the same digest
joined 97,620,353 to merged 97,618,373, minus 1,980 (minus 0.0020%)
boundary drops 1,980 · 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-27T18:46:25Z 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 10,414,551 121,495,177 0-39 f4afbd7d333ebae144eb6a94ed320a3c206fe6f866662411a4c7f4a3ce36a9f9 book 1,418,965 74,450,046 40-45 3a054d6adaeffe254b61dff6f9bff6b347a52a3d67cbccf337d564ee739dbeba last_trade_price 72,189 4,049,364 46-46 219b761a2374ab09ec7d59059587e600abff6c86c9346267d244a8f82460d911 market_resolved 2,887 359,512 47-47 83c446236ba90a4a2a75ccc40c48b593e1e7243f8d2244bd55d9e2c56a7b1cb6 new_market 8,066 673,095 48-48 870c9667265da5a23eb373c55ece661e9305eb8a830f1de4787510127193569a price_change 85,698,211 898,027,834 49-375 e3c3fcadd933d19625f6fbb535f216380569206e8f2ca90e62fcc9bf952b5d3c tick_size_change 3,504 129,060 376-376 45356170365393a7aaf4a568d14df5a4c7068c4760f2986260bc6e9baf96b1ad EVENT MIX count share price_change 85,698,211 87.79% best_bid_ask 10,414,551 10.67% book 1,418,965 1.45% last_trade_price 72,189 0.07% new_market 8,066 <0.01% tick_size_change 3,504 <0.01% market_resolved 2,887 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,414,792 10,414,551 241 3,045 FULL book 1,418,993 1,418,965 28 203,465 FULL last_trade_price 72,190 72,189 1 269 FULL market_resolved 2,887 2,887 0 88 FULL new_market 8,066 8,066 0 0 FULL price_change 85,699,921 85,698,211 1,710 2,589 FULL tick_size_change 3,504 3,504 0 157 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,004,733 7,804,435 5ms 29ms 440ms 17.9s 0 transport_latency_assumed best_bid_ask g 10,395,275 2,422 80ms 213ms 1.5s 45.6s 0 transport_latency_assumed best_bid_ask h 10,410,543 310,051 19ms 37ms 699ms 1.5min 0 transport_latency_assumed best_bid_ask i 10,411,612 268,845 27ms 40ms 227ms 9.0s 0 transport_latency_assumed best_bid_ask k 10,411,528 2,028,798 13ms 26ms 334ms 1.3min 0 transport_latency_assumed book c 1,392,874 1,364,639 1.1h 2.8d 43.3d 120.8d 0 book_staleness book g 153,727 6,463 97ms 6.8s 12.7h 120.7d 0 book_staleness book h 155,181 8,544 25ms 387ms 2.1h 102.2d 0 book_staleness book i 153,755 7,109 34ms 528ms 22.0s 102.2d 0 book_staleness book k 157,417 32,210 17ms 276ms 7.6h 102.1d 0 book_staleness last_trade_price c 62,997 53,394 6ms 62ms 815ms 9.1s 0 transport_latency_assumed last_trade_price g 68,374 44 99ms 2.4s 18.6s 45.4s 0 transport_latency_assumed last_trade_price h 71,858 2,378 20ms 147ms 1.0s 58.2s 0 transport_latency_assumed last_trade_price i 71,918 1,582 32ms 201ms 3.6s 9.1s 0 transport_latency_assumed last_trade_price k 72,008 14,791 14ms 67ms 457ms 55.8s 0 transport_latency_assumed market_resolved c 2,536 2,205 7ms 7.0min 10.2min 10.4min 0 transport_latency_assumed market_resolved g 2,186 67 86ms 548ms 51.0s 55.8s 0 transport_latency_assumed market_resolved h 2,186 59 20ms 249ms 49.3s 49.5s 0 transport_latency_assumed market_resolved i 2,186 44 30ms 230ms 50.0s 52.5s 0 transport_latency_assumed market_resolved k 2,186 512 14ms 190ms 49.2s 49.3s 0 transport_latency_assumed new_market c 6,164 3,213 22.0s 8.5min 11.5min 12.2min 0 transport_latency_assumed new_market g 4,195 568 378ms 47.9s 1.8min 3.8min 0 transport_latency_assumed new_market h 4,195 1,548 165ms 39.7s 1.7min 3.6min 0 transport_latency_assumed new_market i 4,195 1,658 112ms 48.9s 1.8min 3.8min 0 transport_latency_assumed new_market k 4,195 1,079 200ms 49.1s 1.8min 3.8min 0 transport_latency_assumed price_change c 74,373,262 64,012,988 5ms 36ms 501ms 22.1s 0 transport_latency_assumed price_change g 84,995,865 32,304 81ms 328ms 5.7s 45.6s 0 transport_latency_assumed price_change h 85,612,237 2,707,430 19ms 49ms 826ms 1.5min 0 transport_latency_assumed price_change i 85,648,499 2,253,112 28ms 53ms 464ms 9.2s 0 transport_latency_assumed price_change k 85,642,141 16,692,377 13ms 33ms 390ms 1.3min 0 transport_latency_assumed tick_size_change c 2,880 2,466 5ms 22ms 195ms 609ms 0 transport_latency_assumed tick_size_change g 3,500 not meas. 79ms 207ms 1.5s 8.5s 0 transport_latency_assumed tick_size_change h 3,504 62 18ms 30ms 1.3s 15.1s 0 transport_latency_assumed tick_size_change i 3,504 76 25ms 34ms 68ms 451ms 0 transport_latency_assumed tick_size_change k 3,504 900 13ms 17ms 370ms 6.7s 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/16/2026-09-27T16.parquet sha256sum 2026-09-27T16.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.