Hour audit: 2026-09-17T06
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-17T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T06:00:00.000001950+00:00 · last event 2026-09-17T06:59:59.999945896+00:00
VOLUME 103,720,025 rows · 1,068,752,920 bytes (1019.24 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 103,037,549 · c: 103,016,231 · f: 102,976,144 · g: 102,944,060 · e: 102,609,406 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,032,170 (2.92%) · c: 99,621,081 (96.05%) · f: 332,887 (0.32%) · g: 183,021 (0.18%) · e: 550,866 (0.53%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,720,025 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 26f3bc51b1f17e88594f0410b069633fa8732c3082e1e40fcfb3e5f918413289
the corpus checksum ledger names this file with the same digest
joined 103,722,085 to merged 103,720,025, minus 2,060 (minus 0.0020%)
boundary drops 2,060 · 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-17T07:56:51Z 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,421,201 126,530,771 0-43 cdd936282cbed52b47fa22596630f69e79a26ddc0c660f406d2a0014542ee602 book 1,035,148 74,693,912 44-47 fa1603a347023e3ee7d3891bba0e1a1c5644fb399aafc4740c5d9a59c08d7abe last_trade_price 42,074 2,410,912 48-48 086082ebf98d1d46bfc5488a2a09de706a4c571a9bda8d30960d0d98a85d4b05 market_resolved 598 99,770 49-49 ee36105730cbd1ed949fc4b094f7eb46df085d6b732a7bb89549f0a2a2a0ba92 new_market 1,324 125,873 50-50 726e2d590ad3f4be95db2d63fbd0e490ec515169c275011d9d3cf9c83706190c price_change 91,217,884 863,646,400 51-398 171bccdd9effda6a36a9bd024439fedb85b15b9555ea15a4b691465c0f5d793c tick_size_change 1,796 65,531 399-399 23f210ed2799267ac236f96c2198c1ad8d87f72c3f8046cb4bc364035a380665 EVENT MIX count share price_change 91,217,884 87.95% best_bid_ask 11,421,201 11.01% book 1,035,148 1.00% last_trade_price 42,074 0.04% tick_size_change 1,796 <0.01% new_market 1,324 <0.01% market_resolved 598 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,421,378 11,421,201 177 187 FULL book 1,035,368 1,035,148 220 129,750 FULL last_trade_price 42,075 42,074 1 0 FULL market_resolved 598 598 0 1 FULL new_market 1,324 1,324 0 0 FULL price_change 91,219,546 91,217,884 1,662 68 FULL tick_size_change 1,796 1,796 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,419,258 11,107,185 5ms 8ms 68ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,400,936 27,635 38ms 44ms 120ms 5.5s 0 transport_latency_assumed best_bid_ask f 11,417,314 10,671 46ms 51ms 141ms 7.1s 0 transport_latency_assumed best_bid_ask g 11,416,013 1,244 77ms 94ms 243ms 11.7s 0 transport_latency_assumed best_bid_ask h 11,417,398 274,466 18ms 22ms 104ms 33.9s 0 transport_latency_assumed book c 364,591 255,909 1.8min 13.6h 35.5d 110.3d 0 book_staleness book e 429,263 225,943 2.2min 12.2h 35.5d 110.4d 0 book_staleness book f 380,170 181,027 1.9min 13.5h 35.6d 110.4d 0 book_staleness book g 355,796 160,267 1.7min 12.7h 35.5d 110.3d 0 book_staleness book h 403,429 212,002 2.2min 13.7h 35.6d 110.3d 0 book_staleness last_trade_price c 42,008 40,299 10ms 41ms 190ms 5.0s 0 transport_latency_assumed last_trade_price e 40,654 168 45ms 97ms 461ms 5.5s 0 transport_latency_assumed last_trade_price f 41,935 108 52ms 105ms 403ms 7.1s 0 transport_latency_assumed last_trade_price g 41,899 8 88ms 182ms 790ms 11.7s 0 transport_latency_assumed last_trade_price h 41,945 1,491 23ms 62ms 307ms 11.4s 0 transport_latency_assumed market_resolved c 598 596 5ms 8ms 33ms 113ms 0 transport_latency_assumed market_resolved e 597 1 104ms 149ms 312ms 576ms 0 transport_latency_assumed market_resolved f 597 not meas. 119ms 190ms 316ms 607ms 0 transport_latency_assumed market_resolved g 598 not meas. 204ms 294ms 422ms 902ms 0 transport_latency_assumed market_resolved h 597 1 38ms 62ms 134ms 231ms 0 transport_latency_assumed new_market c 822 526 85ms 22.2s 1.3min 1.7min 0 transport_latency_assumed new_market e 822 231 150ms 20.4s 1.2min 1.7min 0 transport_latency_assumed new_market f 822 185 160ms 25.2s 1.3min 1.7min 0 transport_latency_assumed new_market g 822 56 245ms 20.8s 1.2min 1.7min 0 transport_latency_assumed new_market h 822 326 120ms 24.5s 1.3min 1.6min 0 transport_latency_assumed price_change c 91,187,158 88,214,788 5ms 9ms 102ms 6.5s 0 transport_latency_assumed price_change e 90,735,338 296,888 39ms 45ms 200ms 5.5s 0 transport_latency_assumed price_change f 91,133,510 140,896 46ms 54ms 214ms 7.1s 0 transport_latency_assumed price_change g 91,127,136 21,446 77ms 96ms 350ms 11.8s 0 transport_latency_assumed price_change h 91,171,562 2,543,866 18ms 24ms 165ms 34.0s 0 transport_latency_assumed tick_size_change c 1,796 1,778 5ms 7ms 20ms 77ms 0 transport_latency_assumed tick_size_change e 1,796 not meas. 39ms 52ms 114ms 173ms 0 transport_latency_assumed tick_size_change f 1,796 not meas. 46ms 51ms 99ms 192ms 0 transport_latency_assumed tick_size_change g 1,796 not meas. 78ms 93ms 341ms 574ms 0 transport_latency_assumed tick_size_change h 1,796 18 18ms 22ms 58ms 679ms 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-17/06/2026-09-17T06.parquet sha256sum 2026-09-17T06.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.