Hour audit: 2026-10-07T14
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-07T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T14:00:00.000058802+00:00 · last event 2026-10-07T14:59:59.999934735+00:00
VOLUME 133,065,182 rows · 1,564,148,332 bytes (1.46 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 132,639,981 · o: 132,437,065 · m: 132,407,628 · h: 132,282,071 · n: 131,899,032 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,769,464 (1.33%) · o: 63,351,618 (47.61%) · m: 65,880,667 (49.51%) · h: 1,971,564 (1.48%) · n: 91,869 (0.07%) (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,065,182 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7c001007c40ea712e887c0f67daf267c0b7c81f21d4cd24561fadba36d8c4483
the corpus checksum ledger names this file with the same digest
joined 133,066,980 to merged 133,065,182, minus 1,798 (minus 0.0014%)
boundary drops 1,798 · 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:43:28Z 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,437,392 139,310,486 0-39 1f3f78938a6ef06e460b9a35d98f73a5e383e75b29657c2cbe7eb6ff304e8f25 book 773,624 70,206,829 40-42 bd897a56bbb8688d168849a4e7a6885aafcc9634096d20ebe775e17d01fbe639 last_trade_price 66,897 3,813,400 43-43 ffab99c4a4402ef58c60f2288e99e0d6b091748f592133620ffa75fe13dd3e59 market_resolved 840 139,459 44-44 10a3e03463ede400bc4c7416746d44c1f56041878ec79c83ddd2080add2932ab new_market 1,115 110,493 45-45 34a7e70c912c22efba151dcc7faab316c15a715ce0189ff18ba2af2b0df09f5d price_change 121,781,158 1,348,899,780 46-510 9e3104ceed9020c0b3cc5b185294c8c32ff9678cb355448469a36a83729d6bd5 tick_size_change 4,156 154,796 511-511 1a1c1711242885dbb42400efe0681d68fe88094b57902dc23e4f3f8253fb27db EVENT MIX count share price_change 121,781,158 91.52% best_bid_ask 10,437,392 7.84% book 773,624 0.58% last_trade_price 66,897 0.05% tick_size_change 4,156 <0.01% new_market 1,115 <0.01% market_resolved 840 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,437,504 10,437,392 112 73 FULL book 774,144 773,624 520 225,231 FULL last_trade_price 66,897 66,897 0 0 FULL market_resolved 840 840 0 0 FULL new_market 1,115 1,115 0 0 FULL price_change 121,782,324 121,781,158 1,166 41 FULL tick_size_change 4,156 4,156 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,436,156 141,909 20ms 41ms 205ms 49.0s 0 transport_latency_assumed best_bid_ask i 10,430,634 95,065 22ms 42ms 165ms 7.2s 0 transport_latency_assumed best_bid_ask m 10,435,702 5,162,810 6ms 23ms 112ms 3.0s 0 transport_latency_assumed best_bid_ask n 10,431,162 4,020 45ms 73ms 331ms 19.3s 0 transport_latency_assumed best_bid_ask o 10,436,029 5,033,588 6ms 23ms 116ms 6.4s 0 transport_latency_assumed book h 139,220 6,053 27ms 286ms 3.7h 112.1d 0 book_staleness book i 668,650 482,028 5.6min 1.7d 46.0d 130.7d 0 book_staleness book m 197,223 117,343 15ms 4.1h 30.2d 130.7d 0 book_staleness book n 180,481 41,431 127ms 2.6h 30.1d 112.2d 0 book_staleness book o 204,461 126,769 16ms 5.8h 30.2d 130.7d 0 book_staleness last_trade_price h 66,764 1,264 23ms 166ms 1.7s 9.3s 0 transport_latency_assumed last_trade_price i 66,466 685 27ms 237ms 2.4s 7.2s 0 transport_latency_assumed last_trade_price m 66,674 31,799 8ms 35ms 188ms 1.8s 0 transport_latency_assumed last_trade_price n 65,318 62 63ms 1.5s 10.5s 19.3s 0 transport_latency_assumed last_trade_price o 66,790 33,087 8ms 36ms 204ms 1.8s 0 transport_latency_assumed market_resolved h 839 8 21ms 59ms 11.4s 51.9s 0 transport_latency_assumed market_resolved i 839 13 23ms 54ms 11.5s 51.9s 0 transport_latency_assumed market_resolved m 839 424 7ms 29ms 11.4s 51.9s 0 transport_latency_assumed market_resolved n 839 1 47ms 120ms 28.6s 28.7s 0 transport_latency_assumed market_resolved o 839 394 7ms 25ms 12.5s 53.4s 0 transport_latency_assumed new_market h 672 149 119ms 11.5s 28.7s 1.3min 0 transport_latency_assumed new_market i 672 150 102ms 14.4s 45.4s 1.6min 0 transport_latency_assumed new_market m 672 442 42ms 11.0s 27.6s 1.5min 0 transport_latency_assumed new_market n 672 107 175ms 11.8s 45.1s 1.6min 0 transport_latency_assumed new_market o 672 267 57ms 10.2s 28.6s 1.4min 0 transport_latency_assumed price_change h 121,634,264 1,822,114 21ms 50ms 342ms 49.0s 0 transport_latency_assumed price_change i 121,468,564 1,191,486 22ms 54ms 545ms 7.2s 0 transport_latency_assumed price_change m 121,702,362 60,565,758 6ms 26ms 126ms 3.5s 0 transport_latency_assumed price_change n 121,216,404 46,248 46ms 122ms 3.4s 19.3s 0 transport_latency_assumed price_change o 121,724,118 58,155,552 6ms 26ms 131ms 6.4s 0 transport_latency_assumed tick_size_change h 4,156 67 20ms 40ms 104ms 2.2s 0 transport_latency_assumed tick_size_change i 4,156 37 22ms 45ms 117ms 223ms 0 transport_latency_assumed tick_size_change m 4,156 2,091 6ms 24ms 107ms 248ms 0 transport_latency_assumed tick_size_change n 4,156 not meas. 45ms 76ms 199ms 629ms 0 transport_latency_assumed tick_size_change o 4,156 1,961 6ms 23ms 116ms 267ms 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/14/2026-10-07T14.parquet sha256sum 2026-10-07T14.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.