Hour audit: 2026-10-07T23
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-07T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T23:00:00.000058755+00:00 · last event 2026-10-07T23:59:59.999987764+00:00
VOLUME 117,452,436 rows · 1,316,896,944 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 117,391,140 · i: 117,367,274 · o: 117,329,277 · n: 117,313,905 · h: 117,102,964 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 61,116,947 (52.04%) · i: 766,653 (0.65%) · o: 54,686,057 (46.56%) · n: 60,676 (0.05%) · h: 822,103 (0.70%) (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 117,452,436 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ea180cf174f78696d31d636c47f059fbd21843d07bfe0605524d46eb99a52a84
the corpus checksum ledger names this file with the same digest
joined 117,453,798 to merged 117,452,436, minus 1,362 (minus 0.0012%)
boundary drops 1,362 · 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-08T01:29:19Z 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 10,103,798 127,901,572 0-38 d673ab1d59a4cf15f73e183a4513e953ec4fe29529078e0bf18e1c51dd848031 book 141,687 13,993,688 39-39 3de1d5badda8fb8e9a9aab2015191739f5c240aa7a71f8e553afdfb5594ee1fe last_trade_price 55,966 3,120,852 40-40 04cf40d1d42cbd37b1eb102aeaee40f8fd46ad22f538f6fb2bd8406abfdb8ffb market_resolved 840 124,967 41-41 dbd5cdb8bbd0788cee51ea8eb786c01aa993f971c0f823b74293e405f2ba4bee new_market 2,187 203,464 42-42 05c0b0919e1bc8d4b3837fb5dd52a46f03137fe6ef1608ced6cf61b26dd00ada price_change 107,143,534 1,170,051,185 43-451 aa4215318759744c61f1df2dd142de1e8b156140fe9a1eb6e9627e568b83289c tick_size_change 4,424 162,509 452-452 eecd60c0eac32e0b1a11f29940138701e33afb5d0483371bb110f58c40877cd6 EVENT MIX count share price_change 107,143,534 91.22% best_bid_ask 10,103,798 8.60% book 141,687 0.12% last_trade_price 55,966 0.05% tick_size_change 4,424 <0.01% new_market 2,187 <0.01% market_resolved 840 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,103,932 10,103,798 134 76 FULL book 141,693 141,687 6 8,546 FULL last_trade_price 55,966 55,966 0 0 FULL market_resolved 840 840 0 0 FULL new_market 2,187 2,187 0 0 FULL price_change 107,144,756 107,143,534 1,222 40 FULL tick_size_change 4,424 4,424 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,095,085 67,180 18ms 30ms 390ms 59.9s 0 transport_latency_assumed best_bid_ask i 10,102,158 61,073 21ms 31ms 146ms 4.0s 0 transport_latency_assumed best_bid_ask m 10,103,188 5,261,369 4ms 14ms 140ms 5.9s 0 transport_latency_assumed best_bid_ask n 10,101,632 4,223 44ms 62ms 336ms 20.0s 0 transport_latency_assumed best_bid_ask o 10,103,184 4,709,953 4ms 14ms 137ms 6.5s 0 transport_latency_assumed book h 123,604 11,984 22ms 1.6s 1.1d 112.4d 0 book_staleness book i 116,712 4,080 23ms 150ms 2.6h 112.5d 0 book_staleness book m 117,846 62,331 7ms 54ms 3.8h 112.5d 0 book_staleness book n 120,652 7,461 51ms 4.1s 15.1h 112.5d 0 book_staleness book o 117,172 55,831 7ms 44ms 1.8h 112.5d 0 book_staleness last_trade_price h 55,062 382 19ms 118ms 1.3s 29.9s 0 transport_latency_assumed last_trade_price i 55,769 457 23ms 87ms 626ms 3.0s 0 transport_latency_assumed last_trade_price m 55,857 28,960 6ms 25ms 218ms 1.6s 0 transport_latency_assumed last_trade_price n 55,586 36 51ms 1.2s 10.8s 20.0s 0 transport_latency_assumed last_trade_price o 55,894 26,131 6ms 23ms 226ms 1.7s 0 transport_latency_assumed market_resolved h 768 45 20ms 610ms 40.5s 55.8s 0 transport_latency_assumed market_resolved i 768 113 24ms 28.2s 54.4s 57.8s 0 transport_latency_assumed market_resolved m 768 356 6ms 25.7s 52.3s 56.8s 0 transport_latency_assumed market_resolved n 768 5 46ms 304ms 47.7s 47.7s 0 transport_latency_assumed market_resolved o 768 321 6ms 28.6s 54.4s 58.2s 0 transport_latency_assumed new_market h 1,287 262 182ms 1.5min 2.4min 2.8min 0 transport_latency_assumed new_market i 1,287 320 101ms 1.4min 2.4min 2.9min 0 transport_latency_assumed new_market m 1,287 743 56ms 1.5min 2.4min 2.7min 0 transport_latency_assumed new_market n 1,287 233 89ms 1.5min 2.3min 2.6min 0 transport_latency_assumed new_market o 1,287 629 86ms 1.6min 2.4min 2.7min 0 transport_latency_assumed price_change h 106,822,734 742,244 18ms 35ms 579ms 1.0min 0 transport_latency_assumed price_change i 107,086,156 700,606 21ms 35ms 231ms 4.0s 0 transport_latency_assumed price_change m 107,107,770 55,760,794 4ms 15ms 141ms 6.4s 0 transport_latency_assumed price_change n 107,029,556 48,718 44ms 79ms 1.0s 20.0s 0 transport_latency_assumed price_change o 107,046,548 49,891,172 5ms 15ms 137ms 6.9s 0 transport_latency_assumed tick_size_change h 4,424 6 18ms 28ms 79ms 242ms 0 transport_latency_assumed tick_size_change i 4,424 4 21ms 34ms 103ms 148ms 0 transport_latency_assumed tick_size_change m 4,424 2,394 4ms 9ms 31ms 100ms 0 transport_latency_assumed tick_size_change n 4,424 not meas. 43ms 54ms 122ms 910ms 0 transport_latency_assumed tick_size_change o 4,424 2,020 4ms 10ms 37ms 275ms 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/23/2026-10-07T23.parquet sha256sum 2026-10-07T23.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.