Hour audit: 2026-09-07T13
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-07T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T13:00:00.001373004+00:00 · last event 2026-09-07T13:59:59.999976259+00:00
VOLUME 94,649,335 rows · 997,410,521 bytes (951.20 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 94,164,402 · e: 93,988,372 · h: 93,938,156 · f: 93,903,439 · g: 93,854,340 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 90,160,696 (95.26%) · e: 409,631 (0.43%) · h: 3,727,479 (3.94%) · f: 309,746 (0.33%) · g: 41,783 (0.04%) (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 94,649,335 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c436cc0166acacabd56f9e74da0543503ca727a62d814b49e9c349a52d7e582f
the corpus checksum ledger names this file with the same digest
joined 94,651,254 to merged 94,649,335, minus 1,919 (minus 0.0020%)
boundary drops 1,919 · 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-07T14:55:15Z 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 9,527,592 102,301,105 0-36 5703bcb15758ee4218a240dcd9e651b19cd2d301d3021734e9e87b6c2122aa1a book 850,733 68,662,605 37-40 c515590dddc4d78819696931c061e6137c2b8d2f39d17b6340efaf741f56f297 last_trade_price 58,566 3,312,455 41-41 bc5e1ee2536c0197c7befe42fe55ea3ecc0bef578dea76d3f2d563ca788f7c86 market_resolved 1,021 167,584 42-42 296f8d009c40cc4bcbb3a7d6eff6f9d4ac243a09ecace02cda7b1150ded1c683 new_market 1,497 151,984 43-43 2f1c2679e3f8bf8dc1c08bca0680619bdbcb9daafaba996bba5a4140555d6a1f price_change 84,207,326 821,636,810 44-365 f7c8c16c586fba394e6276990f7bbef01a95ec02680a97af510a0232567cb44b tick_size_change 2,600 95,274 366-366 0f8e92cd36ec8ec4b286a6b16e8c14ba009ce18b1ddd391133271ada418aa966 EVENT MIX count share price_change 84,207,326 88.97% best_bid_ask 9,527,592 10.07% book 850,733 0.90% last_trade_price 58,566 0.06% tick_size_change 2,600 <0.01% new_market 1,497 <0.01% market_resolved 1,021 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,527,807 9,527,592 215 174 FULL book 850,743 850,733 10 167,170 FULL last_trade_price 58,566 58,566 0 0 FULL market_resolved 1,021 1,021 0 0 FULL new_market 1,497 1,497 0 0 FULL price_change 84,209,020 84,207,326 1,694 699 FULL tick_size_change 2,600 2,600 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,525,400 9,148,500 5ms 10ms 110ms 4.3s 0 transport_latency_assumed best_bid_ask e 9,523,169 20,996 41ms 46ms 164ms 3.0s 0 transport_latency_assumed best_bid_ask f 9,523,543 11,763 45ms 50ms 172ms 9.6s 0 transport_latency_assumed best_bid_ask g 9,524,557 903 83ms 106ms 379ms 13.2s 0 transport_latency_assumed best_bid_ask h 9,524,693 345,430 18ms 23ms 119ms 9.6s 0 transport_latency_assumed book c 396,238 290,731 2.3min 5.8h 29.0d 100.6d 0 book_staleness book e 393,715 173,811 2.3min 5.9h 26.8d 100.7d 0 book_staleness book f 395,852 176,231 2.3min 5.7h 28.9d 100.6d 0 book_staleness book g 190,925 29,346 146ms 3.1h 16.0d 100.6d 0 book_staleness book h 405,016 180,614 2.6min 5.8h 29.0d 100.6d 0 book_staleness last_trade_price c 58,539 55,529 10ms 42ms 244ms 4.9s 0 transport_latency_assumed last_trade_price e 58,533 152 48ms 131ms 913ms 5.0s 0 transport_latency_assumed last_trade_price f 58,547 84 51ms 146ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price g 58,541 19 95ms 288ms 2.6s 13.1s 0 transport_latency_assumed last_trade_price h 58,497 2,782 23ms 59ms 296ms 9.1s 0 transport_latency_assumed market_resolved c 1,021 985 5ms 11ms 95ms 378ms 0 transport_latency_assumed market_resolved e 1,021 not meas. 42ms 120ms 453ms 802ms 0 transport_latency_assumed market_resolved f 1,021 2 46ms 126ms 441ms 1.2s 0 transport_latency_assumed market_resolved g 1,021 not meas. 85ms 263ms 766ms 1.3s 0 transport_latency_assumed market_resolved h 1,021 34 19ms 54ms 182ms 803ms 0 transport_latency_assumed new_market c 969 593 85ms 15.0s 49.3s 1.3min 0 transport_latency_assumed new_market e 969 246 169ms 19.0s 53.2s 2.9min 0 transport_latency_assumed new_market f 969 114 184ms 13.6s 51.5s 1.1min 0 transport_latency_assumed new_market g 969 119 303ms 21.4s 47.5s 2.9min 0 transport_latency_assumed new_market h 969 425 130ms 19.0s 51.7s 1.1min 0 transport_latency_assumed price_change c 84,179,635 80,661,826 5ms 11ms 130ms 4.5s 0 transport_latency_assumed price_change e 84,008,365 214,422 41ms 50ms 244ms 4.8s 0 transport_latency_assumed price_change f 83,920,907 121,552 45ms 54ms 257ms 9.7s 0 transport_latency_assumed price_change g 84,075,727 11,392 84ms 125ms 562ms 13.4s 0 transport_latency_assumed price_change h 83,945,360 3,198,134 18ms 25ms 146ms 9.6s 0 transport_latency_assumed tick_size_change c 2,600 2,532 5ms 8ms 109ms 481ms 0 transport_latency_assumed tick_size_change e 2,600 4 40ms 46ms 172ms 330ms 0 transport_latency_assumed tick_size_change f 2,600 not meas. 44ms 49ms 194ms 341ms 0 transport_latency_assumed tick_size_change g 2,600 4 82ms 100ms 426ms 651ms 0 transport_latency_assumed tick_size_change h 2,600 60 18ms 24ms 170ms 967ms 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-07/13/2026-09-07T13.parquet sha256sum 2026-09-07T13.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.