Hour audit: 2026-09-12T22
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-12T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T22:00:00.000031873+00:00 · last event 2026-09-12T22:59:59.999966610+00:00
VOLUME 132,540,118 rows · 1,444,490,697 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 127,904,149 · h: 127,900,985 · g: 122,995,577 · f: 122,919,517 · c: 69,213,542 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 3,097,901 (2.34%) · h: 61,789,704 (46.62%) · g: 178,274 (0.13%) · f: 779,441 (0.59%) · c: 66,694,798 (50.32%) (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 132,540,118 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fbe84a643f01c5fca36e82f6816ee2fe4c20f1a34812b696cb0d1f8e50031cd2
the corpus checksum ledger names this file with the same digest
joined 132,553,425 to merged 132,540,118, minus 13,307 (minus 0.0100%)
boundary drops 13,307 · 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-13T01:08:18Z 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,308,310 139,089,249 0-46 64d647de09f01bcc7ea954a0791b12adcf4a9af505501f30c82a5809f1ff2db9 book 4,617,120 131,206,262 47-64 ba8ca65cdbc37feca7de5be52df9c6486c87c4d95db598b1fa260af631343cb7 last_trade_price 51,400 2,997,217 65-65 e36c2a53e5616caf3e6de9fd55b767c622ffd98e799ad1509df46957ec7204c8 market_resolved 62,315 4,412,271 66-66 906398694d69dc380bd1644a31aec8e352b8f2ea87d16ede47181d57927c8f86 new_market 53,955 2,239,309 67-67 59b493231189cce58f45acbba23b5e0002cbfe99320b4462fd3eaa4752c8b29c price_change 115,439,246 1,162,755,496 68-508 11fd9541179841916ad696507923050141a942c9b2d05e2bb9830908c90ec7e3 tick_size_change 7,772 285,869 509-509 95fb2319030c4e7ce40b7ed4eb454f29f3b353cca647f3a537fc8deba7dd114c EVENT MIX count share price_change 115,439,246 87.10% best_bid_ask 12,308,310 9.29% book 4,617,120 3.48% market_resolved 62,315 0.05% new_market 53,955 0.04% last_trade_price 51,400 0.04% tick_size_change 7,772 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,308,638 12,308,310 328 13,640 FULL book 4,626,882 4,617,120 9,762 193,744 FULL last_trade_price 51,400 51,400 0 1,306 FULL market_resolved 62,356 62,315 41 22,363 FULL new_market 53,991 53,955 36 11,677 FULL price_change 115,442,370 115,439,246 3,124 9,706 FULL tick_size_change 7,788 7,772 16 1,022 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,222,368 5,993,140 5ms 11ms 99ms 3.2s 0 transport_latency_assumed best_bid_ask e 12,306,754 292,201 39ms 45ms 187ms 5.1s 0 transport_latency_assumed best_bid_ask f 11,753,229 60,118 45ms 53ms 224ms 5.9s 0 transport_latency_assumed best_bid_ask g 11,782,503 6,008 78ms 96ms 406ms 12.4s 0 transport_latency_assumed best_bid_ask h 12,306,380 5,956,843 18ms 26ms 272ms 43.3s 0 transport_latency_assumed book c 4,386,993 4,328,256 25.3min 1.2d 35.2d 106.0d 0 book_staleness book e 109,104 5,576 41ms 121ms 11.4s 87.4d 0 book_staleness book f 492,801 107,795 5.0min 23.6h 30.8d 106.0d 0 book_staleness book g 515,233 118,684 5.4min 1.0d 31.1d 106.0d 0 book_staleness book h 120,627 56,809 22ms 4.8s 1.2d 106.0d 0 book_staleness last_trade_price c 24,738 23,560 11ms 43ms 230ms 4.9s 0 transport_latency_assumed last_trade_price e 51,325 1,679 46ms 108ms 718ms 5.0s 0 transport_latency_assumed last_trade_price f 48,487 523 52ms 126ms 715ms 5.9s 0 transport_latency_assumed last_trade_price g 49,085 44 93ms 242ms 1.8s 12.4s 0 transport_latency_assumed last_trade_price h 51,330 25,594 23ms 68ms 442ms 9.2s 0 transport_latency_assumed market_resolved c 60,172 59,937 1.7h 4.9h 6.9h 7.1h 0 transport_latency_assumed market_resolved e 4,134 163 75ms 183ms 516ms 49.3s 0 transport_latency_assumed market_resolved f 4,065 74 85ms 196ms 5.1min 5.4min 0 transport_latency_assumed market_resolved g 4,126 148 136ms 355ms 4.0min 4.5min 0 transport_latency_assumed market_resolved h 4,133 1,993 35ms 69ms 685ms 48.9s 0 transport_latency_assumed new_market c 53,748 53,016 1.8h 5.5h 6.7h 7.1h 0 transport_latency_assumed new_market e 1,194 180 226ms 17.6s 25.9s 1.0h 0 transport_latency_assumed new_market f 1,194 188 214ms 17.8s 36.2s 2.8h 0 transport_latency_assumed new_market g 1,194 211 346ms 20.5s 27.8s 2.6h 0 transport_latency_assumed new_market h 1,194 360 174ms 18.3s 28.2s 1.1h 0 transport_latency_assumed price_change c 58,461,571 56,232,988 6ms 12ms 108ms 4.0s 0 transport_latency_assumed price_change e 115,423,862 2,797,977 39ms 47ms 227ms 6.0s 0 transport_latency_assumed price_change f 110,612,269 610,716 45ms 56ms 266ms 6.0s 0 transport_latency_assumed price_change g 110,635,892 53,179 78ms 103ms 492ms 12.4s 0 transport_latency_assumed price_change h 115,409,549 55,744,386 18ms 28ms 286ms 44.1s 0 transport_latency_assumed tick_size_change c 3,952 3,901 5ms 9ms 24ms 52ms 0 transport_latency_assumed tick_size_change e 7,776 125 39ms 44ms 85ms 190ms 0 transport_latency_assumed tick_size_change f 7,472 27 45ms 51ms 123ms 337ms 0 transport_latency_assumed tick_size_change g 7,544 not meas. 77ms 91ms 223ms 592ms 0 transport_latency_assumed tick_size_change h 7,772 3,719 18ms 21ms 94ms 9.0s 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/22/2026-09-12T22.parquet sha256sum 2026-09-12T22.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.