Hour audit: 2026-10-10T00
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-10T00 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 120,108,358 rows · 1,384,793,517 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 119,377,518 · o: 119,118,761 · m: 118,977,283 · h: 118,951,708 · n: 118,719,603 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 929,643 (0.77%) · o: 56,219,517 (46.81%) · m: 62,192,519 (51.78%) · h: 619,937 (0.52%) · n: 146,742 (0.12%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 120,108,358 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cdf2f0789c73dc2a61171a751b20dc5e9122b1a29e7c7539dc8b7776dee919bd
no line in the corpus checksum ledger names this file
joined 120,114,395 to merged 120,108,358, minus 6,037 (minus 0.0050%)
boundary drops 6,037 · 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-10T09:39: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 6/8 pass, 1 finding, 1 not evaluated
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
SKIPPED the hour's minutes have not been measured
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 11,528,178 142,345,247 0-43 9ef2dff4e40542361662e301113b9fb23d5fc1c7e19d687cb7073477179bfc66 book 929,555 81,170,029 44-47 67b708b101eec82e934bde72602058644d606bb3cb8efc11cce08d6b1b903b88 last_trade_price 52,870 2,996,128 48-48 f96d8701c47af4aaebb12a2da2d4e4b0e0b06b8bda41463aa7e78a8d63952819 market_resolved 1,184 190,840 49-49 70c975443898e5d8c4be98a59b74869e98577fbe72f3546c20c9352620e8a130 new_market 1,303 129,058 50-50 766c0ea41b5236de315a422b1252fbe63eb1d2ba40f3315b853b027c5b08fb29 price_change 107,592,824 1,156,506,525 51-461 ec91cc637e3b7254af9f9e53f2134cf4cbac2ce216e1d9dd1e95da06d9a25392 tick_size_change 2,444 88,198 462-462 c403de865cd3e798e93a9b6d581a0bad54d946fc65d1d6b30668c9d13617ffc0 EVENT MIX count share price_change 107,592,824 89.58% best_bid_ask 11,528,178 9.60% book 929,555 0.77% last_trade_price 52,870 0.04% tick_size_change 2,444 <0.01% new_market 1,303 <0.01% market_resolved 1,184 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,528,788 11,528,178 610 69 FULL book 929,580 929,555 25 255,867 FULL last_trade_price 52,874 52,870 4 2 FULL market_resolved 1,184 1,184 0 0 FULL new_market 1,303 1,303 0 0 FULL price_change 107,598,222 107,592,824 5,398 1,298 FULL tick_size_change 2,444 2,444 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,525,891 31,143 18ms 25ms 228ms 58.2s 0 transport_latency_assumed best_bid_ask i 11,527,167 33,850 21ms 28ms 82ms 3.1s 0 transport_latency_assumed best_bid_ask m 11,526,698 6,067,451 4ms 10ms 62ms 5.3s 0 transport_latency_assumed best_bid_ask n 11,525,886 4,439 44ms 53ms 178ms 8.6s 0 transport_latency_assumed best_bid_ask o 11,526,642 5,391,295 4ms 10ms 66ms 13.1s 0 transport_latency_assumed book h 477,759 242,507 5.5min 1.8d 48.5d 133.1d 0 book_staleness book i 244,850 131,777 22.7s 15.9h 45.2d 133.1d 0 book_staleness book m 423,002 231,518 4.3min 1.6d 48.5d 133.1d 0 book_staleness book n 296,117 92,981 1.3min 23.7h 47.6d 133.1d 0 book_staleness book o 420,411 230,772 4.2min 1.7d 48.5d 133.1d 0 book_staleness last_trade_price h 52,846 298 19ms 37ms 318ms 58.2s 0 transport_latency_assumed last_trade_price i 52,855 134 22ms 42ms 402ms 1.9s 0 transport_latency_assumed last_trade_price m 52,753 26,825 5ms 12ms 139ms 5.2s 0 transport_latency_assumed last_trade_price n 52,734 17 46ms 125ms 1.5s 6.9s 0 transport_latency_assumed last_trade_price o 52,790 25,596 5ms 14ms 120ms 4.5s 0 transport_latency_assumed market_resolved h 1,177 1 21ms 84ms 44.4s 54.6s 0 transport_latency_assumed market_resolved i 1,177 67 22ms 111ms 33.9s 58.0s 0 transport_latency_assumed market_resolved m 1,177 567 5ms 16ms 35.5s 45.3s 0 transport_latency_assumed market_resolved n 1,177 not meas. 47ms 208ms 52.4s 52.4s 0 transport_latency_assumed market_resolved o 1,177 549 5ms 15ms 52.0s 52.0s 0 transport_latency_assumed new_market h 835 376 49ms 12.2s 1.8min 2.5min 0 transport_latency_assumed new_market i 835 159 109ms 1.2min 2.2min 2.6min 0 transport_latency_assumed new_market m 835 371 76ms 1.1min 2.3min 2.6min 0 transport_latency_assumed new_market n 835 71 220ms 16.5s 2.2min 2.5min 0 transport_latency_assumed new_market o 835 326 96ms 15.4s 1.9min 2.2min 0 transport_latency_assumed price_change h 106,890,756 345,612 18ms 27ms 281ms 58.4s 0 transport_latency_assumed price_change i 107,548,190 763,656 21ms 29ms 138ms 3.1s 0 transport_latency_assumed price_change m 106,970,374 55,864,582 4ms 10ms 78ms 6.1s 0 transport_latency_assumed price_change n 106,840,410 49,234 44ms 57ms 300ms 10.0s 0 transport_latency_assumed price_change o 107,114,462 50,569,740 5ms 10ms 82ms 13.1s 0 transport_latency_assumed tick_size_change h 2,444 not meas. 18ms 22ms 54ms 147ms 0 transport_latency_assumed tick_size_change i 2,444 not meas. 21ms 27ms 46ms 63ms 0 transport_latency_assumed tick_size_change m 2,444 1,205 4ms 9ms 28ms 45ms 0 transport_latency_assumed tick_size_change n 2,444 not meas. 44ms 50ms 73ms 208ms 0 transport_latency_assumed tick_size_change o 2,444 1,239 4ms 9ms 23ms 44ms 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-10/00/2026-10-10T00.parquet sha256sum 2026-10-10T00.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.