Hour audit: 2026-09-29T21
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-29T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T21:00:00.000034039+00:00 · last event 2026-09-29T21:59:59.999705851+00:00
VOLUME 90,211,792 rows · 958,518,047 bytes (914.11 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 89,987,474 · c: 89,978,139 · i: 89,963,256 · h: 89,792,776 · g: 89,785,040 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,428,078 (6.02%) · c: 82,857,416 (91.85%) · i: 1,002,181 (1.11%) · h: 860,763 (0.95%) · g: 63,354 (0.07%) (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 90,211,792 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5fd67eba280414ef414bd7c6e047004607bae62ab7838b1967b7b5f41d070b66
the corpus checksum ledger names this file with the same digest
joined 90,215,368 to merged 90,211,792, minus 3,576 (minus 0.0040%)
boundary drops 3,576 · 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-30T00:09:48Z 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,062,004 118,862,633 0-38 5b1734f52775c1a29266d4e4512f4990c30cc7dec2915c1ac92aab4df26c1c68 book 316,913 30,860,631 39-40 b2b5449f726dfcf689a96680926be86ee95a516263f0f2da7a2e66cc0ff24c91 last_trade_price 44,130 2,589,507 41-41 b47b15e32f23a816f2abe4c7d73a3b76364f5fba5fe8d02958774198e9d3c302 market_resolved 1,107 157,648 42-42 122f59d5bbc11239803f5f39d57c67db5f279e5004892cb61cc66366ca523656 new_market 1,472 143,478 43-43 7559c02961a142d6ecdc3b4d0204b185b3f99fe85b2434828630e01cfc22cd01 price_change 79,782,646 804,741,349 44-348 db1097ac3820afb80fd8cff839e715a925f87e65842d2598a80ed4862e38265e tick_size_change 3,520 129,509 349-349 5824641c3b333e078df98f9d18a6d820c931e8bc8fd67396859dd920f385a595 EVENT MIX count share price_change 79,782,646 88.44% best_bid_ask 10,062,004 11.15% book 316,913 0.35% last_trade_price 44,130 0.05% tick_size_change 3,520 <0.01% new_market 1,472 <0.01% market_resolved 1,107 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,062,320 10,062,004 316 249 FULL book 317,147 316,913 234 100,334 FULL last_trade_price 44,132 44,130 2 11 FULL market_resolved 1,107 1,107 0 1 FULL new_market 1,472 1,472 0 0 FULL price_change 79,785,670 79,782,646 3,024 305 FULL tick_size_change 3,520 3,520 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,060,032 9,316,999 5ms 11ms 192ms 18.9s 0 transport_latency_assumed best_bid_ask g 10,056,768 1,774 79ms 98ms 456ms 31.8s 0 transport_latency_assumed best_bid_ask h 10,045,331 83,880 19ms 35ms 523ms 2.5min 0 transport_latency_assumed best_bid_ask i 10,059,758 95,022 21ms 25ms 134ms 6.8s 0 transport_latency_assumed best_bid_ask k 10,059,913 564,329 12ms 18ms 129ms 21.0s 0 transport_latency_assumed book c 149,294 130,929 14ms 18.1h 24.3d 104.5d 0 book_staleness book g 139,769 44,283 206ms 14.8h 24.3d 104.5d 0 book_staleness book h 151,392 56,759 73ms 18.1h 24.3d 123.0d 0 book_staleness book i 130,684 35,707 30ms 10.5h 22.5d 104.5d 0 book_staleness book k 138,861 49,235 24ms 14.5h 24.3d 123.0d 0 book_staleness last_trade_price c 43,830 39,597 6ms 23ms 378ms 1.8s 0 transport_latency_assumed last_trade_price g 43,166 37 92ms 476ms 10.2s 31.9s 0 transport_latency_assumed last_trade_price h 43,485 463 22ms 131ms 1.3s 45.5s 0 transport_latency_assumed last_trade_price i 43,780 639 23ms 80ms 729ms 1.7s 0 transport_latency_assumed last_trade_price k 43,811 3,394 14ms 35ms 329ms 5.1s 0 transport_latency_assumed market_resolved c 966 914 5ms 10ms 54.8s 55.4s 0 transport_latency_assumed market_resolved g 966 not meas. 81ms 259ms 47.1s 57.6s 0 transport_latency_assumed market_resolved h 965 6 21ms 92ms 48.2s 1.7min 0 transport_latency_assumed market_resolved i 966 161 22ms 38.1s 55.2s 56.9s 0 transport_latency_assumed market_resolved k 966 26 13ms 67ms 55.7s 55.7s 0 transport_latency_assumed new_market c 917 387 152ms 19.1s 1.7min 2.0min 0 transport_latency_assumed new_market g 917 202 352ms 24.8s 1.5min 1.9min 0 transport_latency_assumed new_market h 917 127 203ms 25.1s 1.6min 29.9min 0 transport_latency_assumed new_market i 917 442 77ms 17.3s 1.6min 29.9min 0 transport_latency_assumed new_market k 917 314 182ms 23.1s 1.7min 2.1min 0 transport_latency_assumed price_change c 79,719,580 73,365,334 5ms 13ms 222ms 25.3s 0 transport_latency_assumed price_change g 79,539,934 17,058 79ms 127ms 1.4s 32.1s 0 transport_latency_assumed price_change h 79,547,166 719,489 20ms 43ms 625ms 2.5min 0 transport_latency_assumed price_change i 79,723,631 870,166 21ms 29ms 288ms 7.7s 0 transport_latency_assumed price_change k 79,739,486 4,810,599 12ms 20ms 166ms 21.0s 0 transport_latency_assumed tick_size_change c 3,520 3,256 5ms 13ms 183ms 391ms 0 transport_latency_assumed tick_size_change g 3,520 not meas. 79ms 109ms 645ms 1.0s 0 transport_latency_assumed tick_size_change h 3,520 39 20ms 40ms 1.1s 15.0s 0 transport_latency_assumed tick_size_change i 3,520 44 21ms 30ms 153ms 439ms 0 transport_latency_assumed tick_size_change k 3,520 181 13ms 21ms 92ms 310ms 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/21/2026-09-29T21.parquet sha256sum 2026-09-29T21.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.