Hour audit: 2026-10-01T16
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-10-01T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T16:00:00.000004663+00:00 · last event 2026-10-01T16:59:59.999995770+00:00
VOLUME 118,983,909 rows · 1,272,729,472 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 118,765,919 · k: 118,501,937 · h: 118,488,147 · m: 118,485,873 · g: 118,189,435 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 947,715 (0.80%) · k: 2,496,638 (2.10%) · h: 1,012,658 (0.85%) · m: 114,258,466 (96.03%) · g: 268,432 (0.23%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 811b57ac6a39418e6083002215c4a9584aea64470b9209cfd51a182e6f656c68
the corpus checksum ledger names this file with the same digest
joined 118,986,570 to merged 118,983,909, minus 2,661 (minus 0.0022%)
boundary drops 2,661 · 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-10-01T19:12:00Z as ghikm
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,507,290 123,483,944 0-40 ae2eea1195d12a651d59728c14235be67500392b2e6818a70dbdd445318951fb book 629,872 57,202,160 41-43 46769d41ef5edcaa43bbe0ce08f0846e00b26ace3890f4a062605b28392d7323 last_trade_price 63,579 3,628,151 44-44 a3352c4a70ec1943458e1aea6ec675e98dc599305b6ba5a9a46b239b84f47b02 market_resolved 954 145,208 45-45 43eea09fb62af0881f2e288c38e40119bc2bcaa3cbadb9061fa061a38559f42b new_market 4,922 459,485 46-46 11ebcad4ed2d98304af3ff85956d7fea40bcabba04422f88905080d789d11b7e price_change 107,773,632 1,086,319,936 47-458 cf1dfe26f1d7be1b35e8fc7a99cfbf08f9c0670ab1fc2605a1cad7018232528a tick_size_change 3,660 132,633 459-459 4a2f1aac17d530aa009d06b23183633e3f88eabf5849be8ee626334d9c36fd43 EVENT MIX count share price_change 107,773,632 90.58% best_bid_ask 10,507,290 8.83% book 629,872 0.53% last_trade_price 63,579 0.05% new_market 4,922 <0.01% tick_size_change 3,660 <0.01% market_resolved 954 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,507,503 10,507,290 213 573 FULL book 629,880 629,872 8 176,015 FULL last_trade_price 63,581 63,579 2 7 FULL market_resolved 954 954 0 1 FULL new_market 4,922 4,922 0 0 FULL price_change 107,776,070 107,773,632 2,438 204 FULL tick_size_change 3,660 3,660 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,498,547 18,558 75ms 101ms 685ms 31.2s 0 transport_latency_assumed best_bid_ask h 10,501,148 82,319 21ms 36ms 1.2s 1.1min 0 transport_latency_assumed best_bid_ask i 10,500,883 55,700 32ms 52ms 296ms 49.5s 0 transport_latency_assumed best_bid_ask k 10,502,627 210,518 15ms 28ms 505ms 1.6min 0 transport_latency_assumed best_bid_ask m 10,504,523 10,140,195 5ms 10ms 165ms 10.0s 0 transport_latency_assumed book g 196,309 50,648 94ms 11.4h 26.1d 124.8d 0 book_staleness book h 192,099 48,416 36ms 10.1h 24.3d 124.8d 0 book_staleness book i 498,934 324,497 6.3min 2.7d 40.1d 124.8d 0 book_staleness book k 194,545 50,397 25ms 10.8h 26.1d 124.7d 0 book_staleness book m 172,936 155,914 7ms 3.5h 13.9d 124.7d 0 book_staleness last_trade_price g 62,905 156 76ms 230ms 4.8s 28.5s 0 transport_latency_assumed last_trade_price h 63,551 501 22ms 50ms 1.2s 48.4s 0 transport_latency_assumed last_trade_price i 63,513 391 46ms 59ms 502ms 5.6s 0 transport_latency_assumed last_trade_price k 63,566 1,234 16ms 35ms 686ms 1.1min 0 transport_latency_assumed last_trade_price m 63,553 61,297 6ms 11ms 213ms 6.0s 0 transport_latency_assumed market_resolved g 896 7 77ms 322ms 42.1s 51.0s 0 transport_latency_assumed market_resolved h 897 28 23ms 93ms 55.4s 55.4s 0 transport_latency_assumed market_resolved i 897 43 46ms 229ms 49.2s 52.6s 0 transport_latency_assumed market_resolved k 897 70 16ms 109ms 47.3s 52.2s 0 transport_latency_assumed market_resolved m 897 806 6ms 128ms 50.6s 53.6s 0 transport_latency_assumed new_market g 2,918 709 299ms 36.3s 44.8s 1.7min 0 transport_latency_assumed new_market h 2,918 574 206ms 32.6s 42.2s 1.7min 0 transport_latency_assumed new_market i 2,918 980 182ms 35.2s 44.5s 1.7min 0 transport_latency_assumed new_market k 2,918 515 256ms 35.1s 44.8s 1.3min 0 transport_latency_assumed new_market m 2,918 2,144 81ms 35.9s 42.1s 1.8min 0 transport_latency_assumed price_change g 107,424,200 198,334 75ms 129ms 1.8s 31.4s 0 transport_latency_assumed price_change h 107,723,874 880,798 21ms 37ms 1.2s 1.3min 0 transport_latency_assumed price_change i 107,695,114 566,092 36ms 53ms 355ms 49.5s 0 transport_latency_assumed price_change k 107,733,724 2,233,846 15ms 31ms 515ms 1.6min 0 transport_latency_assumed price_change m 107,737,386 103,894,562 5ms 10ms 172ms 10.2s 0 transport_latency_assumed tick_size_change g 3,660 20 77ms 213ms 830ms 1.6s 0 transport_latency_assumed tick_size_change h 3,660 22 21ms 47ms 2.2s 20.4s 0 transport_latency_assumed tick_size_change i 3,660 12 39ms 54ms 501ms 5.3s 0 transport_latency_assumed tick_size_change k 3,660 58 15ms 32ms 672ms 50.6s 0 transport_latency_assumed tick_size_change m 3,660 3,548 5ms 10ms 244ms 425ms 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-10-01/16/2026-10-01T16.parquet sha256sum 2026-10-01T16.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.