Hour audit: 2026-09-15T14
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-15T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T14:00:00.001907889+00:00 · last event 2026-09-15T14:59:59.999977430+00:00
VOLUME 118,723,204 rows · 1,298,050,175 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,579,747 · e: 117,456,998 · f: 117,427,678 · g: 116,715,652 · c: 104,437,168 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,659,436 (16.56%) · e: 969,849 (0.82%) · f: 397,937 (0.34%) · g: 79,632 (0.07%) · c: 97,616,350 (82.22%) (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 118,723,204 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8c1d20cd464e98f417e69e86e509b98df1deadc9637eb8e890af82f11144088d
the corpus checksum ledger names this file with the same digest
joined 118,725,629 to merged 118,723,204, minus 2,425 (minus 0.0020%)
boundary drops 2,425 · 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-15T16:37: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 11,382,366 131,847,300 0-43 2ca3c2ccc2d9cfc93fa2780da3bd3dae97ba9468bb1e2838ce09b303012a0556 book 1,249,232 78,768,446 44-48 a06c6afa04716ba4fde6eab00185870a24f94ef30c143dbb8e33d2ecea4e052f last_trade_price 70,045 3,956,936 49-49 b1f6a69f65babacaa0d073210c1d2a37833a4e6e6f331d2ee1169aa65ac3a15e market_resolved 904 132,067 50-50 2372281d4370c122f5a56a14f2bf2ad5696516f878b064ce4c972cef15a19f67 new_market 1,457 150,891 51-51 7aec42976873edd01b38d633fbb89bf0821624cb8a66e7a1aacc02de42e68e46 price_change 106,015,444 1,081,705,881 52-456 4b4a13efe593a6c299a32ab549444133fb60ae3e1bdaed0101e6bf2667ac4ce3 tick_size_change 3,756 137,713 457-457 8c7157eea89e1a92a54bc97be8eaba11c50ba508cdb6a13c1b6350bbc4ac5aa1 EVENT MIX count share price_change 106,015,444 89.30% best_bid_ask 11,382,366 9.59% book 1,249,232 1.05% last_trade_price 70,045 0.06% tick_size_change 3,756 <0.01% new_market 1,457 <0.01% market_resolved 904 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,382,690 11,382,366 324 1,715 FULL book 1,249,346 1,249,232 114 169,345 FULL last_trade_price 70,046 70,045 1 269 FULL market_resolved 904 904 0 5 FULL new_market 1,457 1,457 0 5 FULL price_change 106,017,430 106,015,444 1,986 898 FULL tick_size_change 3,756 3,756 0 132 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,963,209 9,358,927 5ms 14ms 120ms 13.2s 0 transport_latency_assumed best_bid_ask e 11,378,661 83,973 39ms 50ms 267ms 12.8s 0 transport_latency_assumed best_bid_ask f 11,378,347 24,520 44ms 57ms 261ms 20.0s 0 transport_latency_assumed best_bid_ask g 11,361,417 2,086 80ms 112ms 562ms 25.2s 0 transport_latency_assumed best_bid_ask h 11,380,706 1,912,860 17ms 28ms 137ms 40.8s 0 transport_latency_assumed book c 1,207,200 1,190,427 8.0min 2.4d 37.1d 108.7d 0 book_staleness book e 150,793 4,630 43ms 1.6s 1.6h 90.1d 0 book_staleness book f 154,158 5,163 48ms 1.4s 9.0h 90.2d 0 book_staleness book g 196,189 24,215 179ms 45.3min 13.8d 108.7d 0 book_staleness book h 148,408 24,797 21ms 66ms 2.9min 90.1d 0 book_staleness last_trade_price c 62,415 57,937 11ms 49ms 249ms 5.0s 0 transport_latency_assumed last_trade_price e 69,418 434 54ms 535ms 7.2s 13.0s 0 transport_latency_assumed last_trade_price f 69,307 277 58ms 344ms 4.6s 20.0s 0 transport_latency_assumed last_trade_price g 65,898 26 101ms 2.0s 15.2s 25.2s 0 transport_latency_assumed last_trade_price h 69,815 11,371 23ms 73ms 369ms 6.1s 0 transport_latency_assumed market_resolved c 813 781 6ms 3.3min 4.9min 5.9min 0 transport_latency_assumed market_resolved e 812 4 40ms 117ms 344ms 610ms 0 transport_latency_assumed market_resolved f 812 2 45ms 123ms 360ms 513ms 0 transport_latency_assumed market_resolved g 812 not meas. 83ms 246ms 628ms 1.4s 0 transport_latency_assumed market_resolved h 812 117 18ms 51ms 149ms 264ms 0 transport_latency_assumed new_market c 965 583 99ms 35.2s 1.6min 2.9h 0 transport_latency_assumed new_market e 958 153 218ms 32.1s 1.3min 1.6min 0 transport_latency_assumed new_market f 958 197 198ms 33.3s 1.3min 1.8min 0 transport_latency_assumed new_market g 958 139 338ms 29.0s 1.3min 1.6min 0 transport_latency_assumed new_market h 958 385 164ms 32.1s 1.3min 1.4min 0 transport_latency_assumed price_change c 93,199,338 87,004,700 6ms 17ms 172ms 13.5s 0 transport_latency_assumed price_change e 105,852,600 880,624 39ms 71ms 1.6s 13.0s 0 transport_latency_assumed price_change f 105,820,340 367,770 44ms 76ms 923ms 20.1s 0 transport_latency_assumed price_change g 105,086,622 53,166 82ms 166ms 4.1s 25.2s 0 transport_latency_assumed price_change h 105,975,292 17,709,184 17ms 34ms 247ms 41.0s 0 transport_latency_assumed tick_size_change c 3,228 2,995 5ms 15ms 106ms 7.1s 0 transport_latency_assumed tick_size_change e 3,756 31 39ms 59ms 199ms 351ms 0 transport_latency_assumed tick_size_change f 3,756 8 45ms 59ms 189ms 1.4s 0 transport_latency_assumed tick_size_change g 3,756 not meas. 81ms 109ms 375ms 931ms 0 transport_latency_assumed tick_size_change h 3,756 722 17ms 30ms 86ms 831ms 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-15/14/2026-09-15T14.parquet sha256sum 2026-09-15T14.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.