Hour audit: 2026-09-28T04
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-28T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T04:00:00.000426287+00:00 · last event 2026-09-28T04:59:59.999966207+00:00
VOLUME 97,558,010 rows · 1,005,853,031 bytes (959.26 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 97,478,940 · i: 97,470,752 · c: 97,464,594 · h: 97,360,572 · g: 97,187,640 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 4,089,967 (4.19%) · i: 4,808,619 (4.93%) · c: 87,691,433 (89.89%) · h: 946,332 (0.97%) · g: 21,659 (0.02%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4e489cd85c7fc6e193d92a65f71836cfff167290540df89b1d9698b563c644e4
the corpus checksum ledger names this file with the same digest
joined 97,559,667 to merged 97,558,010, minus 1,657 (minus 0.0017%)
boundary drops 1,657 · 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-28T06:37:09Z 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,809,323 121,079,652 0-41 b6c035f43eb046051d8fc68db9d4cf99afbb8d27bd245f89d15e2159e1cb51ec book 148,773 14,808,099 42-42 7d502ca74d5072562a4788239eec6b87e11644083787a064bc0d334c98074e1e last_trade_price 48,129 2,775,096 43-43 5a41fd6028bb6bbb5dbb84d185def96959a788220656985a8db0055abb99a255 market_resolved 1,408 228,594 44-44 a3a1771803141688f66d06f87e4b0439877db08514ae6dc905f7ab33184be1c7 new_market 3,257 311,556 45-45 70fa71bd3cc6c2c38082a30699b565fefdf58a28fe631167e9f34fa00279ec2b price_change 86,544,484 865,437,931 46-376 bbc6074f808634686d73548bacb02cc79c8756baa7d56ff7ce049c9ceceb69cd tick_size_change 2,636 97,142 377-377 f7eb79b038d1ccd5f2edfee55210432b2fee030f79443acd13c435a30a96233f EVENT MIX count share price_change 86,544,484 88.71% best_bid_ask 10,809,323 11.08% book 148,773 0.15% last_trade_price 48,129 0.05% new_market 3,257 <0.01% tick_size_change 2,636 <0.01% market_resolved 1,408 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,809,535 10,809,323 212 228 FULL book 148,775 148,773 2 17,419 FULL last_trade_price 48,130 48,129 1 0 FULL market_resolved 1,408 1,408 0 4 FULL new_market 3,257 3,257 0 0 FULL price_change 86,545,926 86,544,484 1,442 383 FULL tick_size_change 2,636 2,636 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,807,124 9,813,390 5ms 13ms 339ms 14.3s 0 transport_latency_assumed best_bid_ask g 10,802,298 1,373 77ms 105ms 813ms 31.8s 0 transport_latency_assumed best_bid_ask h 10,804,160 90,967 18ms 29ms 732ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,807,138 490,583 13ms 19ms 170ms 5.6s 0 transport_latency_assumed best_bid_ask k 10,806,846 413,010 12ms 21ms 409ms 1.1min 0 transport_latency_assumed book c 113,308 97,397 7ms 54.0s 8.6d 102.8d 0 book_staleness book g 104,717 6,372 82ms 3.3s 1.0d 102.7d 0 book_staleness book h 116,474 18,552 23ms 13.9min 8.6d 121.3d 0 book_staleness book i 102,833 9,764 15ms 149ms 9.0h 102.7d 0 book_staleness book k 111,111 16,688 16ms 4.7s 5.4d 121.2d 0 book_staleness last_trade_price c 47,906 41,984 6ms 29ms 666ms 6.2s 0 transport_latency_assumed last_trade_price g 47,201 25 80ms 425ms 10.2s 31.1s 0 transport_latency_assumed last_trade_price h 47,760 767 20ms 68ms 1.7s 1.2min 0 transport_latency_assumed last_trade_price i 48,027 2,641 15ms 50ms 622ms 5.5s 0 transport_latency_assumed last_trade_price k 48,033 2,712 14ms 46ms 624ms 1.1min 0 transport_latency_assumed market_resolved c 1,374 1,213 5ms 21ms 29.7s 51.1s 0 transport_latency_assumed market_resolved g 1,374 8 79ms 237ms 40.1s 47.2s 0 transport_latency_assumed market_resolved h 1,378 5 20ms 71ms 29.5s 49.7s 0 transport_latency_assumed market_resolved i 1,378 150 14ms 87ms 56.1s 57.4s 0 transport_latency_assumed market_resolved k 1,374 32 13ms 45ms 34.7s 56.1s 0 transport_latency_assumed new_market c 2,042 865 254ms 47.5s 1.1min 1.5min 0 transport_latency_assumed new_market g 2,042 315 561ms 46.9s 1.0min 1.5min 0 transport_latency_assumed new_market h 2,042 453 265ms 47.5s 1.0min 1.7min 0 transport_latency_assumed new_market i 2,042 920 228ms 47.0s 57.9s 1.7min 0 transport_latency_assumed new_market k 2,042 704 315ms 44.8s 56.4s 1.5min 0 transport_latency_assumed price_change c 86,490,204 77,734,296 5ms 16ms 386ms 15.1s 0 transport_latency_assumed price_change g 86,227,376 13,562 77ms 127ms 1.5s 32.0s 0 transport_latency_assumed price_change h 86,386,126 835,520 18ms 35ms 812ms 1.3min 0 transport_latency_assumed price_change i 86,506,698 4,304,369 13ms 24ms 245ms 5.6s 0 transport_latency_assumed price_change k 86,506,898 3,656,737 12ms 25ms 436ms 1.1min 0 transport_latency_assumed tick_size_change c 2,636 2,288 5ms 72ms 444ms 1.5s 0 transport_latency_assumed tick_size_change g 2,632 4 77ms 251ms 1.2s 14.6s 0 transport_latency_assumed tick_size_change h 2,632 68 18ms 68ms 790ms 18.7s 0 transport_latency_assumed tick_size_change i 2,636 192 14ms 48ms 345ms 575ms 0 transport_latency_assumed tick_size_change k 2,636 84 12ms 122ms 1.5s 2.0s 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-28/04/2026-09-28T04.parquet sha256sum 2026-09-28T04.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.