Hour audit: 2026-10-07T18
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-07T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T18:00:00.000026383+00:00 · last event 2026-10-07T18:59:59.999995827+00:00
VOLUME 112,949,648 rows · 1,278,697,535 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 112,775,583 · m: 112,713,473 · h: 112,691,243 · i: 112,666,353 · n: 112,243,153 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 53,295,164 (47.18%) · m: 57,892,772 (51.26%) · h: 867,327 (0.77%) · i: 809,006 (0.72%) · n: 85,379 (0.08%) (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 112,949,648 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 889542db260c0ef30cc00c6d23e03c9cdc5cd3933addd94855171bb3724a16a1
the corpus checksum ledger names this file with the same digest
joined 112,951,072 to merged 112,949,648, minus 1,424 (minus 0.0013%)
boundary drops 1,424 · 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-07T20:02:54Z 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,736,720 124,541,308 0-37 1bd14c4732419410cb48b6cfc3ce91ed882f57e41c47f6d3729f83a364ee83d0 book 288,255 30,008,179 38-39 981429510c2d89d83cbbfc753373aad659a2bb372b75c33696dff506627f383d last_trade_price 56,090 3,219,668 40-40 14d7654edab035b98ce5f769a96d4e0eb736420c911167a66271d1960757636e market_resolved 654 105,527 41-41 b8c7f21959dfe07a1b26214c345672cbb99e3b2ceb9c187990890df7243d82c6 new_market 2,779 269,125 42-42 68db174a065c3fc93c292cc8cd72389ec7710f40c2b1e3587a252877ba2ffa48 price_change 102,863,018 1,119,182,166 43-435 4c9d4e95e2dae5c28cf4d763a4a806a002306269da17a4069e88785e820a6d1c tick_size_change 2,132 80,405 436-436 845bc6ee46e2164d05a21d1d123a6cad852b5a7f933f471b7f0411a4ab95f8c1 EVENT MIX count share price_change 102,863,018 91.07% best_bid_ask 9,736,720 8.62% book 288,255 0.26% last_trade_price 56,090 0.05% new_market 2,779 <0.01% tick_size_change 2,132 <0.01% market_resolved 654 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,736,812 9,736,720 92 379 FULL book 288,259 288,255 4 74,728 FULL last_trade_price 56,092 56,090 2 3 FULL market_resolved 654 654 0 1 FULL new_market 2,779 2,779 0 0 FULL price_change 102,864,344 102,863,018 1,326 83 FULL tick_size_change 2,132 2,132 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,732,066 65,218 19ms 42ms 509ms 2.6min 0 transport_latency_assumed best_bid_ask i 9,732,243 65,118 22ms 35ms 221ms 21.4s 0 transport_latency_assumed best_bid_ask m 9,733,249 4,987,830 5ms 16ms 154ms 7.8s 0 transport_latency_assumed best_bid_ask n 9,727,258 4,285 44ms 71ms 564ms 36.0s 0 transport_latency_assumed best_bid_ask o 9,734,554 4,614,269 5ms 16ms 171ms 27.8s 0 transport_latency_assumed book h 145,770 29,590 37ms 1.3h 28.1d 129.2d 0 book_staleness book i 163,068 47,479 57ms 4.4h 30.3d 130.8d 0 book_staleness book m 151,890 89,543 11ms 2.2h 28.4d 112.4d 0 book_staleness book n 150,160 36,339 150ms 2.7h 30.3d 130.9d 0 book_staleness book o 147,869 85,304 10ms 2.0h 28.4d 112.4d 0 book_staleness last_trade_price h 55,795 530 23ms 239ms 1.8s 1.0min 0 transport_latency_assumed last_trade_price i 55,676 307 27ms 458ms 2.9s 21.5s 0 transport_latency_assumed last_trade_price m 55,764 27,903 7ms 33ms 268ms 2.1s 0 transport_latency_assumed last_trade_price n 54,184 45 63ms 2.6s 11.4s 36.0s 0 transport_latency_assumed last_trade_price o 55,958 27,305 7ms 28ms 276ms 6.0s 0 transport_latency_assumed market_resolved h 644 10 22ms 280ms 33.3s 35.9s 0 transport_latency_assumed market_resolved i 644 57 25ms 257ms 51.0s 55.8s 0 transport_latency_assumed market_resolved m 644 286 7ms 95ms 51.2s 55.7s 0 transport_latency_assumed market_resolved n 643 1 47ms 376ms 43.0s 45.4s 0 transport_latency_assumed market_resolved o 644 300 7ms 96ms 51.2s 55.9s 0 transport_latency_assumed new_market h 1,740 340 225ms 41.2s 52.8s 1.6min 0 transport_latency_assumed new_market i 1,740 450 127ms 41.1s 51.8s 1.7min 0 transport_latency_assumed new_market m 1,740 1,038 69ms 39.0s 50.6s 1.6min 0 transport_latency_assumed new_market n 1,740 327 302ms 42.5s 49.8s 1.2min 0 transport_latency_assumed new_market o 1,740 624 130ms 42.2s 51.3s 1.1min 0 transport_latency_assumed price_change h 102,753,096 771,628 20ms 55ms 796ms 2.8min 0 transport_latency_assumed price_change i 102,710,850 695,586 22ms 49ms 940ms 21.8s 0 transport_latency_assumed price_change m 102,768,054 52,785,034 5ms 18ms 179ms 9.1s 0 transport_latency_assumed price_change n 102,307,036 44,382 45ms 131ms 4.3s 37.8s 0 transport_latency_assumed price_change o 102,832,686 48,566,388 6ms 18ms 193ms 28.5s 0 transport_latency_assumed tick_size_change h 2,132 11 21ms 68ms 1.0s 17.8s 0 transport_latency_assumed tick_size_change i 2,132 9 22ms 48ms 140ms 2.8s 0 transport_latency_assumed tick_size_change m 2,132 1,138 6ms 18ms 123ms 317ms 0 transport_latency_assumed tick_size_change n 2,132 not meas. 45ms 89ms 512ms 746ms 0 transport_latency_assumed tick_size_change o 2,132 974 6ms 20ms 153ms 1.6s 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/18/2026-10-07T18.parquet sha256sum 2026-10-07T18.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.