Hour audit: 2026-09-27T10
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-27T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T10:00:00.000022453+00:00 · last event 2026-09-27T10:59:59.999975690+00:00
VOLUME 107,255,774 rows · 1,144,072,947 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 106,093,102 · g: 106,010,833 · k: 103,173,603 · c: 97,565,855 · i: 96,876,124 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,103,577 (3.83%) · g: 48,831 (0.05%) · k: 12,440,646 (11.60%) · c: 89,911,483 (83.83%) · i: 751,237 (0.70%) (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 107,255,774 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 02c737f185f7e367d07d6daeefe6fc3ff2fb88145271ffb4e38634bf424b9912
the corpus checksum ledger names this file with the same digest
joined 107,258,019 to merged 107,255,774, minus 2,245 (minus 0.0021%)
boundary drops 2,245 · 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-27T16:05:40Z 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,808,773 119,584,973 0-41 16a8d2d57da301f7c61accb75e5087d788eb3491fca66d64287d65ee41d7b672 book 1,213,102 73,255,121 42-46 9215c837b4768dd6530fa9d7394559138be6a2e325831bbddaa8b21ec86a15fb last_trade_price 58,802 3,310,466 47-47 ab57aaa1e4cd337b25c7c491a92f4ebe8c49e400742fc28dd6638f80694e42b8 market_resolved 803 93,587 48-48 17069d7322a7cddfbceaf01f05eb361e771031fe837c576cb6f688fc4adb24ac new_market 1,692 153,321 49-49 c88227984776b1cf80ba4849df79bc4003ae02d5e006bd99823e1fd54b9e66f2 price_change 95,170,230 946,363,617 50-413 9e194f511972129ff58fabde516c504ad11b0abf278bc94540ea4c174e4de098 tick_size_change 2,372 88,006 414-414 124a5db2c4308a3aa5525a55520813bfa8b25013c05bbadf36d82beb92de39d3 EVENT MIX count share price_change 95,170,230 88.73% best_bid_ask 10,808,773 10.08% book 1,213,102 1.13% last_trade_price 58,802 0.05% tick_size_change 2,372 <0.01% new_market 1,692 <0.01% market_resolved 803 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,808,948 10,808,773 175 1,306 FULL book 1,213,112 1,213,102 10 195,959 FULL last_trade_price 58,802 58,802 0 358 FULL market_resolved 803 803 0 46 FULL new_market 1,692 1,692 0 0 FULL price_change 95,172,290 95,170,230 2,060 1,084 FULL tick_size_change 2,372 2,372 0 123 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,853,862 9,153,078 5ms 11ms 123ms 3.6s 0 transport_latency_assumed best_bid_ask g 10,805,029 2,961 77ms 98ms 467ms 18.5s 0 transport_latency_assumed best_bid_ask h 10,806,792 393,493 18ms 24ms 151ms 1.0min 0 transport_latency_assumed best_bid_ask i 9,856,834 42,152 33ms 43ms 107ms 3.0s 0 transport_latency_assumed best_bid_ask k 10,470,799 1,217,089 12ms 17ms 82ms 5.0s 0 transport_latency_assumed book c 975,630 846,129 50.5min 3.0d 45.6d 120.5d 0 book_staleness book g 126,366 3,423 89ms 2.4s 6.6h 120.5d 0 book_staleness book h 122,974 8,607 22ms 97ms 6.0h 101.9d 0 book_staleness book i 741,861 278,343 38.2min 2.5d 42.8d 120.5d 0 book_staleness book k 539,563 76,600 17.5min 2.5d 35.9d 120.5d 0 book_staleness last_trade_price c 52,221 46,734 6ms 23ms 298ms 2.7s 0 transport_latency_assumed last_trade_price g 58,179 81 89ms 560ms 7.4s 18.5s 0 transport_latency_assumed last_trade_price h 58,525 2,935 19ms 52ms 453ms 40.5s 0 transport_latency_assumed last_trade_price i 51,143 399 35ms 76ms 517ms 1.3s 0 transport_latency_assumed last_trade_price k 56,264 8,653 13ms 33ms 230ms 1.5s 0 transport_latency_assumed market_resolved c 591 546 5ms 5.5min 8.4min 8.5min 0 transport_latency_assumed market_resolved g 552 4 80ms 212ms 563ms 45.8s 0 transport_latency_assumed market_resolved h 552 85 20ms 43.8s 55.4s 55.4s 0 transport_latency_assumed market_resolved i 556 109 38ms 5.9min 7.2min 7.2min 0 transport_latency_assumed market_resolved k 512 59 13ms 52ms 52.2s 59.5s 0 transport_latency_assumed new_market c 1,111 471 169ms 7.2min 8.1min 8.2min 0 transport_latency_assumed new_market g 969 178 309ms 27.3s 36.5s 56.9s 0 transport_latency_assumed new_market h 969 293 160ms 29.5s 42.9s 1.2min 0 transport_latency_assumed new_market i 969 311 131ms 26.1s 3.9min 5.9min 0 transport_latency_assumed new_market k 969 439 111ms 29.8s 54.9s 1.6min 0 transport_latency_assumed price_change c 86,680,364 79,862,528 5ms 12ms 173ms 6.7s 0 transport_latency_assumed price_change g 95,017,366 42,184 78ms 118ms 1.2s 18.6s 0 transport_latency_assumed price_change h 95,100,918 3,698,038 18ms 27ms 237ms 1.6min 0 transport_latency_assumed price_change i 86,222,661 429,922 33ms 44ms 191ms 3.9s 0 transport_latency_assumed price_change k 92,103,260 11,137,558 12ms 19ms 117ms 7.3s 0 transport_latency_assumed tick_size_change c 2,076 1,997 5ms 8ms 26ms 63ms 0 transport_latency_assumed tick_size_change g 2,372 not meas. 77ms 92ms 216ms 302ms 0 transport_latency_assumed tick_size_change h 2,372 126 18ms 21ms 42ms 96ms 0 transport_latency_assumed tick_size_change i 2,100 1 33ms 40ms 64ms 101ms 0 transport_latency_assumed tick_size_change k 2,236 248 12ms 16ms 31ms 116ms 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/10/2026-09-27T10.parquet sha256sum 2026-09-27T10.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.