Hour audit: 2026-09-25T10
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-25T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T10:00:00.000044795+00:00 · last event 2026-09-25T10:59:59.999622923+00:00
VOLUME 116,776,224 rows · 1,215,063,482 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 116,710,907 · k: 116,654,518 · h: 116,654,341 · i: 116,644,168 · g: 116,536,758 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,130,416 (92.60%) · k: 6,586,381 (5.64%) · h: 1,256,998 (1.08%) · i: 767,895 (0.66%) · g: 34,534 (0.03%) (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 116,776,224 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a8466fe44c4c7c4f89c6580b0388009e8a23cc1adebde12886d783af470fb14e
the corpus checksum ledger names this file with the same digest
joined 116,778,386 to merged 116,776,224, minus 2,162 (minus 0.0019%)
boundary drops 2,162 · 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-25T12:46:13Z as cghik
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 11,772,284 136,925,355 0-44 c347b61f6b22fe2712dad248138e28010570417197be6c3230ea2745d3b4492d book 184,939 18,837,536 45-45 37ca70823d8dfcdea4b4e1c6d7f0582d5a5f3ed73d367357e2bc7d8a9aebc3a9 last_trade_price 50,503 2,905,492 46-46 340556ce61805e150cce62c58dfd828a1bb33e572b9eb730ce783abf836622f8 market_resolved 698 113,477 47-47 d80bec2ae9e4f05ba593fd1c2ac9b34d2a1ec0da4ebb8dba4212c22e569245a8 new_market 846 90,649 48-48 5de27e4d37274fca147fde575db34aa21b5dd6c039d187ae8a346e5c19a13183 price_change 104,764,610 1,054,775,657 49-448 f6891d95b4c392be17b7a1b05c340c28a57c284326e875872edde5bc6d8b07fd tick_size_change 2,344 87,387 449-449 00c6a71d854322e554b836f2a50f8167e3bb279a50f38602c4eaf48ba28223c9 EVENT MIX count share price_change 104,764,610 89.71% best_bid_ask 11,772,284 10.08% book 184,939 0.16% last_trade_price 50,503 0.04% tick_size_change 2,344 <0.01% new_market 846 <0.01% market_resolved 698 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,772,488 11,772,284 204 106 FULL book 184,945 184,939 6 34,780 FULL last_trade_price 50,503 50,503 0 1 FULL market_resolved 698 698 0 0 FULL new_market 846 846 0 0 FULL price_change 104,766,562 104,764,610 1,952 135 FULL tick_size_change 2,344 2,344 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,771,286 10,979,041 5ms 11ms 87ms 4.7s 0 transport_latency_assumed best_bid_ask g 11,768,360 455 78ms 99ms 298ms 22.0s 0 transport_latency_assumed best_bid_ask h 11,771,062 103,984 19ms 28ms 109ms 7.1s 0 transport_latency_assumed best_bid_ask i 11,771,056 70,512 20ms 27ms 103ms 4.7s 0 transport_latency_assumed best_bid_ask k 11,770,795 618,292 12ms 18ms 81ms 4.9s 0 transport_latency_assumed book c 151,386 139,384 10ms 4.7h 19.9d 118.5d 0 book_staleness book g 130,489 27,831 96ms 21.9min 18.0d 118.5d 0 book_staleness book h 104,733 4,631 23ms 76ms 30.5min 100.0d 0 book_staleness book i 105,520 3,733 23ms 219ms 12.7h 100.0d 0 book_staleness book k 105,498 9,360 16ms 73ms 13.1h 100.0d 0 book_staleness last_trade_price c 50,309 45,638 6ms 22ms 171ms 1.1s 0 transport_latency_assumed last_trade_price g 49,867 30 89ms 385ms 11.9s 22.0s 0 transport_latency_assumed last_trade_price h 50,334 1,167 20ms 52ms 262ms 2.6s 0 transport_latency_assumed last_trade_price i 50,328 347 23ms 109ms 803ms 4.0s 0 transport_latency_assumed last_trade_price k 50,201 3,321 14ms 37ms 256ms 3.2s 0 transport_latency_assumed market_resolved c 663 586 5ms 31ms 55.3s 57.0s 0 transport_latency_assumed market_resolved g 663 not meas. 80ms 237ms 55.9s 56.0s 0 transport_latency_assumed market_resolved h 663 3 20ms 101ms 55.7s 55.8s 0 transport_latency_assumed market_resolved i 663 63 21ms 205ms 50.1s 50.2s 0 transport_latency_assumed market_resolved k 663 46 13ms 37ms 35.8s 56.7s 0 transport_latency_assumed new_market c 597 389 50ms 8.4s 41.6s 1.5min 0 transport_latency_assumed new_market g 597 28 232ms 19.8s 50.5s 1.5min 0 transport_latency_assumed new_market h 597 128 74ms 22.2s 1.4min 1.6min 0 transport_latency_assumed new_market i 597 169 79ms 19.9s 1.3min 1.6min 0 transport_latency_assumed new_market k 597 132 58ms 258ms 41.3s 53.6s 0 transport_latency_assumed price_change c 104,734,322 96,963,280 5ms 13ms 104ms 5.0s 0 transport_latency_assumed price_change g 104,584,438 6,190 79ms 114ms 1.0s 22.1s 0 transport_latency_assumed price_change h 104,724,608 1,147,054 19ms 32ms 149ms 7.3s 0 transport_latency_assumed price_change i 104,713,660 693,056 21ms 32ms 216ms 5.2s 0 transport_latency_assumed price_change k 104,724,420 5,955,030 13ms 21ms 105ms 5.4s 0 transport_latency_assumed tick_size_change c 2,344 2,098 5ms 20ms 78ms 110ms 0 transport_latency_assumed tick_size_change g 2,344 not meas. 79ms 110ms 279ms 554ms 0 transport_latency_assumed tick_size_change h 2,344 31 19ms 39ms 138ms 196ms 0 transport_latency_assumed tick_size_change i 2,344 15 21ms 36ms 119ms 298ms 0 transport_latency_assumed tick_size_change k 2,344 200 13ms 27ms 96ms 267ms 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-25/10/2026-09-25T10.parquet sha256sum 2026-09-25T10.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.