Hour audit: 2026-09-12T17
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-12T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T17:00:00.000040495+00:00 · last event 2026-09-12T17:59:59.999843651+00:00
VOLUME 131,405,640 rows · 1,445,634,368 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 126,320,313 · h: 126,318,658 · g: 126,315,857 · f: 120,701,351 · c: 60,850,188 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,689,067 (2.05%) · h: 69,507,561 (52.90%) · g: 66,404 (0.05%) · f: 599,786 (0.46%) · c: 58,542,822 (44.55%) (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 131,405,640 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3805eee0eb6b644a3091ce9bcfb43a9598674e5cf93018433bf5337e3d466bd4
the corpus checksum ledger names this file with the same digest
joined 131,422,444 to merged 131,405,640, minus 16,804 (minus 0.0128%)
boundary drops 16,804 · 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-12T19:06: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 13,189,117 148,758,950 0-50 94f4f59459654f56c33541fdfb7da8c6e64c3a03fadff56fe1fa6c9a92992c49 book 5,119,462 137,157,756 51-70 b8f47643e59d5fa5be1381c463164d7cbd1e0023ab1f476980d8f72d5144d7cb last_trade_price 57,406 3,368,355 71-71 4fd5a83680a5779ea2b89a84c824d7d881f888c413453885b9b283cea451f1e2 market_resolved 39,326 1,280,576 72-72 8e77c5f601c693d97745483ac13f299b1cf1f5880fb234b4cc0ed19c098b7c4b new_market 29,963 599,412 73-73 4c0fdd1f19c167af2d73f2d6d4d6b2ef3c397eb4dd36e41a767492ef5adc1042 price_change 112,961,490 1,152,650,467 74-504 00744c9dc0bd169132dd904ef25bd76e7bc3caecb01633f0b58ff1fadf3d3dd7 tick_size_change 8,876 324,535 505-505 1bbf624c683476c4b28c7c8c8d6a855b1f5711627fe52949f74b6ea5a1d6d8aa EVENT MIX count share price_change 112,961,490 85.96% best_bid_ask 13,189,117 10.04% book 5,119,462 3.90% last_trade_price 57,406 0.04% market_resolved 39,326 0.03% new_market 29,963 0.02% tick_size_change 8,876 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,189,370 13,189,117 253 15,127 FULL book 5,133,339 5,119,462 13,877 199,670 FULL last_trade_price 57,407 57,406 1 1,666 FULL market_resolved 39,347 39,326 21 5,087 FULL new_market 29,995 29,963 32 2,088 FULL price_change 112,964,110 112,961,490 2,620 11,888 FULL tick_size_change 8,876 8,876 0 1,224 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,964,072 5,731,081 6ms 12ms 137ms 14.1s 0 transport_latency_assumed best_bid_ask e 13,187,118 264,350 40ms 46ms 170ms 4.1s 0 transport_latency_assumed best_bid_ask f 12,548,355 47,617 47ms 55ms 206ms 4.1s 0 transport_latency_assumed best_bid_ask g 13,185,220 4,966 77ms 93ms 357ms 21.7s 0 transport_latency_assumed best_bid_ask h 13,188,171 7,141,103 18ms 27ms 166ms 44.1s 0 transport_latency_assumed book c 4,992,921 4,968,228 18.0min 23.8h 32.0d 105.8d 0 book_staleness book e 121,395 6,356 43ms 122ms 3.9s 87.3d 0 book_staleness book f 521,766 66,586 3.8min 19.4h 28.0d 105.8d 0 book_staleness book g 143,596 8,367 87ms 4.2min 3.4d 105.8d 0 book_staleness book h 121,003 69,925 23ms 62ms 2.4s 31.9d 0 book_staleness last_trade_price c 21,846 20,853 11ms 46ms 255ms 4.8s 0 transport_latency_assumed last_trade_price e 57,215 1,571 48ms 118ms 630ms 4.9s 0 transport_latency_assumed last_trade_price f 54,638 603 54ms 132ms 808ms 4.9s 0 transport_latency_assumed last_trade_price g 57,325 50 92ms 238ms 3.5s 21.3s 0 transport_latency_assumed last_trade_price h 57,351 34,329 25ms 70ms 389ms 9.7s 0 transport_latency_assumed market_resolved c 37,788 37,699 54.9min 1.8h 2.2h 2.3h 0 transport_latency_assumed market_resolved e 2,672 106 44ms 163ms 334ms 850ms 0 transport_latency_assumed market_resolved f 2,594 26 55ms 194ms 48.4s 5.5min 0 transport_latency_assumed market_resolved g 2,672 2 90ms 256ms 48.3s 1.0min 0 transport_latency_assumed market_resolved h 2,672 1,493 30ms 69ms 53.7s 1.0min 0 transport_latency_assumed new_market c 29,832 29,002 1.0h 1.7h 2.1h 2.3h 0 transport_latency_assumed new_market e 1,090 232 177ms 16.4s 44.9s 11.2min 0 transport_latency_assumed new_market f 1,089 168 202ms 24.1s 50.2s 33.3min 0 transport_latency_assumed new_market g 1,090 133 279ms 15.1s 43.4s 13.2min 0 transport_latency_assumed new_market h 1,090 428 157ms 23.0s 47.6s 35.2min 0 transport_latency_assumed price_change c 49,799,669 47,751,963 6ms 13ms 161ms 15.7s 0 transport_latency_assumed price_change e 112,941,947 2,416,344 41ms 49ms 226ms 4.9s 0 transport_latency_assumed price_change f 107,564,409 484,776 47ms 58ms 272ms 4.9s 0 transport_latency_assumed price_change g 112,917,078 52,886 77ms 98ms 475ms 22.1s 0 transport_latency_assumed price_change h 112,939,495 62,255,521 19ms 29ms 201ms 44.1s 0 transport_latency_assumed tick_size_change c 4,060 3,996 5ms 11ms 29ms 143ms 0 transport_latency_assumed tick_size_change e 8,876 108 40ms 44ms 83ms 514ms 0 transport_latency_assumed tick_size_change f 8,500 10 47ms 51ms 103ms 241ms 0 transport_latency_assumed tick_size_change g 8,876 not meas. 76ms 90ms 186ms 459ms 0 transport_latency_assumed tick_size_change h 8,876 4,762 18ms 23ms 50ms 747ms 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-12/17/2026-09-12T17.parquet sha256sum 2026-09-12T17.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.