Hour audit: 2026-09-29T07
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-29T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T07:00:00.000026179+00:00 · last event 2026-09-29T07:59:59.999495687+00:00
VOLUME 93,702,033 rows · 987,547,215 bytes (941.80 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 93,472,468 · g: 93,421,321 · h: 92,605,952 · i: 91,758,663 · c: 91,229,155 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,778,561 (6.17%) · g: 55,185 (0.06%) · h: 1,102,308 (1.18%) · i: 1,256,208 (1.34%) · c: 85,509,771 (91.26%) (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 93,702,033 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 48e1065b997f2ec3e8643d490f4a5a474ce259f60dac62469e0e719664d62ad9
the corpus checksum ledger names this file with the same digest
joined 93,703,407 to merged 93,702,033, minus 1,374 (minus 0.0015%)
boundary drops 1,374 · 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-29T10:11:24Z 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 9,374,436 109,073,817 0-35 5c7b0f4225ac21f3489914db4d100c072e63813e0696c22f8a9b71a58ebae914 book 235,512 23,103,577 36-36 c789fadd5d1f37965d09332ba2b59e623669cbd2f79f20156595b61f86c61696 last_trade_price 52,654 3,004,149 37-37 4b563192e0f7ebf7f905bf4bb6bfa92044b7641623aafd98f2f6db3dce046ac0 market_resolved 789 120,427 38-38 c0c34623d79547202cbe3bd50d4854e55b33496916ee6e0686efb20c0fae4d32 new_market 872 91,936 39-39 9611f0787e2015d3eabed916c264ec2540bb148b483d9e10ba8dd1f4f90ec243 price_change 84,034,962 850,980,328 40-360 ac7924f977ba3a2a4046c3385c71db268979ba88602f88d69d06462cbd12748f tick_size_change 2,808 104,251 361-361 3c274ad080ccb804553146fec4ee3f743ee41beb35d1cde5240ee370c9081d19 EVENT MIX count share price_change 84,034,962 89.68% best_bid_ask 9,374,436 10.00% book 235,512 0.25% last_trade_price 52,654 0.06% tick_size_change 2,808 <0.01% new_market 872 <0.01% market_resolved 789 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,374,592 9,374,436 156 3,068 FULL book 235,512 235,512 0 50,381 FULL last_trade_price 52,654 52,654 0 143 FULL market_resolved 789 789 0 29 FULL new_market 872 872 0 0 FULL price_change 84,036,180 84,034,962 1,218 5,252 FULL tick_size_change 2,808 2,808 0 43 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,092,257 8,570,562 5ms 10ms 94ms 6.6s 0 transport_latency_assumed best_bid_ask g 9,369,704 1,367 78ms 99ms 466ms 17.8s 0 transport_latency_assumed best_bid_ask h 9,332,375 96,926 18ms 26ms 217ms 1.3min 0 transport_latency_assumed best_bid_ask i 9,167,319 111,344 20ms 25ms 121ms 21.0s 0 transport_latency_assumed best_bid_ask k 9,372,624 594,237 13ms 21ms 111ms 19.5s 0 transport_latency_assumed book c 127,135 116,941 7ms 50.9min 17.2d 103.9d 0 book_staleness book g 139,782 34,064 111ms 6.1h 21.9d 122.4d 0 book_staleness book h 158,029 55,129 38ms 9.1h 21.9d 103.9d 0 book_staleness book i 108,257 3,530 22ms 165ms 5.8h 103.9d 0 book_staleness book k 127,063 25,848 17ms 32.2min 13.7d 103.9d 0 book_staleness last_trade_price c 52,055 48,297 6ms 19ms 416ms 3.7s 0 transport_latency_assumed last_trade_price g 51,710 35 88ms 978ms 8.0s 17.8s 0 transport_latency_assumed last_trade_price h 49,803 570 20ms 79ms 1.2s 21.7s 0 transport_latency_assumed last_trade_price i 52,118 792 22ms 102ms 1.1s 6.7s 0 transport_latency_assumed last_trade_price k 52,287 2,960 14ms 51ms 615ms 9.6s 0 transport_latency_assumed market_resolved c 715 660 5ms 14ms 1.1min 2.3min 0 transport_latency_assumed market_resolved g 733 4 78ms 221ms 698ms 35.9s 0 transport_latency_assumed market_resolved h 732 9 19ms 40ms 26.1s 41.7s 0 transport_latency_assumed market_resolved i 722 63 21ms 112ms 54.4s 2.1min 0 transport_latency_assumed market_resolved k 729 53 14ms 35ms 267ms 46.0s 0 transport_latency_assumed new_market c 597 289 118ms 16.9s 37.3s 1.3min 0 transport_latency_assumed new_market g 597 67 351ms 14.9s 1.1min 1.8min 0 transport_latency_assumed new_market h 597 159 178ms 16.2s 35.0s 35.4s 0 transport_latency_assumed new_market i 597 156 162ms 12.7s 49.6s 1.5min 0 transport_latency_assumed new_market k 597 201 182ms 15.5s 37.5s 1.2min 0 transport_latency_assumed price_change c 81,953,712 76,770,474 5ms 12ms 116ms 6.6s 0 transport_latency_assumed price_change g 83,855,987 19,648 78ms 134ms 1.6s 18.0s 0 transport_latency_assumed price_change h 83,061,608 949,468 18ms 33ms 325ms 1.5min 0 transport_latency_assumed price_change i 82,426,890 1,140,302 20ms 30ms 235ms 23.3s 0 transport_latency_assumed price_change k 83,916,360 5,155,070 13ms 25ms 142ms 21.3s 0 transport_latency_assumed tick_size_change c 2,684 2,548 5ms 9ms 68ms 368ms 0 transport_latency_assumed tick_size_change g 2,808 not meas. 78ms 93ms 240ms 1.2s 0 transport_latency_assumed tick_size_change h 2,808 47 19ms 27ms 139ms 255ms 0 transport_latency_assumed tick_size_change i 2,760 21 20ms 34ms 191ms 259ms 0 transport_latency_assumed tick_size_change k 2,808 192 13ms 21ms 90ms 249ms 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/07/2026-09-29T07.parquet sha256sum 2026-09-29T07.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.