Hour audit: 2026-10-05T04
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-05T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T04:00:00.000000533+00:00 · last event 2026-10-05T04:59:59.999960428+00:00
VOLUME 107,134,456 rows · 1,166,732,870 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 107,052,157 · m: 106,962,303 · h: 106,920,680 · i: 106,911,119 · n: 106,684,177 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 52,297,403 (48.81%) · m: 53,471,562 (49.91%) · h: 812,776 (0.76%) · i: 447,197 (0.42%) · n: 105,518 (0.10%) (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 107,134,456 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 94672be28fdddf7f9a731a9d0599bdd17cb99cce54880ac8575ade64c02f5d82
the corpus checksum ledger names this file with the same digest
joined 107,135,552 to merged 107,134,456, minus 1,096 (minus 0.0010%)
boundary drops 1,096 · 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-05T05:59:39Z 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,938,840 120,627,159 0-37 8710740a28638f72cb9ee456b2a1e95ef8bcf001bfcb54b5502f4a8c8b93d3b4 book 148,594 16,292,448 38-38 b4a2848785c805e62399a740faa525c54dd24734f6091cfc0690f902f846753c last_trade_price 49,508 2,810,952 39-39 f5754e71189a3ee7dc731bd771d8a5c221af70b9ec3449accb023345a343c62a market_resolved 974 146,715 40-40 9fb53db50772211829d3a8fc53d33db77bc3478bf4a379c0cc17ea45e84ff7d2 new_market 3,400 333,265 41-41 5cfe75204d2af82b7cfd25f63e8df7a35e092c68eeb1eb11e75852e6a1438f9d price_change 96,990,888 1,025,217,049 42-411 955dc5179083c682049acfd0251550509d3d9ef48fe65118a5611409272169b4 tick_size_change 2,252 85,100 412-412 90d7ddfdefbf0fbafa1d9b95f485a97746877236fe1b527de7ecf07259b1f250 EVENT MIX count share price_change 96,990,888 90.53% best_bid_ask 9,938,840 9.28% book 148,594 0.14% last_trade_price 49,508 0.05% new_market 3,400 <0.01% tick_size_change 2,252 <0.01% market_resolved 974 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,938,948 9,938,840 108 229 FULL book 148,598 148,594 4 18,783 FULL last_trade_price 49,508 49,508 0 0 FULL market_resolved 974 974 0 0 FULL new_market 3,400 3,400 0 0 FULL price_change 96,991,872 96,990,888 984 1,240 FULL tick_size_change 2,252 2,252 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,934,663 68,966 18ms 33ms 848ms 1.5min 0 transport_latency_assumed best_bid_ask i 9,935,502 35,751 21ms 35ms 372ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,937,326 4,964,020 5ms 15ms 125ms 9.8s 0 transport_latency_assumed best_bid_ask n 9,932,896 7,162 48ms 73ms 418ms 27.7s 0 transport_latency_assumed best_bid_ask o 9,937,531 4,862,941 5ms 15ms 148ms 7.1s 0 transport_latency_assumed book h 117,577 15,804 23ms 1.2min 8.1d 109.8d 0 book_staleness book i 111,460 9,952 25ms 2.5s 1.2d 109.7d 0 book_staleness book m 108,374 59,657 7ms 127ms 12.4h 109.7d 0 book_staleness book n 113,247 12,377 52ms 12.1s 3.1d 109.8d 0 book_staleness book o 107,840 50,804 7ms 111ms 10.8h 109.8d 0 book_staleness last_trade_price h 49,266 422 20ms 90ms 1.9s 1.2min 0 transport_latency_assumed last_trade_price i 49,265 249 23ms 82ms 2.0s 1.0min 0 transport_latency_assumed last_trade_price m 49,443 26,510 6ms 21ms 240ms 8.9s 0 transport_latency_assumed last_trade_price n 48,506 74 50ms 196ms 6.4s 27.7s 0 transport_latency_assumed last_trade_price o 49,462 22,253 6ms 24ms 272ms 2.3s 0 transport_latency_assumed market_resolved h 903 3 20ms 28.5s 52.8s 55.8s 0 transport_latency_assumed market_resolved i 903 128 24ms 25.4s 55.6s 56.4s 0 transport_latency_assumed market_resolved m 903 398 6ms 26.5s 51.3s 56.9s 0 transport_latency_assumed market_resolved n 903 29 50ms 194ms 53.1s 53.1s 0 transport_latency_assumed market_resolved o 903 416 6ms 69ms 56.2s 1.0min 0 transport_latency_assumed new_market h 2,189 383 339ms 52.7s 1.0min 1.7min 0 transport_latency_assumed new_market i 2,189 279 334ms 51.5s 1.0min 1.5min 0 transport_latency_assumed new_market m 2,189 994 152ms 52.5s 1.0min 1.6min 0 transport_latency_assumed new_market n 2,189 406 339ms 53.3s 1.1min 1.6min 0 transport_latency_assumed new_market o 2,189 1,338 108ms 51.9s 1.0min 1.6min 0 transport_latency_assumed price_change h 96,813,830 727,174 18ms 41ms 1.1s 1.5min 0 transport_latency_assumed price_change i 96,809,548 400,830 22ms 42ms 642ms 1.1min 0 transport_latency_assumed price_change m 96,861,816 48,418,997 5ms 17ms 144ms 9.8s 0 transport_latency_assumed price_change n 96,584,184 85,470 48ms 86ms 1.4s 28.0s 0 transport_latency_assumed price_change o 96,951,980 47,358,417 5ms 17ms 170ms 8.3s 0 transport_latency_assumed tick_size_change h 2,252 24 18ms 34ms 1.0s 4.2s 0 transport_latency_assumed tick_size_change i 2,252 8 22ms 36ms 252ms 511ms 0 transport_latency_assumed tick_size_change m 2,252 986 5ms 23ms 165ms 306ms 0 transport_latency_assumed tick_size_change n 2,252 not meas. 48ms 67ms 447ms 4.8s 0 transport_latency_assumed tick_size_change o 2,252 1,234 5ms 14ms 68ms 104ms 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-05/04/2026-10-05T04.parquet sha256sum 2026-10-05T04.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.