Hour audit: 2026-10-04T22
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-04T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T22:00:00.000002175+00:00 · last event 2026-10-04T22:59:59.999998605+00:00
VOLUME 127,564,460 rows · 1,506,281,357 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 127,008,801 · m: 126,938,340 · h: 126,935,068 · i: 126,912,523 · n: 121,080,635 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 62,605,575 (49.08%) · m: 62,083,932 (48.67%) · h: 1,355,098 (1.06%) · i: 901,530 (0.71%) · n: 618,325 (0.48%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e4dc9508a78b17669af45d6d560282ffbca9a4bfc7d4f52bd3d93f9b76209948
the corpus checksum ledger names this file with the same digest
joined 127,566,410 to merged 127,564,460, minus 1,950 (minus 0.0015%)
boundary drops 1,950 · 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-05T00:22:26Z 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,864,968 139,196,626 0-41 efda8294142ce30236ffec5a6b771699cccd1ea07f92213d5b757febf68fbf89 book 664,824 64,198,702 42-44 1e2aef70fb33f5774ee6b372a123cc36dea96c232a1f91cdd7a70adb3c67df12 last_trade_price 70,040 4,007,457 45-45 fddcfdb49d25169b9a25d0a5e00dd932fa903c580fc759dd75f278c29e89aece market_resolved 3,140 469,369 46-46 1980207cd972e183bc4773159fda90b84d980ee27baf38a5b014f71975aa0f38 new_market 2,984 271,404 47-47 681310a291cf08f38fb5e397bcc5ef4f3c5c317c44aa00abe63a803345209979 price_change 115,953,948 1,296,516,349 48-490 54a5c04125b00277c3a51cde4e96e0c15d312707b246d8eb679e6bfe16ef1d2d tick_size_change 4,556 167,567 491-491 7660b748300fa023eb309ae4c1e52a85ee1ad319cea7689a4a38605e87e99f6a EVENT MIX count share price_change 115,953,948 90.90% best_bid_ask 10,864,968 8.52% book 664,824 0.52% last_trade_price 70,040 0.05% tick_size_change 4,556 <0.01% market_resolved 3,140 <0.01% new_market 2,984 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,865,076 10,864,968 108 737 FULL book 664,918 664,824 94 236,060 FULL last_trade_price 70,040 70,040 0 68 FULL market_resolved 3,140 3,140 0 41 FULL new_market 2,984 2,984 0 0 FULL price_change 115,955,696 115,953,948 1,748 2,575 FULL tick_size_change 4,556 4,556 0 22 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,862,823 103,627 19ms 35ms 367ms 1.1min 0 transport_latency_assumed best_bid_ask i 10,862,026 74,498 19ms 38ms 283ms 22.6s 0 transport_latency_assumed best_bid_ask m 10,863,796 5,308,826 5ms 19ms 139ms 4.8s 0 transport_latency_assumed best_bid_ask n 10,348,120 7,169 48ms 80ms 420ms 29.6s 0 transport_latency_assumed best_bid_ask o 10,864,058 5,370,848 5ms 19ms 150ms 8.1s 0 transport_latency_assumed book h 144,966 4,068 24ms 172ms 2.1min 109.5d 0 book_staleness book i 144,510 3,162 27ms 650ms 2.2min 68.1d 0 book_staleness book m 144,526 69,037 8ms 49ms 6.1s 109.4d 0 book_staleness book n 650,551 515,730 8.0min 23.7h 43.4d 128.0d 0 book_staleness book o 146,220 72,827 8ms 55ms 28.5min 109.5d 0 book_staleness last_trade_price h 69,923 980 21ms 117ms 755ms 1.0min 0 transport_latency_assumed last_trade_price i 69,631 338 25ms 413ms 6.2s 8.3s 0 transport_latency_assumed last_trade_price m 69,924 33,768 7ms 31ms 242ms 4.3s 0 transport_latency_assumed last_trade_price n 65,492 89 60ms 638ms 11.4s 29.7s 0 transport_latency_assumed last_trade_price o 69,989 34,865 7ms 30ms 247ms 7.3s 0 transport_latency_assumed market_resolved h 2,930 18 21ms 18.0s 48.2s 56.3s 0 transport_latency_assumed market_resolved i 2,930 302 22ms 15.1s 52.2s 56.1s 0 transport_latency_assumed market_resolved m 2,930 1,376 7ms 15.0s 51.9s 56.3s 0 transport_latency_assumed market_resolved n 2,968 155 51ms 26.0s 9.8min 12.3min 0 transport_latency_assumed market_resolved o 2,930 1,289 7ms 19.7s 51.8s 54.4s 0 transport_latency_assumed new_market h 1,740 219 161ms 27.1s 52.6s 1.7min 0 transport_latency_assumed new_market i 1,740 429 141ms 30.6s 49.6s 1.5min 0 transport_latency_assumed new_market m 1,740 759 49ms 25.8s 47.4s 1.4min 0 transport_latency_assumed new_market n 2,108 518 250ms 6.1min 8.0min 8.4min 0 transport_latency_assumed new_market o 1,740 1,059 48ms 26.8s 56.8s 1.5min 0 transport_latency_assumed price_change h 115,848,130 1,246,157 19ms 42ms 508ms 1.1min 0 transport_latency_assumed price_change i 115,827,130 822,789 20ms 50ms 711ms 24.9s 0 transport_latency_assumed price_change m 115,850,868 56,667,914 6ms 21ms 167ms 5.0s 0 transport_latency_assumed price_change n 110,006,928 94,660 49ms 102ms 2.0s 29.8s 0 transport_latency_assumed price_change o 115,919,308 57,122,428 6ms 21ms 176ms 8.2s 0 transport_latency_assumed tick_size_change h 4,556 29 19ms 30ms 296ms 7.2s 0 transport_latency_assumed tick_size_change i 4,556 12 19ms 32ms 254ms 1.2s 0 transport_latency_assumed tick_size_change m 4,556 2,252 5ms 15ms 95ms 249ms 0 transport_latency_assumed tick_size_change n 4,468 4 48ms 68ms 336ms 970ms 0 transport_latency_assumed tick_size_change o 4,556 2,259 5ms 17ms 104ms 289ms 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-04/22/2026-10-04T22.parquet sha256sum 2026-10-04T22.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.