Hour audit: 2026-09-16T02
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-16T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T02:00:00.000039908+00:00 · last event 2026-09-16T02:59:59.999991293+00:00
VOLUME 115,472,380 rows · 1,195,867,756 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 114,827,989 · e: 114,827,778 · h: 114,804,173 · f: 114,797,570 · g: 110,528,117 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 110,105,183 (95.35%) · e: 504,408 (0.44%) · h: 4,314,641 (3.74%) · f: 226,031 (0.20%) · g: 322,117 (0.28%) (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 115,472,380 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a166f527314280470364b8df1293e782343300eb605cbcdeeaffdafd7bb68a76
the corpus checksum ledger names this file with the same digest
joined 115,476,803 to merged 115,472,380, minus 4,423 (minus 0.0038%)
boundary drops 4,423 · 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-16T04:36:41Z 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,677,614 140,721,880 0-48 9f29d65fbccfd28edfdf0eb1c131e9e9fec7103506ffcb740cef057face33b65 book 811,192 65,133,764 49-52 5d17bcc3d78bbf55b5b512c8d5159644894c9da48ddfcae28c3681d170518d69 last_trade_price 45,017 2,563,440 53-53 b72c2b9bb1d777bcc397d51ac53c27a70aa0efe474b5abb611b614281782dc0b market_resolved 1,806 282,709 54-54 a62b74e14a1da4dc4a4982a949ad6fbc5ed1725024e00b3c0dbe549203b9b073 new_market 1,111 112,932 55-55 7c88267508c3ab65419677027e7d6509b4bc4bb580eef71afd4a1d5ac3eccd68 price_change 101,928,204 985,476,324 56-444 a4e7962af00b90a709ef2e4f0351622c6686a51912393f6b2c569c1f570dced5 tick_size_change 7,436 261,715 445-445 51123c41d5d148b4cf1866299352012305b5d3ef16da6d1d53ac75a0431d202e EVENT MIX count share price_change 101,928,204 88.27% best_bid_ask 12,677,614 10.98% book 811,192 0.70% last_trade_price 45,017 0.04% tick_size_change 7,436 <0.01% market_resolved 1,806 <0.01% new_market 1,111 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,677,892 12,677,614 278 520 FULL book 813,126 811,192 1,934 169,832 FULL last_trade_price 45,018 45,017 1 54 FULL market_resolved 1,806 1,806 0 2 FULL new_market 1,111 1,111 0 1 FULL price_change 101,930,414 101,928,204 2,210 119 FULL tick_size_change 7,436 7,436 0 106 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,675,843 12,199,293 5ms 9ms 77ms 2.3s 0 transport_latency_assumed best_bid_ask e 12,674,228 36,187 39ms 45ms 133ms 6.1s 0 transport_latency_assumed best_bid_ask f 12,673,415 10,896 46ms 56ms 167ms 3.0s 0 transport_latency_assumed best_bid_ask g 12,206,606 956 82ms 115ms 315ms 16.4s 0 transport_latency_assumed best_bid_ask h 12,673,916 430,282 18ms 25ms 101ms 11.8s 0 transport_latency_assumed book c 228,606 175,116 21.4s 1.1h 24.5d 109.2d 0 book_staleness book e 241,057 106,517 29.0s 1.2h 24.5d 109.2d 0 book_staleness book f 245,196 104,758 32.5s 1.5h 24.5d 109.2d 0 book_staleness book g 469,603 313,257 2.9min 16.8h 35.3d 109.2d 0 book_staleness book h 252,288 111,544 37.1s 1.1h 24.5d 109.2d 0 book_staleness last_trade_price c 44,911 42,287 10ms 44ms 209ms 4.9s 0 transport_latency_assumed last_trade_price e 44,916 332 46ms 103ms 888ms 6.2s 0 transport_latency_assumed last_trade_price f 44,710 127 54ms 113ms 551ms 4.9s 0 transport_latency_assumed last_trade_price g 42,953 13 96ms 207ms 1.4s 16.5s 0 transport_latency_assumed last_trade_price h 44,720 2,258 24ms 67ms 270ms 6.1s 0 transport_latency_assumed market_resolved c 1,761 1,729 5ms 10ms 46.8s 55.6s 0 transport_latency_assumed market_resolved e 1,761 1 104ms 153ms 288ms 5.4s 0 transport_latency_assumed market_resolved f 1,761 2 109ms 183ms 344ms 2.5min 0 transport_latency_assumed market_resolved g 1,760 3 196ms 305ms 54.6s 5.6min 0 transport_latency_assumed market_resolved h 1,761 71 35ms 60ms 142ms 1.1s 0 transport_latency_assumed new_market c 706 411 71ms 29.4s 1.1min 28.5d 0 transport_latency_assumed new_market e 706 104 138ms 19.2s 1.0min 1.3min 0 transport_latency_assumed new_market f 706 128 162ms 23.2s 1.1min 2.7min 0 transport_latency_assumed new_market g 723 118 307ms 53.6s 4.2min 47.9min 0 transport_latency_assumed new_market h 706 350 99ms 22.6s 1.3min 5.8min 0 transport_latency_assumed price_change c 101,868,726 97,679,296 5ms 11ms 88ms 2.5s 0 transport_latency_assumed price_change e 101,857,674 361,246 39ms 50ms 203ms 6.2s 0 transport_latency_assumed price_change f 101,824,346 110,120 46ms 61ms 240ms 7.9s 0 transport_latency_assumed price_change g 97,799,460 7,770 83ms 125ms 425ms 16.7s 0 transport_latency_assumed price_change h 101,823,346 3,769,772 18ms 29ms 128ms 20.8s 0 transport_latency_assumed tick_size_change c 7,436 7,051 4ms 12ms 236ms 446ms 0 transport_latency_assumed tick_size_change e 7,436 21 39ms 53ms 200ms 569ms 0 transport_latency_assumed tick_size_change f 7,436 not meas. 46ms 116ms 368ms 459ms 0 transport_latency_assumed tick_size_change g 7,012 not meas. 83ms 111ms 247ms 634ms 0 transport_latency_assumed tick_size_change h 7,436 364 18ms 28ms 78ms 705ms 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-16/02/2026-09-16T02.parquet sha256sum 2026-09-16T02.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.