Hour audit: 2026-09-14T08
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-14T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T08:00:00.000138658+00:00 · last event 2026-09-14T08:59:59.999961665+00:00
VOLUME 105,913,337 rows · 1,097,299,244 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 104,527,137 · e: 104,508,730 · h: 104,489,841 · g: 104,458,650 · c: 90,264,067 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 260,433 (0.25%) · e: 869,543 (0.82%) · h: 18,445,967 (17.42%) · g: 35,527 (0.03%) · c: 86,301,867 (81.48%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,913,337 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bae35732d1c8b6c77edc1eb8ef212d1c9eb99f2e4e083efece3f606610d3650f
the corpus checksum ledger names this file with the same digest
joined 105,915,348 to merged 105,913,337, minus 2,011 (minus 0.0019%)
boundary drops 2,011 · 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-14T09:57:12Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,670,039 115,775,731 0-40 05ad95e480fdd9bd45697a1931d8afdd2ac00c1ca414567b2ce56d69571e4293 book 1,453,702 73,236,751 41-46 17aa038241cf8e8580d48acf9bde044a5fe91d80a5b292e1153646ea8a9362e1 last_trade_price 50,015 2,910,427 47-47 5fabac2afe505b3d3f41946bccf1ffe15f8ae27f23687e609b8f9757cf47e5cc market_resolved 1,123 127,416 48-48 8c0f2f896440087f4c8dac92fa41e05eb6cb18a59d7469cb8cbbe09cee22d647 new_market 1,720 139,167 49-49 80b03403420a8a11940ad4a6fc494b2e3c76e68036502f2d5907a6b71a1abea5 price_change 93,734,682 903,826,347 50-407 32100f90e236e1c2b17189475900fbbd60b61e450dcc03f4a38210e95584ffdb tick_size_change 2,056 77,004 408-408 e3c48c67916f8754f029aa7af3a52b92f6c546a4054e8b2e6e305d637660315a EVENT MIX count share price_change 93,734,682 88.50% best_bid_ask 10,670,039 10.07% book 1,453,702 1.37% last_trade_price 50,015 0.05% tick_size_change 2,056 <0.01% new_market 1,720 <0.01% market_resolved 1,123 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,670,327 10,670,039 288 2,280 FULL book 1,453,768 1,453,702 66 163,581 FULL last_trade_price 50,016 50,015 1 290 FULL market_resolved 1,123 1,123 0 6 FULL new_market 1,720 1,720 0 36 FULL price_change 93,736,338 93,734,682 1,656 1,889 FULL tick_size_change 2,056 2,056 0 68 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,082,409 8,703,112 5ms 11ms 101ms 3.8s 0 transport_latency_assumed best_bid_ask e 10,667,723 80,555 40ms 46ms 181ms 8.2s 0 transport_latency_assumed best_bid_ask f 10,668,008 22,990 47ms 55ms 197ms 7.2s 0 transport_latency_assumed best_bid_ask g 10,664,906 2,018 81ms 99ms 386ms 28.5s 0 transport_latency_assumed best_bid_ask h 10,668,635 1,861,364 18ms 25ms 138ms 41.2s 0 transport_latency_assumed book c 1,425,794 1,416,835 34.1min 2.6d 36.8d 107.4d 0 book_staleness book e 107,162 3,069 42ms 265ms 2.8h 88.9d 0 book_staleness book f 106,520 1,483 49ms 257ms 21.6min 88.9d 0 book_staleness book g 130,483 11,570 92ms 59.9min 6.9d 107.4d 0 book_staleness book h 106,098 20,745 21ms 72ms 5.5min 88.9d 0 book_staleness last_trade_price c 41,710 39,446 11ms 51ms 230ms 5.0s 0 transport_latency_assumed last_trade_price e 49,782 580 48ms 185ms 1.6s 8.2s 0 transport_latency_assumed last_trade_price f 49,870 212 56ms 196ms 1.5s 7.2s 0 transport_latency_assumed last_trade_price g 49,498 52 95ms 351ms 6.2s 29.1s 0 transport_latency_assumed last_trade_price h 49,819 9,725 24ms 80ms 361ms 7.3s 0 transport_latency_assumed market_resolved c 983 961 6ms 10.0min 13.6min 16.5min 0 transport_latency_assumed market_resolved e 761 3 41ms 187ms 55.7s 55.7s 0 transport_latency_assumed market_resolved f 761 1 48ms 192ms 55.2s 55.2s 0 transport_latency_assumed market_resolved g 761 not meas. 87ms 250ms 805ms 1.0min 0 transport_latency_assumed market_resolved h 761 158 19ms 71ms 55.1s 55.1s 0 transport_latency_assumed new_market c 1,261 943 14.6s 12.7min 33.0min 33.1min 0 transport_latency_assumed new_market e 826 184 212ms 18.8s 31.0s 53.5s 0 transport_latency_assumed new_market f 826 111 199ms 17.0s 31.4s 58.9s 0 transport_latency_assumed new_market g 826 139 354ms 19.6s 30.1s 58.2s 0 transport_latency_assumed new_market h 826 343 142ms 17.1s 31.7s 1.4min 0 transport_latency_assumed price_change c 79,710,126 76,138,852 5ms 13ms 121ms 3.8s 0 transport_latency_assumed price_change e 93,680,420 785,152 40ms 52ms 293ms 8.2s 0 transport_latency_assumed price_change f 93,699,096 235,636 47ms 62ms 307ms 7.3s 0 transport_latency_assumed price_change g 93,610,120 21,748 82ms 110ms 667ms 32.1s 0 transport_latency_assumed price_change h 93,661,646 16,553,294 18ms 28ms 173ms 41.2s 0 transport_latency_assumed tick_size_change c 1,784 1,718 5ms 11ms 61ms 568ms 0 transport_latency_assumed tick_size_change e 2,056 not meas. 40ms 48ms 234ms 447ms 0 transport_latency_assumed tick_size_change f 2,056 not meas. 47ms 54ms 271ms 445ms 0 transport_latency_assumed tick_size_change g 2,056 not meas. 81ms 98ms 328ms 744ms 0 transport_latency_assumed tick_size_change h 2,056 338 18ms 27ms 164ms 607ms 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-14/08/2026-09-14T08.parquet sha256sum 2026-09-14T08.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.