Hour audit: 2026-10-04T14
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-04T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T14:00:00.000022837+00:00 · last event 2026-10-04T14:59:59.999968991+00:00
VOLUME 116,347,086 rows · 1,325,697,367 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 116,288,972 · m: 116,264,228 · i: 116,254,092 · h: 116,238,466 · n: 116,127,886 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 60,164,102 (51.71%) · m: 54,636,412 (46.96%) · i: 507,575 (0.44%) · h: 928,614 (0.80%) · n: 110,383 (0.09%) (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 116,347,086 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f987742977b0e9b5706b78df9863e9c2b47856e41fcec7faf980a3ae9c4d1864
the corpus checksum ledger names this file with the same digest
joined 116,349,422 to merged 116,347,086, minus 2,336 (minus 0.0020%)
boundary drops 2,336 · 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-04T16:03:17Z 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,573,316 121,401,943 0-36 92d24cbb71182a808fd843bf2e44546b16281c714e8ea3b38906f23435b46048 book 135,341 14,623,726 37-37 0ac4e5b858e7ebbbc5a4ddd0f4b1a308a56169169ccf384e6497194312ea5fb2 last_trade_price 56,486 3,288,759 38-38 0b15ec6a00c030fbab40f6ddb7ae06c9a4999c7d67822c5c78443b8c5f156a46 market_resolved 712 117,339 39-39 d99a1578971140521c8758b3be31959b379ff7adebe28208f0130931171d9e87 new_market 4,349 473,602 40-40 8ecbc5be9aa7d4e62f15d0a59650e8bec2d68ac7cc7b8b63362a97ac55d27c4d price_change 106,571,578 1,184,271,782 41-447 1bbc7f034d2c96dafe1dd71c1821957d03b4d9406c64c662d2a24e1829cdbc03 tick_size_change 5,304 193,462 448-448 e6fd66e857a1f03b6265111f2ecec8c1efcffa29239f1176fb9a09ff1b1e8c38 EVENT MIX count share price_change 106,571,578 91.60% best_bid_ask 9,573,316 8.23% book 135,341 0.12% last_trade_price 56,486 0.05% tick_size_change 5,304 <0.01% new_market 4,349 <0.01% market_resolved 712 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,573,622 9,573,316 306 299 FULL book 135,341 135,341 0 5,766 FULL last_trade_price 56,486 56,486 0 1 FULL market_resolved 712 712 0 0 FULL new_market 4,349 4,349 0 0 FULL price_change 106,573,608 106,571,578 2,030 940 FULL tick_size_change 5,304 5,304 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,570,632 68,850 19ms 34ms 740ms 2.3min 0 transport_latency_assumed best_bid_ask i 9,570,421 37,829 23ms 37ms 309ms 10.6s 0 transport_latency_assumed best_bid_ask m 9,572,060 4,585,596 5ms 15ms 190ms 18.9s 0 transport_latency_assumed best_bid_ask n 9,567,833 7,402 47ms 71ms 482ms 37.9s 0 transport_latency_assumed best_bid_ask o 9,572,026 4,873,639 5ms 15ms 185ms 8.2s 0 transport_latency_assumed book h 123,062 6,972 24ms 499ms 2.5h 109.2d 0 book_staleness book i 121,854 4,893 27ms 538ms 1.3h 109.1d 0 book_staleness book m 120,988 53,849 8ms 88ms 12.6min 109.2d 0 book_staleness book n 121,411 4,774 53ms 2.3s 2.2h 109.0d 0 book_staleness book o 120,608 64,853 7ms 70ms 3.2min 109.2d 0 book_staleness last_trade_price h 56,307 653 21ms 85ms 1.3s 55.8s 0 transport_latency_assumed last_trade_price i 56,251 209 26ms 149ms 2.9s 7.5s 0 transport_latency_assumed last_trade_price m 56,440 25,123 6ms 28ms 319ms 7.3s 0 transport_latency_assumed last_trade_price n 55,759 70 53ms 404ms 8.7s 38.2s 0 transport_latency_assumed last_trade_price o 56,433 30,431 6ms 24ms 283ms 6.6s 0 transport_latency_assumed market_resolved h 698 9 21ms 60ms 514ms 22.5s 0 transport_latency_assumed market_resolved i 698 7 24ms 73ms 357ms 57.6s 0 transport_latency_assumed market_resolved m 698 350 6ms 16ms 56.1s 1.0min 0 transport_latency_assumed market_resolved n 698 2 49ms 122ms 356ms 58.5s 0 transport_latency_assumed market_resolved o 698 344 6ms 16ms 50.6s 1.0min 0 transport_latency_assumed new_market h 3,157 800 16.7s 35.7s 1.1min 1.7min 0 transport_latency_assumed new_market i 3,157 689 19.2s 41.0s 1.0min 1.7min 0 transport_latency_assumed new_market m 3,157 1,271 17.9s 35.5s 1.1min 1.7min 0 transport_latency_assumed new_market n 3,157 395 17.4s 38.1s 1.2min 1.7min 0 transport_latency_assumed new_market o 3,157 1,194 17.9s 36.0s 1.0min 1.2min 0 transport_latency_assumed price_change h 106,479,306 851,318 19ms 41ms 955ms 2.3min 0 transport_latency_assumed price_change i 106,496,407 463,948 23ms 46ms 503ms 10.8s 0 transport_latency_assumed price_change m 106,505,581 49,967,637 5ms 17ms 226ms 21.1s 0 transport_latency_assumed price_change n 106,373,724 97,740 47ms 96ms 2.0s 38.6s 0 transport_latency_assumed price_change o 106,530,746 55,190,935 5ms 17ms 216ms 8.6s 0 transport_latency_assumed tick_size_change h 5,304 12 18ms 28ms 380ms 34.4s 0 transport_latency_assumed tick_size_change i 5,304 not meas. 23ms 33ms 95ms 959ms 0 transport_latency_assumed tick_size_change m 5,304 2,586 5ms 11ms 41ms 574ms 0 transport_latency_assumed tick_size_change n 5,304 not meas. 47ms 61ms 217ms 672ms 0 transport_latency_assumed tick_size_change o 5,304 2,706 5ms 11ms 50ms 991ms 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/14/2026-10-04T14.parquet sha256sum 2026-10-04T14.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.