Hour audit: 2026-09-15T18
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-15T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T18:00:00.000333269+00:00 · last event 2026-09-15T18:59:59.999976309+00:00
VOLUME 136,497,710 rows · 1,535,900,483 bytes (1.43 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 132,840,759 · e: 132,216,375 · g: 121,378,198 · f: 120,680,948 · c: 89,250,262 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 48,398,373 (35.46%) · e: 2,476,978 (1.81%) · g: 195,711 (0.14%) · f: 1,561,300 (1.14%) · c: 83,865,348 (61.44%) (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 136,497,710 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d12d511e096b01051d71a5fafd972e11f8ba4d0f3527af281d9eaabc977bc951
the corpus checksum ledger names this file with the same digest
joined 136,501,044 to merged 136,497,710, minus 3,334 (minus 0.0024%)
boundary drops 3,334 · 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-15T20:02:49Z 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 13,560,212 160,525,638 0-51 19885e2bc1d7e521e82d32ec643e379fff9d9b6fe5a71bfc1a9dbb2f6a2ba3f4 book 3,690,718 128,850,557 52-66 6258536a9419dc1fba86f86ae573cc18b93bdd4f01e2561f4be7c3e80fb0bf81 last_trade_price 77,075 4,412,576 67-67 f5c16d460707cd61aeb97a8c0c466287cd40119d2c6bbb0b8168d03d00941345 market_resolved 1,544 123,360 68-68 4f4e6e408b99add2f1a05c4dc7f216f46494e2ae137f7cec6e01b3f52e9af11a new_market 1,359 102,678 69-69 7d936211704e0ee22ae45bd0bbb6d876aecd6a38b2e79e831cdf43f9b66bb964 price_change 119,162,606 1,240,180,547 70-524 2f9af5ffcb6dd2c502e55e346c45fe56527109f250c6e5b4db016a2ea194c935 tick_size_change 4,196 153,852 525-525 1d304e1c451abd16f60637a1f3d8436f82d6150c132f46877ba0ab805ae6898d EVENT MIX count share price_change 119,162,606 87.30% best_bid_ask 13,560,212 9.93% book 3,690,718 2.70% last_trade_price 77,075 0.06% tick_size_change 4,196 <0.01% market_resolved 1,544 <0.01% new_market 1,359 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,560,580 13,560,212 368 6,597 FULL book 3,691,626 3,690,718 908 172,110 FULL last_trade_price 77,075 77,075 0 987 FULL market_resolved 1,544 1,544 0 57 FULL new_market 1,359 1,359 0 9 FULL price_change 119,164,664 119,162,606 2,058 3,096 FULL tick_size_change 4,196 4,196 0 465 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,917,232 8,416,245 6ms 16ms 89ms 2.0s 0 transport_latency_assumed best_bid_ask e 13,541,698 227,125 42ms 59ms 259ms 48.9s 0 transport_latency_assumed best_bid_ask f 12,234,270 111,800 45ms 62ms 216ms 28.0s 0 transport_latency_assumed best_bid_ask g 12,394,637 3,229 86ms 157ms 563ms 1.0min 0 transport_latency_assumed best_bid_ask h 13,556,310 4,801,813 20ms 34ms 112ms 16.3s 0 transport_latency_assumed book c 3,280,405 3,239,610 5.4min 3.2d 38.1d 108.9d 0 book_staleness book e 166,969 12,703 48ms 5.2s 38.9min 90.2d 0 book_staleness book f 803,401 238,422 3.7min 23.9h 35.0d 108.9d 0 book_staleness book g 778,027 138,101 3.7min 23.2h 35.0d 108.9d 0 book_staleness book h 164,823 61,882 25ms 97ms 19.9min 90.3d 0 book_staleness last_trade_price c 49,928 45,858 13ms 56ms 806ms 5.0s 0 transport_latency_assumed last_trade_price e 74,454 1,535 61ms 1.4s 8.6s 23.2s 0 transport_latency_assumed last_trade_price f 69,502 959 64ms 751ms 10.0s 15.5s 0 transport_latency_assumed last_trade_price g 67,533 69 118ms 1.9s 15.3s 30.7s 0 transport_latency_assumed last_trade_price h 76,627 28,654 28ms 86ms 381ms 6.6s 0 transport_latency_assumed market_resolved c 1,264 1,211 5.1min 15.6min 26.0min 26.3min 0 transport_latency_assumed market_resolved e 697 8 47ms 337ms 58.7s 1.0min 0 transport_latency_assumed market_resolved f 683 46 48ms 407ms 5.2min 6.9min 0 transport_latency_assumed market_resolved g 679 42 112ms 502ms 4.7min 4.7min 0 transport_latency_assumed market_resolved h 696 237 23ms 120ms 57.6s 1.0min 0 transport_latency_assumed new_market c 1,149 930 3.8min 13.4min 14.9min 1.2h 0 transport_latency_assumed new_market e 591 73 165ms 12.7s 18.7s 1.0min 0 transport_latency_assumed new_market f 593 103 154ms 12.2s 20.2s 2.3h 0 transport_latency_assumed new_market g 591 52 252ms 12.6s 19.5s 6.7min 0 transport_latency_assumed new_market h 591 201 83ms 12.6s 45.9s 1.5min 0 transport_latency_assumed price_change c 76,997,508 72,158,814 7ms 19ms 149ms 2.0s 0 transport_latency_assumed price_change e 118,427,770 2,235,462 42ms 82ms 3.6s 49.0s 0 transport_latency_assumed price_change f 107,568,735 1,209,962 45ms 83ms 1.6s 28.0s 0 transport_latency_assumed price_change g 108,132,911 54,218 87ms 197ms 4.9s 1.0min 0 transport_latency_assumed price_change h 119,037,516 43,504,150 20ms 39ms 177ms 17.7s 0 transport_latency_assumed tick_size_change c 2,776 2,680 6ms 13ms 39ms 74ms 0 transport_latency_assumed tick_size_change e 4,196 72 41ms 49ms 108ms 3.4s 0 transport_latency_assumed tick_size_change f 3,764 8 44ms 63ms 390ms 949ms 0 transport_latency_assumed tick_size_change g 3,820 not meas. 85ms 134ms 236ms 483ms 0 transport_latency_assumed tick_size_change h 4,196 1,436 20ms 33ms 80ms 587ms 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/18/2026-09-15T18.parquet sha256sum 2026-09-15T18.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.