Hour audit: 2026-09-13T05
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-13T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T05:00:00.000652925+00:00 · last event 2026-09-13T05:59:59.999885221+00:00
VOLUME 104,919,787 rows · 1,064,515,829 bytes (1015.20 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 104,481,143 · f: 104,466,773 · e: 104,458,899 · g: 104,452,118 · c: 100,455,262 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,683,183 (6.37%) · f: 108,689 (0.10%) · e: 351,415 (0.33%) · g: 24,715 (0.02%) · c: 97,751,785 (93.17%) (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 104,919,787 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a064a33b048b4acea02283d853ba934a610ea49134273162a069c85af712fdb0
the corpus checksum ledger names this file with the same digest
joined 104,923,499 to merged 104,919,787, minus 3,712 (minus 0.0035%)
boundary drops 3,712 · 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-13T07:00:07Z 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,778,918 114,946,221 0-41 5a0cdc3ceb7a7743d6db76df31953e763fa7f8bd5c8964ea0c1a93d946536bab book 551,488 53,537,470 42-44 d95c7bb23858b7168dfee49f359c75004845304cca2b4190038023165373c510 last_trade_price 41,387 2,438,861 45-45 211cf2916efc9b9794c081c08c9f635a28dd8f5389b2101cdcc6b4e4145fbad5 market_resolved 1,353 205,178 46-46 15d41f02f00b4a9be1352b95c1ada581d16139bbd099539fd8534a226e48a80c new_market 1,109 114,702 47-47 52cf1c2df966b80be27327ef2aeb995611cd22c4bb2704c9d7b8006f412b8b51 price_change 93,542,816 891,976,957 48-404 d0b23f71810c3aa82ea831c88aab00d25a8971131fb2973acc47f50544e245fc tick_size_change 2,716 98,891 405-405 354fd48283dc236a142e90cc5c5730ae210a8c5eab36bb445063b6b7e0e0eb89 EVENT MIX count share price_change 93,542,816 89.16% best_bid_ask 10,778,918 10.27% book 551,488 0.53% last_trade_price 41,387 0.04% tick_size_change 2,716 <0.01% market_resolved 1,353 <0.01% new_market 1,109 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,779,157 10,778,918 239 607 FULL book 552,854 551,488 1,366 175,761 FULL last_trade_price 41,388 41,387 1 97 FULL market_resolved 1,353 1,353 0 3 FULL new_market 1,109 1,109 0 0 FULL price_change 93,544,922 93,542,816 2,106 506 FULL tick_size_change 2,716 2,716 0 28 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,333,825 10,066,526 4ms 8ms 64ms 4.0s 0 transport_latency_assumed best_bid_ask e 10,777,462 33,163 42ms 45ms 91ms 1.9s 0 transport_latency_assumed best_bid_ask f 10,777,637 9,806 47ms 50ms 105ms 3.4s 0 transport_latency_assumed best_bid_ask g 10,775,797 788 77ms 90ms 222ms 4.3s 0 transport_latency_assumed best_bid_ask h 10,778,130 668,635 18ms 20ms 67ms 15.0s 0 transport_latency_assumed book c 493,059 485,618 6.9min 1.5d 32.4d 106.3d 0 book_staleness book e 133,737 18,787 45ms 5.6h 21.5d 87.8d 0 book_staleness book f 114,713 10,755 50ms 1.8h 7.6d 106.3d 0 book_staleness book g 129,426 17,741 90ms 5.2h 13.6d 106.3d 0 book_staleness book h 121,133 18,587 22ms 2.6h 7.6d 106.3d 0 book_staleness last_trade_price c 39,966 38,592 9ms 35ms 152ms 4.9s 0 transport_latency_assumed last_trade_price e 41,303 221 47ms 94ms 249ms 5.0s 0 transport_latency_assumed last_trade_price f 41,320 66 53ms 100ms 310ms 5.0s 0 transport_latency_assumed last_trade_price g 41,346 11 88ms 189ms 909ms 5.0s 0 transport_latency_assumed last_trade_price h 41,357 2,497 22ms 50ms 188ms 7.3s 0 transport_latency_assumed market_resolved c 1,273 1,247 4ms 9ms 4.4min 4.7min 0 transport_latency_assumed market_resolved e 1,276 51 45ms 179ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,276 1 49ms 156ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,276 not meas. 89ms 249ms 58.0s 1.0min 0 transport_latency_assumed market_resolved h 1,276 54 20ms 57ms 149ms 6.5s 0 transport_latency_assumed new_market c 729 408 73ms 17.2s 17.1min 4.6h 0 transport_latency_assumed new_market e 727 147 124ms 17.0s 41.7s 50.5s 0 transport_latency_assumed new_market f 727 163 102ms 18.3s 37.6s 3.3h 0 transport_latency_assumed new_market g 727 85 183ms 20.2s 39.6s 2.8h 0 transport_latency_assumed new_market h 727 306 92ms 19.9s 45.9s 5.0h 0 transport_latency_assumed price_change c 89,583,806 87,156,866 4ms 8ms 72ms 4.5s 0 transport_latency_assumed price_change e 93,501,678 299,046 42ms 46ms 118ms 2.7s 0 transport_latency_assumed price_change f 93,528,384 87,898 47ms 51ms 127ms 3.8s 0 transport_latency_assumed price_change g 93,500,830 6,090 77ms 91ms 271ms 4.6s 0 transport_latency_assumed price_change h 93,535,804 5,992,916 18ms 21ms 77ms 18.4s 0 transport_latency_assumed tick_size_change c 2,604 2,528 4ms 9ms 37ms 89ms 0 transport_latency_assumed tick_size_change e 2,716 not meas. 41ms 44ms 71ms 128ms 0 transport_latency_assumed tick_size_change f 2,716 not meas. 46ms 49ms 73ms 158ms 0 transport_latency_assumed tick_size_change g 2,716 not meas. 77ms 90ms 114ms 220ms 0 transport_latency_assumed tick_size_change h 2,716 188 18ms 20ms 36ms 50ms 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-13/05/2026-09-13T05.parquet sha256sum 2026-09-13T05.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.