Hour audit: 2026-09-30T13
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-30T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T13:00:00.000087548+00:00 · last event 2026-09-30T13:59:59.999852806+00:00
VOLUME 133,583,344 rows · 1,480,177,411 bytes (1.38 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 132,505,319 · i: 132,503,950 · m: 132,423,202 · g: 125,948,410 · k: 120,758,359 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,598,622 (2.69%) · i: 749,664 (0.56%) · m: 120,816,142 (90.44%) · g: 193,553 (0.14%) · k: 8,225,363 (6.16%) (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 133,583,344 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3306ac9ce98c0802fd6c29eef4501373ff969af6886d76ec2667633dab3b8e10
the corpus checksum ledger names this file with the same digest
joined 133,611,645 to merged 133,583,344, minus 28,301 (minus 0.0212%)
boundary drops 28,301 · 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-30T20:07:21Z 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 12,506,294 148,494,703 0-47 795031d3f02131d77a7239249f87c328f4d1ca55231709f7a3e8f9af0795ad4d book 1,184,641 83,326,619 48-52 5cb25bd43362e4d3a5823dda71d60dc40f0a9d620159d32d860325db97e74206 last_trade_price 67,328 3,823,979 53-53 c364edb151ed91349753261d710ae6c2c12b5efb12e09d771768979258174c5a market_resolved 1,172 155,371 54-54 abd1562617f9d49f90e938b0af8c7a4a9830d5f22b4d38b0206a4af6a2486d1d new_market 1,043 111,123 55-55 9b43921277c69a755770a5ff04d1abaf6c95b1cd3526336aabad24639bd80e1d price_change 119,818,926 1,242,599,822 56-513 95d64552fb319d85e12b17482e878ec744a460b4cfd42a6bc9b97a3e920d8f6d tick_size_change 3,940 144,642 514-514 e3285281677e148f7bde6d2ae1c2dfacf0f420caf28a6f9529d36e8a53b94c1a EVENT MIX count share price_change 119,818,926 89.70% best_bid_ask 12,506,294 9.36% book 1,184,641 0.89% last_trade_price 67,328 0.05% tick_size_change 3,940 <0.01% market_resolved 1,172 <0.01% new_market 1,043 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,506,384 12,506,294 90 2,210 FULL book 1,211,724 1,184,641 27,083 227,758 FULL last_trade_price 67,328 67,328 0 307 FULL market_resolved 1,172 1,172 0 158 FULL new_market 1,085 1,043 42 109 FULL price_change 119,820,012 119,818,926 1,086 1,953 FULL tick_size_change 3,940 3,940 0 116 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,932,436 3,069 79ms 102ms 353ms 17.1s 0 transport_latency_assumed best_bid_ask h 12,505,060 282,809 17ms 27ms 217ms 34.5s 0 transport_latency_assumed best_bid_ask i 12,505,344 63,340 22ms 52ms 126ms 5.4s 0 transport_latency_assumed best_bid_ask k 11,294,620 597,006 15ms 33ms 124ms 8.1s 0 transport_latency_assumed best_bid_ask m 12,502,085 11,560,070 5ms 13ms 75ms 4.0s 0 transport_latency_assumed book g 591,623 159,447 11.3min 2.1d 39.0d 123.6d 0 book_staleness book h 139,054 6,277 22ms 68ms 2.7h 105.1d 0 book_staleness book i 136,113 1,794 29ms 75ms 825ms 1.5d 0 book_staleness book k 1,048,268 895,916 37.0min 3.0d 39.0d 123.6d 0 book_staleness book m 138,620 121,207 8ms 29ms 7.0min 30.6d 0 book_staleness last_trade_price g 61,795 20 84ms 414ms 8.9s 17.1s 0 transport_latency_assumed last_trade_price h 67,309 2,586 19ms 48ms 423ms 8.1s 0 transport_latency_assumed last_trade_price i 67,298 566 28ms 71ms 395ms 4.2s 0 transport_latency_assumed last_trade_price k 60,623 5,729 16ms 40ms 178ms 1.6s 0 transport_latency_assumed last_trade_price m 67,001 58,427 7ms 22ms 119ms 3.3s 0 transport_latency_assumed market_resolved g 827 9 80ms 254ms 3.5min 5.1min 0 transport_latency_assumed market_resolved h 829 20 19ms 28.0s 54.9s 55.0s 0 transport_latency_assumed market_resolved i 829 7 27ms 79ms 32.6s 56.7s 0 transport_latency_assumed market_resolved k 1,013 343 22ms 8.6min 14.5min 16.0min 0 transport_latency_assumed market_resolved m 829 793 6ms 24.4s 55.0s 57.6s 0 transport_latency_assumed new_market g 633 66 215ms 16.7s 5.6min 5.7min 0 transport_latency_assumed new_market h 633 121 204ms 16.8s 34.0s 1.3min 0 transport_latency_assumed new_market i 633 165 82ms 20.2s 42.0s 1.8min 0 transport_latency_assumed new_market k 782 333 104ms 4.8min 9.0min 9.5min 0 transport_latency_assumed new_market m 633 358 70ms 20.3s 30.7s 1.5min 0 transport_latency_assumed price_change g 113,357,264 30,942 79ms 124ms 2.7s 17.1s 0 transport_latency_assumed price_change h 119,788,494 3,306,706 18ms 31ms 321ms 34.5s 0 transport_latency_assumed price_change i 119,789,793 683,784 22ms 56ms 205ms 7.8s 0 transport_latency_assumed price_change k 108,349,469 6,725,780 15ms 35ms 137ms 9.0s 0 transport_latency_assumed price_change m 119,710,094 109,071,714 6ms 16ms 104ms 4.2s 0 transport_latency_assumed tick_size_change g 3,832 not meas. 79ms 96ms 177ms 316ms 0 transport_latency_assumed tick_size_change h 3,940 103 17ms 30ms 57ms 2.5s 0 transport_latency_assumed tick_size_change i 3,940 8 22ms 58ms 91ms 116ms 0 transport_latency_assumed tick_size_change k 3,584 256 14ms 33ms 79ms 138ms 0 transport_latency_assumed tick_size_change m 3,940 3,573 6ms 15ms 37ms 96ms 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/13/2026-09-30T13.parquet sha256sum 2026-09-30T13.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.