Hour audit: 2026-09-28T12
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-28T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T12:00:00.000006204+00:00 · last event 2026-09-28T12:59:59.999969968+00:00
VOLUME 101,979,053 rows · 1,095,066,103 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 101,916,593 · c: 101,914,840 · k: 101,899,104 · i: 101,879,623 · g: 101,201,859 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,019,172 (1.00%) · c: 89,606,102 (87.87%) · k: 5,482,775 (5.38%) · i: 5,834,789 (5.72%) · g: 36,215 (0.04%) (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 101,979,053 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c02bbe87a525b678b3298f197e67246de37e0864b8d87077cedfc7cad5f69b91
the corpus checksum ledger names this file with the same digest
joined 101,980,710 to merged 101,979,053, minus 1,657 (minus 0.0016%)
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-28T14:37:05Z 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,588,318 112,629,091 0-36 b0560d7de0da09de5798316fb23609e6706373f1ad4ade3cd98d68335c1d8ebf book 142,503 14,890,762 37-37 c705b1ea2c697687679234f29d537b84e56c047a09b431ee3c3e290e52c46d02 last_trade_price 58,658 3,365,243 38-38 b3082f35e33698dfa5d31929feb4acff26df510f40a172eec397c5d86633a501 market_resolved 736 111,988 39-39 c783364aebbbe816f76c37f933510a2bca681381d671545a41effd5d5465df65 new_market 1,743 178,187 40-40 96cbf718aa7298dc9842b8188e49046d59dbf4bfe9bdc46bf34290cdfca05036 price_change 92,184,143 962,619,136 41-392 f84eab75af8426c83990b2ecbc6524d77535a3cbedc0a9db32366662aa14bc71 tick_size_change 2,952 109,141 393-393 48f4a9219a5ad2767258df65468372fe7dad8c14f57256b5e35b2f4eab5c33f3 EVENT MIX count share price_change 92,184,143 90.40% best_bid_ask 9,588,318 9.40% book 142,503 0.14% last_trade_price 58,658 0.06% tick_size_change 2,952 <0.01% new_market 1,743 <0.01% market_resolved 736 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,588,478 9,588,318 160 291 FULL book 142,527 142,503 24 6,912 FULL last_trade_price 58,660 58,658 2 0 FULL market_resolved 736 736 0 0 FULL new_market 1,743 1,743 0 0 FULL price_change 92,185,614 92,184,143 1,471 258 FULL tick_size_change 2,952 2,952 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,586,832 8,510,004 5ms 15ms 156ms 22.6s 0 transport_latency_assumed best_bid_ask g 9,575,945 1,581 79ms 112ms 715ms 27.2s 0 transport_latency_assumed best_bid_ask h 9,586,032 83,357 19ms 29ms 251ms 48.7s 0 transport_latency_assumed best_bid_ask i 9,585,589 534,050 12ms 22ms 185ms 17.4s 0 transport_latency_assumed best_bid_ask k 9,586,196 459,326 12ms 22ms 172ms 14.8s 0 transport_latency_assumed book c 122,846 105,526 7ms 49ms 8.3h 59.0d 0 book_staleness book g 121,701 6,987 88ms 6.4s 1.3d 103.1d 0 book_staleness book h 126,175 7,378 24ms 261ms 19.1h 103.1d 0 book_staleness book i 123,642 11,075 15ms 191ms 14.8h 103.1d 0 book_staleness book k 123,770 11,537 16ms 80ms 14.5h 103.1d 0 book_staleness last_trade_price c 58,547 50,919 6ms 26ms 334ms 7.8s 0 transport_latency_assumed last_trade_price g 55,757 23 89ms 1.6s 14.9s 27.4s 0 transport_latency_assumed last_trade_price h 58,509 573 20ms 92ms 699ms 9.2s 0 transport_latency_assumed last_trade_price i 58,368 2,860 14ms 94ms 800ms 6.8s 0 transport_latency_assumed last_trade_price k 58,513 4,283 13ms 39ms 304ms 8.0s 0 transport_latency_assumed market_resolved c 686 586 6ms 95ms 55.5s 55.5s 0 transport_latency_assumed market_resolved g 686 9 82ms 361ms 54.6s 54.7s 0 transport_latency_assumed market_resolved h 686 1 20ms 152ms 53.0s 53.1s 0 transport_latency_assumed market_resolved i 686 118 14ms 25.8s 52.5s 54.8s 0 transport_latency_assumed market_resolved k 686 22 13ms 303ms 39.1s 39.2s 0 transport_latency_assumed new_market c 1,153 634 111ms 28.7s 41.0s 1.6min 0 transport_latency_assumed new_market g 1,153 153 361ms 22.1s 41.8s 1.7min 0 transport_latency_assumed new_market h 1,153 254 165ms 21.4s 43.0s 1.6min 0 transport_latency_assumed new_market i 1,153 299 144ms 19.3s 41.7s 1.8min 0 transport_latency_assumed new_market k 1,153 403 184ms 21.3s 41.0s 1.7min 0 transport_latency_assumed price_change c 92,141,824 80,935,807 5ms 18ms 219ms 23.7s 0 transport_latency_assumed price_change g 91,443,665 27,462 80ms 193ms 5.8s 27.5s 0 transport_latency_assumed price_change h 92,141,086 927,585 19ms 38ms 382ms 48.9s 0 transport_latency_assumed price_change i 92,107,233 5,286,222 12ms 32ms 375ms 17.4s 0 transport_latency_assumed price_change k 92,125,834 5,007,067 12ms 26ms 242ms 14.8s 0 transport_latency_assumed tick_size_change c 2,952 2,626 5ms 14ms 165ms 684ms 0 transport_latency_assumed tick_size_change g 2,952 not meas. 79ms 97ms 466ms 1.7s 0 transport_latency_assumed tick_size_change h 2,952 24 19ms 31ms 236ms 2.8s 0 transport_latency_assumed tick_size_change i 2,952 165 12ms 22ms 146ms 801ms 0 transport_latency_assumed tick_size_change k 2,952 137 12ms 22ms 147ms 966ms 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/12/2026-09-28T12.parquet sha256sum 2026-09-28T12.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.