Hour audit: 2026-09-19T06
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-19T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T06:00:00.000014885+00:00 · last event 2026-09-19T06:59:59.999688241+00:00
VOLUME 100,696,034 rows · 1,005,424,698 bytes (958.85 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 100,615,635 · e: 100,571,893 · f: 100,541,502 · g: 100,504,827 · h: 100,476,304 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 97,178,325 (96.51%) · e: 227,893 (0.23%) · f: 162,989 (0.16%) · g: 33,326 (0.03%) · h: 3,093,501 (3.07%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,696,034 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4f3475c8e7cd6399bbeda5d8d2df0787fe194f018a71120a739232682ea690dd
the corpus checksum ledger names this file with the same digest
joined 100,698,904 to merged 100,696,034, minus 2,870 (minus 0.0029%)
boundary drops 2,870 · 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-19T07:56:58Z 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,831,688 122,114,591 0-41 36747a9502e11e5ea88bfe01e5bb762dcf7cb728cac22272e3ad57ed7ecfb56e book 131,490 13,268,190 42-42 a12a5cdc9db8d60a89acca4fa40c8b4797e19c8088be692bbc534d30fe2f8a6d last_trade_price 46,537 2,730,393 43-43 283af04e067008ebfb7fe0feb0a42786a79f284b247d4380e6b554432a06b10a market_resolved 744 121,731 44-44 42832705e99e23e21d4fa6e5f083e0b19ecb367832cb109b1708ff3ddbc84807 new_market 933 96,981 45-45 a63addc14110d751ebdf36f7ff90a3df32e6fb82118e1b8d33c3d7503c532504 price_change 89,682,566 865,865,052 46-388 3761583b75999b6842a2ccc9a2699a0e96330e6464ba34cda62a39e3426d2258 tick_size_change 2,076 77,452 389-389 1f41219304f9eed24819244edd5ac1c39e2ba30c67ee525ed77a61f8087e2902 EVENT MIX count share price_change 89,682,566 89.06% best_bid_ask 10,831,688 10.76% book 131,490 0.13% last_trade_price 46,537 0.05% tick_size_change 2,076 <0.01% new_market 933 <0.01% market_resolved 744 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,831,966 10,831,688 278 104 FULL book 131,492 131,490 2 11,008 FULL last_trade_price 46,537 46,537 0 0 FULL market_resolved 744 744 0 0 FULL new_market 933 933 0 0 FULL price_change 89,685,156 89,682,566 2,590 129 FULL tick_size_change 2,076 2,076 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,830,876 10,502,520 4ms 8ms 72ms 4.9s 0 transport_latency_assumed best_bid_ask e 10,829,842 19,379 45ms 49ms 148ms 5.8s 0 transport_latency_assumed best_bid_ask f 10,829,576 11,419 47ms 53ms 154ms 4.9s 0 transport_latency_assumed best_bid_ask g 10,828,908 1,464 77ms 91ms 259ms 15.0s 0 transport_latency_assumed best_bid_ask h 10,825,151 296,906 18ms 22ms 110ms 8.2s 0 transport_latency_assumed book c 102,216 95,937 6ms 57ms 14.6h 93.8d 0 book_staleness book e 101,935 5,202 47ms 220ms 14.5h 112.3d 0 book_staleness book f 103,199 6,228 49ms 227ms 14.7h 112.3d 0 book_staleness book g 110,838 12,617 82ms 1.4min 1.8d 93.8d 0 book_staleness book h 102,516 11,506 21ms 125ms 14.7h 112.4d 0 book_staleness last_trade_price c 46,339 43,993 9ms 46ms 268ms 5.0s 0 transport_latency_assumed last_trade_price e 46,354 184 52ms 137ms 622ms 5.7s 0 transport_latency_assumed last_trade_price f 46,337 192 54ms 127ms 545ms 5.0s 0 transport_latency_assumed last_trade_price g 46,341 51 87ms 214ms 3.0s 13.4s 0 transport_latency_assumed last_trade_price h 45,881 2,117 23ms 69ms 334ms 5.3s 0 transport_latency_assumed market_resolved c 737 720 4ms 8ms 74ms 1.0min 0 transport_latency_assumed market_resolved e 737 8 47ms 197ms 633ms 56.4s 0 transport_latency_assumed market_resolved f 737 not meas. 50ms 197ms 615ms 59.3s 0 transport_latency_assumed market_resolved g 737 4 86ms 251ms 511ms 808ms 0 transport_latency_assumed market_resolved h 737 12 18ms 65ms 2.4s 56.8s 0 transport_latency_assumed new_market c 635 438 73ms 34.5s 1.7min 2.1min 0 transport_latency_assumed new_market e 635 64 157ms 53.0s 1.6min 1.9min 0 transport_latency_assumed new_market f 635 113 176ms 53.3s 1.7min 1.9min 0 transport_latency_assumed new_market g 635 32 262ms 47.7s 1.6min 1.9min 0 transport_latency_assumed new_market h 635 286 112ms 22.6s 1.8min 2.6min 0 transport_latency_assumed price_change c 89,632,756 86,532,725 4ms 9ms 92ms 6.0s 0 transport_latency_assumed price_change e 89,590,314 203,056 45ms 54ms 251ms 7.1s 0 transport_latency_assumed price_change f 89,558,942 145,032 48ms 58ms 242ms 5.5s 0 transport_latency_assumed price_change g 89,515,292 19,158 78ms 95ms 404ms 15.4s 0 transport_latency_assumed price_change h 89,499,308 2,782,595 18ms 25ms 157ms 8.2s 0 transport_latency_assumed tick_size_change c 2,076 1,992 5ms 12ms 65ms 182ms 0 transport_latency_assumed tick_size_change e 2,076 not meas. 45ms 53ms 120ms 582ms 0 transport_latency_assumed tick_size_change f 2,076 5 48ms 58ms 187ms 288ms 0 transport_latency_assumed tick_size_change g 2,076 not meas. 78ms 103ms 250ms 312ms 0 transport_latency_assumed tick_size_change h 2,076 79 18ms 36ms 201ms 233ms 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-19/06/2026-09-19T06.parquet sha256sum 2026-09-19T06.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.