Hour audit: 2026-10-01T04
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-01T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T04:00:00.000188846+00:00 · last event 2026-10-01T04:59:59.999998209+00:00
VOLUME 105,939,502 rows · 1,100,104,918 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 99,087,132 · m: 96,433,186 · i: 94,799,701 · k: 92,658,294 · g: 92,277,326 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,767,311 (5.44%) · m: 74,606,152 (70.42%) · i: 817,455 (0.77%) · k: 24,624,130 (23.24%) · g: 124,454 (0.12%) (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 105,939,502 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e11121a9ddbad08aaaad6b7fc802a8119d02c1cc7a15b70eba97262b6d54360c
the corpus checksum ledger names this file with the same digest
joined 105,941,712 to merged 105,939,502, minus 2,210 (minus 0.0021%)
boundary drops 2,210 · 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-01T07:06:16Z 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 11,027,528 127,768,863 0-42 208180cda534030d6c73e148b5d84ec9eda52de9f3659561c45dfd92c9f58f3e book 170,323 18,466,075 43-43 b62ddd93630a80db1d38834835eaf66e21c83fc8260414711389d954a1dc8e96 last_trade_price 47,896 2,778,959 44-44 bfb1d20141ea46bad3b79d98ddb3e0fefe92f9566139e97b1f1d422178981ba6 market_resolved 1,056 162,506 45-45 370b8971e6e2f528510bf3d7b6ba5b8910edc715f9b862b8489db8ebbcc726f6 new_market 2,361 227,185 46-46 269e5b86ea89890787bbb85889c072eae5d05ea156079210db54a00a3f4de79a price_change 94,687,990 949,403,739 47-408 2da3aabd48483784e847d0c6fb998fc3fe0d1f5c6a209cabb4cccd7ab38dca79 tick_size_change 2,348 87,662 409-409 c6ef36130aa69a4237c9cf8016dfcf0f2d2a6bc41220b7c8c91f3c184597d5b7 EVENT MIX count share price_change 94,687,990 89.38% best_bid_ask 11,027,528 10.41% book 170,323 0.16% last_trade_price 47,896 0.05% new_market 2,361 <0.01% tick_size_change 2,348 <0.01% market_resolved 1,056 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,027,736 11,027,528 208 202 FULL book 170,347 170,323 24 33,345 FULL last_trade_price 47,900 47,896 4 1 FULL market_resolved 1,056 1,056 0 0 FULL new_market 2,361 2,361 0 0 FULL price_change 94,689,964 94,687,990 1,974 58,508 FULL tick_size_change 2,348 2,348 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 11,025,502 4,391 78ms 100ms 561ms 17.1s 0 transport_latency_assumed best_bid_ask h 11,025,642 220,057 17ms 28ms 767ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,026,516 28,738 30ms 62ms 275ms 11.8s 0 transport_latency_assumed best_bid_ask k 11,026,053 2,167,659 10ms 22ms 483ms 35.5s 0 transport_latency_assumed best_bid_ask m 11,026,867 8,606,683 5ms 21ms 99ms 4.8s 0 transport_latency_assumed book g 100,619 2,884 84ms 244ms 4.2h 105.7d 0 book_staleness book h 129,881 34,817 23ms 5.2h 23.8d 124.3d 0 book_staleness book i 100,125 2,510 32ms 101ms 2.3min 105.6d 0 book_staleness book k 120,271 42,509 15ms 1.5h 20.8d 124.3d 0 book_staleness book m 114,747 87,603 10ms 6.4min 4.0d 46.6d 0 book_staleness last_trade_price g 47,764 32 83ms 182ms 3.0s 17.1s 0 transport_latency_assumed last_trade_price h 47,876 1,871 19ms 39ms 723ms 29.6s 0 transport_latency_assumed last_trade_price i 47,885 154 32ms 75ms 614ms 4.9s 0 transport_latency_assumed last_trade_price k 47,879 12,165 12ms 30ms 529ms 14.0s 0 transport_latency_assumed last_trade_price m 47,883 33,674 8ms 31ms 162ms 2.2s 0 transport_latency_assumed market_resolved g 992 26 82ms 234ms 50.0s 50.1s 0 transport_latency_assumed market_resolved h 992 28 19ms 757ms 51.3s 56.0s 0 transport_latency_assumed market_resolved i 992 4 40ms 12.0s 55.2s 55.3s 0 transport_latency_assumed market_resolved k 992 240 12ms 310ms 50.0s 55.3s 0 transport_latency_assumed market_resolved m 992 758 8ms 15.9s 54.5s 54.6s 0 transport_latency_assumed new_market g 1,461 271 256ms 15.6s 31.7s 1.7min 0 transport_latency_assumed new_market h 1,461 345 268ms 17.1s 30.3s 1.7min 0 transport_latency_assumed new_market i 1,461 379 233ms 14.9s 32.7s 1.7min 0 transport_latency_assumed new_market k 1,461 228 311ms 15.9s 32.0s 1.8min 0 transport_latency_assumed new_market m 1,461 1,138 92ms 16.0s 31.2s 1.5min 0 transport_latency_assumed price_change g 81,098,640 116,850 78ms 110ms 751ms 17.1s 0 transport_latency_assumed price_change h 87,878,932 5,510,158 18ms 31ms 805ms 1.3min 0 transport_latency_assumed price_change i 83,620,374 785,666 31ms 66ms 376ms 11.8s 0 transport_latency_assumed price_change k 81,459,290 22,400,850 11ms 25ms 522ms 32.5s 0 transport_latency_assumed price_change m 85,238,888 65,874,466 6ms 24ms 128ms 5.8s 0 transport_latency_assumed tick_size_change g 2,348 not meas. 79ms 98ms 209ms 2.3s 0 transport_latency_assumed tick_size_change h 2,348 35 18ms 28ms 58ms 2.1s 0 transport_latency_assumed tick_size_change i 2,348 4 30ms 61ms 106ms 134ms 0 transport_latency_assumed tick_size_change k 2,348 479 11ms 23ms 110ms 144ms 0 transport_latency_assumed tick_size_change m 2,348 1,830 5ms 18ms 62ms 107ms 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-01/04/2026-10-01T04.parquet sha256sum 2026-10-01T04.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.