Hour audit: 2026-09-27T02
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-27T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T02:00:00.000092223+00:00 · last event 2026-09-27T02:59:59.999971121+00:00
VOLUME 137,074,971 rows · 1,539,825,465 bytes (1.43 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured g: 128,446,485 · h: 123,166,698 · i: 123,035,517 · k: 122,922,187 · c: 100,636,557 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 184,422 (0.13%) · h: 5,817,056 (4.24%) · i: 3,497,166 (2.55%) · k: 34,058,924 (24.85%) · c: 93,517,403 (68.22%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 cb771b53d359ef46b0b5a48c4b90113e81bc451b74f7a714911cbd5cba2bb01c
the corpus checksum ledger names this file with the same digest
joined 137,079,867 to merged 137,074,971, minus 4,896 (minus 0.0036%)
boundary drops 4,896 · 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-28T16:38:49Z 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 15,062,914 170,580,193 0-57 a9e0b743a8ad09c476b4afb96ae3319df35bb259c0400be941ba210cdc424a43 book 3,226,133 105,704,083 58-70 f042162d2c00a9731a8bd2a83eb3dc23c78fc3fc93cc5665b3a4e9057b598982 last_trade_price 46,506 2,724,404 71-71 be8ccca3a0c1c16980395e6b6207ed3bc5957cff38fb5457628f656ee986b90e market_resolved 21,867 1,371,582 72-72 159329944edc81af5aa32d32666360d3c2a4e98033479b904b2893f92d41dcec new_market 5,445 365,752 73-73 4d2815f3145c3f7c9e53ed828293b0a0edda3f1c6f3f6e780cfdafd50acb9d6c price_change 118,702,690 1,257,180,755 74-526 f8f35ee751c03e0dcb821cd3e234e0d147490b4e7e75bedb5b675f7e3a9a9382 tick_size_change 9,416 341,860 527-527 f36587bad696448363a39d54148a021ce81012c40d9a061d98f6514267167153 EVENT MIX count share price_change 118,702,690 86.60% best_bid_ask 15,062,914 10.99% book 3,226,133 2.35% last_trade_price 46,506 0.03% market_resolved 21,867 0.02% tick_size_change 9,416 <0.01% new_market 5,445 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,063,160 15,062,914 246 5,155 FULL book 3,228,503 3,226,133 2,370 2,206 FULL last_trade_price 46,507 46,506 1 798 FULL market_resolved 21,938 21,867 71 3,245 FULL new_market 5,467 5,445 22 837 FULL price_change 118,704,876 118,702,690 2,186 3,545 FULL tick_size_change 9,416 9,416 0 666 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,106,613 10,336,904 5ms 13ms 119ms 3.0s 0 transport_latency_assumed best_bid_ask g 14,413,904 8,536 80ms 109ms 381ms 15.3s 0 transport_latency_assumed best_bid_ask h 13,801,099 599,007 19ms 62ms 241ms 45.8s 0 transport_latency_assumed best_bid_ask i 13,803,811 352,116 20ms 28ms 101ms 3.9s 0 transport_latency_assumed best_bid_ask k 13,790,204 3,766,351 14ms 22ms 118ms 7.4s 0 transport_latency_assumed book c 2,767,112 2,638,093 1.6h 6.4d 46.3d 120.2d 0 book_staleness book g 504,644 99,496 23.1min 5.2d 39.0d 120.2d 0 book_staleness book h 902,586 212,521 57.2min 5.3d 45.3d 120.2d 0 book_staleness book i 912,699 195,396 57.8min 5.2d 45.3d 120.2d 0 book_staleness book k 909,018 80,627 57.6min 5.2d 45.3d 120.2d 0 book_staleness last_trade_price c 32,560 29,326 6ms 22ms 214ms 1.7s 0 transport_latency_assumed last_trade_price g 43,822 58 84ms 222ms 3.6s 15.4s 0 transport_latency_assumed last_trade_price h 42,750 2,584 22ms 72ms 475ms 10.0s 0 transport_latency_assumed last_trade_price i 42,428 1,690 21ms 42ms 203ms 3.2s 0 transport_latency_assumed last_trade_price k 42,357 12,848 15ms 33ms 213ms 7.2s 0 transport_latency_assumed market_resolved c 20,116 18,461 18.1min 1.0h 1.3h 1.4h 0 transport_latency_assumed market_resolved g 5,320 479 84ms 52.9s 7.8min 8.4min 0 transport_latency_assumed market_resolved h 5,423 971 28ms 5.1min 7.8min 8.2min 0 transport_latency_assumed market_resolved i 5,562 607 22ms 6.3min 11.6min 12.1min 0 transport_latency_assumed market_resolved k 5,676 1,349 15ms 6.7min 12.2min 12.7min 0 transport_latency_assumed new_market c 4,895 4,078 14.3min 58.7min 1.2h 1.3h 0 transport_latency_assumed new_market g 1,431 91 249ms 45.4s 7.6min 7.8min 0 transport_latency_assumed new_market h 1,416 301 101ms 39.7s 6.9min 8.2min 0 transport_latency_assumed new_market i 1,438 551 65ms 1.2min 7.5min 9.0min 0 transport_latency_assumed new_market k 1,446 424 86ms 2.3min 9.0min 9.1min 0 transport_latency_assumed price_change c 86,697,493 80,483,095 5ms 14ms 128ms 5.3s 0 transport_latency_assumed price_change g 113,468,064 75,754 81ms 120ms 543ms 15.4s 0 transport_latency_assumed price_change h 108,404,624 5,001,403 19ms 63ms 258ms 45.9s 0 transport_latency_assumed price_change i 108,260,787 2,946,696 20ms 30ms 121ms 4.0s 0 transport_latency_assumed price_change k 108,164,686 30,195,742 14ms 24ms 129ms 7.6s 0 transport_latency_assumed tick_size_change c 7,768 7,446 5ms 9ms 40ms 604ms 0 transport_latency_assumed tick_size_change g 9,300 8 80ms 97ms 315ms 5.3s 0 transport_latency_assumed tick_size_change h 8,800 269 18ms 51ms 90ms 1.8s 0 transport_latency_assumed tick_size_change i 8,792 110 20ms 24ms 56ms 141ms 0 transport_latency_assumed tick_size_change k 8,800 1,583 14ms 17ms 54ms 647ms 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/02/2026-09-27T02.parquet sha256sum 2026-09-27T02.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.