Hour audit: 2026-09-29T12
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-29T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T12:00:00.000071387+00:00 · last event 2026-09-29T12:59:59.999905411+00:00
VOLUME 113,375,060 rows · 1,301,267,783 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 111,955,223 · g: 110,988,990 · k: 107,138,116 · c: 106,905,582 · i: 106,835,836 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,426,642 (2.14%) · g: 68,019 (0.06%) · k: 12,246,198 (10.80%) · c: 92,287,593 (81.40%) · i: 6,346,608 (5.60%) (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 113,375,060 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8a82765bf90b62e8988a3d6d7e6f369fd4f5f8fd652cfddb1c60c06aa541cdab
the corpus checksum ledger names this file with the same digest
joined 113,377,147 to merged 113,375,060, minus 2,087 (minus 0.0018%)
boundary drops 2,087 · 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-29T15:17:41Z 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 11,507,968 138,798,627 0-43 dcd9b644466276e5c32700e4918b589c4761a40d63be1f4f51ee31d3f28b7f9b book 1,453,904 85,907,358 44-49 814fd47ce83882bdd5c575b46fff0eb5717bbc1aa2377d46390a15ff01edb5ac last_trade_price 58,667 3,425,229 50-50 256388538a9f37fcf0de39dd86a165356cf84e46e5c8a27d71e80b3e16708d11 market_resolved 901 134,728 51-51 6994fda66cc16d811b044b16f6f1e5e5437ecfd78415d2aa35122ac996b78ac9 new_market 1,212 125,536 52-52 4486b1714043055c936f3b587afe2cb6008f04786f35afc5ec1e59b82befd9bc price_change 100,348,320 1,071,438,260 53-435 355ce7f13efc1f00df633ae4f7d7710572e003068736c633bba01ccc0cb01c2b tick_size_change 4,088 148,618 436-436 9f56a01355f44de30d8cc0ffbb19c7f785ec4289406e6fa7292372983967f288 EVENT MIX count share price_change 100,348,320 88.51% best_bid_ask 11,507,968 10.15% book 1,453,904 1.28% last_trade_price 58,667 0.05% tick_size_change 4,088 <0.01% new_market 1,212 <0.01% market_resolved 901 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,508,172 11,507,968 204 1,544 FULL book 1,454,068 1,453,904 164 223,433 FULL last_trade_price 58,668 58,667 1 255 FULL market_resolved 901 901 0 71 FULL new_market 1,212 1,212 0 0 FULL price_change 100,350,038 100,348,320 1,718 1,597 FULL tick_size_change 4,088 4,088 0 111 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,013,489 9,571,672 6ms 20ms 192ms 8.1s 0 transport_latency_assumed best_bid_ask g 11,485,862 4,044 78ms 117ms 684ms 41.0s 0 transport_latency_assumed best_bid_ask h 11,504,236 213,298 19ms 35ms 355ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,026,259 609,524 19ms 32ms 336ms 19.1s 0 transport_latency_assumed best_bid_ask k 10,965,946 1,109,430 13ms 26ms 160ms 6.5s 0 transport_latency_assumed book c 521,889 236,921 32.1min 2.2d 38.0d 122.6d 0 book_staleness book g 132,843 14,064 97ms 17.9min 9.9d 104.1d 0 book_staleness book h 153,456 29,170 31ms 5.5h 22.1d 122.6d 0 book_staleness book i 1,137,258 757,124 1.6h 2.4d 37.9d 122.6d 0 book_staleness book k 577,758 416,625 48.9min 2.3d 37.9d 122.6d 0 book_staleness last_trade_price c 54,350 46,855 7ms 31ms 285ms 3.1s 0 transport_latency_assumed last_trade_price g 55,126 38 90ms 1.9s 16.1s 38.0s 0 transport_latency_assumed last_trade_price h 58,440 1,551 21ms 103ms 735ms 20.5s 0 transport_latency_assumed last_trade_price i 52,901 2,483 21ms 273ms 3.0s 11.1s 0 transport_latency_assumed last_trade_price k 55,881 7,740 15ms 48ms 302ms 2.2s 0 transport_latency_assumed market_resolved c 783 622 6ms 297ms 56.5s 56.6s 0 transport_latency_assumed market_resolved g 815 not meas. 81ms 387ms 56.2s 56.3s 0 transport_latency_assumed market_resolved h 815 29 21ms 21.0s 56.9s 57.4s 0 transport_latency_assumed market_resolved i 794 139 21ms 22.3s 2.0min 2.0min 0 transport_latency_assumed market_resolved k 797 111 15ms 24.0s 5.6min 5.6min 0 transport_latency_assumed new_market c 829 320 115ms 26.3s 4.4min 4.4min 0 transport_latency_assumed new_market g 806 198 136ms 17.3s 55.7s 1.1min 0 transport_latency_assumed new_market h 806 157 156ms 9.5s 35.1s 1.6min 0 transport_latency_assumed new_market i 806 317 120ms 19.5s 58.0s 2.2min 0 transport_latency_assumed new_market k 832 220 150ms 56.5s 5.7min 5.9min 0 transport_latency_assumed price_change c 95,310,390 82,427,800 6ms 24ms 213ms 9.4s 0 transport_latency_assumed price_change g 99,309,450 49,674 79ms 198ms 5.5s 41.0s 0 transport_latency_assumed price_change h 100,233,382 2,182,400 19ms 45ms 468ms 1.1min 0 transport_latency_assumed price_change i 94,613,814 4,976,864 20ms 52ms 1.2s 19.1s 0 transport_latency_assumed price_change k 95,532,938 10,711,582 14ms 31ms 191ms 9.0s 0 transport_latency_assumed tick_size_change c 3,852 3,403 6ms 17ms 142ms 373ms 0 transport_latency_assumed tick_size_change g 4,088 1 78ms 184ms 520ms 1.5s 0 transport_latency_assumed tick_size_change h 4,088 37 19ms 31ms 607ms 8.7s 0 transport_latency_assumed tick_size_change i 4,004 157 20ms 31ms 125ms 764ms 0 transport_latency_assumed tick_size_change k 3,964 490 14ms 21ms 62ms 388ms 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/12/2026-09-29T12.parquet sha256sum 2026-09-29T12.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.