Hour audit: 2026-09-15T13
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-15T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T13:00:00.000565659+00:00 · last event 2026-09-15T13:59:59.999924651+00:00
VOLUME 106,020,291 rows · 1,136,963,072 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 105,716,236 · c: 105,495,153 · e: 105,474,565 · h: 105,458,520 · f: 105,418,586 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 557,705 (0.53%) · c: 100,350,696 (94.65%) · e: 337,320 (0.32%) · h: 4,605,884 (4.34%) · f: 168,686 (0.16%) (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 106,020,291 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 34eca116e683d25a0411180bddea544cd2c04459559bfa8d800921a5ac60033c
the corpus checksum ledger names this file with the same digest
joined 106,022,204 to merged 106,020,291, minus 1,913 (minus 0.0018%)
boundary drops 1,913 · 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-15T14:59:32Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 11,407,396 128,159,764 0-43 2ad09a929af933b164235c3ee3caada0524149b2498eead7d1ef3dd74fd950b9 book 636,502 57,363,448 44-46 1eefcc3a3dd0ffc611d469e6329dcbcef05bd12574bcc92bd0cfc98a267e8dc3 last_trade_price 61,582 3,467,072 47-47 7a1448740197309880802080b02d1d64a1dde3f6b00a31e0aa5d997de9a09c76 market_resolved 994 152,632 48-48 b32f927ed93860636c902bb4fc7fbd61d03d5248c41b756b23127cb18ad63bcf new_market 989 104,880 49-49 fcb0837303bc159e675577994a41bfe24aed3ec914f6cceee41d05e81a8aab97 price_change 93,909,508 946,385,264 50-408 94dfa4b327f93741e3396138d923e8a03b3c0b6a3d3d044ee74207c7c9f84656 tick_size_change 3,320 120,732 409-409 bbf107d875cfc42f1b460d75154fd12e13f4056beb32296d861f87476af9dffc EVENT MIX count share price_change 93,909,508 88.58% best_bid_ask 11,407,396 10.76% book 636,502 0.60% last_trade_price 61,582 0.06% tick_size_change 3,320 <0.01% market_resolved 994 <0.01% new_market 989 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,407,652 11,407,396 256 196 FULL book 636,544 636,502 42 169,313 FULL last_trade_price 61,583 61,582 1 1 FULL market_resolved 994 994 0 0 FULL new_market 989 989 0 0 FULL price_change 93,911,122 93,909,508 1,614 176 FULL tick_size_change 3,320 3,320 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,406,409 10,905,502 5ms 12ms 77ms 3.4s 0 transport_latency_assumed best_bid_ask e 11,405,331 28,354 38ms 46ms 171ms 6.4s 0 transport_latency_assumed best_bid_ask f 11,404,761 11,191 45ms 55ms 178ms 8.3s 0 transport_latency_assumed best_bid_ask g 11,393,197 3,428 78ms 102ms 347ms 16.5s 0 transport_latency_assumed best_bid_ask h 11,405,408 458,921 18ms 25ms 105ms 11.1s 0 transport_latency_assumed book c 131,148 121,879 7ms 29ms 1.1h 90.1d 0 book_staleness book e 130,309 2,666 41ms 186ms 13.6min 90.1d 0 book_staleness book f 132,243 3,272 48ms 247ms 1.9h 90.1d 0 book_staleness book g 626,712 499,475 3.9min 1.3d 34.8d 108.6d 0 book_staleness book h 130,652 9,210 21ms 63ms 22.9min 90.0d 0 book_staleness last_trade_price c 61,385 57,932 11ms 46ms 211ms 5.0s 0 transport_latency_assumed last_trade_price e 61,418 189 47ms 161ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 61,285 166 54ms 171ms 2.1s 7.1s 0 transport_latency_assumed last_trade_price g 60,732 194 92ms 276ms 6.3s 16.5s 0 transport_latency_assumed last_trade_price h 61,345 3,101 24ms 70ms 306ms 7.0s 0 transport_latency_assumed market_resolved c 936 881 6ms 17ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 936 57 41ms 236ms 59.8s 1.0min 0 transport_latency_assumed market_resolved f 936 4 47ms 276ms 59.9s 1.0min 0 transport_latency_assumed market_resolved g 936 24 85ms 250ms 713ms 1.1s 0 transport_latency_assumed market_resolved h 936 28 20ms 95ms 59.9s 1.0min 0 transport_latency_assumed new_market c 679 453 71ms 17.0s 29.4s 1.4min 0 transport_latency_assumed new_market e 679 106 186ms 20.2s 30.2s 1.1min 0 transport_latency_assumed new_market f 679 115 177ms 18.9s 30.1s 1.1min 0 transport_latency_assumed new_market g 679 68 273ms 15.7s 30.0s 34.0s 0 transport_latency_assumed new_market h 679 247 96ms 407ms 28.8s 1.1min 0 transport_latency_assumed price_change c 93,891,276 89,260,904 5ms 13ms 115ms 4.6s 0 transport_latency_assumed price_change e 93,872,572 305,938 39ms 56ms 359ms 9.8s 0 transport_latency_assumed price_change f 93,815,362 153,938 45ms 65ms 362ms 9.7s 0 transport_latency_assumed price_change g 93,630,660 54,516 78ms 123ms 841ms 16.5s 0 transport_latency_assumed price_change h 93,856,180 4,134,212 18ms 30ms 173ms 11.3s 0 transport_latency_assumed tick_size_change c 3,320 3,145 5ms 13ms 59ms 334ms 0 transport_latency_assumed tick_size_change e 3,320 10 39ms 61ms 157ms 394ms 0 transport_latency_assumed tick_size_change f 3,320 not meas. 45ms 59ms 153ms 289ms 0 transport_latency_assumed tick_size_change g 3,320 not meas. 78ms 124ms 341ms 1.1s 0 transport_latency_assumed tick_size_change h 3,320 165 18ms 28ms 89ms 2.9s 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-15/13/2026-09-15T13.parquet sha256sum 2026-09-15T13.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.