Hour audit: 2026-10-04T13
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-04T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T13:00:00.000014131+00:00 · last event 2026-10-04T13:59:59.999954023+00:00
VOLUME 107,528,589 rows · 1,204,721,927 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 107,473,469 · h: 107,468,312 · i: 107,466,887 · n: 107,441,685 · m: 107,431,463 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 54,231,202 (50.43%) · h: 487,321 (0.45%) · i: 316,906 (0.29%) · n: 48,835 (0.05%) · m: 52,444,325 (48.77%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,528,589 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 525d6a63e823d2e8ab4cc1e46ba278186c20b0c3ed4ec1a5a5cc39f9c919a50f
the corpus checksum ledger names this file with the same digest
joined 107,535,805 to merged 107,528,589, minus 7,216 (minus 0.0067%)
boundary drops 7,216 · 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-04T15:00:41Z 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 9,104,870 113,946,853 0-34 024c03683439ff55b5255835e74e77849b8bfb290903e5dda61d0be4c0dd9237 book 126,789 13,552,141 35-35 d31348df6eaf3cbab3f410c6e49f1f59e927def4a9f4b3b05f2428b75a820e0d last_trade_price 55,476 3,262,308 36-36 15ec1f8a70a9ec4026b47a26b4b0cae9c6da93dbda8cd326cf41e70b9c1a7020 market_resolved 760 110,879 37-37 9f731be96a510fa93536b335f3d19fcc0506f23483f4f3f24440448fe454de1e new_market 2,334 222,925 38-38 680020635394a9223afedf2c17c96efe8c836f77e976cd61b6e2123a8f0be352 price_change 98,233,416 1,072,216,924 39-413 44364d9e627a6e9daa6fc076307716bafb67a35b0faf42dbd03ed27557a8677b tick_size_change 4,944 183,438 414-414 543abd37d41a3390ac595e004b0db7f07d95ebf44a552e7d860498d33b9702d7 EVENT MIX count share price_change 98,233,416 91.36% best_bid_ask 9,104,870 8.47% book 126,789 0.12% last_trade_price 55,476 0.05% tick_size_change 4,944 <0.01% new_market 2,334 <0.01% market_resolved 760 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,104,944 9,104,870 74 193 FULL book 126,791 126,789 2 5,409 FULL last_trade_price 55,476 55,476 0 0 FULL market_resolved 760 760 0 0 FULL new_market 2,334 2,334 0 0 FULL price_change 98,240,556 98,233,416 7,140 635 FULL tick_size_change 4,944 4,944 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,102,897 36,921 18ms 26ms 280ms 49.8s 0 transport_latency_assumed best_bid_ask i 9,103,228 25,899 20ms 27ms 157ms 6.8s 0 transport_latency_assumed best_bid_ask m 9,103,872 4,444,222 5ms 11ms 90ms 7.0s 0 transport_latency_assumed best_bid_ask n 9,102,452 3,088 46ms 58ms 248ms 12.9s 0 transport_latency_assumed best_bid_ask o 9,103,900 4,594,740 5ms 11ms 94ms 6.6s 0 transport_latency_assumed book h 116,136 3,415 23ms 77ms 47.7min 109.1d 0 book_staleness book i 115,690 2,696 23ms 99ms 8.2min 109.1d 0 book_staleness book m 116,465 61,535 7ms 29ms 58.3min 109.1d 0 book_staleness book n 117,164 3,742 51ms 310ms 1.3h 109.1d 0 book_staleness book o 116,066 55,401 7ms 30ms 36.3min 109.1d 0 book_staleness last_trade_price h 55,342 340 20ms 41ms 633ms 36.3s 0 transport_latency_assumed last_trade_price i 55,424 174 22ms 61ms 600ms 3.3s 0 transport_latency_assumed last_trade_price m 55,369 28,494 6ms 16ms 182ms 2.6s 0 transport_latency_assumed last_trade_price n 55,283 38 50ms 159ms 3.2s 12.9s 0 transport_latency_assumed last_trade_price o 55,368 26,430 6ms 17ms 187ms 6.6s 0 transport_latency_assumed market_resolved h 682 64 20ms 52ms 597ms 36.3s 0 transport_latency_assumed market_resolved i 682 15 22ms 73ms 56.5s 56.5s 0 transport_latency_assumed market_resolved m 682 379 6ms 44.7s 56.3s 57.3s 0 transport_latency_assumed market_resolved n 682 not meas. 48ms 125ms 56.0s 56.1s 0 transport_latency_assumed market_resolved o 682 302 6ms 45.2s 57.4s 58.2s 0 transport_latency_assumed new_market h 1,421 215 166ms 35.1s 1.3min 1.8min 0 transport_latency_assumed new_market i 1,421 240 126ms 33.4s 1.3min 1.8min 0 transport_latency_assumed new_market m 1,421 814 63ms 35.9s 1.3min 1.8min 0 transport_latency_assumed new_market n 1,421 187 193ms 32.5s 1.2min 1.7min 0 transport_latency_assumed new_market o 1,421 878 62ms 35.4s 1.3min 1.8min 0 transport_latency_assumed price_change h 98,186,890 446,358 18ms 29ms 375ms 49.9s 0 transport_latency_assumed price_change i 98,185,498 287,878 21ms 31ms 278ms 7.0s 0 transport_latency_assumed price_change m 98,148,710 47,906,438 5ms 12ms 100ms 7.4s 0 transport_latency_assumed price_change n 98,159,739 41,780 47ms 67ms 542ms 13.0s 0 transport_latency_assumed price_change o 98,191,088 49,550,962 5ms 12ms 105ms 7.4s 0 transport_latency_assumed tick_size_change h 4,944 8 18ms 27ms 526ms 5.0s 0 transport_latency_assumed tick_size_change i 4,944 4 20ms 26ms 299ms 1.5s 0 transport_latency_assumed tick_size_change m 4,944 2,443 5ms 11ms 72ms 346ms 0 transport_latency_assumed tick_size_change n 4,944 not meas. 46ms 58ms 388ms 672ms 0 transport_latency_assumed tick_size_change o 4,944 2,489 5ms 11ms 89ms 941ms 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/13/2026-10-04T13.parquet sha256sum 2026-10-04T13.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.