Hour audit: 2026-10-04T05
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-04T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T05:00:00.000124301+00:00 · last event 2026-10-04T05:59:59.999972878+00:00
VOLUME 101,387,496 rows · 1,056,236,335 bytes (1007.31 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 101,328,986 · i: 101,306,319 · k: 101,304,606 · h: 101,303,844 · g: 101,212,657 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 96,853,085 (95.53%) · i: 426,899 (0.42%) · k: 3,118,776 (3.08%) · h: 956,843 (0.94%) · g: 31,893 (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 101,387,496 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f795da59d45bbae8bbf341aeed0582b5271e1176895ec8b91f1a71a570b7d3ed
the corpus checksum ledger names this file with the same digest
joined 101,389,303 to merged 101,387,496, minus 1,807 (minus 0.0018%)
boundary drops 1,807 · 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-04T07:44:17Z as ghikm
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,713,982 113,362,364 0-37 063cc39b504a3af9bf3a8f42438efb0fe01b02374d5d3d007ea967dff4341d31 book 142,632 14,362,509 38-38 7d526bc4fd451b5c21bcc624e846a88615cdee6d809ddd620d6618b0217fdafb last_trade_price 46,029 2,684,944 39-39 c584383a609518bcda1787a3fd0c1eefeb99954b6305f1ba4f2682c1a838daa8 market_resolved 1,645 261,988 40-40 9ad5cbaaaca4aa0d6d3c9f3e2f4a5067e6c1430f5464ac3e60820305e55fbddc new_market 2,360 260,032 41-41 8d4ba50d7b3755d7954883945f45a14eb62ca49f74fd8c2612d3c1276557aa00 price_change 91,477,380 924,018,696 42-390 b3197a9e014b4c152f3c546f024cd854ca4c77be000f0ab9ca19ff9d58312f2e tick_size_change 3,468 127,640 391-391 e1f8ee397399d91e970554176112b22ea730191f513d63aa358e4964de0bd21f EVENT MIX count share price_change 91,477,380 90.23% best_bid_ask 9,713,982 9.58% book 142,632 0.14% last_trade_price 46,029 0.05% tick_size_change 3,468 <0.01% new_market 2,360 <0.01% market_resolved 1,645 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,714,182 9,713,982 200 158 FULL book 142,660 142,632 28 20,791 FULL last_trade_price 46,030 46,029 1 0 FULL market_resolved 1,645 1,645 0 0 FULL new_market 2,360 2,360 0 0 FULL price_change 91,478,958 91,477,380 1,578 424 FULL tick_size_change 3,468 3,468 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,710,944 925 76ms 96ms 526ms 53.0s 0 transport_latency_assumed best_bid_ask h 9,712,800 75,951 17ms 24ms 369ms 1.4min 0 transport_latency_assumed best_bid_ask i 9,712,823 32,826 21ms 27ms 191ms 11.8s 0 transport_latency_assumed best_bid_ask k 9,712,788 276,971 13ms 21ms 271ms 1.2min 0 transport_latency_assumed best_bid_ask m 9,713,211 9,327,309 4ms 9ms 76ms 5.1s 0 transport_latency_assumed book g 114,779 20,125 83ms 12.1min 24.8d 127.3d 0 book_staleness book h 105,903 13,078 21ms 8.2s 4.9d 125.7d 0 book_staleness book i 97,414 3,010 23ms 82ms 1.2h 108.7d 0 book_staleness book k 102,706 11,377 16ms 1.1s 1.4d 108.7d 0 book_staleness book m 102,924 95,042 6ms 882ms 2.2d 119.6d 0 book_staleness last_trade_price g 45,687 7 80ms 196ms 10.9s 52.7s 0 transport_latency_assumed last_trade_price h 45,971 729 19ms 32ms 466ms 49.0s 0 transport_latency_assumed last_trade_price i 45,973 277 22ms 38ms 427ms 4.0s 0 transport_latency_assumed last_trade_price k 46,005 2,037 14ms 28ms 460ms 33.1s 0 transport_latency_assumed last_trade_price m 45,902 42,979 5ms 13ms 150ms 3.1s 0 transport_latency_assumed market_resolved g 1,590 1 78ms 592ms 52.9s 1.9min 0 transport_latency_assumed market_resolved h 1,590 11 19ms 2.7s 49.0s 49.1s 0 transport_latency_assumed market_resolved i 1,590 10 22ms 121ms 52.4s 56.1s 0 transport_latency_assumed market_resolved k 1,590 73 14ms 244ms 52.8s 54.2s 0 transport_latency_assumed market_resolved m 1,590 1,550 5ms 20.6s 52.8s 54.2s 0 transport_latency_assumed new_market g 1,775 401 22.8s 1.1min 1.4min 1.7min 0 transport_latency_assumed new_market h 1,775 625 23.6s 1.1min 1.4min 1.5min 0 transport_latency_assumed new_market i 1,775 413 24.8s 1.1min 1.4min 1.5min 0 transport_latency_assumed new_market k 1,775 189 23.3s 1.1min 1.4min 1.6min 0 transport_latency_assumed new_market m 1,775 732 23.9s 1.0min 1.4min 1.4min 0 transport_latency_assumed price_change g 91,334,414 10,434 76ms 105ms 799ms 53.0s 0 transport_latency_assumed price_change h 91,432,337 866,414 17ms 25ms 441ms 1.4min 0 transport_latency_assumed price_change i 91,443,276 390,356 21ms 28ms 291ms 12.3s 0 transport_latency_assumed price_change k 91,436,278 2,828,066 13ms 22ms 315ms 1.6min 0 transport_latency_assumed price_change m 91,460,116 87,382,110 4ms 10ms 114ms 10.1s 0 transport_latency_assumed tick_size_change g 3,468 not meas. 76ms 94ms 657ms 45.9s 0 transport_latency_assumed tick_size_change h 3,468 35 17ms 26ms 688ms 6.3s 0 transport_latency_assumed tick_size_change i 3,468 7 21ms 30ms 370ms 515ms 0 transport_latency_assumed tick_size_change k 3,464 63 13ms 23ms 721ms 14.0s 0 transport_latency_assumed tick_size_change m 3,468 3,363 4ms 9ms 129ms 275ms 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/05/2026-10-04T05.parquet sha256sum 2026-10-04T05.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.