Hour audit: 2026-09-08T18
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-08T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T18:00:00.000044564+00:00 · last event 2026-09-08T18:59:59.999960787+00:00
VOLUME 102,947,960 rows · 1,110,645,587 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 102,094,812 · e: 101,961,195 · f: 101,867,799 · g: 101,550,225 · c: 94,481,224 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,726,819 (13.33%) · e: 966,268 (0.94%) · f: 495,359 (0.48%) · g: 52,014 (0.05%) · c: 87,707,500 (85.20%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4a3ef973de98e0e75156347a5eb1a55f6d37e4ce20dd11a56d8a80133996cbc2
the corpus checksum ledger names this file with the same digest
joined 102,950,648 to merged 102,947,960, minus 2,688 (minus 0.0026%)
boundary drops 2,688 · 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-08T20:34:48Z 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,342,108 116,624,036 0-39 62d4aa04ee1c6cdb9b139a25b2a99243e295e82549f63ced4998b1952bd649ea book 916,641 66,734,523 40-43 92a53d636d1cd356f506a3b0c991973d4625e8ce7cd1acafb66631cad3a17a72 last_trade_price 69,440 3,955,325 44-44 9ed57309b40bcfb480cbf3a48ac6af70b442ce765c9f4e999246d6746b22e825 market_resolved 1,507 211,496 45-45 b7bc00f80355ea567aa9308fd1c82ce948e3358eaecd52a05599041d7ecad117 new_market 6,598 638,664 46-46 83bd438e59d1180befbc909fe5b8832faeba3e03628131642872d3f1a987778d price_change 91,608,262 921,181,698 47-396 a6b17b790cd722e169c66dbc13f49773b516732b5ad3417e166bd82308494172 tick_size_change 3,404 125,982 397-397 d4a46ac06f0568aff46ed5ba9e3db113188b49c3af7d499ab16afe7bb95f1a92 EVENT MIX count share price_change 91,608,262 88.99% best_bid_ask 10,342,108 10.05% book 916,641 0.89% last_trade_price 69,440 0.07% new_market 6,598 <0.01% tick_size_change 3,404 <0.01% market_resolved 1,507 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,342,280 10,342,108 172 1,643 FULL book 916,690 916,641 49 182,240 FULL last_trade_price 69,443 69,440 3 147 FULL market_resolved 1,507 1,507 0 3 FULL new_market 6,598 6,598 0 0 FULL price_change 91,610,726 91,608,262 2,464 1,031 FULL tick_size_change 3,404 3,404 0 34 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,503,335 8,826,359 5ms 20ms 301ms 32.5s 0 transport_latency_assumed best_bid_ask e 10,331,207 102,409 41ms 65ms 389ms 19.4s 0 transport_latency_assumed best_bid_ask f 10,328,472 51,187 47ms 76ms 418ms 30.8s 0 transport_latency_assumed best_bid_ask g 10,316,177 4,178 86ms 184ms 913ms 35.3s 0 transport_latency_assumed best_bid_ask h 10,335,638 1,357,975 19ms 36ms 718ms 54.3s 0 transport_latency_assumed book c 886,457 869,174 10.5min 22.1h 28.1d 101.8d 0 book_staleness book e 149,436 5,890 44ms 778ms 5.5min 83.2d 0 book_staleness book f 149,903 4,891 50ms 971ms 1.3h 83.3d 0 book_staleness book g 163,687 13,438 101ms 59.6s 1.1d 101.8d 0 book_staleness book h 151,925 23,248 24ms 258ms 30.2min 37.3d 0 book_staleness last_trade_price c 63,858 59,120 10ms 61ms 406ms 5.0s 0 transport_latency_assumed last_trade_price e 68,206 556 50ms 346ms 6.6s 19.4s 0 transport_latency_assumed last_trade_price f 67,966 330 56ms 385ms 5.8s 30.4s 0 transport_latency_assumed last_trade_price g 66,407 43 104ms 761ms 14.5s 35.2s 0 transport_latency_assumed last_trade_price h 69,052 9,391 25ms 106ms 1.0s 40.1s 0 transport_latency_assumed market_resolved c 1,401 1,313 6ms 4.6min 10.2min 10.9min 0 transport_latency_assumed market_resolved e 1,296 35 47ms 375ms 52.2s 54.5s 0 transport_latency_assumed market_resolved f 1,296 18 55ms 372ms 52.0s 54.5s 0 transport_latency_assumed market_resolved g 1,296 1 100ms 600ms 1.4s 3.4s 0 transport_latency_assumed market_resolved h 1,296 140 22ms 157ms 59.7s 59.7s 0 transport_latency_assumed new_market c 4,045 2,322 128ms 20.5s 1.7min 9.7min 0 transport_latency_assumed new_market e 4,031 1,047 206ms 22.1s 1.6min 2.7min 0 transport_latency_assumed new_market f 4,031 763 232ms 18.4s 1.6min 3.9min 0 transport_latency_assumed new_market g 4,031 554 336ms 22.1s 1.5min 2.7min 0 transport_latency_assumed new_market h 4,031 1,912 149ms 20.6s 1.6min 3.3min 0 transport_latency_assumed price_change c 84,018,860 77,946,204 5ms 23ms 308ms 32.5s 0 transport_latency_assumed price_change e 91,403,615 856,313 41ms 89ms 671ms 19.4s 0 transport_latency_assumed price_change f 91,312,727 438,150 47ms 101ms 720ms 30.8s 0 transport_latency_assumed price_change g 90,995,223 33,798 86ms 239ms 2.1s 35.3s 0 transport_latency_assumed price_change h 91,529,466 12,333,797 19ms 42ms 691ms 54.6s 0 transport_latency_assumed tick_size_change c 3,268 3,008 5ms 26ms 524ms 658ms 0 transport_latency_assumed tick_size_change e 3,404 18 41ms 62ms 427ms 598ms 0 transport_latency_assumed tick_size_change f 3,404 20 47ms 77ms 473ms 670ms 0 transport_latency_assumed tick_size_change g 3,404 2 85ms 216ms 880ms 13.0s 0 transport_latency_assumed tick_size_change h 3,404 356 19ms 38ms 469ms 4.4s 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-08/18/2026-09-08T18.parquet sha256sum 2026-09-08T18.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.