Hour audit: 2026-09-14T16
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-14T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T16:00:00.000020852+00:00 · last event 2026-09-14T16:59:59.999975400+00:00
VOLUME 116,511,580 rows · 1,243,210,144 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 114,372,834 · e: 114,365,753 · h: 114,353,548 · g: 114,223,559 · c: 89,842,026 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 390,345 (0.34%) · e: 1,505,135 (1.29%) · h: 29,262,241 (25.12%) · g: 94,938 (0.08%) · c: 85,258,921 (73.18%) (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 116,511,580 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 34a6148aa865ae6786c9306bda529d54c48421ab3b9caf2ae58dc77b0d69a2f0
the corpus checksum ledger names this file with the same digest
joined 116,516,239 to merged 116,511,580, minus 4,659 (minus 0.0040%)
boundary drops 4,659 · 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-14T17:59:30Z 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,845,599 122,459,952 0-41 c6f90c10d82ac4bc27d50b1f3681c41495dc1d1d46a86c167b52f893f065fec3 book 2,169,106 90,627,436 42-50 39c0b4296b8d41ea3e0a972c57e0b42c6688588453de9f64fc9eaa2be36ad5c5 last_trade_price 61,131 3,534,781 51-51 c0b6f9da615b9eb0f706a77d9ac18fff2958460532fe2807fc10bf13686833c2 market_resolved 2,170 244,133 52-52 9cf6544bc6fce6c20aa291c3a0233b07ae2613eb001c9b5da5129637473118cb new_market 1,835 177,900 53-53 178e97225b4291bc866b66998f69b6a6292f4f2d2a903d44be2d81e9e0ee01fe price_change 103,427,795 1,024,692,982 54-448 e22a66c7963f75ad2cf510d2e606f50491e4357317d5148d0d9a275eeb27a7a0 tick_size_change 3,944 145,406 449-449 73e7d530d92b138f76adf9d70218bf9f8589a8a440b8e8e785b41bc5ba10c104 EVENT MIX count share price_change 103,427,795 88.77% best_bid_ask 10,845,599 9.31% book 2,169,106 1.86% last_trade_price 61,131 0.05% tick_size_change 3,944 <0.01% market_resolved 2,170 <0.01% new_market 1,835 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,845,780 10,845,599 181 3,070 FULL book 2,171,745 2,169,106 2,639 166,494 FULL last_trade_price 61,134 61,131 3 557 FULL market_resolved 2,170 2,170 0 45 FULL new_market 1,835 1,835 0 4 FULL price_change 103,429,631 103,427,795 1,836 2,435 FULL tick_size_change 3,944 3,944 0 282 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,287,105 7,875,698 5ms 14ms 128ms 5.2s 0 transport_latency_assumed best_bid_ask e 10,842,832 138,276 40ms 56ms 240ms 13.8s 0 transport_latency_assumed best_bid_ask f 10,842,226 31,241 48ms 62ms 256ms 12.1s 0 transport_latency_assumed best_bid_ask g 10,838,499 2,602 82ms 106ms 476ms 25.1s 0 transport_latency_assumed best_bid_ask h 10,843,914 2,797,782 18ms 29ms 147ms 9.1s 0 transport_latency_assumed book c 2,119,306 2,104,365 24.2min 2.9d 37.1d 107.8d 0 book_staleness book e 135,105 6,129 45ms 1.6s 20.6h 89.3d 0 book_staleness book f 134,165 3,657 52ms 1.2s 20.6h 107.8d 0 book_staleness book g 176,331 21,175 107ms 3.3h 11.9d 107.8d 0 book_staleness book h 130,011 33,780 23ms 83ms 24.7min 33.9d 0 book_staleness last_trade_price c 46,294 43,688 11ms 51ms 256ms 4.9s 0 transport_latency_assumed last_trade_price e 60,957 842 57ms 359ms 5.6s 13.8s 0 transport_latency_assumed last_trade_price f 60,883 212 62ms 351ms 5.2s 12.3s 0 transport_latency_assumed last_trade_price g 60,367 263 100ms 548ms 12.1s 25.1s 0 transport_latency_assumed last_trade_price h 61,015 16,126 25ms 85ms 447ms 8.8s 0 transport_latency_assumed market_resolved c 1,852 1,808 9ms 10.2min 16.4min 16.5min 0 transport_latency_assumed market_resolved e 1,466 21 53ms 195ms 437ms 1.0min 0 transport_latency_assumed market_resolved f 1,466 2 55ms 198ms 425ms 1.0min 0 transport_latency_assumed market_resolved g 1,466 not meas. 95ms 262ms 703ms 1.1s 0 transport_latency_assumed market_resolved h 1,466 339 22ms 67ms 169ms 1.9s 0 transport_latency_assumed new_market c 1,260 792 110ms 5.1min 144.1d 144.1d 0 transport_latency_assumed new_market e 1,134 233 225ms 20.6s 144.1d 144.1d 0 transport_latency_assumed new_market f 1,134 203 216ms 16.0s 144.1d 144.1d 0 transport_latency_assumed new_market g 1,134 138 333ms 18.5s 144.1d 144.1d 0 transport_latency_assumed new_market h 1,134 469 137ms 17.4s 144.1d 144.1d 0 transport_latency_assumed price_change c 79,383,393 75,229,785 6ms 15ms 148ms 7.8s 0 transport_latency_assumed price_change e 103,320,315 1,359,583 41ms 67ms 836ms 13.8s 0 transport_latency_assumed price_change f 103,329,016 355,030 49ms 75ms 739ms 12.2s 0 transport_latency_assumed price_change g 103,141,818 70,760 83ms 133ms 2.5s 25.1s 0 transport_latency_assumed price_change h 103,312,064 26,412,637 18ms 33ms 202ms 9.2s 0 transport_latency_assumed tick_size_change c 2,816 2,785 5ms 9ms 19ms 44ms 0 transport_latency_assumed tick_size_change e 3,944 51 40ms 51ms 125ms 4.6s 0 transport_latency_assumed tick_size_change f 3,944 not meas. 48ms 53ms 106ms 1.2s 0 transport_latency_assumed tick_size_change g 3,944 not meas. 82ms 94ms 218ms 390ms 0 transport_latency_assumed tick_size_change h 3,944 1,108 18ms 22ms 48ms 171ms 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-14/16/2026-09-14T16.parquet sha256sum 2026-09-14T16.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.