Hour audit: 2026-10-07T19
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-10-07T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T19:00:00.000037312+00:00 · last event 2026-10-07T19:59:59.999971159+00:00
VOLUME 114,251,982 rows · 1,356,137,171 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 113,424,168 · m: 113,418,440 · i: 112,916,128 · h: 112,844,704 · n: 112,669,780 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 53,336,367 (46.68%) · m: 58,438,283 (51.15%) · i: 1,128,812 (0.99%) · h: 1,049,844 (0.92%) · n: 298,676 (0.26%) (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 114,251,982 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b1e5f02118510d9345e055fdb3f22064800917fd0f57ee62deaa4739a7b43089
the corpus checksum ledger names this file with the same digest
joined 114,253,342 to merged 114,251,982, minus 1,360 (minus 0.0012%)
boundary drops 1,360 · 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-10-07T21:03:21Z as himno
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,693,144 127,173,010 0-36 7568d583fd5a6e4648653c25e6b4812cbc33270892c2b01a704a24c3b1d8459c book 1,187,461 92,617,887 37-41 c68e1934a4220da2f90171b961e0e6727622b73c8043c6ce4b8e9a5ec77f01c8 last_trade_price 58,334 3,379,101 42-42 7e2e1c9477d564358c164f05dbfd9ab5a72eabf5db3bbd09bdd29efc33bb9d7a market_resolved 794 128,894 43-43 259ea9c771cbed27d280e768347adc9b7d45321fdd2454a8d15900e1ba89e918 new_market 3,225 316,927 44-44 c6a1496f859ce53b7b768109d41a023758d92d4aa15f114948e15c23ca23d08d price_change 103,306,716 1,131,131,961 45-439 67cd33af46bedc14d2315f5f5f1a189eed3b35b863e73c52ec171d030c6e29c7 tick_size_change 2,308 86,016 440-440 0e9f224828d5ad4afef1da4aa09499cc6a80fc5afae905135ebd0106cfd41335 EVENT MIX count share price_change 103,306,716 90.42% best_bid_ask 9,693,144 8.48% book 1,187,461 1.04% last_trade_price 58,334 0.05% new_market 3,225 <0.01% tick_size_change 2,308 <0.01% market_resolved 794 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,693,290 9,693,144 146 169 FULL book 1,187,525 1,187,461 64 221,191 FULL last_trade_price 58,334 58,334 0 0 FULL market_resolved 794 794 0 2 FULL new_market 3,225 3,225 0 0 FULL price_change 103,307,866 103,306,716 1,150 88 FULL tick_size_change 2,308 2,308 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,665,998 63,303 20ms 110ms 729ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,672,922 84,417 21ms 37ms 274ms 15.8s 0 transport_latency_assumed best_bid_ask m 9,685,991 4,904,826 5ms 17ms 182ms 7.4s 0 transport_latency_assumed best_bid_ask n 9,673,189 6,506 44ms 79ms 610ms 28.0s 0 transport_latency_assumed best_bid_ask o 9,686,272 4,634,092 5ms 18ms 206ms 28.4s 0 transport_latency_assumed book h 629,100 299,737 7.5min 1.8d 46.2d 130.9d 0 book_staleness book i 392,830 138,758 2.7min 1.2d 46.2d 130.9d 0 book_staleness book m 538,354 282,984 5.7min 1.5d 46.2d 130.9d 0 book_staleness book n 517,062 201,336 5.7min 1.6d 46.2d 130.9d 0 book_staleness book o 533,266 264,646 5.5min 1.5d 46.2d 130.9d 0 book_staleness last_trade_price h 56,441 335 36ms 487ms 5.1s 54.4s 0 transport_latency_assumed last_trade_price i 56,539 387 30ms 629ms 5.4s 15.8s 0 transport_latency_assumed last_trade_price m 57,714 30,903 7ms 34ms 281ms 7.5s 0 transport_latency_assumed last_trade_price n 54,432 88 76ms 2.2s 14.0s 28.1s 0 transport_latency_assumed last_trade_price o 57,767 26,621 7ms 40ms 317ms 5.8s 0 transport_latency_assumed market_resolved h 773 14 31ms 16.0s 49.2s 1.3min 0 transport_latency_assumed market_resolved i 775 84 25ms 12.8s 55.5s 1.2min 0 transport_latency_assumed market_resolved m 775 365 6ms 13.4s 45.5s 1.6min 0 transport_latency_assumed market_resolved n 775 10 48ms 414ms 52.4s 55.6s 0 transport_latency_assumed market_resolved o 775 321 7ms 13.5s 41.9s 56.2s 0 transport_latency_assumed new_market h 2,038 537 329ms 43.5s 59.6s 1.9min 0 transport_latency_assumed new_market i 2,038 508 129ms 43.6s 59.6s 1.6min 0 transport_latency_assumed new_market m 2,038 1,040 189ms 43.8s 59.6s 1.7min 0 transport_latency_assumed new_market n 2,038 388 291ms 43.4s 59.9s 1.5min 0 transport_latency_assumed new_market o 2,038 752 140ms 44.4s 59.0s 1.8min 0 transport_latency_assumed price_change h 102,488,046 685,910 21ms 150ms 2.0s 1.2min 0 transport_latency_assumed price_change i 102,788,716 904,602 22ms 61ms 1.5s 15.9s 0 transport_latency_assumed price_change m 103,131,264 53,216,998 6ms 20ms 208ms 7.7s 0 transport_latency_assumed price_change n 102,419,980 90,348 45ms 166ms 5.5s 28.1s 0 transport_latency_assumed price_change o 103,141,742 48,408,858 6ms 22ms 228ms 28.4s 0 transport_latency_assumed tick_size_change h 2,308 8 21ms 189ms 1.5s 34.1s 0 transport_latency_assumed tick_size_change i 2,308 56 22ms 57ms 290ms 903ms 0 transport_latency_assumed tick_size_change m 2,304 1,167 6ms 30ms 328ms 779ms 0 transport_latency_assumed tick_size_change n 2,304 not meas. 44ms 138ms 658ms 15.7s 0 transport_latency_assumed tick_size_change o 2,308 1,077 6ms 36ms 283ms 1.3s 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-10-07/19/2026-10-07T19.parquet sha256sum 2026-10-07T19.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.