Hour audit: 2026-09-28T01
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-28T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T01:00:00.000038548+00:00 · last event 2026-09-28T01:59:59.999940136+00:00
VOLUME 113,497,892 rows · 1,186,763,330 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 113,433,942 · h: 113,395,928 · g: 113,042,511 · c: 111,922,771 · i: 111,581,935 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 8,578,751 (7.56%) · h: 1,900,455 (1.67%) · g: 10,889 (0.01%) · c: 101,106,592 (89.08%) · i: 1,901,205 (1.68%) (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 113,497,892 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b5c03dbad7c79f5826ccc0f315e1bfd58708c9bfaaf583209031099f20144964
the corpus checksum ledger names this file with the same digest
joined 113,499,812 to merged 113,497,892, minus 1,920 (minus 0.0017%)
boundary drops 1,920 · 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-28T04:10:18Z 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 12,174,084 138,031,952 0-46 f2092d49e035cbcb35f7117893dbba548b114aa29f709db9c9dd37ae2204cd1f book 140,669 14,869,270 47-47 e448e4db3583b9225b458fba99907570faa711052dba546940f3f09f91c5afa6 last_trade_price 54,424 3,085,415 48-48 29169aaa59d3b1b9403d9de424674cb835f70dcb50372e99e5576b037ae9f536 market_resolved 1,729 271,186 49-49 40f8b29c3908df0b72006f2f4cf514ce5f485287c960f114c21ef52c9703a875 new_market 1,289 136,357 50-50 b8e9273def9aee5bac066a102b7106de59ff84dee4e2d8f03dc28d6c1bcc62d4 price_change 101,122,429 1,028,957,193 51-436 db3a6b3c02f1076a1444aef89234f192a6e65d9e73b253558720c985a7f74756 tick_size_change 3,268 120,081 437-437 52c1239c76054bcb40410b44131f4f6e56465bc122ffaae34941bfffaef4be6c EVENT MIX count share price_change 101,122,429 89.10% best_bid_ask 12,174,084 10.73% book 140,669 0.12% last_trade_price 54,424 0.05% tick_size_change 3,268 <0.01% market_resolved 1,729 <0.01% new_market 1,289 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,174,314 12,174,084 230 1,723 FULL book 140,671 140,669 2 11,258 FULL last_trade_price 54,424 54,424 0 117 FULL market_resolved 1,729 1,729 0 26 FULL new_market 1,289 1,289 0 0 FULL price_change 101,124,117 101,122,429 1,688 3,124 FULL tick_size_change 3,268 3,268 0 21 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,010,580 10,940,815 4ms 14ms 130ms 5.5s 0 transport_latency_assumed best_bid_ask g 12,166,070 647 80ms 104ms 430ms 29.8s 0 transport_latency_assumed best_bid_ask h 12,172,118 185,087 18ms 30ms 163ms 42.4s 0 transport_latency_assumed best_bid_ask i 11,974,135 187,758 20ms 27ms 100ms 1.4s 0 transport_latency_assumed best_bid_ask k 12,172,054 859,777 13ms 24ms 141ms 32.0s 0 transport_latency_assumed book c 121,350 106,639 6ms 993ms 5.4d 102.6d 0 book_staleness book g 114,142 4,067 87ms 3.2s 21.1h 102.6d 0 book_staleness book h 113,832 5,704 22ms 78ms 13.0h 102.6d 0 book_staleness book i 112,922 5,817 22ms 86ms 10.2h 102.6d 0 book_staleness book k 120,486 18,442 17ms 228ms 3.2d 102.6d 0 book_staleness last_trade_price c 53,983 47,794 5ms 24ms 201ms 2.2s 0 transport_latency_assumed last_trade_price g 53,382 5 87ms 1.0s 10.3s 30.0s 0 transport_latency_assumed last_trade_price h 54,250 1,113 19ms 49ms 248ms 9.8s 0 transport_latency_assumed last_trade_price i 53,884 912 21ms 55ms 334ms 1.6s 0 transport_latency_assumed last_trade_price k 54,307 4,600 14ms 36ms 222ms 5.7s 0 transport_latency_assumed market_resolved c 1,679 1,305 5ms 23.1s 49.7s 2.3min 0 transport_latency_assumed market_resolved g 1,692 not meas. 91ms 23.2s 48.3s 51.0s 0 transport_latency_assumed market_resolved h 1,692 23 22ms 21.4s 46.5s 55.3s 0 transport_latency_assumed market_resolved i 1,679 306 24ms 21.3s 53.9s 2.4min 0 transport_latency_assumed market_resolved k 1,692 95 16ms 26.5s 50.1s 52.1s 0 transport_latency_assumed new_market c 872 488 98ms 21.0s 45.9s 1.1min 0 transport_latency_assumed new_market g 872 126 348ms 21.5s 37.6s 1.7min 0 transport_latency_assumed new_market h 872 244 137ms 18.4s 1.0min 1.2min 0 transport_latency_assumed new_market i 872 304 106ms 10.8s 36.1s 1.6min 0 transport_latency_assumed new_market k 872 127 198ms 11.9s 36.1s 1.5min 0 transport_latency_assumed price_change c 99,731,075 90,006,532 5ms 17ms 141ms 5.5s 0 transport_latency_assumed price_change g 100,703,085 6,044 81ms 137ms 3.4s 30.0s 0 transport_latency_assumed price_change h 101,049,896 1,708,242 18ms 35ms 204ms 42.4s 0 transport_latency_assumed price_change i 99,435,223 1,706,075 20ms 32ms 150ms 1.9s 0 transport_latency_assumed price_change k 101,081,263 7,695,536 13ms 27ms 156ms 35.0s 0 transport_latency_assumed tick_size_change c 3,232 3,019 4ms 10ms 57ms 254ms 0 transport_latency_assumed tick_size_change g 3,268 not meas. 80ms 99ms 210ms 532ms 0 transport_latency_assumed tick_size_change h 3,268 42 18ms 28ms 88ms 263ms 0 transport_latency_assumed tick_size_change i 3,220 33 20ms 26ms 61ms 86ms 0 transport_latency_assumed tick_size_change k 3,268 174 14ms 22ms 50ms 290ms 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/01/2026-09-28T01.parquet sha256sum 2026-09-28T01.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.