Hour audit: 2026-09-12T10
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-12T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T10:00:00.000409239+00:00 · last event 2026-09-12T10:59:59.999968183+00:00
VOLUME 117,996,877 rows · 1,262,959,223 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 113,897,262 · h: 113,860,466 · f: 113,845,309 · e: 113,837,014 · c: 66,406,304 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 98,164 (0.08%) · h: 48,773,131 (41.33%) · f: 691,030 (0.59%) · e: 4,056,846 (3.44%) · c: 64,377,706 (54.56%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 117,996,877 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0d42582146d7cfbdca53e65630248afdb5ecc9f7a23c49a699705282ff145497
the corpus checksum ledger names this file with the same digest
joined 118,009,928 to merged 117,996,877, minus 13,051 (minus 0.0111%)
boundary drops 13,051 · 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-12T12:35:46Z 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,573,030 118,408,127 0-40 11e63d12b1501d9adee2e20174b05f63f7ae648935417baeddce43600e3ce9f7 book 4,215,571 126,042,202 41-57 ebefd5b30009112c3a6f2eb4b4bbbd0ae7774e8ddb3d631bec8d4b6d836a4463 last_trade_price 48,877 2,904,794 58-58 6f4363ead16eb66e6c0aab518fb230e168f29a4af271ee9a7c16d12b4af0de9b market_resolved 5,424 216,742 59-59 c50ee036ce81fe4a298bbdf7a8af5754a656c895312d77271aa61e9b3163d5f9 new_market 8,849 338,686 60-60 76128eed58ceb8a2008bc1e3f6c6469de36bcd25a41b120fe876174b25f89903 price_change 103,140,894 1,013,546,621 61-454 1f94b8b3beb4ada308057d1b662a31eae45e5d8e496926ae195b229b147656e2 tick_size_change 4,232 155,986 455-455 9ef040b0eaf479ac9800c0c3aa0f9ae1d585b38922503214e74fac6b478c3940 EVENT MIX count share price_change 103,140,894 87.41% best_bid_ask 10,573,030 8.96% book 4,215,571 3.57% last_trade_price 48,877 0.04% new_market 8,849 <0.01% market_resolved 5,424 <0.01% tick_size_change 4,232 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,573,222 10,573,030 192 11,697 FULL book 4,226,429 4,215,571 10,858 204,037 FULL last_trade_price 48,878 48,877 1 1,033 FULL market_resolved 5,424 5,424 0 678 FULL new_market 8,851 8,849 2 542 FULL price_change 103,142,892 103,140,894 1,998 7,992 FULL tick_size_change 4,232 4,232 0 456 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,873,488 5,690,495 5ms 11ms 61ms 3.6s 0 transport_latency_assumed best_bid_ask e 10,570,210 371,075 40ms 45ms 210ms 3.6s 0 transport_latency_assumed best_bid_ask f 10,570,506 63,014 48ms 55ms 264ms 3.0s 0 transport_latency_assumed best_bid_ask g 10,568,365 6,951 82ms 104ms 463ms 18.3s 0 transport_latency_assumed best_bid_ask h 10,570,972 4,441,495 17ms 30ms 274ms 43.3s 0 transport_latency_assumed book c 4,146,534 4,123,746 20.4min 16.8h 31.7d 105.5d 0 book_staleness book e 120,817 11,441 43ms 3.7min 2.1d 105.5d 0 book_staleness book f 116,918 7,065 50ms 32.0s 17.3h 87.0d 0 book_staleness book g 189,128 27,145 288ms 5.1h 20.8d 97.8d 0 book_staleness book h 115,313 46,174 22ms 5.7s 16.5h 105.5d 0 book_staleness last_trade_price c 27,511 26,355 11ms 40ms 182ms 4.9s 0 transport_latency_assumed last_trade_price e 48,737 1,480 47ms 106ms 629ms 5.0s 0 transport_latency_assumed last_trade_price f 48,769 386 54ms 116ms 619ms 5.0s 0 transport_latency_assumed last_trade_price g 48,797 47 94ms 227ms 3.3s 18.4s 0 transport_latency_assumed last_trade_price h 48,803 20,609 23ms 66ms 402ms 38.0s 0 transport_latency_assumed market_resolved c 5,183 5,159 48.4min 1.7h 2.0h 2.1h 0 transport_latency_assumed market_resolved e 565 24 42ms 127ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 565 5 49ms 137ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 565 1 89ms 253ms 480ms 863ms 0 transport_latency_assumed market_resolved h 565 235 18ms 63ms 141ms 614ms 0 transport_latency_assumed new_market c 8,041 7,369 21.0min 1.4h 1.8h 2.0h 0 transport_latency_assumed new_market e 1,344 364 193ms 12.6s 31.8s 1.1min 0 transport_latency_assumed new_market f 1,344 334 203ms 17.4s 41.3s 1.4min 0 transport_latency_assumed new_market g 1,344 188 356ms 19.8s 52.1s 1.1min 0 transport_latency_assumed new_market h 1,344 594 169ms 19.0s 35.4s 58.4s 0 transport_latency_assumed price_change c 56,343,139 54,522,214 5ms 11ms 69ms 4.6s 0 transport_latency_assumed price_change e 103,091,109 3,672,341 40ms 47ms 261ms 3.7s 0 transport_latency_assumed price_change f 103,102,975 620,214 48ms 58ms 313ms 9.3s 0 transport_latency_assumed price_change g 103,084,831 63,832 82ms 111ms 580ms 18.4s 0 transport_latency_assumed price_change h 103,119,237 44,262,293 17ms 33ms 289ms 48.8s 0 transport_latency_assumed tick_size_change c 2,408 2,368 5ms 9ms 20ms 42ms 0 transport_latency_assumed tick_size_change e 4,232 121 40ms 44ms 98ms 293ms 0 transport_latency_assumed tick_size_change f 4,232 12 48ms 52ms 154ms 528ms 0 transport_latency_assumed tick_size_change g 4,232 not meas. 81ms 95ms 399ms 870ms 0 transport_latency_assumed tick_size_change h 4,232 1,731 17ms 22ms 110ms 1.4s 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-12/10/2026-09-12T10.parquet sha256sum 2026-09-12T10.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.