Hour audit: 2026-09-10T22
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-10T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T22:00:00.000041897+00:00 · last event 2026-09-10T22:59:59.999941939+00:00
VOLUME 103,501,103 rows · 1,049,426,279 bytes (1000.81 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 102,995,364 · f: 102,785,119 · e: 102,685,731 · h: 102,668,864 · c: 98,720,399 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 103,137 (0.10%) · f: 216,963 (0.21%) · e: 638,688 (0.62%) · h: 8,437,460 (8.15%) · c: 94,104,855 (90.92%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,501,103 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c50658fd1b058e5af01c392d7dc98987885906a7a203ea1fe864776261c4400a
the corpus checksum ledger names this file with the same digest
joined 103,506,149 to merged 103,501,103, minus 5,046 (minus 0.0049%)
boundary drops 5,046 · 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-11T00:35: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 10,762,290 116,726,415 0-41 4390a3effb136593b182dae85e7df4355b7488890753459251291b9c186d9cd9 book 528,824 55,804,973 42-44 524ce3c474dedaafb6e95d99c2bf3eb7626700a5f712c3005c28b653b845a724 last_trade_price 40,363 2,372,412 45-45 1741f356726bba46b4e0626483166684584814c0d5cef1f806ae24209fd505d1 market_resolved 766 123,863 46-46 133f068949fc6d91e1c1c4880bb83963e396cdd907a78c4ad603f5b6a01a0b01 new_market 1,772 183,637 47-47 d2cba1e43cfe31668c8f7f9a9f34bd675e830164e953db844eafc65407d9b6df price_change 92,164,776 872,946,700 48-399 d1a7d501609afe4e0e2d8b7a7ef1c9e6ca5b50dde0063a3d1d28417b1ad3a2c8 tick_size_change 2,312 85,308 400-400 0819338960eb0dfd81715a400f074f35cf27bd3f301456253afe9960a6634392 EVENT MIX count share price_change 92,164,776 89.05% best_bid_ask 10,762,290 10.40% book 528,824 0.51% last_trade_price 40,363 0.04% tick_size_change 2,312 <0.01% new_market 1,772 <0.01% market_resolved 766 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,762,713 10,762,290 423 627 FULL book 529,220 528,824 396 202,709 FULL last_trade_price 40,366 40,363 3 87 FULL market_resolved 766 766 0 6 FULL new_market 1,772 1,772 0 4 FULL price_change 92,169,000 92,164,776 4,224 498 FULL tick_size_change 2,312 2,312 0 28 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,286,309 9,832,500 5ms 10ms 141ms 7.9s 0 transport_latency_assumed best_bid_ask e 10,761,030 65,509 38ms 46ms 178ms 4.5s 0 transport_latency_assumed best_bid_ask f 10,760,969 18,999 45ms 54ms 196ms 3.3s 0 transport_latency_assumed best_bid_ask g 10,759,362 2,022 79ms 100ms 383ms 16.8s 0 transport_latency_assumed best_bid_ask h 10,761,609 843,260 18ms 23ms 166ms 17.9s 0 transport_latency_assumed book c 492,956 445,589 8.9min 22.6h 29.1d 104.0d 0 book_staleness book e 85,744 1,780 41ms 276ms 3.1s 39.4d 0 book_staleness book f 86,176 1,580 48ms 323ms 17.2s 85.3d 0 book_staleness book g 160,122 71,728 1.1s 10.2h 19.3d 104.0d 0 book_staleness book h 85,782 8,147 22ms 92ms 3.0s 85.3d 0 book_staleness last_trade_price c 38,260 36,329 10ms 43ms 231ms 4.9s 0 transport_latency_assumed last_trade_price e 40,286 302 49ms 205ms 1.6s 5.0s 0 transport_latency_assumed last_trade_price f 40,252 85 56ms 224ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price g 40,272 61 98ms 477ms 4.6s 16.8s 0 transport_latency_assumed last_trade_price h 40,308 3,586 23ms 80ms 432ms 5.5s 0 transport_latency_assumed market_resolved c 746 717 5ms 13ms 1.8min 2.0min 0 transport_latency_assumed market_resolved e 752 7 40ms 188ms 664ms 1.0s 0 transport_latency_assumed market_resolved f 752 1 46ms 195ms 717ms 1.1s 0 transport_latency_assumed market_resolved g 752 not meas. 86ms 354ms 1.2s 5.4s 0 transport_latency_assumed market_resolved h 752 41 18ms 77ms 403ms 46.3s 0 transport_latency_assumed new_market c 1,168 607 93ms 14.0s 2.1min 2.9min 0 transport_latency_assumed new_market e 1,172 255 145ms 21.9s 2.3min 2.9min 0 transport_latency_assumed new_market f 1,172 180 169ms 16.4s 2.2min 2.9min 0 transport_latency_assumed new_market g 1,172 168 250ms 18.2s 2.2min 2.8min 0 transport_latency_assumed new_market h 1,172 562 100ms 18.4s 2.3min 2.9min 0 transport_latency_assumed price_change c 87,898,760 83,786,987 5ms 12ms 178ms 11.2s 0 transport_latency_assumed price_change e 91,794,435 570,823 39ms 51ms 319ms 4.5s 0 transport_latency_assumed price_change f 91,893,486 196,114 45ms 60ms 344ms 3.5s 0 transport_latency_assumed price_change g 92,031,372 29,158 80ms 116ms 677ms 16.8s 0 transport_latency_assumed price_change h 91,776,929 7,581,694 18ms 25ms 229ms 28.9s 0 transport_latency_assumed tick_size_change c 2,200 2,126 5ms 9ms 62ms 225ms 0 transport_latency_assumed tick_size_change e 2,312 12 38ms 46ms 210ms 363ms 0 transport_latency_assumed tick_size_change f 2,312 4 45ms 51ms 162ms 347ms 0 transport_latency_assumed tick_size_change g 2,312 not meas. 79ms 95ms 289ms 618ms 0 transport_latency_assumed tick_size_change h 2,312 170 18ms 23ms 78ms 3.6s 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-10/22/2026-09-10T22.parquet sha256sum 2026-09-10T22.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.