Hour audit: 2026-09-27T08
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-27T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T08:00:00.000257510+00:00 · last event 2026-09-27T08:59:59.999888705+00:00
VOLUME 102,626,614 rows · 1,091,737,129 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 102,181,671 · i: 102,160,968 · h: 102,124,794 · g: 101,907,910 · c: 98,247,389 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 9,673,922 (9.43%) · i: 2,007,037 (1.96%) · h: 1,608,603 (1.57%) · g: 43,436 (0.04%) · c: 89,293,616 (87.01%) (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 102,626,614 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 50da297e44756798bdf31565cfda06091f8b4cd937cb5b6530a8a69f3eb76446
the corpus checksum ledger names this file with the same digest
joined 102,628,914 to merged 102,626,614, minus 2,300 (minus 0.0022%)
boundary drops 2,300 · 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-27T15:14:07Z 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,735,376 121,162,379 0-40 73cc85c5864fd1af9d20bb86da9575b77010a653997a798395e00d99b19b66e6 book 525,582 51,951,142 41-43 a105a50da517de9a47f679b40ee3ec4cd8228d23fd02b29822a722fb14c5629d last_trade_price 57,558 3,244,835 44-44 208c5f1f4da358cdb6d9c7eda8b42b1ac878bde4dc0e10b134901b0f17ece972 market_resolved 751 104,083 45-45 a1c7df22e4be1a16902a678c425984a2fa0847163701491af5edb350d6f1eb37 new_market 4,973 471,741 46-46 d03774d79a9932be13fd18f738ef46af90e1980f4a11cee19796ef3b932564e1 price_change 91,300,574 913,565,436 47-395 c1c4755bb2a20176ea1ad17a4b8a505e595d60dc6a27ea8a3c938f2275153531 tick_size_change 1,800 66,309 396-396 ca50195d932d5145f6c9620c7e8560cfddc950521dabcafc94364278aa7ae432 EVENT MIX count share price_change 91,300,574 88.96% best_bid_ask 10,735,376 10.46% book 525,582 0.51% last_trade_price 57,558 0.06% new_market 4,973 <0.01% tick_size_change 1,800 <0.01% market_resolved 751 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,735,644 10,735,376 268 879 FULL book 525,604 525,582 22 191,969 FULL last_trade_price 57,558 57,558 0 110 FULL market_resolved 751 751 0 24 FULL new_market 4,973 4,973 0 0 FULL price_change 91,302,584 91,300,574 2,010 387 FULL tick_size_change 1,800 1,800 0 32 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,281,983 9,385,399 5ms 12ms 216ms 9.8s 0 transport_latency_assumed best_bid_ask g 10,724,905 3,698 77ms 113ms 967ms 34.3s 0 transport_latency_assumed best_bid_ask h 10,729,870 156,585 18ms 25ms 482ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,732,170 200,435 20ms 25ms 159ms 4.8s 0 transport_latency_assumed best_bid_ask k 10,731,622 989,259 12ms 18ms 244ms 56.7s 0 transport_latency_assumed book c 510,231 489,789 16.5min 2.5d 35.8d 120.4d 0 book_staleness book g 127,700 8,490 89ms 8.1s 2.5d 101.9d 0 book_staleness book h 123,929 5,975 22ms 276ms 3.9h 101.8d 0 book_staleness book i 122,110 6,154 23ms 147ms 9.0s 120.4d 0 book_staleness book k 124,140 15,174 15ms 142ms 4.0h 120.4d 0 book_staleness last_trade_price c 55,050 48,996 6ms 24ms 261ms 4.3s 0 transport_latency_assumed last_trade_price g 55,840 9 84ms 654ms 15.9s 30.1s 0 transport_latency_assumed last_trade_price h 57,212 1,156 19ms 69ms 1.0s 54.9s 0 transport_latency_assumed last_trade_price i 57,475 1,296 22ms 68ms 673ms 4.8s 0 transport_latency_assumed last_trade_price k 57,354 6,101 13ms 37ms 328ms 15.5s 0 transport_latency_assumed market_resolved c 718 644 5ms 6.0min 8.0min 8.2min 0 transport_latency_assumed market_resolved g 635 not meas. 86ms 538ms 53.3s 57.0s 0 transport_latency_assumed market_resolved h 635 11 19ms 137ms 30.8s 58.0s 0 transport_latency_assumed market_resolved i 635 21 22ms 132ms 29.9s 57.8s 0 transport_latency_assumed market_resolved k 635 75 13ms 79ms 30.0s 57.6s 0 transport_latency_assumed new_market c 3,094 1,439 102ms 27.4s 3.5min 5.0min 0 transport_latency_assumed new_market g 3,058 653 346ms 34.1s 1.0min 1.7min 0 transport_latency_assumed new_market h 3,058 616 187ms 30.6s 1.1min 1.7min 0 transport_latency_assumed new_market i 3,058 1,254 146ms 36.0s 1.0min 1.6min 0 transport_latency_assumed new_market k 3,058 1,011 187ms 33.8s 1.0min 1.7min 0 transport_latency_assumed price_change c 87,394,641 79,365,717 5ms 14ms 224ms 9.8s 0 transport_latency_assumed price_change g 90,993,972 30,586 78ms 153ms 3.4s 34.3s 0 transport_latency_assumed price_change h 91,208,290 1,444,244 18ms 30ms 532ms 1.2min 0 transport_latency_assumed price_change i 91,243,720 1,797,876 20ms 29ms 215ms 4.8s 0 transport_latency_assumed price_change k 91,263,062 8,662,151 12ms 20ms 259ms 56.7s 0 transport_latency_assumed tick_size_change c 1,672 1,632 4ms 7ms 20ms 169ms 0 transport_latency_assumed tick_size_change g 1,800 not meas. 77ms 92ms 237ms 349ms 0 transport_latency_assumed tick_size_change h 1,800 16 18ms 21ms 44ms 1.7s 0 transport_latency_assumed tick_size_change i 1,800 1 20ms 23ms 56ms 1.7s 0 transport_latency_assumed tick_size_change k 1,800 151 12ms 15ms 41ms 69ms 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-27/08/2026-09-27T08.parquet sha256sum 2026-09-27T08.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.