Hour audit: 2026-09-10T07
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-10T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T07:00:00.000348079+00:00 · last event 2026-09-10T07:59:59.999969801+00:00
VOLUME 92,933,778 rows · 936,315,050 bytes (892.94 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 92,552,543 · h: 92,542,661 · c: 92,540,605 · f: 92,538,486 · g: 92,374,667 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 346,215 (0.37%) · h: 2,476,356 (2.66%) · c: 89,880,690 (96.71%) · f: 198,335 (0.21%) · g: 32,182 (0.03%) (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 92,933,778 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 73ba7d782eb5e4b6d1bbabcb2fe77da2ca768c9f42d4ab2ffd1903b4fe7078ea
the corpus checksum ledger names this file with the same digest
joined 92,937,827 to merged 92,933,778, minus 4,049 (minus 0.0044%)
boundary drops 4,049 · 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-10T08:54:32Z 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,901,752 107,536,972 0-37 29210dfe96939651075fe2d6d8fa683251e2affc279c5f2aca7ca236f83bed3c book 637,976 58,423,625 38-40 1a754de526e90184620d33cbbbf2c820f17456cf14d463d98f4d5541abb27ca2 last_trade_price 45,797 2,628,225 41-41 cf6d8af855327fa4824631ff92380a3deba4a30d1310e2bf45d6483bf615f50f market_resolved 553 85,752 42-42 ca709caf3b655eda5c780a6ad21d3b98925abec82fee6f2ba518076c7437b19b new_market 536 62,314 43-43 ef9a86165564b26437a7847a339c129c507420cfb651cce09d095e3b5f00164d price_change 82,345,392 766,450,957 44-358 66949f35aab854921d801f7aef27280fd8a89fdd83b96f1dbd3ff42be6e9b938 tick_size_change 1,772 65,212 359-359 2453d6b9399fe414a51e911fc2938886d0dce06ea26e17d0565950fbac378d00 EVENT MIX count share price_change 82,345,392 88.61% best_bid_ask 9,901,752 10.65% book 637,976 0.69% last_trade_price 45,797 0.05% tick_size_change 1,772 <0.01% market_resolved 553 <0.01% new_market 536 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,901,841 9,901,752 89 116 FULL book 638,598 637,976 622 174,197 FULL last_trade_price 45,799 45,797 2 0 FULL market_resolved 553 553 0 0 FULL new_market 536 536 0 0 FULL price_change 82,348,728 82,345,392 3,336 67 FULL tick_size_change 1,772 1,772 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,900,670 9,641,606 5ms 8ms 60ms 8.1s 0 transport_latency_assumed best_bid_ask e 9,899,189 18,250 38ms 43ms 97ms 2.6s 0 transport_latency_assumed best_bid_ask f 9,899,182 5,460 45ms 49ms 116ms 2.7s 0 transport_latency_assumed best_bid_ask g 9,899,695 853 75ms 89ms 196ms 9.8s 0 transport_latency_assumed best_bid_ask h 9,900,058 235,583 17ms 20ms 73ms 15.5s 0 transport_latency_assumed book c 262,872 208,184 1.3min 13.7h 18.8d 103.4d 0 book_staleness book e 289,999 144,879 2.1min 14.9h 21.5d 103.4d 0 book_staleness book f 275,775 129,404 1.7min 14.5h 18.8d 103.4d 0 book_staleness book g 126,915 19,819 88ms 1.3h 4.7d 103.4d 0 book_staleness book h 287,989 135,690 2.1min 15.1h 18.8d 103.4d 0 book_staleness last_trade_price c 45,757 44,109 10ms 38ms 175ms 5.0s 0 transport_latency_assumed last_trade_price e 45,739 212 44ms 93ms 403ms 5.0s 0 transport_latency_assumed last_trade_price f 45,733 75 51ms 103ms 449ms 5.0s 0 transport_latency_assumed last_trade_price g 45,715 18 89ms 180ms 492ms 7.3s 0 transport_latency_assumed last_trade_price h 45,772 1,383 22ms 60ms 291ms 9.5s 0 transport_latency_assumed market_resolved c 524 519 5ms 9ms 29ms 85ms 0 transport_latency_assumed market_resolved e 524 13 39ms 194ms 48.1s 1.0min 0 transport_latency_assumed market_resolved f 524 9 46ms 196ms 48.1s 1.0min 0 transport_latency_assumed market_resolved g 524 not meas. 85ms 367ms 59.0s 59.0s 0 transport_latency_assumed market_resolved h 524 12 18ms 95ms 48.3s 1.0min 0 transport_latency_assumed new_market c 410 230 53ms 14.9s 57.3s 1.3min 0 transport_latency_assumed new_market e 410 97 125ms 16.1s 27.9s 54.9s 0 transport_latency_assumed new_market f 410 43 125ms 15.7s 29.1s 1.1min 0 transport_latency_assumed new_market g 410 56 136ms 13.9s 23.4s 1.1min 0 transport_latency_assumed new_market h 410 110 66ms 15.5s 24.1s 27.6s 0 transport_latency_assumed price_change c 82,328,600 79,984,394 5ms 9ms 76ms 8.1s 0 transport_latency_assumed price_change e 82,314,910 182,760 38ms 43ms 136ms 2.6s 0 transport_latency_assumed price_change f 82,315,090 63,344 45ms 50ms 164ms 2.8s 0 transport_latency_assumed price_change g 82,299,636 11,436 75ms 90ms 261ms 10.2s 0 transport_latency_assumed price_change h 82,306,136 2,103,458 17ms 21ms 103ms 16.3s 0 transport_latency_assumed tick_size_change c 1,772 1,648 5ms 12ms 101ms 192ms 0 transport_latency_assumed tick_size_change e 1,772 4 39ms 45ms 127ms 217ms 0 transport_latency_assumed tick_size_change f 1,772 not meas. 45ms 50ms 207ms 482ms 0 transport_latency_assumed tick_size_change g 1,772 not meas. 75ms 91ms 351ms 923ms 0 transport_latency_assumed tick_size_change h 1,772 120 17ms 25ms 67ms 540ms 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/07/2026-09-10T07.parquet sha256sum 2026-09-10T07.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.