Hour audit: 2026-09-27T04
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-27T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T04:00:00.000024891+00:00 · last event 2026-09-27T04:59:59.999976988+00:00
VOLUME 65,995,477 rows · 696,771,268 bytes (664.49 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 65,772,077 · i: 65,754,555 · k: 65,745,360 · h: 65,738,448 · g: 65,487,752 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 60,074,192 (91.03%) · i: 2,134,799 (3.23%) · k: 2,930,563 (4.44%) · h: 782,163 (1.19%) · g: 73,760 (0.11%) (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 65,995,477 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fa682da466f8d966897c7fbea6038b79f4aa63b591956d071588cbde9a0afb4d
the corpus checksum ledger names this file with the same digest
joined 65,997,430 to merged 65,995,477, minus 1,953 (minus 0.0030%)
boundary drops 1,953 · 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-27T13:48:52Z as cghik
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 7,851,830 89,917,305 0-29 0b4d821a5f7db7f714b7f13cfc4ec15aec44362ea41c30afae8217039257f270 book 330,803 29,957,135 30-31 62934adc15e449a45ac8f75300d9ab26cd34bb839176401da3c7a4a0d8d784d3 last_trade_price 32,399 1,910,969 32-32 5e277d3008ee20acfd1eb1270c558000adc11e5acb7c86489fd6c0b7164ac5f3 market_resolved 4,838 716,923 33-33 41a069f18cc6a363c31e23506dae4320132e4f70990ace31edc1d0c9fbe07f39 new_market 5,387 555,479 34-34 4f465d4ff00cf09f9d2b80b435f70677bc3c1dd5f42b1e50237578df5838a15a price_change 57,765,000 572,763,851 35-255 f2cd527a0acec1b17dcec6bc1a68a47a0f8e568423f54f5e01de1eebd7d7cc0d tick_size_change 5,220 191,110 256-256 478ab952443c98fa359d5cf2f404c10892e2088cbbdcdd1ab20cd938385ec2cf EVENT MIX count share price_change 57,765,000 87.53% best_bid_ask 7,851,830 11.90% book 330,803 0.50% last_trade_price 32,399 0.05% new_market 5,387 <0.01% tick_size_change 5,220 <0.01% market_resolved 4,838 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,852,040 7,851,830 210 522 FULL book 330,805 330,803 2 108,827 FULL last_trade_price 32,400 32,399 1 0 FULL market_resolved 4,838 4,838 0 0 FULL new_market 5,387 5,387 0 0 FULL price_change 57,766,740 57,765,000 1,740 134 FULL tick_size_change 5,220 5,220 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,848,248 7,266,724 4ms 9ms 403ms 11.4s 0 transport_latency_assumed best_bid_ask g 7,841,523 1,934 79ms 156ms 1.1s 40.3s 0 transport_latency_assumed best_bid_ask h 7,846,026 72,587 18ms 31ms 1.0s 1.8min 0 transport_latency_assumed best_bid_ask i 7,847,711 218,234 20ms 24ms 215ms 4.9s 0 transport_latency_assumed best_bid_ask k 7,847,494 292,351 12ms 17ms 371ms 1.2min 0 transport_latency_assumed book c 133,312 112,398 566ms 42.0min 35.6d 120.3d 0 book_staleness book g 130,997 49,208 2.8s 41.6min 35.6d 120.3d 0 book_staleness book h 136,337 54,825 2.1s 41.6min 35.6d 120.3d 0 book_staleness book i 136,080 55,562 1.5s 42.3min 35.6d 120.3d 0 book_staleness book k 135,742 58,810 1.4s 41.6min 35.6d 102.2d 0 book_staleness last_trade_price c 32,334 29,275 5ms 20ms 521ms 3.5s 0 transport_latency_assumed last_trade_price g 31,483 1 81ms 395ms 13.5s 40.3s 0 transport_latency_assumed last_trade_price h 32,302 355 19ms 69ms 2.3s 1.5min 0 transport_latency_assumed last_trade_price i 32,347 1,001 21ms 41ms 616ms 4.9s 0 transport_latency_assumed last_trade_price k 32,261 1,767 13ms 27ms 402ms 1.2min 0 transport_latency_assumed market_resolved c 4,533 3,819 5ms 24.1s 49.8s 54.4s 0 transport_latency_assumed market_resolved g 4,533 157 79ms 437ms 53.7s 57.0s 0 transport_latency_assumed market_resolved h 4,533 31 19ms 20.9s 51.0s 57.1s 0 transport_latency_assumed market_resolved i 4,533 68 21ms 22.1s 49.9s 56.8s 0 transport_latency_assumed market_resolved k 4,533 763 13ms 21.4s 51.3s 56.3s 0 transport_latency_assumed new_market c 3,696 1,571 382ms 1.0min 1.2min 1.7min 0 transport_latency_assumed new_market g 3,696 616 680ms 1.0min 1.2min 1.8min 0 transport_latency_assumed new_market h 3,696 594 337ms 1.1min 1.2min 1.6min 0 transport_latency_assumed new_market i 3,696 1,549 256ms 1.1min 1.3min 1.9min 0 transport_latency_assumed new_market k 3,696 1,057 409ms 1.0min 1.2min 1.7min 0 transport_latency_assumed price_change c 57,744,734 52,655,822 4ms 15ms 548ms 12.0s 0 transport_latency_assumed price_change g 57,470,304 21,844 79ms 237ms 3.1s 40.5s 0 transport_latency_assumed price_change h 57,710,334 653,632 18ms 48ms 1.4s 1.8min 0 transport_latency_assumed price_change i 57,724,968 1,858,216 20ms 29ms 445ms 5.0s 0 transport_latency_assumed price_change k 57,716,414 2,575,486 12ms 22ms 516ms 1.2min 0 transport_latency_assumed tick_size_change c 5,220 4,583 4ms 26ms 313ms 626ms 0 transport_latency_assumed tick_size_change g 5,216 not meas. 79ms 226ms 815ms 1.1s 0 transport_latency_assumed tick_size_change h 5,220 139 18ms 46ms 747ms 4.1s 0 transport_latency_assumed tick_size_change i 5,220 169 20ms 32ms 204ms 423ms 0 transport_latency_assumed tick_size_change k 5,220 329 12ms 26ms 313ms 2.2s 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-27/04/2026-09-27T04.parquet sha256sum 2026-09-27T04.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.