Hour audit: 2026-09-30T05
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-30T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T05:00:00.000405161+00:00 · last event 2026-09-30T05:59:59.999930039+00:00
VOLUME 99,251,495 rows · 1,013,434,582 bytes (966.49 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 99,041,143 · i: 99,026,450 · h: 98,946,685 · g: 98,876,533 · m: 98,807,630 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,673,140 (2.69%) · i: 603,325 (0.61%) · h: 813,138 (0.82%) · g: 44,714 (0.05%) · m: 95,117,178 (95.83%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 99,251,495 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6cb4f110536d2b544a3cae5a9825f51f7f81a2a2bfdb98a79c6b94a721f3e653
the corpus checksum ledger names this file with the same digest
joined 99,257,707 to merged 99,251,495, minus 6,212 (minus 0.0063%)
boundary drops 6,212 · 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-30T15:58:05Z as ghikm
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,457,441 107,744,075 0-36 8fb449935b1666a1630975f8969f010bedd26943221ed9e02ebabf52149199b1 book 261,449 25,851,596 37-37 ad99a2ee0db9f4fed1a32ec2d3307719d4cc7dd8cb42c23ff4f6096600f1e631 last_trade_price 50,646 2,799,096 38-38 7cdd86023bea1b3de2404c780504450dffbf313593ab3c12fb924b652ee3fd4d market_resolved 1,207 193,692 39-39 20291a865f6ac68baab357b9580f3f28deda7402186b50d8ca48a7d19e66850b new_market 1,084 111,317 40-40 222f718f6cfc94034aa2966adb39d427e3d07cf6a4891c0d698ac7c177115ba5 price_change 89,476,688 875,490,757 41-382 3835b7899144a1cbc7d3e52495c7dfcfcbb443941ef77e77a4ca63516a71e3a6 tick_size_change 2,980 109,270 383-383 3be2059a2ebd64eff401490078b0522cb4254f1a2fb34988e4f8c71e3839dbc8 EVENT MIX count share price_change 89,476,688 90.15% best_bid_ask 9,457,441 9.53% book 261,449 0.26% last_trade_price 50,646 0.05% tick_size_change 2,980 <0.01% market_resolved 1,207 <0.01% new_market 1,084 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,458,011 9,457,441 570 148 FULL book 262,715 261,449 1,266 65,764 FULL last_trade_price 50,646 50,646 0 1 FULL market_resolved 1,207 1,207 0 0 FULL new_market 1,084 1,084 0 0 FULL price_change 89,481,064 89,476,688 4,376 92 FULL tick_size_change 2,980 2,980 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,451,733 825 78ms 101ms 365ms 41.6s 0 transport_latency_assumed best_bid_ask h 9,451,764 66,463 18ms 27ms 150ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,453,721 38,795 21ms 29ms 121ms 10.7s 0 transport_latency_assumed best_bid_ask k 9,455,452 236,656 13ms 24ms 132ms 53.5s 0 transport_latency_assumed best_bid_ask m 9,444,614 9,114,702 4ms 8ms 58ms 6.6s 0 transport_latency_assumed book g 140,301 35,196 101ms 6.9h 22.8d 123.3d 0 book_staleness book h 120,664 18,273 22ms 14.5min 4.2d 104.8d 0 book_staleness book i 145,643 43,345 30ms 6.6h 22.8d 123.3d 0 book_staleness book k 135,315 32,105 19ms 5.8h 22.8d 123.3d 0 book_staleness book m 140,928 132,530 7ms 6.1h 24.6d 104.8d 0 book_staleness last_trade_price g 49,465 22 84ms 361ms 5.4s 41.6s 0 transport_latency_assumed last_trade_price h 50,163 610 19ms 58ms 355ms 38.9s 0 transport_latency_assumed last_trade_price i 50,154 639 22ms 52ms 272ms 2.1s 0 transport_latency_assumed last_trade_price k 50,354 1,738 14ms 47ms 284ms 3.9s 0 transport_latency_assumed last_trade_price m 49,891 47,637 5ms 11ms 102ms 1.4s 0 transport_latency_assumed market_resolved g 1,170 110 80ms 468ms 54.6s 54.6s 0 transport_latency_assumed market_resolved h 1,170 9 18ms 85ms 48.4s 48.5s 0 transport_latency_assumed market_resolved i 1,170 22 22ms 68ms 54.6s 55.4s 0 transport_latency_assumed market_resolved k 1,170 20 14ms 80ms 45.7s 56.7s 0 transport_latency_assumed market_resolved m 1,170 1,046 4ms 27ms 45.9s 56.9s 0 transport_latency_assumed new_market g 724 119 276ms 24.3s 59.8s 1.6min 0 transport_latency_assumed new_market h 724 192 135ms 17.8s 1.0min 1.5min 0 transport_latency_assumed new_market i 724 147 150ms 16.8s 1.0min 1.1min 0 transport_latency_assumed new_market k 724 91 202ms 17.2s 1.0min 1.3min 0 transport_latency_assumed new_market m 724 535 71ms 12.2s 57.7s 1.8min 0 transport_latency_assumed price_change g 89,230,160 8,442 78ms 122ms 725ms 41.6s 0 transport_latency_assumed price_change h 89,319,220 727,567 18ms 33ms 205ms 1.2min 0 transport_latency_assumed price_change i 89,372,058 520,357 21ms 34ms 150ms 16.1s 0 transport_latency_assumed price_change k 89,395,148 2,402,446 13ms 28ms 159ms 56.0s 0 transport_latency_assumed price_change m 89,167,323 85,817,876 4ms 9ms 71ms 6.6s 0 transport_latency_assumed tick_size_change g 2,980 not meas. 77ms 97ms 232ms 453ms 0 transport_latency_assumed tick_size_change h 2,980 24 18ms 28ms 173ms 399ms 0 transport_latency_assumed tick_size_change i 2,980 20 21ms 29ms 120ms 358ms 0 transport_latency_assumed tick_size_change k 2,980 84 13ms 21ms 113ms 657ms 0 transport_latency_assumed tick_size_change m 2,980 2,852 4ms 8ms 95ms 233ms 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-30/05/2026-09-30T05.parquet sha256sum 2026-09-30T05.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.