Hour audit: 2026-09-02T21
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-02T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T21:00:00.038258362+00:00 · last event 2026-09-02T21:59:59.999985412+00:00
VOLUME 99,843,674 rows · 1,018,859,974 bytes (971.66 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 99,531,269 · h: 99,475,005 · b: 99,348,193 · e: 99,114,284 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 136,535 (0.14%) · h: 517,871 (0.52%) · b: 76,281 (0.08%) · e: 99,112,987 (99.27%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 99,843,674 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 694aecd6e1def8ad2317f640273af7ea15107ed4f30c8f408b9262d034c5947b
the corpus checksum ledger names this file with the same digest
joined 99,845,435 to merged 99,843,674, minus 1,761 (minus 0.0018%)
boundary drops 1,761 · 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-02T23:01:14Z as bceh
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,914,498 130,240,273 0-45 1f7cc685f3b90a72278fac346ddd46dabbe5c93c2668f1d5bc5212391376cdaf book 565,058 51,517,496 46-48 c14cdd5fcb427f3ea721318a597bd3ea00903910b9e0f908df29d7aa04b8892c last_trade_price 50,976 2,926,695 49-49 0520e9286cf1da5531cb8028b487f3e3f4822865eecf6b3f85b9d78e8258c622 market_resolved 1,736 270,993 50-50 c35dd67c3e8380572e901a55be8dd2d0e1ea30642d44be747c7f164e51a9813e new_market 2,148 216,388 51-51 12e4cac1d38465d29b9a398d3b1da1d0ccfa6231f63fda95dad696128a221f70 price_change 87,305,370 832,403,772 52-385 5779091a6285acac40e61c3417bd2d9b806536fd283dd4a54481924d1ed6979f tick_size_change 3,888 143,806 386-386 9f31fd05c4568348288ab2fe92da30eef95ae6e174421e59372809373d225b4e EVENT MIX count share price_change 87,305,370 87.44% best_bid_ask 11,914,498 11.93% book 565,058 0.57% last_trade_price 50,976 0.05% tick_size_change 3,888 <0.01% new_market 2,148 <0.01% market_resolved 1,736 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,914,653 11,914,498 155 203 FULL book 565,244 565,058 186 151,247 FULL last_trade_price 50,976 50,976 0 2 FULL market_resolved 1,736 1,736 0 0 FULL new_market 2,148 2,148 0 0 FULL price_change 87,306,790 87,305,370 1,420 131 FULL tick_size_change 3,888 3,888 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,906,770 18 55ms 92ms 574ms 30.2s 0 transport_latency_assumed best_bid_ask c 11,911,912 5,482 5ms 9ms 157ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,897,655 11,897,542 47ms 105ms 705ms 23.2s 0 transport_latency_assumed best_bid_ask h 11,899,879 11,456 17ms 29ms 231ms 7.6s 0 transport_latency_assumed book b 225,151 74,837 10.1s 2.3h 25.3d 96.0d 0 book_staleness book c 269,853 118,570 29.2s 2.6h 25.3d 96.0d 0 book_staleness book e 243,418 243,354 16.7s 2.4h 25.3d 96.0d 0 book_staleness book h 254,717 128,297 20.7s 2.5h 25.3d 96.0d 0 book_staleness last_trade_price b 50,033 1 85ms 3.2s 14.2s 30.4s 0 transport_latency_assumed last_trade_price c 50,954 184 11ms 46ms 264ms 4.8s 0 transport_latency_assumed last_trade_price e 49,970 49,970 77ms 3.5s 15.1s 23.3s 0 transport_latency_assumed last_trade_price h 50,618 821 27ms 556ms 3.3s 5.9s 0 transport_latency_assumed market_resolved b 1,703 29 61ms 245ms 1.1s 1.0min 0 transport_latency_assumed market_resolved c 1,703 not meas. 5ms 10ms 55.2s 58.5s 0 transport_latency_assumed market_resolved e 1,703 1,703 48ms 300ms 56.7s 1.1min 0 transport_latency_assumed market_resolved h 1,703 4 19ms 90ms 56.7s 1.0min 0 transport_latency_assumed new_market b 1,374 113 250ms 27.0s 1.9min 2.7min 0 transport_latency_assumed new_market c 1,374 312 67ms 26.1s 2.0min 4.3min 0 transport_latency_assumed new_market e 1,374 1,374 219ms 28.2s 2.0min 2.2min 0 transport_latency_assumed new_market h 1,374 349 119ms 26.2s 1.9min 2.2min 0 transport_latency_assumed price_change b 87,159,278 1,283 56ms 113ms 1.7s 30.4s 0 transport_latency_assumed price_change c 87,291,585 11,987 5ms 9ms 196ms 3.6s 0 transport_latency_assumed price_change e 86,916,276 86,915,156 47ms 129ms 2.6s 23.3s 0 transport_latency_assumed price_change h 87,262,834 376,944 17ms 30ms 411ms 7.7s 0 transport_latency_assumed tick_size_change b 3,884 not meas. 55ms 102ms 436ms 4.5s 0 transport_latency_assumed tick_size_change c 3,888 not meas. 5ms 8ms 84ms 686ms 0 transport_latency_assumed tick_size_change e 3,888 3,888 47ms 129ms 362ms 989ms 0 transport_latency_assumed tick_size_change h 3,880 not meas. 17ms 35ms 116ms 776ms 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-02/21/2026-09-02T21.parquet sha256sum 2026-09-02T21.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.