Hour audit: 2026-09-01T12
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.
1 finding
- a machine expected this hour contributed nothing. Of the 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T12 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T12:00:00.018169349+00:00 · last event 2026-09-01T12:59:59.999925947+00:00
VOLUME 83,330,107 rows · 854,705,489 bytes (815.11 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 83,048,403 · c: 83,023,876 · e: 82,134,636 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,066,745 (1.28%) · c: 130,104 (0.16%) · e: 82,133,258 (98.56%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 83,330,107 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 d1978b7e733201f091198518b8a73b2f154e7c0d347ebbb6cd851a18e171cad4
the corpus checksum ledger names this file with the same digest
joined 83,332,895 to merged 83,330,107, minus 2,788 (minus 0.0033%)
boundary drops 2,788 · 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-01T16:56:28Z as ceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 5,239,994 63,359,152 0-19 c5bd53cc64bd1d99c5d6f50ac709ae4ec5fc3d2dd53df042d10614416d215907 book 598,724 54,167,118 20-22 9b3d4f82c1333d3d5af731122b739ef4bc9d61e859cbbf4be233d2d47e59cb46 last_trade_price 66,543 3,657,582 23-23 3d6a6e776eaff20652b8d2cfa9c0715312046c109e969a7d0f35cbaa31d7508d market_resolved 1,031 164,834 24-24 90967e0213dc019eb1c097506989dc65561661e449003a6492deb540d0b3d52c new_market 821 93,547 25-25 08a997978d4d17ec3e4fb2022aa7e44d570321631f8bfe042f1cf5ec832b61e6 price_change 77,420,090 732,204,673 26-321 1073fd8c9f89c2f19f8f9bab611ec6665a6182587a4d83bedbb00f2fedcb2d8d tick_size_change 2,904 106,694 322-322 0e50a0819c7cac4034851088b0144cecdcdd0054fd825b8bac42fea0bc4a48cb EVENT MIX count share price_change 77,420,090 92.91% best_bid_ask 5,239,994 6.29% book 598,724 0.72% last_trade_price 66,543 0.08% tick_size_change 2,904 <0.01% market_resolved 1,031 <0.01% new_market 821 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,240,030 5,239,994 36 67,364 PARTIAL book 600,688 598,724 1,964 151,191 PARTIAL last_trade_price 66,543 66,543 0 3,337 PARTIAL market_resolved 1,031 1,031 0 1,021 PARTIAL new_market 821 821 0 620 PARTIAL price_change 77,420,878 77,420,090 788 126,605 PARTIAL tick_size_change 2,904 2,904 0 726 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,239,314 810 4ms 8ms 93ms 8.9s 0 transport_latency_assumed best_bid_ask e 5,205,400 5,205,364 43ms 123ms 3.9s 22.9s 0 transport_latency_assumed best_bid_ask h 5,238,100 33,820 18ms 29ms 301ms 17.2s 0 transport_latency_assumed book c 308,600 121,043 10.8s 3.6h 23.9d 94.6d 0 book_staleness book e 285,193 284,639 13.8s 3.7h 30.0d 94.6d 0 book_staleness book h 352,258 193,042 27.8s 4.2h 24.0d 94.6d 0 book_staleness last_trade_price c 66,489 62 10ms 44ms 250ms 5.0s 0 transport_latency_assumed last_trade_price e 61,060 61,060 91ms 5.9s 14.8s 22.7s 0 transport_latency_assumed last_trade_price h 66,396 5,421 29ms 460ms 2.2s 6.5s 0 transport_latency_assumed market_resolved c 1,021 not meas. 4ms 12ms 49.7s 51.0s 0 transport_latency_assumed market_resolved e 1,021 1,021 43ms 438ms 47.0s 59.8s 0 transport_latency_assumed market_resolved h 1,021 10 19ms 109ms 51.8s 53.6s 0 transport_latency_assumed new_market c 620 57 63ms 15.6s 25.0s 1.4min 0 transport_latency_assumed new_market e 620 620 238ms 17.6s 24.4s 1.6min 0 transport_latency_assumed new_market h 620 144 125ms 597ms 22.2s 1.7min 0 transport_latency_assumed price_change c 77,404,928 8,132 4ms 8ms 118ms 9.8s 0 transport_latency_assumed price_change e 76,578,446 76,577,658 43ms 156ms 6.4s 22.9s 0 transport_latency_assumed price_change h 77,387,104 834,300 19ms 34ms 437ms 29.7s 0 transport_latency_assumed tick_size_change c 2,904 not meas. 4ms 7ms 41ms 275ms 0 transport_latency_assumed tick_size_change e 2,896 2,896 43ms 119ms 569ms 2.8s 0 transport_latency_assumed tick_size_change h 2,904 8 19ms 33ms 165ms 5.6s 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-01/12/2026-09-01T12.parquet sha256sum 2026-09-01T12.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.