Hour audit: 2026-10-07T16
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-07T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T16:00:00.000072695+00:00 · last event 2026-10-07T16:59:59.999966371+00:00
VOLUME 116,984,612 rows · 1,330,755,663 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 116,758,998 · m: 116,673,898 · h: 116,437,789 · n: 116,370,738 · i: 116,115,908 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 59,521,178 (50.88%) · m: 55,658,102 (47.58%) · h: 731,795 (0.63%) · n: 170,231 (0.15%) · i: 903,306 (0.77%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a918fba673565def986a2c45b130a6c0e1475b075c1c75afc7e20aa4b9dbbf82
the corpus checksum ledger names this file with the same digest
joined 116,986,212 to merged 116,984,612, minus 1,600 (minus 0.0014%)
boundary drops 1,600 · 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-07T18:05:16Z 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,135,829 132,106,972 0-38 067d5c4abcffc8d85706c6fae566a29895d9e85289017ca8a043b2e0e949ceb6 book 155,208 16,999,623 39-39 424e03c770b83c41f4530268c93363942eb7db848c48d1440de03ba40c74ce90 last_trade_price 59,998 3,434,277 40-40 8aee5d3e5acb6dc3c15fa6274efd7d4d3b1d6eea6cf05a92a4887b63f10adc7f market_resolved 909 149,582 41-41 b6a94121989f904d37b6510ca63a1a10b00427dae944e8e40b102b44e5f01a6f new_market 1,532 148,912 42-42 9db6e3734ada5746cdbf784b9dbad671a4600834212242abea57ce56240cf1ca price_change 106,627,824 1,176,460,556 43-449 be16c3ea175ae36f0e963799094d92eef1cb5286a93ff4058008e2e14cb087b9 tick_size_change 3,312 122,861 450-450 a6687015f7a7b3a43360ed81a1c91215ca13b1c2591ab5353d22d76329e21e88 EVENT MIX count share price_change 106,627,824 91.15% best_bid_ask 10,135,829 8.66% book 155,208 0.13% last_trade_price 59,998 0.05% tick_size_change 3,312 <0.01% new_market 1,532 <0.01% market_resolved 909 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,136,001 10,135,829 172 67 FULL book 155,238 155,208 30 9,842 FULL last_trade_price 59,998 59,998 0 1 FULL market_resolved 909 909 0 0 FULL new_market 1,532 1,532 0 0 FULL price_change 106,629,222 106,627,824 1,398 53 FULL tick_size_change 3,312 3,312 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,121,243 60,143 23ms 123ms 443ms 43.5s 0 transport_latency_assumed best_bid_ask i 10,111,502 75,771 22ms 37ms 277ms 9.5s 0 transport_latency_assumed best_bid_ask m 10,127,869 4,822,658 5ms 17ms 145ms 24.7s 0 transport_latency_assumed best_bid_ask n 10,128,880 11,163 45ms 71ms 431ms 27.4s 0 transport_latency_assumed best_bid_ask o 10,129,677 5,166,094 5ms 17ms 153ms 12.5s 0 transport_latency_assumed book h 125,723 6,654 49ms 970ms 8.1h 130.8d 0 book_staleness book i 125,290 8,066 30ms 1.2s 8.4h 112.2d 0 book_staleness book m 126,461 60,540 8ms 75ms 6.8h 112.2d 0 book_staleness book n 129,016 11,906 72ms 12.1s 1.8d 112.2d 0 book_staleness book o 125,868 68,042 8ms 69ms 5.6h 69.0d 0 book_staleness last_trade_price h 58,806 350 40ms 461ms 3.4s 17.8s 0 transport_latency_assumed last_trade_price i 58,103 425 28ms 476ms 2.9s 8.6s 0 transport_latency_assumed last_trade_price m 59,287 27,220 7ms 34ms 244ms 3.7s 0 transport_latency_assumed last_trade_price n 58,097 150 74ms 3.6s 18.4s 27.4s 0 transport_latency_assumed last_trade_price o 59,516 31,853 7ms 33ms 251ms 3.0s 0 transport_latency_assumed market_resolved h 909 5 39ms 329ms 36.7s 45.2s 0 transport_latency_assumed market_resolved i 909 65 25ms 186ms 34.0s 39.2s 0 transport_latency_assumed market_resolved m 909 421 7ms 57ms 34.6s 39.6s 0 transport_latency_assumed market_resolved n 909 1 49ms 356ms 49.9s 54.4s 0 transport_latency_assumed market_resolved o 909 417 7ms 49ms 34.2s 39.2s 0 transport_latency_assumed new_market h 936 275 140ms 30.2s 35.7s 62.3d 0 transport_latency_assumed new_market i 936 231 130ms 30.3s 36.0s 62.3d 0 transport_latency_assumed new_market m 936 441 52ms 16.7s 37.3s 62.3d 0 transport_latency_assumed new_market n 936 247 230ms 19.9s 35.8s 62.3d 0 transport_latency_assumed new_market o 936 338 61ms 16.8s 37.5s 62.3d 0 transport_latency_assumed price_change h 106,126,860 664,346 25ms 151ms 1.3s 46.7s 0 transport_latency_assumed price_change i 105,815,856 818,736 22ms 55ms 1.1s 9.6s 0 transport_latency_assumed price_change m 106,355,124 50,745,204 5ms 20ms 164ms 24.7s 0 transport_latency_assumed price_change n 106,049,588 146,740 46ms 135ms 5.4s 27.5s 0 transport_latency_assumed price_change o 106,438,780 54,252,798 5ms 20ms 167ms 12.8s 0 transport_latency_assumed tick_size_change h 3,312 22 23ms 116ms 647ms 950ms 0 transport_latency_assumed tick_size_change i 3,312 12 22ms 43ms 1.4s 1.5s 0 transport_latency_assumed tick_size_change m 3,312 1,618 5ms 16ms 90ms 197ms 0 transport_latency_assumed tick_size_change n 3,312 24 44ms 58ms 127ms 304ms 0 transport_latency_assumed tick_size_change o 3,312 1,636 5ms 16ms 68ms 212ms 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/16/2026-10-07T16.parquet sha256sum 2026-10-07T16.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.