Hour audit: 2026-10-02T03
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-02T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T03:00:00.000044723+00:00 · last event 2026-10-02T03:59:59.999983370+00:00
VOLUME 113,516,405 rows · 1,174,268,099 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 113,030,318 · i: 113,021,482 · m: 113,016,984 · g: 113,003,303 · k: 107,722,745 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 307,711 (0.27%) · i: 96,514 (0.09%) · m: 111,028,804 (97.81%) · g: 7,058 (0.01%) · k: 2,076,318 (1.83%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,516,405 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 351e8b6af5dac9d1f366ac90afc483d3a668960eb862e7c3dd8871b942accf32
the corpus checksum ledger names this file with the same digest
joined 113,518,346 to merged 113,516,405, minus 1,941 (minus 0.0017%)
boundary drops 1,941 · 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-02T05:45:19Z 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 8,437,018 96,832,602 0-32 a146e2f427e9a77d7d7bd8ae290792d4c39de2c26ba5f9ca468f74353273f06b book 584,443 59,604,583 33-35 82be6c8595232fbe566f04019c8cd3936f87a5535ffbc48b20a70980b5765a81 last_trade_price 52,004 2,871,760 36-36 d34040cac751160dcb7f6999437d7d5d389c9541a7bba07a3b629df3b0946b60 market_resolved 2,277 318,432 37-37 f5204c9cbcdd2e810879fa26ce216b5dae89f5d2fb626e5f5b878de8bea8a322 new_market 843 102,947 38-38 39ced115fd5f7fd797950295081df4fc71af3da78021659f8ddf282d49697595 price_change 104,435,176 1,013,072,025 39-437 84d1a05b82cadfc55d8137972b3cc2f5c2d6ff8d52cbb2a55442f03f6a095c26 tick_size_change 4,644 168,251 438-438 c96979524f163d50dfad84d6b16caa40092062f3713ac04ecdfd210a37b3651d EVENT MIX count share price_change 104,435,176 92.00% best_bid_ask 8,437,018 7.43% book 584,443 0.51% last_trade_price 52,004 0.05% tick_size_change 4,644 <0.01% market_resolved 2,277 <0.01% new_market 843 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,437,196 8,437,018 178 435 FULL book 584,457 584,443 14 234,189 FULL last_trade_price 52,004 52,004 0 82 FULL market_resolved 2,277 2,277 0 294 FULL new_market 844 843 1 483 FULL price_change 104,436,924 104,435,176 1,748 263 FULL tick_size_change 4,644 4,644 0 35 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,435,956 266 75ms 90ms 183ms 5.1s 0 transport_latency_assumed best_bid_ask h 8,436,602 21,557 17ms 31ms 68ms 18.1s 0 transport_latency_assumed best_bid_ask i 8,436,405 6,373 22ms 41ms 64ms 5.1s 0 transport_latency_assumed best_bid_ask k 7,974,962 112,556 13ms 19ms 121ms 7.7s 0 transport_latency_assumed best_bid_ask m 8,436,900 8,296,266 5ms 7ms 29ms 3.8s 0 transport_latency_assumed book g 109,182 3,766 77ms 115ms 2.6h 106.7d 0 book_staleness book h 104,456 549 20ms 34ms 90ms 9.8s 0 book_staleness book i 104,456 364 23ms 45ms 102ms 4.0s 0 book_staleness book k 574,426 475,748 31.4min 1.1d 40.6d 125.2d 0 book_staleness book m 108,160 104,016 6ms 10ms 2.5h 40.6d 0 book_staleness last_trade_price g 51,993 4 77ms 97ms 270ms 2.4s 0 transport_latency_assumed last_trade_price h 51,990 155 18ms 32ms 79ms 8.7s 0 transport_latency_assumed last_trade_price i 51,989 55 23ms 44ms 91ms 2.0s 0 transport_latency_assumed last_trade_price k 49,009 829 13ms 21ms 116ms 1.0s 0 transport_latency_assumed last_trade_price m 51,990 50,961 5ms 8ms 30ms 1.3s 0 transport_latency_assumed market_resolved g 1,685 43 76ms 211ms 49.1s 53.2s 0 transport_latency_assumed market_resolved h 1,685 5 18ms 51ms 53.4s 54.8s 0 transport_latency_assumed market_resolved i 1,685 94 34ms 12.5s 50.3s 50.4s 0 transport_latency_assumed market_resolved k 2,132 570 14ms 22.8min 36.4min 39.5min 0 transport_latency_assumed market_resolved m 1,685 1,565 5ms 12.6s 50.0s 50.1s 0 transport_latency_assumed new_market g 229 3 108ms 1.1s 14.9s 1.3min 0 transport_latency_assumed new_market h 229 49 36ms 10.2s 14.0s 14.5s 0 transport_latency_assumed new_market i 229 28 53ms 8.0s 12.4s 1.2min 0 transport_latency_assumed new_market k 776 575 30.5min 32.5min 37.5min 37.6min 0 transport_latency_assumed new_market m 229 188 20ms 9.1s 58.6s 1.8min 0 transport_latency_assumed price_change g 104,399,614 2,976 75ms 92ms 293ms 6.6s 0 transport_latency_assumed price_change h 104,430,712 285,388 17ms 31ms 86ms 18.6s 0 transport_latency_assumed price_change i 104,422,074 89,600 22ms 42ms 90ms 5.1s 0 transport_latency_assumed price_change k 99,116,936 1,486,008 13ms 20ms 122ms 8.0s 0 transport_latency_assumed price_change m 104,413,376 102,571,204 5ms 7ms 32ms 4.4s 0 transport_latency_assumed tick_size_change g 4,644 not meas. 75ms 85ms 175ms 217ms 0 transport_latency_assumed tick_size_change h 4,644 8 18ms 31ms 46ms 53ms 0 transport_latency_assumed tick_size_change i 4,644 not meas. 23ms 42ms 59ms 120ms 0 transport_latency_assumed tick_size_change k 4,504 32 13ms 19ms 116ms 126ms 0 transport_latency_assumed tick_size_change m 4,644 4,604 5ms 7ms 13ms 40ms 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/03/2026-10-02T03.parquet sha256sum 2026-10-02T03.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.