Hour audit: 2026-09-15T04
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-15T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T04:00:00.000009339+00:00 · last event 2026-09-15T04:59:59.999445368+00:00
VOLUME 97,604,681 rows · 988,850,151 bytes (943.04 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 97,433,550 · h: 97,411,800 · e: 97,249,847 · f: 97,244,695 · g: 97,144,026 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 93,055,091 (95.34%) · h: 3,719,596 (3.81%) · e: 511,304 (0.52%) · f: 265,327 (0.27%) · g: 53,363 (0.05%) (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 97,604,681 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0c37d37f39f5a505b18544290b06dbf34ecb3cd36c977f17f805a0c35f214be7
the corpus checksum ledger names this file with the same digest
joined 97,608,617 to merged 97,604,681, minus 3,936 (minus 0.0040%)
boundary drops 3,936 · 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-15T05:55:39Z 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 an incident recorded by the venue intersects this hour: Scheduled CLOB maintenance, no downtime expected, 2026-09-15T04:00Z to 2026-09-15T04:30ZThe 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 11,656,810 128,197,238 0-44 fb82dee547f28dfa2912640055db04124cd0475b866758276812b404799e35f9 book 352,135 35,827,198 45-46 4ad2df28e8aeb3b445c3b5b1a6cafaebe6bef7cda5f642a635e5fdb26c0442aa last_trade_price 45,680 2,603,497 47-47 8e544644227f3c7c7fd1b978a6695d785959b332717efbc93137e1c8e8063589 market_resolved 1,264 205,735 48-48 96780d0db0d81de761fc54fc66febf7054830814742bcac3517ccf8ebaf72b3a new_market 3,658 353,148 49-49 254b13ae98a53777fe862feb4b033f7d5d61409a40c1a68607d2a2ab1461809d price_change 85,542,406 820,448,847 50-376 0d5071736cba87ce51b8b626577d421f0139152d8ca112d254944cbc028c01a1 tick_size_change 2,728 99,905 377-377 01c0e6502a51fb9f22136dca19c11f636326a6c63365bf9156cf2143d9cdfdff EVENT MIX count share price_change 85,542,406 87.64% best_bid_ask 11,656,810 11.94% book 352,135 0.36% last_trade_price 45,680 0.05% new_market 3,658 <0.01% tick_size_change 2,728 <0.01% market_resolved 1,264 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,657,053 11,656,810 243 166 FULL book 352,253 352,135 118 97,272 FULL last_trade_price 45,681 45,680 1 0 FULL market_resolved 1,264 1,264 0 0 FULL new_market 3,658 3,658 0 0 FULL price_change 85,545,980 85,542,406 3,574 52 FULL tick_size_change 2,728 2,728 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,655,579 11,173,633 4ms 9ms 189ms 7.8s 0 transport_latency_assumed best_bid_ask e 11,651,368 58,545 43ms 51ms 279ms 14.6s 0 transport_latency_assumed best_bid_ask f 11,654,191 29,526 49ms 58ms 288ms 15.4s 0 transport_latency_assumed best_bid_ask g 11,652,348 3,071 81ms 115ms 630ms 29.2s 0 transport_latency_assumed best_bid_ask h 11,654,228 392,035 17ms 24ms 353ms 23.6s 0 transport_latency_assumed book c 204,956 185,653 4.0s 7.2h 23.6d 108.3d 0 book_staleness book e 110,772 11,269 46ms 16.8s 3.5d 89.8d 0 book_staleness book f 106,604 8,292 51ms 2.8s 2.0d 108.3d 0 book_staleness book g 128,058 26,076 98ms 23.8min 9.6d 90.2d 0 book_staleness book h 221,504 120,845 14.4s 8.7h 23.6d 108.3d 0 book_staleness last_trade_price c 45,506 42,804 10ms 51ms 299ms 4.8s 0 transport_latency_assumed last_trade_price e 45,438 341 51ms 171ms 7.4s 14.6s 0 transport_latency_assumed last_trade_price f 45,333 218 57ms 166ms 2.3s 15.4s 0 transport_latency_assumed last_trade_price g 45,179 36 97ms 343ms 8.5s 29.3s 0 transport_latency_assumed last_trade_price h 45,431 2,281 23ms 82ms 498ms 7.5s 0 transport_latency_assumed market_resolved c 1,261 1,216 4ms 9ms 223ms 567ms 0 transport_latency_assumed market_resolved e 1,261 11 52ms 126ms 401ms 46.7s 0 transport_latency_assumed market_resolved f 1,261 1 63ms 141ms 396ms 953ms 0 transport_latency_assumed market_resolved g 1,261 not meas. 119ms 270ms 820ms 1.4s 0 transport_latency_assumed market_resolved h 1,261 36 29ms 61ms 516ms 57.5s 0 transport_latency_assumed new_market c 2,270 1,386 116ms 37.7s 1.8min 2.0min 0 transport_latency_assumed new_market e 2,270 310 213ms 32.4s 1.3min 1.9min 0 transport_latency_assumed new_market f 2,270 680 201ms 39.2s 1.6min 4.5min 0 transport_latency_assumed new_market g 2,270 264 352ms 43.8s 1.8min 2.0min 0 transport_latency_assumed new_market h 2,270 1,018 169ms 42.4s 1.6min 6.2min 0 transport_latency_assumed price_change c 85,521,250 81,647,714 5ms 11ms 208ms 8.8s 0 transport_latency_assumed price_change e 85,436,010 440,828 44ms 62ms 513ms 14.8s 0 transport_latency_assumed price_change f 85,432,308 226,610 49ms 68ms 463ms 15.4s 0 transport_latency_assumed price_change g 85,312,182 23,916 83ms 141ms 1.0s 29.2s 0 transport_latency_assumed price_change h 85,484,378 3,203,338 17ms 29ms 389ms 26.3s 0 transport_latency_assumed tick_size_change c 2,728 2,685 4ms 6ms 45ms 85ms 0 transport_latency_assumed tick_size_change e 2,728 not meas. 42ms 46ms 95ms 214ms 0 transport_latency_assumed tick_size_change f 2,728 not meas. 48ms 53ms 117ms 313ms 0 transport_latency_assumed tick_size_change g 2,728 not meas. 81ms 96ms 267ms 749ms 0 transport_latency_assumed tick_size_change h 2,728 43 17ms 20ms 75ms 2.2s 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-15/04/2026-09-15T04.parquet sha256sum 2026-09-15T04.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.