Hour audit: 2026-09-29T00
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-29T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T00:00:00.000047711+00:00 · last event 2026-09-29T00:59:59.999972943+00:00
VOLUME 99,558,353 rows · 1,049,638,051 bytes (1001.01 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 99,403,791 · c: 99,363,700 · k: 99,360,961 · i: 99,320,775 · g: 98,670,585 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,343,588 (2.35%) · c: 90,188,267 (90.59%) · k: 5,659,878 (5.68%) · i: 1,287,172 (1.29%) · g: 79,448 (0.08%) (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 99,558,353 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f83df8e7f7013b232b3c1c62d7b53a88e96b5a88709c16a068fdd11e06ec8f40
the corpus checksum ledger names this file with the same digest
joined 99,565,403 to merged 99,558,353, minus 7,050 (minus 0.0071%)
boundary drops 7,050 · 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-29T03:08: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 10,965,824 125,247,339 0-41 b6fe79d474821ad0c2128889affe267ee88d881d50a0a5900b5db3a7b1fcb437 book 331,208 29,763,953 42-43 a1cdeb0f76ead81b9312246cfe5b6d12b2a2381b5fa00369af0e7fe73a4fab52 last_trade_price 72,796 3,924,533 44-44 a60a908f59f313b867a9a8f37a24bf133b73aa203939b83cf8ff54e178ec1cbb market_resolved 856 138,118 45-45 3a0037d33af9e8bd0dd6afca8add814b768b792b6503ee8148b9ca09aad1b3ff new_market 2,843 288,270 46-46 775ce5d6210d892742b9f40994f3a374e4794cecbfd776f35b92b202c2e81217 price_change 88,181,682 889,025,162 47-383 5c63a36a92f8dc3be2efebe1bf2ad7d32298308d42557841eb9eaa24051b595e tick_size_change 3,144 114,730 384-384 f16a1b7c8429a40038245cbf8c319c52057897a6ed9e0147c6057584df41aaa4 EVENT MIX count share price_change 88,181,682 88.57% best_bid_ask 10,965,824 11.01% book 331,208 0.33% last_trade_price 72,796 0.07% tick_size_change 3,144 <0.01% new_market 2,843 <0.01% market_resolved 856 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,966,772 10,965,824 948 243 FULL book 331,240 331,208 32 75,117 FULL last_trade_price 72,796 72,796 0 0 FULL market_resolved 856 856 0 0 FULL new_market 2,843 2,843 0 0 FULL price_change 88,187,752 88,181,682 6,070 242 FULL tick_size_change 3,144 3,144 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,964,368 10,057,295 5ms 14ms 153ms 18.7s 0 transport_latency_assumed best_bid_ask g 10,937,916 4,487 82ms 110ms 518ms 29.3s 0 transport_latency_assumed best_bid_ask h 10,963,456 221,782 18ms 27ms 219ms 29.1s 0 transport_latency_assumed best_bid_ask i 10,963,326 122,234 24ms 32ms 171ms 27.4s 0 transport_latency_assumed best_bid_ask k 10,963,131 560,026 13ms 25ms 205ms 1.1min 0 transport_latency_assumed book c 184,125 159,193 8ms 1.9h 19.7d 122.1d 0 book_staleness book g 161,740 24,060 94ms 42.1min 9.4d 103.6d 0 book_staleness book h 231,324 81,360 37ms 13.2h 24.4d 122.1d 0 book_staleness book i 157,586 11,180 28ms 327ms 1.1d 103.6d 0 book_staleness book k 196,794 55,415 19ms 6.2h 21.6d 122.1d 0 book_staleness last_trade_price c 72,682 63,025 6ms 37ms 338ms 3.3s 0 transport_latency_assumed last_trade_price g 65,761 147 87ms 823ms 12.5s 28.9s 0 transport_latency_assumed last_trade_price h 72,572 2,345 19ms 76ms 617ms 6.3s 0 transport_latency_assumed last_trade_price i 72,504 1,243 27ms 110ms 634ms 7.6s 0 transport_latency_assumed last_trade_price k 72,397 6,036 14ms 54ms 348ms 20.5s 0 transport_latency_assumed market_resolved c 830 750 5ms 20ms 54.0s 54.0s 0 transport_latency_assumed market_resolved g 830 13 83ms 222ms 1.1s 57.8s 0 transport_latency_assumed market_resolved h 830 7 19ms 64ms 52.0s 57.1s 0 transport_latency_assumed market_resolved i 830 31 26ms 85ms 36.2s 1.2min 0 transport_latency_assumed market_resolved k 830 55 14ms 39ms 52.1s 52.2s 0 transport_latency_assumed new_market c 1,853 936 100ms 50.5s 2.3min 2.8min 0 transport_latency_assumed new_market g 1,853 191 254ms 56.0s 2.2min 3.5min 0 transport_latency_assumed new_market h 1,853 725 113ms 54.1s 2.2min 3.5min 0 transport_latency_assumed new_market i 1,853 580 108ms 58.5s 2.3min 3.5min 0 transport_latency_assumed new_market k 1,853 411 170ms 58.2s 2.3min 3.5min 0 transport_latency_assumed price_change c 88,136,698 79,904,184 5ms 18ms 192ms 23.0s 0 transport_latency_assumed price_change g 87,499,341 50,550 83ms 141ms 2.7s 29.3s 0 transport_latency_assumed price_change h 88,130,612 2,037,350 18ms 33ms 307ms 29.2s 0 transport_latency_assumed price_change i 88,121,532 1,151,892 24ms 39ms 277ms 27.4s 0 transport_latency_assumed price_change k 88,122,812 5,037,706 13ms 29ms 248ms 1.2min 0 transport_latency_assumed tick_size_change c 3,144 2,884 5ms 12ms 120ms 220ms 0 transport_latency_assumed tick_size_change g 3,144 not meas. 82ms 98ms 272ms 619ms 0 transport_latency_assumed tick_size_change h 3,144 19 18ms 25ms 91ms 1.1s 0 transport_latency_assumed tick_size_change i 3,144 12 24ms 30ms 63ms 133ms 0 transport_latency_assumed tick_size_change k 3,144 229 13ms 19ms 60ms 279ms 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-29/00/2026-09-29T00.parquet sha256sum 2026-09-29T00.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.