Hour audit: 2026-10-05T18
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-10-05T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T18:00:00.001240279+00:00 · last event 2026-10-05T18:59:59.999814022+00:00
VOLUME 105,170,336 rows · 1,188,460,981 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 105,047,931 · m: 105,025,860 · h: 104,993,091 · i: 104,959,367 · n: 104,831,920 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 52,597,249 (50.01%) · m: 50,998,542 (48.49%) · h: 917,768 (0.87%) · i: 588,434 (0.56%) · n: 68,343 (0.06%) (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 105,170,336 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 377b99f353fd87201961a1966f0600cc2fd358dcc6c36de4a177dec30fa49919
the corpus checksum ledger names this file with the same digest
joined 105,171,323 to merged 105,170,336, minus 987 (minus 0.0009%)
boundary drops 987 · 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-10-05T19:58:59Z as himno
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 9,272,570 120,320,793 0-35 19ef7146437c8c7813f9cf37978b4d11e3c9a2b7e4db074ec5dd615a82a37444 book 145,285 16,451,854 36-36 96a7a2ce7d1daf17aa80cdbbe667d0d377eef49b743e9552601e9a389d3ed69b last_trade_price 60,003 3,467,946 37-37 2d39f343e2b72323c43ab4d0f633d834ceafa080145dca6bd8240214fed23e15 market_resolved 1,660 250,065 38-38 5aa7a003bdfcf127e0b5714470f88e9fb72c7afb9be37b829044a4dea4f676dc new_market 1,784 171,844 39-39 ee6027e699b6de96f8a2c4a723cf6c37353d3252d8786ad6fb33c140ced1b8ad price_change 95,684,902 1,046,442,103 40-405 0d232f729478d227307202ae07f67596f351f3e2eca20aed54fea0d0630834ac tick_size_change 4,132 153,668 406-406 84a8e091728e3b199b3677692f36f611e9c3e09186718a58e9f4f51039ba38c2 EVENT MIX count share price_change 95,684,902 90.98% best_bid_ask 9,272,570 8.82% book 145,285 0.14% last_trade_price 60,003 0.06% tick_size_change 4,132 <0.01% new_market 1,784 <0.01% market_resolved 1,660 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,272,678 9,272,570 108 84 FULL book 145,326 145,285 41 8,264 FULL last_trade_price 60,003 60,003 0 0 FULL market_resolved 1,660 1,660 0 0 FULL new_market 1,784 1,784 0 0 FULL price_change 95,685,740 95,684,902 838 1,471 FULL tick_size_change 4,132 4,132 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,271,108 70,549 18ms 31ms 218ms 41.2s 0 transport_latency_assumed best_bid_ask i 9,269,452 45,401 21ms 33ms 148ms 4.7s 0 transport_latency_assumed best_bid_ask m 9,271,624 4,491,163 5ms 16ms 91ms 7.5s 0 transport_latency_assumed best_bid_ask n 9,266,612 2,669 44ms 69ms 303ms 20.4s 0 transport_latency_assumed best_bid_ask o 9,272,026 4,662,788 5ms 16ms 96ms 6.0s 0 transport_latency_assumed book h 127,780 7,218 24ms 341ms 6.0h 110.3d 0 book_staleness book i 124,960 4,455 26ms 438ms 1.9h 110.3d 0 book_staleness book m 126,075 65,330 8ms 51ms 2.2h 110.3d 0 book_staleness book n 127,350 8,535 54ms 5.2s 10.1h 110.3d 0 book_staleness book o 124,022 59,747 8ms 43ms 4.8min 110.3d 0 book_staleness last_trade_price h 59,824 483 21ms 147ms 739ms 7.3s 0 transport_latency_assumed last_trade_price i 59,639 344 26ms 251ms 1.7s 4.7s 0 transport_latency_assumed last_trade_price m 59,905 30,593 7ms 27ms 220ms 2.4s 0 transport_latency_assumed last_trade_price n 58,524 46 54ms 1.0s 13.9s 20.2s 0 transport_latency_assumed last_trade_price o 59,926 28,537 7ms 29ms 218ms 3.6s 0 transport_latency_assumed market_resolved h 1,543 24 20ms 88ms 53.6s 53.7s 0 transport_latency_assumed market_resolved i 1,543 228 24ms 31.1s 53.7s 54.0s 0 transport_latency_assumed market_resolved m 1,543 663 6ms 18.5s 54.2s 58.8s 0 transport_latency_assumed market_resolved n 1,543 not meas. 46ms 195ms 53.6s 53.7s 0 transport_latency_assumed market_resolved o 1,543 745 6ms 41ms 46.4s 59.0s 0 transport_latency_assumed new_market h 1,080 282 147ms 35.2s 2.0min 2.4min 0 transport_latency_assumed new_market i 1,080 225 91ms 34.9s 2.0min 2.4min 0 transport_latency_assumed new_market m 1,080 666 44ms 30.5s 2.0min 2.5min 0 transport_latency_assumed new_market n 1,080 116 204ms 24.2s 2.0min 2.4min 0 transport_latency_assumed new_market o 1,080 495 56ms 31.4s 2.1min 2.5min 0 transport_latency_assumed price_change h 95,527,624 839,172 19ms 40ms 402ms 41.5s 0 transport_latency_assumed price_change i 95,498,561 537,769 22ms 47ms 638ms 4.7s 0 transport_latency_assumed price_change m 95,561,501 46,408,158 6ms 18ms 130ms 8.4s 0 transport_latency_assumed price_change n 95,372,679 56,977 45ms 104ms 2.8s 20.4s 0 transport_latency_assumed price_change o 95,585,202 47,842,826 5ms 19ms 135ms 6.2s 0 transport_latency_assumed tick_size_change h 4,132 40 19ms 31ms 115ms 3.6s 0 transport_latency_assumed tick_size_change i 4,132 12 22ms 34ms 130ms 287ms 0 transport_latency_assumed tick_size_change m 4,132 1,969 5ms 17ms 57ms 1.5s 0 transport_latency_assumed tick_size_change n 4,132 not meas. 44ms 65ms 172ms 3.0s 0 transport_latency_assumed tick_size_change o 4,132 2,111 5ms 14ms 53ms 156ms 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-10-05/18/2026-10-05T18.parquet sha256sum 2026-10-05T18.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.