Hour audit: 2026-10-07T13
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-07T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T13:00:00.000038912+00:00 · last event 2026-10-07T13:59:59.999928847+00:00
VOLUME 133,894,153 rows · 1,553,471,723 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 133,610,180 · m: 133,588,180 · h: 133,563,936 · i: 133,291,288 · n: 132,848,238 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 62,516,877 (46.69%) · m: 68,379,464 (51.07%) · h: 1,715,058 (1.28%) · i: 1,137,323 (0.85%) · n: 145,431 (0.11%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 365924b96769f33da0675cf06ac036fd139fe97de40da7e74c906682db1407c9
the corpus checksum ledger names this file with the same digest
joined 133,895,710 to merged 133,894,153, minus 1,557 (minus 0.0012%)
boundary drops 1,557 · 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-07T16:04:36Z 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 11,596,942 152,231,216 0-44 df374a3e88dac014fa4767d5b46c298a2bc08f53d3fce13ae3eed295ea9540fb book 467,111 47,281,846 45-46 780d58775cfc3dbd9df8603a6130c1df2ba5a175db2b832d5068c1d1c34e7745 last_trade_price 68,426 3,886,521 47-47 725e1f21435a35f89d97f3401bee3db355604fa115159e9f63cad687761b96aa market_resolved 811 122,152 48-48 c0c5c79da6d851c644a4d9f2187be8ea3da891afcba8d6f43926751abc373b44 new_market 1,374 134,609 49-49 33511cdeb92447f9c65aa9e6c1f17cbb6db686e5b96f042654b43a4e8f24f8c5 price_change 121,753,905 1,348,084,498 50-514 eeda007b21a7940d46a64fd8c0ddb3558d3bae5e88706eda8a0ab16e87dce585 tick_size_change 5,584 206,428 515-515 62bdfe74c159f1930dcf72469d07d39a373d7510153954d995b10b692635e63d EVENT MIX count share price_change 121,753,905 90.93% best_bid_ask 11,596,942 8.66% book 467,111 0.35% last_trade_price 68,426 0.05% tick_size_change 5,584 <0.01% new_market 1,374 <0.01% market_resolved 811 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,597,116 11,596,942 174 142 FULL book 467,407 467,111 296 136,168 FULL last_trade_price 68,426 68,426 0 1 FULL market_resolved 811 811 0 1 FULL new_market 1,374 1,374 0 0 FULL price_change 121,754,992 121,753,905 1,087 93 FULL tick_size_change 5,584 5,584 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,595,497 135,160 20ms 39ms 258ms 46.5s 0 transport_latency_assumed best_bid_ask i 11,589,926 90,547 22ms 41ms 198ms 8.3s 0 transport_latency_assumed best_bid_ask m 11,595,446 6,001,030 6ms 22ms 128ms 8.6s 0 transport_latency_assumed best_bid_ask n 11,588,229 5,204 45ms 73ms 398ms 27.3s 0 transport_latency_assumed best_bid_ask o 11,595,700 5,365,001 6ms 22ms 132ms 11.0s 0 transport_latency_assumed book h 221,569 79,044 72ms 7.9h 32.0d 130.6d 0 book_staleness book i 184,375 39,812 47ms 2.5h 30.1d 112.1d 0 book_staleness book m 225,489 140,532 22ms 8.7h 32.0d 130.6d 0 book_staleness book n 204,800 63,583 187ms 5.8h 30.1d 130.6d 0 book_staleness book o 225,288 144,140 20ms 10.4h 30.1d 112.1d 0 book_staleness last_trade_price h 68,317 823 23ms 191ms 1.2s 16.3s 0 transport_latency_assumed last_trade_price i 67,678 521 27ms 394ms 3.3s 8.2s 0 transport_latency_assumed last_trade_price m 68,194 32,810 8ms 34ms 180ms 3.4s 0 transport_latency_assumed last_trade_price n 66,029 128 57ms 2.0s 14.9s 27.1s 0 transport_latency_assumed last_trade_price o 68,295 34,144 7ms 32ms 183ms 2.0s 0 transport_latency_assumed market_resolved h 739 3 22ms 43.7s 54.1s 55.0s 0 transport_latency_assumed market_resolved i 739 38 25ms 42.4s 53.5s 1.0min 0 transport_latency_assumed market_resolved m 739 395 7ms 42.4s 53.5s 54.8s 0 transport_latency_assumed market_resolved n 738 55 47ms 167ms 40.5s 57.6s 0 transport_latency_assumed market_resolved o 739 320 7ms 23.0s 56.0s 56.1s 0 transport_latency_assumed new_market h 826 131 128ms 33.2s 52.3s 1.6min 0 transport_latency_assumed new_market i 826 287 104ms 32.5s 48.7s 1.8min 0 transport_latency_assumed new_market m 826 506 46ms 18.9s 48.8s 1.7min 0 transport_latency_assumed new_market n 826 91 188ms 15.4s 35.9s 1.6min 0 transport_latency_assumed new_market o 826 359 64ms 19.8s 36.2s 1.6min 0 transport_latency_assumed price_change h 121,671,404 1,499,832 20ms 50ms 478ms 46.7s 0 transport_latency_assumed price_change i 121,442,160 1,006,072 22ms 56ms 782ms 8.3s 0 transport_latency_assumed price_change m 121,691,902 62,201,532 6ms 25ms 138ms 13.2s 0 transport_latency_assumed price_change n 120,982,032 76,362 46ms 119ms 5.1s 27.3s 0 transport_latency_assumed price_change o 121,713,748 56,970,107 6ms 25ms 145ms 11.0s 0 transport_latency_assumed tick_size_change h 5,584 65 19ms 37ms 104ms 1.2s 0 transport_latency_assumed tick_size_change i 5,584 46 22ms 43ms 142ms 306ms 0 transport_latency_assumed tick_size_change m 5,584 2,659 6ms 20ms 94ms 218ms 0 transport_latency_assumed tick_size_change n 5,584 8 45ms 62ms 146ms 10.2s 0 transport_latency_assumed tick_size_change o 5,584 2,806 6ms 19ms 93ms 229ms 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/13/2026-10-07T13.parquet sha256sum 2026-10-07T13.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.