Hour audit: 2026-09-13T10
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-13T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T10:00:00.002871489+00:00 · last event 2026-09-13T10:59:59.999918597+00:00
VOLUME 106,652,777 rows · 1,115,155,514 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 105,962,820 · h: 105,715,895 · e: 105,702,688 · g: 105,675,000 · c: 97,166,478 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 483,282 (0.45%) · h: 12,741,969 (11.95%) · e: 590,172 (0.55%) · g: 41,232 (0.04%) · c: 92,796,122 (87.01%) (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 106,652,777 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c76b34d9e8bb7a8131a94806d82fe0219977c1ba2da4bb1596d8b42a2a416bda
the corpus checksum ledger names this file with the same digest
joined 106,655,162 to merged 106,652,777, minus 2,385 (minus 0.0022%)
boundary drops 2,385 · 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-13T11:57:36Z 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,011,599 110,548,534 0-38 75df83136fe5252b0cb415f894cd3130399faa2cf5b7fa2735b4ca11ff67f5ab book 1,021,514 68,186,770 39-42 cdc79e1c79e21d75d0f10c73f075d5ceeca2bd8c3bd915e1af6a7ae79c8d277e last_trade_price 48,541 2,829,462 43-43 7c5f11ee505306b00bc39f73f3fbad3281b0dbfd9e31e2d7b43244f61c8025f0 market_resolved 896 108,870 44-44 069b5965fce14f6fa5b8b5679ede509031a6b0ccaab9d6c1e3744d80938a1291 new_market 2,655 261,517 45-45 db610448b85ca008ef1f56ee07212d3a02bad35f368bc9f6240291bcdb345f6b price_change 95,564,300 931,883,866 46-410 962cbfa838d2d36a00db9ef731dcef2f5497d54f432010741b76dbc765c8b92a tick_size_change 3,272 121,019 411-411 aea57d467ce4da9749bd35630891a27452486c2d1f869bffe5937fe00830312b EVENT MIX count share price_change 95,564,300 89.60% best_bid_ask 10,011,599 9.39% book 1,021,514 0.96% last_trade_price 48,541 0.05% tick_size_change 3,272 <0.01% new_market 2,655 <0.01% market_resolved 896 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,011,821 10,011,599 222 1,368 FULL book 1,021,520 1,021,514 6 176,235 FULL last_trade_price 48,542 48,541 1 157 FULL market_resolved 896 896 0 5 FULL new_market 2,655 2,655 0 0 FULL price_change 95,566,456 95,564,300 2,156 828 FULL tick_size_change 3,272 3,272 0 49 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,106,980 8,707,869 5ms 10ms 191ms 6.6s 0 transport_latency_assumed best_bid_ask e 10,007,942 55,111 41ms 47ms 236ms 10.9s 0 transport_latency_assumed best_bid_ask f 10,005,632 29,229 47ms 54ms 244ms 7.9s 0 transport_latency_assumed best_bid_ask g 10,005,616 2,517 82ms 100ms 521ms 22.0s 0 transport_latency_assumed best_bid_ask h 10,008,977 1,216,873 17ms 23ms 281ms 52.1s 0 transport_latency_assumed book c 856,307 844,868 14.3min 1.7d 32.7d 106.5d 0 book_staleness book e 103,204 1,817 44ms 261ms 3.5s 88.0d 0 book_staleness book f 388,174 146,076 2.7min 22.9h 31.7d 106.5d 0 book_staleness book g 129,150 13,803 93ms 42.3min 6.0d 88.0d 0 book_staleness book h 103,505 14,950 21ms 70ms 2.9s 44.0d 0 book_staleness last_trade_price c 43,506 41,435 10ms 46ms 288ms 5.0s 0 transport_latency_assumed last_trade_price e 48,511 308 50ms 187ms 3.2s 10.9s 0 transport_latency_assumed last_trade_price f 48,414 339 55ms 126ms 1.5s 7.9s 0 transport_latency_assumed last_trade_price g 48,241 23 96ms 312ms 6.5s 22.1s 0 transport_latency_assumed last_trade_price h 48,506 6,436 23ms 71ms 520ms 29.1s 0 transport_latency_assumed market_resolved c 772 747 5ms 7.6min 9.9min 10.9min 0 transport_latency_assumed market_resolved e 660 31 43ms 204ms 58.6s 1.0min 0 transport_latency_assumed market_resolved f 660 not meas. 48ms 207ms 58.6s 1.0min 0 transport_latency_assumed market_resolved g 660 not meas. 86ms 248ms 989ms 1.0min 0 transport_latency_assumed market_resolved h 663 118 18ms 61ms 158ms 4.5s 0 transport_latency_assumed new_market c 1,742 1,157 104ms 22.4s 7.4min 20.4min 0 transport_latency_assumed new_market e 1,688 380 199ms 19.1s 41.5s 3.1min 0 transport_latency_assumed new_market f 1,688 353 193ms 18.2s 43.2s 1.4min 0 transport_latency_assumed new_market g 1,688 183 335ms 19.5s 43.1s 58.3s 0 transport_latency_assumed new_market h 1,688 582 168ms 20.8s 45.3s 3.1min 0 transport_latency_assumed price_change c 87,154,095 83,197,233 5ms 11ms 200ms 6.6s 0 transport_latency_assumed price_change e 95,537,411 532,468 42ms 51ms 365ms 10.9s 0 transport_latency_assumed price_change f 95,514,980 307,250 47ms 59ms 318ms 8.1s 0 transport_latency_assumed price_change g 95,486,373 24,706 82ms 112ms 826ms 22.1s 0 transport_latency_assumed price_change h 95,549,284 11,502,643 18ms 25ms 305ms 52.2s 0 transport_latency_assumed tick_size_change c 3,076 2,813 5ms 58ms 473ms 607ms 0 transport_latency_assumed tick_size_change e 3,272 57 42ms 102ms 586ms 881ms 0 transport_latency_assumed tick_size_change f 3,272 35 47ms 136ms 606ms 1.2s 0 transport_latency_assumed tick_size_change g 3,272 not meas. 83ms 184ms 1.1s 1.2s 0 transport_latency_assumed tick_size_change h 3,272 367 18ms 59ms 994ms 5.8s 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-13/10/2026-09-13T10.parquet sha256sum 2026-09-13T10.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.