Hour audit: 2026-10-06T17
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T17 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T17:00:00.000017845+00:00 · last event 2026-10-06T17:59:59.999956504+00:00
VOLUME 115,555,907 rows · 1,382,619,810 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 114,689,148 · o: 114,666,832 · h: 114,603,077 · i: 114,550,727 · n: 114,474,499 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 54,967,264 (47.57%) · o: 58,195,718 (50.36%) · h: 909,202 (0.79%) · i: 1,141,081 (0.99%) · n: 342,642 (0.30%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 b661bb553382d5630c81ec2f41a9e8c0fcbbfe9241b7eaf47b4ace27db45514f
no line in the corpus checksum ledger names this file
joined 115,557,939 to merged 115,555,907, minus 2,032 (minus 0.0018%)
boundary drops 2,032 · 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-06T19:06:25Z 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 7/8 pass, 1 finding
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
FINDING the checksum ledger does not name 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,570,488 135,906,330 0-40 a13a8f6fe7fe9b2cc855cf61e145c65193e72ea059b3857dc3a30c68467264dc book 1,434,339 95,441,096 41-46 2cb28cbe38a03a35efc10eddc6164f7964e424d998498c6a0948f237ec7b6381 last_trade_price 55,125 3,165,448 47-47 b9594a57b99e508974a6c523a3df5e7fe504ada2258b62863ccd7dace4839d60 market_resolved 1,669 261,172 48-48 78de50c67c93dbbbc00c53985ba2c5064527ac690fe99fad104bde5be671320d new_market 3,346 326,788 49-49 bf33432ef6906837c0e616a27d70dc8609c35570691d9c952392fcff2026c1e3 price_change 103,487,992 1,146,091,486 50-444 7f243e79a9468369e4f18ffb56b95bba030c7ea7f15f91616ad96eae44e59e2a tick_size_change 2,948 109,529 445-445 adbcdd1a6565b8c8ce21d8295284b0d8634bec6ad26f787c563f0bab600f77a4 EVENT MIX count share price_change 103,487,992 89.56% best_bid_ask 10,570,488 9.15% book 1,434,339 1.24% last_trade_price 55,125 0.05% new_market 3,346 <0.01% tick_size_change 2,948 <0.01% market_resolved 1,669 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,570,680 10,570,488 192 69 FULL book 1,434,373 1,434,339 34 212,091 FULL last_trade_price 55,125 55,125 0 1 FULL market_resolved 1,669 1,669 0 0 FULL new_market 3,346 3,346 0 0 FULL price_change 103,489,798 103,487,992 1,806 38 FULL tick_size_change 2,948 2,948 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,566,009 54,960 20ms 47ms 397ms 1.4min 0 transport_latency_assumed best_bid_ask i 10,567,156 82,662 21ms 32ms 172ms 4.2s 0 transport_latency_assumed best_bid_ask m 10,568,364 5,067,599 5ms 14ms 127ms 5.4s 0 transport_latency_assumed best_bid_ask n 10,565,415 4,434 45ms 69ms 337ms 10.2s 0 transport_latency_assumed best_bid_ask o 10,568,048 5,360,833 5ms 15ms 149ms 28.5s 0 transport_latency_assumed book h 562,496 257,176 5.9min 1.3d 45.2d 129.8d 0 book_staleness book i 523,730 234,305 5.5min 1.3d 45.2d 129.8d 0 book_staleness book m 603,395 333,064 6.4min 1.3d 45.2d 129.8d 0 book_staleness book n 589,151 279,789 6.2min 1.3d 45.2d 129.8d 0 book_staleness book o 589,854 330,005 6.4min 1.3d 45.2d 129.8d 0 book_staleness last_trade_price h 54,952 271 23ms 202ms 1.2s 1.1min 0 transport_latency_assumed last_trade_price i 54,903 275 26ms 254ms 1.7s 3.9s 0 transport_latency_assumed last_trade_price m 55,037 25,347 6ms 23ms 209ms 2.8s 0 transport_latency_assumed last_trade_price n 54,613 21 55ms 801ms 7.9s 10.2s 0 transport_latency_assumed last_trade_price o 54,986 29,211 6ms 24ms 226ms 4.0s 0 transport_latency_assumed market_resolved h 1,615 21 22ms 23.4s 49.5s 56.5s 0 transport_latency_assumed market_resolved i 1,615 289 24ms 15.1s 47.1s 47.9s 0 transport_latency_assumed market_resolved m 1,615 611 7ms 16.3s 48.4s 49.0s 0 transport_latency_assumed market_resolved n 1,615 44 48ms 29.3s 44.6s 54.7s 0 transport_latency_assumed market_resolved o 1,615 704 6ms 21.5s 53.8s 54.5s 0 transport_latency_assumed new_market h 2,059 599 192ms 43.8s 2.0min 2.7min 0 transport_latency_assumed new_market i 2,059 602 95ms 38.2s 1.9min 2.7min 0 transport_latency_assumed new_market m 2,059 919 78ms 49.2s 2.0min 2.7min 0 transport_latency_assumed new_market n 2,059 246 173ms 44.2s 1.9min 2.7min 0 transport_latency_assumed new_market o 2,059 980 82ms 48.3s 2.0min 2.6min 0 transport_latency_assumed price_change h 103,412,998 596,154 20ms 64ms 664ms 1.4min 0 transport_latency_assumed price_change i 103,398,316 822,890 22ms 43ms 585ms 4.2s 0 transport_latency_assumed price_change m 103,455,730 49,538,270 5ms 16ms 159ms 6.6s 0 transport_latency_assumed price_change n 103,258,698 58,104 46ms 96ms 1.8s 11.3s 0 transport_latency_assumed price_change o 103,447,322 52,472,574 5ms 16ms 177ms 31.0s 0 transport_latency_assumed tick_size_change h 2,948 21 20ms 60ms 438ms 1.6s 0 transport_latency_assumed tick_size_change i 2,948 58 22ms 43ms 151ms 364ms 0 transport_latency_assumed tick_size_change m 2,948 1,454 5ms 22ms 96ms 311ms 0 transport_latency_assumed tick_size_change n 2,948 4 45ms 78ms 418ms 567ms 0 transport_latency_assumed tick_size_change o 2,948 1,411 5ms 27ms 225ms 1.7s 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-06/17/2026-10-06T17.parquet sha256sum 2026-10-06T17.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.