Hour audit: 2026-09-30T02
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-30T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T02:00:00.002440138+00:00 · last event 2026-09-30T02:59:59.997937053+00:00
VOLUME 109,698,217 rows · 1,157,700,604 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 109,115,076 · m: 109,008,400 · g: 108,986,112 · h: 108,854,752 · i: 108,590,882 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 4,084,119 (3.72%) · m: 103,777,902 (94.60%) · g: 212,378 (0.19%) · h: 1,255,949 (1.14%) · i: 367,869 (0.34%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,698,217 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 12930c7af73077b707eed0295bd97a28d44878d1bb65796a4045ff95cf0aea8a
the corpus checksum ledger names this file with the same digest
joined 109,702,062 to merged 109,698,217, minus 3,845 (minus 0.0035%)
boundary drops 3,845 · 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-30T14:38:26Z as ghikm
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,405,424 118,351,816 0-39 a4bc31d670ea55962a840fa8b324af2bc3f738cea744b9c0fd511a1dde3cfa91 book 922,487 73,270,001 40-43 994f8a59ab4081802db1e49b92c6248dee496b40e9240eeda5847ad7a4da42f5 last_trade_price 45,809 2,622,619 44-44 2e12e1d38cbed272b05ab93bde6b6955c85651e52360dfc6016f7ea91e231352 market_resolved 563 92,954 45-45 7161a11af21fddafd3f5319c186a297ac2e50975b916282e625ee2ff1e920eca new_market 1,306 148,999 46-46 934e652ac6023508c52d5d44470dd578a4374e0d46827e0c332865753285e547 price_change 98,320,644 961,887,574 47-422 193585af34650dad404ce8b403fec3a4b1fa76c3f71d4d24a99c800c037c26c2 tick_size_change 1,984 73,841 423-423 3dca6d243a51b435e3193e80d2362e44cc882e6ac737bbf696fd05e6f1d4be82 EVENT MIX count share price_change 98,320,644 89.63% best_bid_ask 10,405,424 9.49% book 922,487 0.84% last_trade_price 45,809 0.04% tick_size_change 1,984 <0.01% new_market 1,306 <0.01% market_resolved 563 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,406,286 10,405,424 862 87 FULL book 922,617 922,487 130 225,400 FULL last_trade_price 45,810 45,809 1 1 FULL market_resolved 563 563 0 0 FULL new_market 1,306 1,306 0 0 FULL price_change 98,323,496 98,320,644 2,852 142 FULL tick_size_change 1,984 1,984 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,398,520 868 79ms 101ms 441ms 23.9s 0 transport_latency_assumed best_bid_ask h 10,393,487 87,144 18ms 26ms 191ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,396,189 28,687 29ms 36ms 160ms 49.5s 0 transport_latency_assumed best_bid_ask k 10,402,595 340,787 13ms 24ms 143ms 1.0min 0 transport_latency_assumed best_bid_ask m 10,396,750 9,947,938 4ms 9ms 71ms 8.0s 0 transport_latency_assumed book g 472,292 201,957 31.5min 2.2d 38.5d 123.2d 0 book_staleness book h 410,008 185,424 16.7min 1.9d 38.5d 123.2d 0 book_staleness book i 98,746 4,256 31ms 196ms 23.6h 104.6d 0 book_staleness book k 436,023 215,700 21.3min 2.2d 38.5d 123.2d 0 book_staleness book m 446,463 315,150 24.1min 2.3d 38.5d 123.2d 0 book_staleness last_trade_price g 45,356 15 85ms 214ms 1.9s 20.1s 0 transport_latency_assumed last_trade_price h 45,196 581 19ms 45ms 447ms 31.0s 0 transport_latency_assumed last_trade_price i 45,200 186 31ms 62ms 475ms 50.0s 0 transport_latency_assumed last_trade_price k 45,577 2,130 14ms 37ms 258ms 29.4s 0 transport_latency_assumed last_trade_price m 45,452 42,897 5ms 13ms 128ms 3.0s 0 transport_latency_assumed market_resolved g 554 not meas. 80ms 218ms 579ms 44.2s 0 transport_latency_assumed market_resolved h 554 2 19ms 43ms 140ms 40.2s 0 transport_latency_assumed market_resolved i 554 14 29ms 62ms 39.4s 56.9s 0 transport_latency_assumed market_resolved k 554 14 14ms 34ms 242ms 57.5s 0 transport_latency_assumed market_resolved m 554 533 4ms 8ms 52ms 39.0s 0 transport_latency_assumed new_market g 993 260 14.3s 30.1s 59.0s 26.4d 0 transport_latency_assumed new_market h 993 253 15.0s 43.6s 1.0min 26.4d 0 transport_latency_assumed new_market i 993 253 14.3s 25.7s 58.9s 1.6min 0 transport_latency_assumed new_market k 993 127 15.9s 46.8s 1.5min 26.4d 0 transport_latency_assumed new_market m 993 413 15.7s 47.0s 59.2s 26.4d 0 transport_latency_assumed price_change g 98,066,413 9,278 79ms 116ms 736ms 24.2s 0 transport_latency_assumed price_change h 98,002,530 982,529 18ms 32ms 266ms 1.7min 0 transport_latency_assumed price_change i 98,047,216 334,469 29ms 42ms 267ms 50.5s 0 transport_latency_assumed price_change k 98,227,350 3,525,285 13ms 28ms 172ms 1.0min 0 transport_latency_assumed price_change m 98,116,204 93,469,083 4ms 11ms 90ms 12.5s 0 transport_latency_assumed tick_size_change g 1,984 not meas. 79ms 95ms 195ms 451ms 0 transport_latency_assumed tick_size_change h 1,984 16 18ms 31ms 130ms 20.3s 0 transport_latency_assumed tick_size_change i 1,984 4 29ms 47ms 644ms 672ms 0 transport_latency_assumed tick_size_change k 1,984 76 13ms 25ms 86ms 461ms 0 transport_latency_assumed tick_size_change m 1,984 1,888 4ms 10ms 45ms 67ms 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-30/02/2026-09-30T02.parquet sha256sum 2026-09-30T02.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.