Hour audit: 2026-09-18T22
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-18T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T22:00:00.000000245+00:00 · last event 2026-09-18T22:59:59.999808056+00:00
VOLUME 103,672,709 rows · 1,096,610,341 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 103,045,603 · h: 102,995,604 · f: 102,944,044 · e: 102,878,775 · g: 102,558,277 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 97,379,256 (93.93%) · h: 4,468,309 (4.31%) · f: 605,658 (0.58%) · e: 957,764 (0.92%) · g: 261,722 (0.25%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 f24c8fb057634c0964937cf2f206236254fd8ba49ff5485181c5af5d2e66b30c
the corpus checksum ledger names this file with the same digest
joined 103,683,427 to merged 103,672,709, minus 10,718 (minus 0.0103%)
boundary drops 10,718 · 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-19T02:15:16Z 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 12,507,614 138,206,570 0-47 cbe31c639817e486981061c0eddac027dc44d2df721e5566f11e69fe4ee3d819 book 891,940 68,222,562 48-51 40bb13171a24ff1b7707d6e019787190d26dca5d126228ca79a5cccdcd46d500 last_trade_price 53,288 3,058,798 52-52 1bf7e6fb7f0e06471f75322db40581787b34667feecd1b62064c75d70a0cd0b5 market_resolved 2,474 405,036 53-53 9b20a27ce4afdc456dade2b8bc8d248edab0afcd1f5dd2236007100698f264e9 new_market 2,367 248,996 54-54 258850cc4d2ae49235e4b9f2c92bc0f6eec35d83dbd9f19355e43bdfb0e6998a price_change 90,211,986 885,174,722 55-399 7811db05c5c9b1fa655010c1c164193c18006c0a870fa9d0ced7cf058cd927cb tick_size_change 3,040 111,479 400-400 59940e2a3f17b00ee8c7a5c56c88249b916e57363e52314820e9a1541bdf15bd EVENT MIX count share price_change 90,211,986 87.02% best_bid_ask 12,507,614 12.06% book 891,940 0.86% last_trade_price 53,288 0.05% tick_size_change 3,040 <0.01% market_resolved 2,474 <0.01% new_market 2,367 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,507,898 12,507,614 284 329 FULL book 899,311 891,940 7,371 195,452 FULL last_trade_price 53,289 53,288 1 2 FULL market_resolved 2,478 2,474 4 6 FULL new_market 2,367 2,367 0 0 FULL price_change 90,215,044 90,211,986 3,058 173 FULL tick_size_change 3,040 3,040 0 21 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,504,850 11,848,421 5ms 13ms 232ms 6.8s 0 transport_latency_assumed best_bid_ask e 12,498,912 88,466 41ms 52ms 340ms 26.6s 0 transport_latency_assumed best_bid_ask f 12,499,421 47,871 46ms 60ms 370ms 21.7s 0 transport_latency_assumed best_bid_ask g 12,492,503 7,128 78ms 104ms 918ms 43.1s 0 transport_latency_assumed best_bid_ask h 12,503,060 515,728 18ms 29ms 381ms 1.2min 0 transport_latency_assumed book c 317,292 223,791 2.0min 6.7h 27.3d 112.0d 0 book_staleness book e 392,108 171,105 4.2min 6.7h 27.4d 112.0d 0 book_staleness book f 400,806 178,197 4.2min 6.7h 27.4d 112.0d 0 book_staleness book g 428,969 181,344 5.6min 6.8h 27.4d 112.0d 0 book_staleness book h 333,465 137,503 2.3min 6.7h 27.4d 112.0d 0 book_staleness last_trade_price c 53,077 50,012 10ms 58ms 392ms 5.0s 0 transport_latency_assumed last_trade_price e 52,510 556 57ms 621ms 6.3s 26.7s 0 transport_latency_assumed last_trade_price f 52,844 429 62ms 691ms 6.6s 20.5s 0 transport_latency_assumed last_trade_price g 50,812 130 96ms 1.1s 12.4s 43.2s 0 transport_latency_assumed last_trade_price h 52,949 2,161 25ms 211ms 1.6s 53.9s 0 transport_latency_assumed market_resolved c 2,467 2,318 5ms 30ms 493ms 1.3s 0 transport_latency_assumed market_resolved e 2,470 20 112ms 289ms 823ms 1.0min 0 transport_latency_assumed market_resolved f 2,470 16 116ms 293ms 810ms 1.4s 0 transport_latency_assumed market_resolved g 2,470 1 198ms 506ms 1.5s 6.9s 0 transport_latency_assumed market_resolved h 2,467 119 36ms 112ms 717ms 1.0min 0 transport_latency_assumed new_market c 1,595 891 124ms 27.6s 78.2d 78.2d 0 transport_latency_assumed new_market e 1,595 478 181ms 24.6s 78.2d 78.2d 0 transport_latency_assumed new_market f 1,595 197 287ms 23.9s 78.2d 78.2d 0 transport_latency_assumed new_market g 1,595 222 284ms 24.4s 78.1d 78.1d 0 transport_latency_assumed new_market h 1,595 579 169ms 22.1s 78.2d 78.2d 0 transport_latency_assumed price_change c 90,163,282 85,250,978 5ms 16ms 265ms 9.6s 0 transport_latency_assumed price_change e 89,928,224 697,128 41ms 72ms 1.8s 26.7s 0 transport_latency_assumed price_change f 89,983,868 378,940 47ms 82ms 2.2s 21.8s 0 transport_latency_assumed price_change g 89,578,888 72,896 79ms 152ms 4.7s 43.6s 0 transport_latency_assumed price_change h 90,099,112 3,812,044 18ms 39ms 549ms 1.2min 0 transport_latency_assumed tick_size_change c 3,040 2,845 5ms 16ms 289ms 1.3s 0 transport_latency_assumed tick_size_change e 2,956 11 41ms 52ms 389ms 671ms 0 transport_latency_assumed tick_size_change f 3,040 8 47ms 60ms 317ms 677ms 0 transport_latency_assumed tick_size_change g 3,040 1 78ms 108ms 742ms 1.4s 0 transport_latency_assumed tick_size_change h 2,956 175 18ms 32ms 405ms 1.1s 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-18/22/2026-09-18T22.parquet sha256sum 2026-09-18T22.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.