Hour audit: 2026-09-18T05
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-18T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T05:00:00.000016088+00:00 · last event 2026-09-18T05:59:59.999998052+00:00
VOLUME 106,014,288 rows · 1,112,551,976 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 105,532,603 · c: 105,532,067 · g: 105,019,542 · e: 104,496,996 · f: 101,566,302 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,491,030 (5.18%) · c: 98,994,950 (93.38%) · g: 91,114 (0.09%) · e: 671,316 (0.63%) · f: 765,878 (0.72%) (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 106,014,288 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4a7e253b3631518c10855ec0a05f6d43c72aca30f293169cae11f2df0d975ef2
the corpus checksum ledger names this file with the same digest
joined 106,017,884 to merged 106,014,288, minus 3,596 (minus 0.0034%)
boundary drops 3,596 · 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-18T06:57:30Z 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,567,453 122,785,297 0-40 3a60f196f2e9845af2623395c447bab1088b032a56f67dd740891404a0725ab2 book 536,155 55,073,954 41-43 79800d4b228ba0d5d407137201dc00e94f51ab7f19bb0d22a9c811151c67a164 last_trade_price 54,435 3,069,682 44-44 6a0cac98a92c9ec86dda339da882aa1efe56c7cd3cea0404ba7d104bfd677c17 market_resolved 512 80,804 45-45 2c8b98c8ff189fa9d143a124fbd2fdb070c32308f260b48b49c8934838533bab new_market 5,583 562,140 46-46 59acced10f39b4bf4cb79d2c359adae1f1a3ece9e194279244057b075ff65846 price_change 94,847,710 929,679,602 47-408 45d9baedf6b52e674a7e7c75fe7e079f32dbfebc62149f75f1ef80e33a18a30c tick_size_change 2,440 91,210 409-409 4865c313a36ca9ab29e8810a6b7345ca448d2ebcb31281e74fe3d32af8a66151 EVENT MIX count share price_change 94,847,710 89.47% best_bid_ask 10,567,453 9.97% book 536,155 0.51% last_trade_price 54,435 0.05% new_market 5,583 <0.01% tick_size_change 2,440 <0.01% market_resolved 512 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,567,623 10,567,453 170 1,220 FULL book 536,181 536,155 26 184,937 FULL last_trade_price 54,438 54,435 3 81 FULL market_resolved 513 512 1 3 FULL new_market 5,583 5,583 0 0 FULL price_change 94,851,106 94,847,710 3,396 541 FULL tick_size_change 2,440 2,440 0 11 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,562,419 9,945,235 4ms 16ms 199ms 3.7s 0 transport_latency_assumed best_bid_ask e 10,519,173 65,134 41ms 65ms 420ms 29.4s 0 transport_latency_assumed best_bid_ask f 10,139,899 37,539 48ms 75ms 359ms 23.6s 0 transport_latency_assumed best_bid_ask g 10,552,297 6,491 81ms 137ms 669ms 44.9s 0 transport_latency_assumed best_bid_ask h 10,562,054 513,054 18ms 37ms 558ms 53.4s 0 transport_latency_assumed book c 128,379 114,345 7ms 507ms 3.9h 111.3d 0 book_staleness book e 135,074 23,125 46ms 2.2min 3.8h 92.8d 0 book_staleness book f 496,885 380,317 2.2min 4.6h 33.8d 111.3d 0 book_staleness book g 122,749 5,781 90ms 3.3s 2.2h 111.3d 0 book_staleness book h 122,166 12,587 21ms 219ms 4.1min 92.8d 0 book_staleness last_trade_price c 54,101 49,836 9ms 59ms 314ms 5.0s 0 transport_latency_assumed last_trade_price e 51,403 410 49ms 432ms 23.7s 29.5s 0 transport_latency_assumed last_trade_price f 51,369 262 59ms 431ms 8.4s 23.6s 0 transport_latency_assumed last_trade_price g 52,162 96 96ms 478ms 13.1s 45.0s 0 transport_latency_assumed last_trade_price h 54,346 3,831 23ms 105ms 708ms 9.8s 0 transport_latency_assumed market_resolved c 486 465 5ms 15ms 151ms 778ms 0 transport_latency_assumed market_resolved e 485 1 42ms 232ms 1.1s 1.6s 0 transport_latency_assumed market_resolved f 508 27 52ms 350ms 5.4min 5.4min 0 transport_latency_assumed market_resolved g 487 not meas. 88ms 381ms 1.1s 2.0s 0 transport_latency_assumed market_resolved h 486 19 19ms 79ms 406ms 1.2min 0 transport_latency_assumed new_market c 3,662 2,158 96ms 49.6s 3.5min 3.9min 0 transport_latency_assumed new_market e 3,662 856 176ms 37.9s 3.4min 4.1min 0 transport_latency_assumed new_market f 3,662 729 202ms 46.0s 3.6min 4.7min 0 transport_latency_assumed new_market g 3,662 377 273ms 37.9s 3.5min 4.1min 0 transport_latency_assumed new_market h 3,662 1,463 139ms 49.6s 3.5min 4.0min 0 transport_latency_assumed price_change c 94,780,580 88,880,712 5ms 20ms 230ms 5.9s 0 transport_latency_assumed price_change e 93,784,767 581,760 41ms 85ms 2.4s 29.4s 0 transport_latency_assumed price_change f 90,871,575 346,972 48ms 94ms 1.2s 23.7s 0 transport_latency_assumed price_change g 94,285,745 78,366 82ms 172ms 2.2s 45.0s 0 transport_latency_assumed price_change h 94,787,449 4,959,900 18ms 42ms 627ms 53.4s 0 transport_latency_assumed tick_size_change c 2,440 2,199 5ms 82ms 343ms 535ms 0 transport_latency_assumed tick_size_change e 2,432 30 41ms 207ms 5.4s 9.4s 0 transport_latency_assumed tick_size_change f 2,404 32 48ms 176ms 543ms 1.2s 0 transport_latency_assumed tick_size_change g 2,440 3 82ms 258ms 711ms 847ms 0 transport_latency_assumed tick_size_change h 2,440 176 18ms 108ms 1.1s 6.8s 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/05/2026-09-18T05.parquet sha256sum 2026-09-18T05.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.