Hour audit: 2026-09-28T15
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-28T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T15:00:00.000120259+00:00 · last event 2026-09-28T15:59:59.999888508+00:00
VOLUME 107,070,564 rows · 1,161,023,982 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 106,989,394 · c: 106,947,838 · k: 104,860,088 · h: 104,613,152 · g: 102,277,058 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,145,680 (2.00%) · c: 89,619,328 (83.70%) · k: 11,144,604 (10.41%) · h: 4,109,149 (3.84%) · g: 51,803 (0.05%) (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,070,564 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c7e86118e26fc054cdd5ceb417f92725a44911b12fe17f1da3edab6cde5a9cd5
the corpus checksum ledger names this file with the same digest
joined 107,072,668 to merged 107,070,564, minus 2,104 (minus 0.0020%)
boundary drops 2,104 · 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-28T18:07: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 9,987,444 120,673,089 0-38 ed9e9ea24676b288bfec2f9eebb94def7e6eef6380c54a6ef9daa14e66585f0e book 182,093 18,389,478 39-39 cd6c601cd7bfa304b2451e519ea0851697ce6b4f0566380e7d61bab119b72410 last_trade_price 59,429 3,444,061 40-40 8b647cb81b4109e2313e35076fcafb3b68ac267bb00a45c3c277c51d64e3e9bb market_resolved 788 125,855 41-41 6df0bf3145b485c2de5768d4e7531b58924c37900d1dad03e83bb281cd4d88d4 new_market 5,922 661,202 42-42 9f89ee5e25e3854239ea04c02b1f6a15d2dc6d7796e07c1a0e000f3d3748703a price_change 96,832,644 1,016,424,422 43-412 6ba856310fcc1154d29f81bdfa7ddc37c539e62ee6c25d0941606fba7a60fb4a tick_size_change 2,244 84,010 413-413 462964d17084dca7c2e891bf10614058420c6d314ac20a81feea249865748da1 EVENT MIX count share price_change 96,832,644 90.44% best_bid_ask 9,987,444 9.33% book 182,093 0.17% last_trade_price 59,429 0.06% new_market 5,922 <0.01% tick_size_change 2,244 <0.01% market_resolved 788 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,987,658 9,987,444 214 1,343 FULL book 182,093 182,093 0 15,358 FULL last_trade_price 59,429 59,429 0 166 FULL market_resolved 788 788 0 37 FULL new_market 5,922 5,922 0 0 FULL price_change 96,834,534 96,832,644 1,890 1,657 FULL tick_size_change 2,244 2,244 0 32 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,985,910 8,448,466 6ms 33ms 323ms 6.8s 0 transport_latency_assumed best_bid_ask g 9,778,520 2,394 82ms 236ms 3.8s 36.7s 0 transport_latency_assumed best_bid_ask h 9,754,101 361,705 19ms 43ms 566ms 1.7min 0 transport_latency_assumed best_bid_ask i 9,985,800 188,000 22ms 44ms 274ms 36.4s 0 transport_latency_assumed best_bid_ask k 9,838,356 986,879 13ms 36ms 280ms 41.1s 0 transport_latency_assumed book c 133,919 107,689 9ms 1.7s 14.6h 103.2d 0 book_staleness book g 134,008 24,117 236ms 55.9min 19.9d 103.2d 0 book_staleness book h 129,491 9,174 26ms 650ms 4.8h 103.2d 0 book_staleness book i 147,975 24,269 36ms 6.6min 9.9d 103.2d 0 book_staleness book k 126,444 16,844 19ms 770ms 15.0h 103.2d 0 book_staleness last_trade_price c 59,227 49,558 7ms 49ms 423ms 7.0s 0 transport_latency_assumed last_trade_price g 50,407 19 151ms 5.7s 20.4s 33.4s 0 transport_latency_assumed last_trade_price h 58,754 2,316 20ms 125ms 896ms 49.8s 0 transport_latency_assumed last_trade_price i 59,257 1,071 25ms 166ms 951ms 6.0s 0 transport_latency_assumed last_trade_price k 56,419 6,465 14ms 66ms 359ms 6.8s 0 transport_latency_assumed market_resolved c 778 643 7ms 67ms 46.4s 53.6s 0 transport_latency_assumed market_resolved g 765 3 90ms 436ms 36.3s 1.7min 0 transport_latency_assumed market_resolved h 764 32 20ms 99ms 45.2s 52.4s 0 transport_latency_assumed market_resolved i 778 33 24ms 146ms 30.6s 57.4s 0 transport_latency_assumed market_resolved k 768 77 15ms 79ms 46.9s 1.4min 0 transport_latency_assumed new_market c 4,274 1,563 122ms 3.7min 5.7min 5.8min 0 transport_latency_assumed new_market g 4,274 468 280ms 3.6min 5.6min 5.7min 0 transport_latency_assumed new_market h 4,274 1,192 123ms 3.3min 5.6min 5.7min 0 transport_latency_assumed new_market i 4,274 1,907 99ms 3.7min 5.6min 5.7min 0 transport_latency_assumed new_market k 4,274 792 155ms 3.6min 5.6min 5.7min 0 transport_latency_assumed price_change c 96,761,486 81,009,448 6ms 39ms 350ms 7.2s 0 transport_latency_assumed price_change g 92,306,880 24,802 85ms 503ms 13.6s 37.0s 0 transport_latency_assumed price_change h 94,663,580 3,734,689 19ms 58ms 719ms 1.7min 0 transport_latency_assumed price_change i 96,789,066 1,930,392 23ms 61ms 445ms 40.0s 0 transport_latency_assumed price_change k 94,831,615 10,133,313 13ms 44ms 295ms 54.0s 0 transport_latency_assumed tick_size_change c 2,244 1,961 6ms 22ms 404ms 469ms 0 transport_latency_assumed tick_size_change g 2,204 not meas. 80ms 127ms 780ms 8.0s 0 transport_latency_assumed tick_size_change h 2,188 41 19ms 29ms 351ms 897ms 0 transport_latency_assumed tick_size_change i 2,244 8 22ms 31ms 338ms 483ms 0 transport_latency_assumed tick_size_change k 2,212 234 12ms 21ms 266ms 400ms 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-28/15/2026-09-28T15.parquet sha256sum 2026-09-28T15.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.