Hour audit: 2026-10-06T11
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-06T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T11:00:00.000143116+00:00 · last event 2026-10-06T11:59:59.999979185+00:00
VOLUME 121,773,760 rows · 1,358,542,475 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 121,731,688 · o: 121,724,003 · i: 121,709,192 · h: 121,707,661 · n: 121,657,827 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 62,096,630 (50.99%) · o: 58,283,776 (47.86%) · i: 604,431 (0.50%) · h: 754,740 (0.62%) · n: 34,183 (0.03%) (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 121,773,760 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 aaa2b1aadc41afdaf6f11827dab2b8ae93180db2a124372507f17790e9395057
the corpus checksum ledger names this file with the same digest
joined 121,775,054 to merged 121,773,760, minus 1,294 (minus 0.0011%)
boundary drops 1,294 · 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-06T13:04: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 11,595,232 147,465,760 0-44 6c972bb97c976c8bc4e866379db5922af3734319d725e2be4894cb6ac3d55247 book 125,558 13,538,689 45-45 b70340f3969cc20c08dea8e7f1110faf16efd741930a7d070fa6902a501ed1b9 last_trade_price 53,770 3,124,453 46-46 7fca9bec86bc8a6b6d2baff78ab7f19ba6a27d3d6bf1ee4e9e738bd5b9fb2657 market_resolved 1,007 164,232 47-47 7b2894cc50e778def34b19214f3122ab0e37b472906db0463134b36448687ad0 new_market 1,347 130,447 48-48 784baa35650c63f77acbd6b31cb4aba65d83281b102d4b68a73c2606170179a0 price_change 109,991,838 1,192,546,881 49-468 d1e725bffc1f29ee07d0be65ff7db55a0740bf8a28897ce26dc13bfc01c113db tick_size_change 5,008 183,368 469-469 180cc90266d7091108a63dc1379339944388b5e12cd0f79448745f5811279f4f EVENT MIX count share price_change 109,991,838 90.32% best_bid_ask 11,595,232 9.52% book 125,558 0.10% last_trade_price 53,770 0.04% tick_size_change 5,008 <0.01% new_market 1,347 <0.01% market_resolved 1,007 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,595,384 11,595,232 152 104 FULL book 125,562 125,558 4 6,626 FULL last_trade_price 53,770 53,770 0 0 FULL market_resolved 1,007 1,007 0 0 FULL new_market 1,347 1,347 0 0 FULL price_change 109,992,976 109,991,838 1,138 87 FULL tick_size_change 5,008 5,008 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,593,866 67,493 18ms 28ms 205ms 57.3s 0 transport_latency_assumed best_bid_ask i 11,593,602 55,587 21ms 30ms 125ms 4.2s 0 transport_latency_assumed best_bid_ask m 11,594,480 5,916,255 5ms 13ms 85ms 6.3s 0 transport_latency_assumed best_bid_ask n 11,593,630 2,157 44ms 56ms 249ms 22.2s 0 transport_latency_assumed best_bid_ask o 11,593,860 5,553,740 5ms 13ms 87ms 11.7s 0 transport_latency_assumed book h 111,696 3,921 24ms 168ms 2.3h 111.0d 0 book_staleness book i 110,384 2,716 25ms 183ms 5.0min 111.0d 0 book_staleness book m 110,074 53,366 7ms 32ms 4.6s 111.0d 0 book_staleness book n 116,587 7,714 49ms 2.9s 18.2h 111.0d 0 book_staleness book o 111,622 57,841 7ms 37ms 1.4h 110.9d 0 book_staleness last_trade_price h 53,630 443 21ms 97ms 832ms 56.3s 0 transport_latency_assumed last_trade_price i 53,483 260 24ms 135ms 847ms 3.9s 0 transport_latency_assumed last_trade_price m 53,695 26,286 6ms 24ms 165ms 2.0s 0 transport_latency_assumed last_trade_price n 53,655 12 49ms 759ms 6.8s 22.2s 0 transport_latency_assumed last_trade_price o 53,574 26,769 6ms 23ms 195ms 4.6s 0 transport_latency_assumed market_resolved h 972 1 20ms 50ms 41.2s 51.5s 0 transport_latency_assumed market_resolved i 972 59 22ms 79ms 53.1s 53.2s 0 transport_latency_assumed market_resolved m 972 472 6ms 18ms 47.9s 56.8s 0 transport_latency_assumed market_resolved n 972 4 45ms 113ms 48.1s 48.2s 0 transport_latency_assumed market_resolved o 972 471 6ms 15ms 47.2s 57.4s 0 transport_latency_assumed new_market h 823 114 167ms 31.2s 49.8s 1.3min 0 transport_latency_assumed new_market i 823 193 134ms 31.8s 52.9s 1.6min 0 transport_latency_assumed new_market m 823 412 64ms 28.0s 50.7s 1.5min 0 transport_latency_assumed new_market n 823 198 229ms 23.8s 51.9s 1.6min 0 transport_latency_assumed new_market o 823 430 70ms 33.5s 57.0s 1.2min 0 transport_latency_assumed price_change h 109,941,666 682,744 19ms 33ms 323ms 57.5s 0 transport_latency_assumed price_change i 109,944,920 545,612 21ms 35ms 287ms 4.2s 0 transport_latency_assumed price_change m 109,966,636 56,097,176 5ms 15ms 95ms 7.1s 0 transport_latency_assumed price_change n 109,887,152 24,098 44ms 71ms 1.1s 22.2s 0 transport_latency_assumed price_change o 109,958,144 52,642,208 5ms 15ms 95ms 13.7s 0 transport_latency_assumed tick_size_change h 5,008 24 18ms 25ms 55ms 1.6s 0 transport_latency_assumed tick_size_change i 5,008 4 21ms 43ms 103ms 3.4s 0 transport_latency_assumed tick_size_change m 5,008 2,663 5ms 11ms 500ms 589ms 0 transport_latency_assumed tick_size_change n 5,008 not meas. 43ms 50ms 123ms 1.4s 0 transport_latency_assumed tick_size_change o 5,008 2,317 5ms 11ms 36ms 344ms 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/11/2026-10-06T11.parquet sha256sum 2026-10-06T11.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.