Hour audit: 2026-09-29T06
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-29T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T06:00:00.000038116+00:00 · last event 2026-09-29T06:59:59.999554966+00:00
VOLUME 86,297,120 rows · 910,672,281 bytes (868.48 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 86,184,241 · k: 86,154,824 · g: 85,595,623 · i: 84,554,778 · c: 83,464,743 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,185,406 (1.37%) · k: 4,761,620 (5.52%) · g: 58,362 (0.07%) · i: 3,231,443 (3.74%) · c: 77,060,289 (89.30%) (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 86,297,120 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0a16d8e082f39c9c38276d0d7045ffdc098d2a2ec3ea2eb0c2c0b728fbb6f29e
the corpus checksum ledger names this file with the same digest
joined 86,298,506 to merged 86,297,120, minus 1,386 (minus 0.0016%)
boundary drops 1,386 · 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-29T09:08:59Z as cghik
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 9,031,594 103,572,258 0-34 4192b0ecaed67f918fc5d8cf0fe1e95c0a6d132b1352b9727afa3fad8d5f14fd book 217,301 20,005,139 35-35 1df2a3596b6eb4a63d468a26203b7a76921f9aebc1d8a4613cd9827b671c339b last_trade_price 56,815 3,155,416 36-36 c7bd3f89154bedcabb816d32ebe1c8e33a973e98c402d2315490c2cdd3824149 market_resolved 645 94,818 37-37 6750f4b006499b470a02024f413cd3166a4f5944aad61151de5510cf8430097a new_market 2,197 253,747 38-38 78428ec46845882399ec0d2f5c414780df0111ff021f3a27d88193aa8b06082a price_change 76,985,668 782,497,474 39-332 2e8a8eaf955c7ddb5fe96ba680bda942d73482e40dc0ba723939402b70b59fee tick_size_change 2,900 107,529 333-333 b1d6e5ab8c4a0d96d66547576483d9f467ecc58c482111ec728d980fb31faacb EVENT MIX count share price_change 76,985,668 89.21% best_bid_ask 9,031,594 10.47% book 217,301 0.25% last_trade_price 56,815 0.07% tick_size_change 2,900 <0.01% new_market 2,197 <0.01% market_resolved 645 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,031,760 9,031,594 166 2,705 FULL book 217,305 217,301 4 38,029 FULL last_trade_price 56,815 56,815 0 129 FULL market_resolved 645 645 0 21 FULL new_market 2,197 2,197 0 0 FULL price_change 76,986,884 76,985,668 1,216 4,532 FULL tick_size_change 2,900 2,900 0 37 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,730,951 8,121,906 5ms 10ms 221ms 8.6s 0 transport_latency_assumed best_bid_ask g 9,012,640 1,758 78ms 103ms 805ms 44.1s 0 transport_latency_assumed best_bid_ask h 9,029,824 103,515 18ms 25ms 433ms 1.6min 0 transport_latency_assumed best_bid_ask i 8,887,976 339,614 15ms 23ms 260ms 42.0s 0 transport_latency_assumed best_bid_ask k 9,030,019 464,801 13ms 20ms 255ms 59.3s 0 transport_latency_assumed book c 128,147 116,937 7ms 14.3s 2.1d 103.8d 0 book_staleness book g 137,679 29,873 96ms 4.8h 21.8d 122.3d 0 book_staleness book h 151,752 35,147 24ms 6.2h 21.8d 103.9d 0 book_staleness book i 119,876 6,816 20ms 314ms 9.6h 103.8d 0 book_staleness book k 139,180 28,528 17ms 56.4min 15.7d 103.8d 0 book_staleness last_trade_price c 55,515 51,444 6ms 15ms 265ms 2.8s 0 transport_latency_assumed last_trade_price g 52,159 39 84ms 874ms 12.1s 39.6s 0 transport_latency_assumed last_trade_price h 56,738 668 20ms 75ms 516ms 47.1s 0 transport_latency_assumed last_trade_price i 56,331 1,103 19ms 135ms 839ms 6.4s 0 transport_latency_assumed last_trade_price k 56,722 3,561 14ms 34ms 334ms 51.7s 0 transport_latency_assumed market_resolved c 559 524 5ms 11ms 1.1min 2.0min 0 transport_latency_assumed market_resolved g 572 not meas. 80ms 318ms 14.3s 49.4s 0 transport_latency_assumed market_resolved h 572 1 20ms 88ms 54.5s 56.8s 0 transport_latency_assumed market_resolved i 566 88 20ms 47.1s 56.9s 2.4min 0 transport_latency_assumed market_resolved k 572 32 14ms 44ms 9.9s 36.3s 0 transport_latency_assumed new_market c 1,707 293 1.1min 3.3min 3.6min 3.6min 0 transport_latency_assumed new_market g 1,707 660 1.1min 3.3min 3.6min 3.6min 0 transport_latency_assumed new_market h 1,707 321 57.5s 3.3min 3.5min 3.6min 0 transport_latency_assumed new_market i 1,707 515 42.2s 3.2min 3.5min 3.6min 0 transport_latency_assumed new_market k 1,707 408 1.0min 3.3min 3.6min 3.6min 0 transport_latency_assumed price_change c 74,545,056 68,766,572 5ms 13ms 258ms 9.1s 0 transport_latency_assumed price_change g 76,387,966 26,032 78ms 162ms 3.3s 44.3s 0 transport_latency_assumed price_change h 76,940,748 1,045,729 18ms 33ms 513ms 1.6min 0 transport_latency_assumed price_change i 75,485,482 2,883,230 16ms 31ms 396ms 42.8s 0 transport_latency_assumed price_change k 76,923,724 4,264,105 13ms 24ms 303ms 1.0min 0 transport_latency_assumed tick_size_change c 2,808 2,613 5ms 9ms 81ms 162ms 0 transport_latency_assumed tick_size_change g 2,900 not meas. 77ms 97ms 391ms 27.0s 0 transport_latency_assumed tick_size_change h 2,900 25 18ms 23ms 167ms 42.3s 0 transport_latency_assumed tick_size_change i 2,840 77 16ms 23ms 84ms 444ms 0 transport_latency_assumed tick_size_change k 2,900 185 13ms 17ms 58ms 1.1s 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-29/06/2026-09-29T06.parquet sha256sum 2026-09-29T06.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.