Hour audit: 2026-10-02T15
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-02T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T15:00:00.000766618+00:00 · last event 2026-10-02T15:59:59.999970016+00:00
VOLUME 144,085,332 rows · 1,691,881,320 bytes (1.58 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 142,109,568 · h: 142,102,327 · i: 129,625,016 · g: 127,833,537 · k: 123,378,928 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 108,425,086 (75.25%) · h: 9,352,571 (6.49%) · i: 6,337,502 (4.40%) · g: 1,030,718 (0.72%) · k: 18,939,455 (13.14%) (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 144,085,332 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 33b65a1253369e59993070c3fb53b700a1a192899f782f79f556aa56d2529835
the corpus checksum ledger names this file with the same digest
joined 144,100,589 to merged 144,085,332, minus 15,257 (minus 0.0106%)
boundary drops 15,257 · 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-02T17:55:09Z 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,538,163 147,802,514 0-44 4333d1b88b56285ed18cd49eef9b84e2dda9731a2e7df8445c05a4a46344bc2b book 2,252,045 117,403,875 45-53 688dbdbb7d73379dd85b8043f273886195cb2cce70fe6dae0020ee479df01178 last_trade_price 72,905 4,213,900 54-54 1b596e45f50e88b6f2d0f15fc00839472cfbfc3a7a99fd76e75989e1d72aa4d3 market_resolved 1,127 148,952 55-55 7279a6afa939976872b3c359b6e34b3c03fe226379b3620b295b48cba13a046a new_market 2,764 222,553 56-56 b50110741a405746070ab78e4253e34abc8a717f9846c8f55827f33ff34d4c54 price_change 130,215,676 1,420,350,400 57-553 b3b5683fc8a9d6034f8fa7e81ca707fe04c4d7a1a286956bd6dd1432a4370a2c tick_size_change 2,652 99,746 554-554 5fd825c7d90c4ef5148f08a44b04d00e8af1f4f7253b243182e2e90c59411330 EVENT MIX count share price_change 130,215,676 90.37% best_bid_ask 11,538,163 8.01% book 2,252,045 1.56% last_trade_price 72,905 0.05% new_market 2,764 <0.01% tick_size_change 2,652 <0.01% market_resolved 1,127 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,538,553 11,538,163 390 4,537 FULL book 2,256,523 2,252,045 4,478 204,225 FULL last_trade_price 72,918 72,905 13 711 FULL market_resolved 1,127 1,127 0 101 FULL new_market 2,764 2,764 0 0 FULL price_change 130,226,052 130,215,676 10,376 2,891 FULL tick_size_change 2,652 2,652 0 151 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,370,528 16,613 82ms 175ms 1.1s 47.8s 0 transport_latency_assumed best_bid_ask h 11,536,438 756,475 21ms 87ms 530ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,483,567 423,603 23ms 81ms 392ms 6.8s 0 transport_latency_assumed best_bid_ask k 9,901,537 1,393,581 16ms 75ms 374ms 9.2s 0 transport_latency_assumed best_bid_ask m 11,536,379 8,947,891 7ms 65ms 376ms 5.0s 0 transport_latency_assumed book g 1,204,624 784,681 52.9min 1.6d 41.1d 125.7d 0 book_staleness book h 315,458 77,723 7.8s 14.6h 39.0d 125.7d 0 book_staleness book i 1,214,539 396,097 51.9min 1.6d 41.1d 125.7d 0 book_staleness book k 1,624,323 799,373 1.1h 2.1d 41.1d 125.7d 0 book_staleness book m 337,683 194,171 19.7s 14.3h 34.2d 125.7d 0 book_staleness last_trade_price g 62,991 143 95ms 1.0s 12.4s 47.6s 0 transport_latency_assumed last_trade_price h 72,887 4,159 24ms 216ms 1.1s 42.1s 0 transport_latency_assumed last_trade_price i 65,802 4,574 26ms 155ms 1.6s 6.8s 0 transport_latency_assumed last_trade_price k 63,261 10,965 18ms 127ms 871ms 3.2s 0 transport_latency_assumed last_trade_price m 72,866 53,064 9ms 120ms 920ms 4.1s 0 transport_latency_assumed market_resolved g 914 55 95ms 42.2s 10.1min 10.7min 0 transport_latency_assumed market_resolved h 891 43 27ms 22.3s 53.6s 55.0s 0 transport_latency_assumed market_resolved i 944 108 39ms 5.3min 12.4min 12.5min 0 transport_latency_assumed market_resolved k 862 188 21ms 44.4s 6.5min 6.6min 0 transport_latency_assumed market_resolved m 891 733 10ms 11.7s 46.2s 53.5s 0 transport_latency_assumed new_market g 1,394 180 388ms 18.3min 19.1min 19.3min 0 transport_latency_assumed new_market h 1,375 508 226ms 18.1min 19.0min 19.2min 0 transport_latency_assumed new_market i 1,860 950 273ms 25.7min 26.3min 26.3min 0 transport_latency_assumed new_market k 1,450 468 213ms 22.5min 23.5min 23.5min 0 transport_latency_assumed new_market m 1,375 658 130ms 18.2min 19.1min 19.3min 0 transport_latency_assumed price_change g 116,190,610 229,046 84ms 263ms 6.8s 47.8s 0 transport_latency_assumed price_change h 130,172,626 8,513,490 22ms 114ms 767ms 1.0min 0 transport_latency_assumed price_change i 117,855,836 5,512,052 24ms 100ms 631ms 6.8s 0 transport_latency_assumed price_change k 111,785,255 16,734,526 17ms 89ms 490ms 9.2s 0 transport_latency_assumed price_change m 130,157,722 99,226,562 8ms 77ms 518ms 5.0s 0 transport_latency_assumed tick_size_change g 2,476 not meas. 83ms 130ms 450ms 1.1s 0 transport_latency_assumed tick_size_change h 2,652 173 22ms 100ms 482ms 5.2s 0 transport_latency_assumed tick_size_change i 2,468 118 23ms 58ms 256ms 640ms 0 transport_latency_assumed tick_size_change k 2,240 354 16ms 87ms 426ms 792ms 0 transport_latency_assumed tick_size_change m 2,652 2,007 8ms 55ms 315ms 602ms 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-02/15/2026-10-02T15.parquet sha256sum 2026-10-02T15.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.