Hour audit: 2026-09-30T00
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-30T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T00:00:00.000021896+00:00 · last event 2026-09-30T00:59:59.999951781+00:00
VOLUME 108,610,654 rows · 1,206,213,927 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cghikm — 6 machines contributed rows
captured c: 108,350,542 · k: 108,329,245 · g: 108,258,394 · i: 108,232,098 · m: 108,017,010 · h: 107,911,441 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 40,919,304 (37.68%) · k: 762,826 (0.70%) · g: 21,418 (0.02%) · i: 289,748 (0.27%) · m: 66,310,343 (61.05%) · h: 307,015 (0.28%) (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 108,610,654 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 9b8439787e4bda2031056448371970e338ccc9eace717c2f71e9b903c208b687
the corpus checksum ledger names this file with the same digest
joined 108,614,207 to merged 108,610,654, minus 3,553 (minus 0.0033%)
boundary drops 3,553 · 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-30T13:21:59Z as cghikm
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,660,878 131,161,768 0-40 70172c695f5edf456cab759d3da4bca5fd2536da2c921fd9bb556896eec5d6cf book 338,665 32,258,778 41-42 bf4294754666ac269ad1e29a1d90927586ff45ef08a69e2458b046c4f278c1a9 last_trade_price 52,281 2,967,080 43-43 0755b5fd071dcc219745c466e56489e95c734be0609555a78ed371d8353c0a66 market_resolved 1,981 313,308 44-44 f63f4195ee14e3d14ab95abe657061336dad2ecd3b7bbbf44d7b7c8c4b098b41 new_market 623 69,790 45-45 99c9ae2c6bf2c3f93475dea05ec5c79851490cd4d285f2f157311c7eee83b137 price_change 97,553,614 1,038,102,777 46-418 455e1c961a2caa2c5e23c29cd8922bc47b9c8b90f5444a031924408cf49eb0c8 tick_size_change 2,612 98,400 419-419 0b7b5655c6dbbfe80d69364d86ed19b95d3855c74b262de6d5c13c6402e00586 EVENT MIX count share price_change 97,553,614 89.82% best_bid_ask 10,660,878 9.82% book 338,665 0.31% last_trade_price 52,281 0.05% tick_size_change 2,612 <0.01% market_resolved 1,981 <0.01% new_market 623 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,661,108 10,660,878 230 399 FULL book 338,911 338,665 246 93,106 FULL last_trade_price 52,282 52,281 1 22 FULL market_resolved 1,981 1,981 0 0 FULL new_market 623 623 0 0 FULL price_change 97,556,690 97,553,614 3,076 636 FULL tick_size_change 2,612 2,612 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,659,486 4,071,071 5ms 16ms 109ms 5.5s 0 transport_latency_assumed best_bid_ask g 10,657,436 178 80ms 101ms 274ms 9.6s 0 transport_latency_assumed best_bid_ask h 10,636,890 26,919 18ms 27ms 119ms 13.8s 0 transport_latency_assumed best_bid_ask i 10,651,516 13,401 20ms 30ms 115ms 6.1s 0 transport_latency_assumed best_bid_ask k 10,659,341 64,188 13ms 23ms 94ms 9.3s 0 transport_latency_assumed best_bid_ask m 10,629,712 6,485,121 4ms 8ms 41ms 5.8s 0 transport_latency_assumed book c 141,078 61,204 8ms 4.0h 22.6d 123.1d 0 book_staleness book g 128,272 18,860 98ms 1.1h 19.6d 123.1d 0 book_staleness book h 113,833 9,022 22ms 252ms 23.9h 104.6d 0 book_staleness book i 241,761 135,909 27.9s 1.2d 38.4d 123.1d 0 book_staleness book k 117,714 10,340 16ms 11.2s 2.9d 123.1d 0 book_staleness book m 142,906 103,330 7ms 1.8h 10.4d 104.6d 0 book_staleness last_trade_price c 52,045 17,607 6ms 31ms 239ms 1.2s 0 transport_latency_assumed last_trade_price g 51,679 10 89ms 307ms 4.8s 9.6s 0 transport_latency_assumed last_trade_price h 51,420 257 19ms 54ms 332ms 3.3s 0 transport_latency_assumed last_trade_price i 51,483 92 22ms 75ms 568ms 1.7s 0 transport_latency_assumed last_trade_price k 52,025 469 14ms 41ms 223ms 9.2s 0 transport_latency_assumed last_trade_price m 51,850 33,846 5ms 11ms 77ms 1.4s 0 transport_latency_assumed market_resolved c 1,913 637 5ms 78ms 51.2s 54.9s 0 transport_latency_assumed market_resolved g 1,913 not meas. 81ms 286ms 46.7s 56.4s 0 transport_latency_assumed market_resolved h 1,913 6 19ms 109ms 47.4s 1.5min 0 transport_latency_assumed market_resolved i 1,913 236 21ms 13.0s 42.7s 55.6s 0 transport_latency_assumed market_resolved k 1,913 15 13ms 18.4s 49.6s 49.7s 0 transport_latency_assumed market_resolved m 1,913 1,087 5ms 37ms 46.6s 55.9s 0 transport_latency_assumed new_market c 445 158 53ms 10.0s 27.5s 1.6min 0 transport_latency_assumed new_market g 445 20 141ms 10.4s 58.9s 1.7min 0 transport_latency_assumed new_market h 445 51 65ms 15.3s 28.5s 1.7min 0 transport_latency_assumed new_market i 445 66 66ms 11.8s 1.2min 1.5min 0 transport_latency_assumed new_market k 445 69 92ms 10.3s 1.1min 1.6min 0 transport_latency_assumed new_market m 445 259 33ms 416ms 34.2s 1.6min 0 transport_latency_assumed price_change c 97,492,963 36,767,713 5ms 19ms 127ms 5.8s 0 transport_latency_assumed price_change g 97,416,037 2,350 80ms 117ms 573ms 9.6s 0 transport_latency_assumed price_change h 97,104,336 270,736 18ms 32ms 189ms 13.8s 0 transport_latency_assumed price_change i 97,282,368 140,036 21ms 36ms 189ms 6.8s 0 transport_latency_assumed price_change k 97,495,195 687,709 13ms 27ms 116ms 9.5s 0 transport_latency_assumed price_change m 97,187,580 59,685,070 4ms 9ms 47ms 5.9s 0 transport_latency_assumed tick_size_change c 2,612 914 5ms 23ms 120ms 499ms 0 transport_latency_assumed tick_size_change g 2,612 not meas. 80ms 104ms 192ms 261ms 0 transport_latency_assumed tick_size_change h 2,604 24 18ms 38ms 134ms 435ms 0 transport_latency_assumed tick_size_change i 2,612 8 21ms 48ms 224ms 274ms 0 transport_latency_assumed tick_size_change k 2,612 36 13ms 29ms 78ms 191ms 0 transport_latency_assumed tick_size_change m 2,604 1,630 4ms 9ms 85ms 149ms 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/00/2026-09-30T00.parquet sha256sum 2026-09-30T00.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.