Hour audit: 2026-09-03T15
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-03T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T15:00:00.017746263+00:00 · last event 2026-09-03T15:59:59.999866825+00:00
VOLUME 115,006,159 rows · 1,213,134,390 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 113,806,907 · e: 112,702,678 · b: 103,486,264 · c: 80,113,522 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,423,733 (1.24%) · e: 112,701,393 (98.00%) · b: 561,829 (0.49%) · c: 319,204 (0.28%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 115,006,159 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 8275430c8a274f6ee3e16a41bfd560b3e33dc752d2ae63d9eff88d1da3ff5777
the corpus checksum ledger names this file with the same digest
joined 115,008,157 to merged 115,006,159, minus 1,998 (minus 0.0017%)
boundary drops 1,998 · 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-03T17:38:56Z 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 10,613,784 121,206,055 0-40 1d0dd7821989716a953ec8aa9cd0388e37234237ed420ed7c0d16a8d9eda6c4c book 1,284,373 82,773,196 41-45 fecbabdf8e91085792babde84037116fbc86ef5489d55e620866a1bc58a2d4b8 last_trade_price 86,471 4,814,669 46-46 de8f92f841a7df3e52801324b37db92852fdc3e1ccb57a79cb6c8fa5979581aa market_resolved 998 113,773 47-47 a0e0a3eefba8238aad5771f3eb5ab35ce5df77e57fb839f500b9aadde2a0c4a5 new_market 779 76,077 48-48 1e41df97606fefca803501a6cbe7dabc4bdf1e2c299f3ae638307a75bac5b619 price_change 103,016,642 1,002,731,539 49-441 caf29ee2810e31eca637417e5fdefee3afe203748965433479e2652171832f37 tick_size_change 3,112 113,188 442-442 edfd2fb942bd6f00c9b2411ea55aef1ec58d086decfcf9c0a0b0b39c407239d0 EVENT MIX count share price_change 103,016,642 89.57% best_bid_ask 10,613,784 9.23% book 1,284,373 1.12% last_trade_price 86,471 0.08% tick_size_change 3,112 <0.01% market_resolved 998 <0.01% new_market 779 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,613,885 10,613,784 101 8,936 FULL book 1,285,091 1,284,373 718 166,913 FULL last_trade_price 86,472 86,471 1 1,003 FULL market_resolved 998 998 0 47 FULL new_market 779 779 0 0 FULL price_change 103,017,820 103,016,642 1,178 10,549 FULL tick_size_change 3,112 3,112 0 256 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,587,661 48 49ms 72ms 405ms 26.3s 0 transport_latency_assumed best_bid_ask c 7,293,888 310 17ms 22ms 60ms 6.8s 0 transport_latency_assumed best_bid_ask e 10,596,531 10,596,436 41ms 69ms 740ms 24.0s 0 transport_latency_assumed best_bid_ask h 10,612,126 16,990 19ms 28ms 100ms 8.2s 0 transport_latency_assumed book b 982,543 561,176 2.6min 3.6h 31.7d 96.7d 0 book_staleness book c 525,179 316,263 1.8min 3.3h 30.2d 96.7d 0 book_staleness book e 279,584 279,374 1.3s 1.5h 21.9d 96.7d 0 book_staleness book h 313,756 127,560 90ms 1.7h 25.7d 96.7d 0 book_staleness last_trade_price b 74,065 4 75ms 3.1s 12.2s 26.5s 0 transport_latency_assumed last_trade_price c 56,148 12 23ms 47ms 153ms 5.0s 0 transport_latency_assumed last_trade_price e 82,918 82,918 69ms 4.3s 11.9s 24.0s 0 transport_latency_assumed last_trade_price h 86,404 3,537 27ms 120ms 746ms 6.9s 0 transport_latency_assumed market_resolved b 795 105 59ms 8.1min 11.1min 11.1min 0 transport_latency_assumed market_resolved c 635 201 20ms 17.7min 20.4min 20.4min 0 transport_latency_assumed market_resolved e 671 671 43ms 388ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 671 21 19ms 110ms 16.8s 1.1min 0 transport_latency_assumed new_market b 519 10 178ms 32.9s 4.9min 5.0min 0 transport_latency_assumed new_market c 499 162 98ms 16.0min 16.1min 16.1min 0 transport_latency_assumed new_market e 492 492 165ms 28.8s 1.0min 1.7min 0 transport_latency_assumed new_market h 492 115 71ms 262ms 1.3min 12.4min 0 transport_latency_assumed price_change b 92,837,845 486 50ms 97ms 3.7s 26.9s 0 transport_latency_assumed price_change c 72,234,897 2,256 17ms 23ms 73ms 7.0s 0 transport_latency_assumed price_change e 101,739,370 101,738,390 42ms 116ms 4.7s 24.0s 0 transport_latency_assumed price_change h 102,790,346 1,275,510 19ms 33ms 165ms 9.0s 0 transport_latency_assumed tick_size_change b 2,836 not meas. 49ms 62ms 133ms 352ms 0 transport_latency_assumed tick_size_change c 2,276 not meas. 18ms 22ms 28ms 65ms 0 transport_latency_assumed tick_size_change e 3,112 3,112 41ms 58ms 134ms 12.1s 0 transport_latency_assumed tick_size_change h 3,112 not meas. 19ms 26ms 60ms 797ms 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-03/15/2026-09-03T15.parquet sha256sum 2026-09-03T15.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.