Hour audit: 2026-09-06T00
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-06T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T00:00:00.071646666+00:00 · last event 2026-09-06T00:59:59.999996822+00:00
VOLUME 123,541,693 rows · 1,278,311,267 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 121,518,011 · e: 121,517,127 · g: 121,155,223 · f: 116,839,216 · c: 99,598,112 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,681 (0.01%) · e: 19,045 (0.02%) · g: 121,151,704 (98.07%) · f: 778,549 (0.63%) · c: 1,581,714 (1.28%) (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 123,541,693 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a354ed9b26c78e6c33a9b0beda356f6133bc6de09e3b42ce0a7508b2153f9072
the corpus checksum ledger names this file with the same digest
joined 123,545,252 to merged 123,541,693, minus 3,559 (minus 0.0029%)
boundary drops 3,559 · 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-06T03:52:09Z 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 12,403,947 133,552,399 0-47 fcd6df009401980e88f6269eca4aa51000f6c27c816c58d1b5cf60a49aab1724 book 2,066,333 84,698,406 48-55 38ce7a40e65bbd6f0941acf1266720b27c7395f65829b17b69b75a99911a9934 last_trade_price 52,431 2,999,447 56-56 a7a801923b20a37e9187c97b3dc0ae1da893506199ee0789adcb4322a854844a market_resolved 3,850 394,795 57-57 7752862ca96a68ff7ad0a10b45652e82b002499217dfb99536684286334ae44d new_market 1,202 113,624 58-58 c46f2e748f232988be5d312db2635301038246a48feb8145bfb72bc333bf79d3 price_change 109,008,122 1,054,940,394 59-474 61f4c5a5abe249619d116b8ef30ae2a26e35b4ed76cd793ceda44c3c6972aa6b tick_size_change 5,808 208,891 475-475 daf39a4acde2cd7563cf13e428d850fd9d65569a6ac6d1b4b2f7e4aa61e302ad EVENT MIX count share price_change 109,008,122 88.24% best_bid_ask 12,403,947 10.04% book 2,066,333 1.67% last_trade_price 52,431 0.04% tick_size_change 5,808 <0.01% market_resolved 3,850 <0.01% new_market 1,202 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,404,310 12,403,947 363 2,994 FULL book 2,066,365 2,066,333 32 182,033 FULL last_trade_price 52,433 52,431 2 444 FULL market_resolved 3,850 3,850 0 76 FULL new_market 1,202 1,202 0 0 FULL price_change 109,011,284 109,008,122 3,162 2,409 FULL tick_size_change 5,808 5,808 0 130 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,978,954 228 4ms 8ms 72ms 2.0s 0 transport_latency_assumed best_bid_ask e 12,403,125 1,283 41ms 47ms 128ms 1.9s 0 transport_latency_assumed best_bid_ask f 11,895,787 25,547 48ms 57ms 153ms 2.5s 0 transport_latency_assumed best_bid_ask g 12,376,613 12,376,250 82ms 104ms 451ms 23.1s 0 transport_latency_assumed best_bid_ask h 12,403,721 639 18ms 28ms 112ms 20.7s 0 transport_latency_assumed book c 1,940,060 1,574,298 17.6min 12.1h 34.5d 99.1d 0 book_staleness book e 108,435 421 43ms 79ms 962ms 4.5s 0 book_staleness book f 474,656 371,036 2.9min 9.6h 33.2d 99.1d 0 book_staleness book g 120,194 120,194 91ms 22.6s 9.1h 99.1d 0 book_staleness book h 108,861 384 21ms 62ms 2.1s 80.5d 0 book_staleness last_trade_price c 41,771 1 9ms 40ms 319ms 5.0s 0 transport_latency_assumed last_trade_price e 52,414 105 47ms 86ms 628ms 5.0s 0 transport_latency_assumed last_trade_price f 50,367 2,175 55ms 105ms 657ms 5.0s 0 transport_latency_assumed last_trade_price g 50,151 50,149 95ms 163ms 2.5s 23.0s 0 transport_latency_assumed last_trade_price h 52,411 1 23ms 66ms 384ms 5.0s 0 transport_latency_assumed market_resolved c 3,472 1,482 7ms 11.3min 19.7min 20.5min 0 transport_latency_assumed market_resolved e 2,356 4 43ms 121ms 45.5s 58.8s 0 transport_latency_assumed market_resolved f 2,345 24 50ms 128ms 52.4s 4.5min 0 transport_latency_assumed market_resolved g 2,340 2,340 88ms 235ms 50.3s 1.0min 0 transport_latency_assumed market_resolved h 2,356 not meas. 20ms 56ms 47.9s 59.4s 0 transport_latency_assumed new_market c 864 215 84ms 10.9min 2.1h 3.3h 0 transport_latency_assumed new_market e 711 110 118ms 18.3s 1.7min 1.9min 0 transport_latency_assumed new_market f 711 129 131ms 12.4s 1.7min 1.3h 0 transport_latency_assumed new_market g 711 711 216ms 16.6s 1.7min 19.4min 0 transport_latency_assumed new_market h 711 37 94ms 13.7s 1.8min 27.1min 0 transport_latency_assumed price_change c 87,627,651 5,490 4ms 9ms 89ms 3.3s 0 transport_latency_assumed price_change e 108,944,278 17,122 41ms 49ms 158ms 3.4s 0 transport_latency_assumed price_change f 104,409,662 379,638 49ms 59ms 181ms 3.4s 0 transport_latency_assumed price_change g 108,599,406 108,596,252 82ms 122ms 557ms 23.1s 0 transport_latency_assumed price_change h 108,944,143 9,620 18ms 30ms 135ms 20.7s 0 transport_latency_assumed tick_size_change c 5,340 not meas. 4ms 7ms 47ms 239ms 0 transport_latency_assumed tick_size_change e 5,808 not meas. 41ms 45ms 98ms 214ms 0 transport_latency_assumed tick_size_change f 5,688 not meas. 48ms 54ms 122ms 222ms 0 transport_latency_assumed tick_size_change g 5,808 5,808 82ms 133ms 287ms 566ms 0 transport_latency_assumed tick_size_change h 5,808 not meas. 18ms 26ms 83ms 247ms 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-06/00/2026-09-06T00.parquet sha256sum 2026-09-06T00.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.