Hour audit: 2026-09-29T03
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-29T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T03:00:00.000031210+00:00 · last event 2026-09-29T03:59:59.999930755+00:00
VOLUME 103,230,246 rows · 1,075,839,238 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 103,128,706 · k: 103,090,263 · i: 103,065,402 · c: 103,042,470 · g: 102,866,469 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,691,294 (2.61%) · k: 6,728,396 (6.52%) · i: 976,793 (0.95%) · c: 92,803,176 (89.90%) · g: 30,587 (0.03%) (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 103,230,246 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7017c4f02c8cd404088d9585134d86c4bb6f508057c98a2c12a34f1574b9123f
the corpus checksum ledger names this file with the same digest
joined 103,233,271 to merged 103,230,246, minus 3,025 (minus 0.0029%)
boundary drops 3,025 · 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-29T06:12:23Z 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 10,878,724 124,117,748 0-41 79f348002523ea657ea9b5af38e267e7503bee78b4bb4bfd24d8003ae5fbf6c3 book 160,276 16,626,757 42-42 c621322095b575a74a9659bad4ec8df8fc5782abb95740724afe30b9b3cd2832 last_trade_price 45,724 2,636,719 43-43 fbec9d937b8d7a8f0cd3600c795b4f822d60595a7235145b3419c9f47232d900 market_resolved 1,253 192,270 44-44 637cb297c1bd9b31213103169392d858c99fafd7b4f726d0d0c56ea504fd61a5 new_market 1,731 188,321 45-45 88a076f5521afeb97499eb6d51650c6e1b52ec92b82741afadc34657da5bcdc2 price_change 92,139,602 930,791,669 46-397 858db93b08bbdfc8b9edbed00eb5f3d42737603a02c44cf47b180ab47008dbe8 tick_size_change 2,936 108,247 398-398 89d2416fc6cd4bf9b3c3d491c41ddc45ae091dc961b270a7d88bc12bc9b00722 EVENT MIX count share price_change 92,139,602 89.26% best_bid_ask 10,878,724 10.54% book 160,276 0.16% last_trade_price 45,724 0.04% tick_size_change 2,936 <0.01% new_market 1,731 <0.01% market_resolved 1,253 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,879,062 10,878,724 338 84 FULL book 160,408 160,276 132 27,047 FULL last_trade_price 45,727 45,724 3 0 FULL market_resolved 1,253 1,253 0 0 FULL new_market 1,731 1,731 0 0 FULL price_change 92,142,154 92,139,602 2,552 251 FULL tick_size_change 2,936 2,936 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,877,253 9,939,530 4ms 14ms 112ms 3.5s 0 transport_latency_assumed best_bid_ask g 10,874,490 1,890 78ms 100ms 337ms 23.7s 0 transport_latency_assumed best_bid_ask h 10,877,954 236,511 17ms 24ms 145ms 45.9s 0 transport_latency_assumed best_bid_ask i 10,877,836 90,720 20ms 29ms 124ms 5.6s 0 transport_latency_assumed best_bid_ask k 10,877,778 610,073 13ms 23ms 139ms 11.6s 0 transport_latency_assumed book c 113,550 99,981 7ms 2.1h 19.8d 103.7d 0 book_staleness book g 103,791 11,297 88ms 12.8s 2.0d 103.7d 0 book_staleness book h 119,095 27,797 22ms 4.4h 19.8d 122.2d 0 book_staleness book i 98,314 5,394 23ms 142ms 12.7h 103.5d 0 book_staleness book k 102,219 15,807 16ms 1.7s 2.0d 103.6d 0 book_staleness last_trade_price c 45,396 39,589 6ms 27ms 208ms 1.2s 0 transport_latency_assumed last_trade_price g 45,050 12 85ms 309ms 5.9s 23.8s 0 transport_latency_assumed last_trade_price h 45,618 1,529 18ms 37ms 250ms 7.4s 0 transport_latency_assumed last_trade_price i 45,587 476 22ms 58ms 339ms 1.4s 0 transport_latency_assumed last_trade_price k 45,565 4,118 14ms 33ms 222ms 3.2s 0 transport_latency_assumed market_resolved c 1,202 1,032 5ms 39ms 54.4s 57.4s 0 transport_latency_assumed market_resolved g 1,202 11 79ms 212ms 52.7s 55.8s 0 transport_latency_assumed market_resolved h 1,202 16 18ms 75ms 54.1s 54.8s 0 transport_latency_assumed market_resolved i 1,202 98 22ms 89ms 48.6s 49.4s 0 transport_latency_assumed market_resolved k 1,202 96 13ms 36ms 45.0s 46.3s 0 transport_latency_assumed new_market c 1,235 530 90ms 11.1s 26.4s 1.6min 0 transport_latency_assumed new_market g 1,235 121 244ms 21.3s 33.0s 1.7min 0 transport_latency_assumed new_market h 1,235 453 112ms 10.2s 25.3s 1.7min 0 transport_latency_assumed new_market i 1,235 321 113ms 19.2s 29.4s 38.1s 0 transport_latency_assumed new_market k 1,235 306 156ms 19.6s 33.5s 1.8min 0 transport_latency_assumed price_change c 92,000,898 82,719,782 5ms 18ms 132ms 3.7s 0 transport_latency_assumed price_change g 91,837,765 17,256 79ms 122ms 1.2s 23.9s 0 transport_latency_assumed price_change h 92,080,666 2,424,926 17ms 28ms 190ms 46.1s 0 transport_latency_assumed price_change i 92,038,292 879,764 21ms 36ms 191ms 6.5s 0 transport_latency_assumed price_change k 92,059,328 6,097,874 13ms 26ms 158ms 12.8s 0 transport_latency_assumed tick_size_change c 2,936 2,732 4ms 12ms 222ms 323ms 0 transport_latency_assumed tick_size_change g 2,936 not meas. 78ms 99ms 358ms 567ms 0 transport_latency_assumed tick_size_change h 2,936 62 17ms 25ms 229ms 980ms 0 transport_latency_assumed tick_size_change i 2,936 20 21ms 31ms 117ms 307ms 0 transport_latency_assumed tick_size_change k 2,936 122 13ms 26ms 129ms 407ms 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/03/2026-09-29T03.parquet sha256sum 2026-09-29T03.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.