Hour audit: 2026-09-30T18
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-09-30T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T18:00:00.000006787+00:00 · last event 2026-09-30T18:59:59.999977910+00:00
VOLUME 111,514,572 rows · 1,227,415,523 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 110,862,599 · i: 110,860,088 · m: 110,825,127 · k: 110,780,691 · g: 105,332,107 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,970,904 (3.56%) · i: 1,744,886 (1.56%) · m: 93,521,103 (83.86%) · k: 11,622,038 (10.42%) · g: 655,641 (0.59%) (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 111,514,572 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4e9728952cb7c0ee3699736662decad8df7d4467cad42d3fd31150b73c0b33d2
the corpus checksum ledger names this file with the same digest
joined 111,518,542 to merged 111,514,572, minus 3,970 (minus 0.0036%)
boundary drops 3,970 · 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-09-30T23:04:31Z 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 10,410,718 122,894,046 0-39 451eb22d202b9a2e696d34faecd141e1ac294f4a5bad1554af0cb5cf73b54d4c book 823,473 70,709,483 40-43 08cd4e9dd3cfd282712b07599bf07d789c8ed37fa10dd1e94b8f82bb79a415cc last_trade_price 57,287 3,311,135 44-44 8bd813f21a4b8a5e092142ca66db1d901298889e72bdd25887f545aac8e9985b market_resolved 1,386 197,620 45-45 86fe8808639e25fd1ab0607ded6f86a2dbcde6d0eb2f9a1303c79a99894468df new_market 3,900 348,809 46-46 fe5b2ad728f979411fde985fe1e1cbd5e35f8cd472b6a84194be22c48e6ef40e price_change 100,214,036 1,028,544,924 47-429 0ee0de59c27ea611e8338373e3b5eb6b3acc6f371f7ca95ceaf9e2ab6fdefdcb tick_size_change 3,772 136,454 430-430 957f9f6517e75062b90c14769a49502bfddadb51af5470500815bab3b5a4b611 EVENT MIX count share price_change 100,214,036 89.87% best_bid_ask 10,410,718 9.34% book 823,473 0.74% last_trade_price 57,287 0.05% new_market 3,900 <0.01% tick_size_change 3,772 <0.01% market_resolved 1,386 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,410,912 10,410,718 194 523 FULL book 823,473 823,473 0 225,859 FULL last_trade_price 57,287 57,287 0 71 FULL market_resolved 1,386 1,386 0 8 FULL new_market 3,900 3,900 0 0 FULL price_change 100,217,812 100,214,036 3,776 501 FULL tick_size_change 3,772 3,772 0 44 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,860,285 6,163 79ms 121ms 704ms 37.8s 0 transport_latency_assumed best_bid_ask h 10,405,943 298,945 19ms 47ms 741ms 2.1min 0 transport_latency_assumed best_bid_ask i 10,407,548 135,025 28ms 55ms 259ms 9.5s 0 transport_latency_assumed best_bid_ask k 10,406,984 988,409 14ms 38ms 392ms 2.0min 0 transport_latency_assumed best_bid_ask m 10,405,996 8,982,176 5ms 22ms 143ms 3.7s 0 transport_latency_assumed book g 704,674 572,578 46.9min 2.6d 39.2d 123.8d 0 book_staleness book h 248,916 45,125 4.8s 1.5d 37.9d 116.1d 0 book_staleness book i 237,516 33,038 1.9s 1.3d 39.0d 123.8d 0 book_staleness book k 237,925 41,406 2.1s 1.3d 36.1d 123.8d 0 book_staleness book m 239,827 131,326 1.8s 1.4d 37.2d 123.8d 0 book_staleness last_trade_price g 53,767 107 85ms 345ms 7.6s 35.2s 0 transport_latency_assumed last_trade_price h 57,143 3,184 21ms 85ms 1.1s 37.0s 0 transport_latency_assumed last_trade_price i 57,211 1,226 31ms 104ms 1.2s 4.2s 0 transport_latency_assumed last_trade_price k 56,779 5,376 16ms 77ms 1.0s 2.0min 0 transport_latency_assumed last_trade_price m 57,013 47,394 7ms 34ms 206ms 1.3s 0 transport_latency_assumed market_resolved g 1,236 43 177ms 27.9s 5.9min 7.4min 0 transport_latency_assumed market_resolved h 1,222 23 38ms 941ms 53.2s 53.2s 0 transport_latency_assumed market_resolved i 1,222 15 48ms 13.1s 50.2s 56.8s 0 transport_latency_assumed market_resolved k 1,222 222 22ms 68ms 29.9s 1.1min 0 transport_latency_assumed market_resolved m 1,214 1,083 7ms 39.8s 52.4s 56.2s 0 transport_latency_assumed new_market g 2,538 595 638ms 1.7min 2.5min 5.0min 0 transport_latency_assumed new_market h 2,168 556 206ms 23.9s 39.8s 1.7min 0 transport_latency_assumed new_market i 2,168 607 151ms 30.4s 43.8s 33.0d 0 transport_latency_assumed new_market k 2,168 592 191ms 33.5s 47.9s 1.6min 0 transport_latency_assumed new_market m 2,168 1,550 82ms 35.4s 43.3s 1.4min 0 transport_latency_assumed price_change g 94,706,011 76,155 79ms 168ms 2.4s 38.1s 0 transport_latency_assumed price_change h 100,143,435 3,622,994 19ms 54ms 794ms 2.2min 0 transport_latency_assumed price_change i 100,150,651 1,574,930 29ms 61ms 453ms 9.5s 0 transport_latency_assumed price_change k 100,071,841 10,585,646 14ms 44ms 448ms 2.1min 0 transport_latency_assumed price_change m 100,115,137 84,354,311 6ms 26ms 160ms 5.0s 0 transport_latency_assumed tick_size_change g 3,596 not meas. 79ms 104ms 534ms 1.0s 0 transport_latency_assumed tick_size_change h 3,772 77 19ms 40ms 406ms 3.9s 0 transport_latency_assumed tick_size_change i 3,772 45 26ms 50ms 446ms 544ms 0 transport_latency_assumed tick_size_change k 3,772 387 14ms 27ms 379ms 6.5s 0 transport_latency_assumed tick_size_change m 3,772 3,263 5ms 18ms 42ms 80ms 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-09-30/18/2026-09-30T18.parquet sha256sum 2026-09-30T18.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.