Hour audit: 2026-09-27T12
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-27T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T12:00:00.000016719+00:00 · last event 2026-09-27T12:59:59.999964017+00:00
VOLUME 103,236,244 rows · 1,099,406,897 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 102,117,498 · k: 102,116,389 · h: 102,091,568 · g: 102,028,675 · c: 89,961,783 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,176,266 (1.14%) · k: 18,027,003 (17.46%) · h: 1,966,413 (1.90%) · g: 12,262 (0.01%) · c: 82,054,300 (79.48%) (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 103,236,244 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 238dd10fc250b38a83ecc8708c8fb75bcacd7235939b667784a92b65453f9b8d
the corpus checksum ledger names this file with the same digest
joined 103,244,784 to merged 103,236,244, minus 8,540 (minus 0.0083%)
boundary drops 8,540 · 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-27T16:59:34Z 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 10,751,094 120,143,429 0-41 a43b008db491386228841d405c7bba7795fd09f0d0ee58016c512fcb2b156cc2 book 1,180,385 67,543,637 42-46 359a074dc71c3031c333057495b54bc86dbab8c39837f6fc583d39c77aa8394a last_trade_price 47,800 2,829,004 47-47 60fd00a281e8a3e3019fa19a4b3901f52cfc70c4f3ff916bc1935d93d20a883b market_resolved 870 117,710 48-48 be7e988d49e518f22a2c1ba41004cfadc347061c69fe356361e3409812ecb66b new_market 3,564 318,091 49-49 40901970fd23f3434d3c3f6c7207176260e2b108486baaa9ffc18c3db08f4c40 price_change 91,249,503 907,164,134 50-398 6a83867f24f97f1aafaa6a275b1d216ac3d62be715618f62a5a1586ede648435 tick_size_change 3,028 110,986 399-399 ac604021291f74ed0fd88a5400a071aaa7507e54b95ba36c1c2e640cfa277552 EVENT MIX count share price_change 91,249,503 88.39% best_bid_ask 10,751,094 10.41% book 1,180,385 1.14% last_trade_price 47,800 0.05% new_market 3,564 <0.01% tick_size_change 3,028 <0.01% market_resolved 870 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,751,652 10,751,094 558 1,899 FULL book 1,183,687 1,180,385 3,302 198,899 FULL last_trade_price 47,805 47,800 5 256 FULL market_resolved 870 870 0 19 FULL new_market 3,564 3,564 0 22 FULL price_change 91,254,178 91,249,503 4,675 1,421 FULL tick_size_change 3,028 3,028 0 105 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,338,206 8,544,090 5ms 12ms 273ms 10.4s 0 transport_latency_assumed best_bid_ask g 10,746,631 1,205 79ms 104ms 646ms 22.6s 0 transport_latency_assumed best_bid_ask h 10,748,092 192,137 18ms 23ms 379ms 47.7s 0 transport_latency_assumed best_bid_ask i 10,748,026 118,450 27ms 37ms 136ms 4.0s 0 transport_latency_assumed best_bid_ask k 10,748,026 1,895,212 12ms 17ms 219ms 1.4min 0 transport_latency_assumed book c 1,166,951 1,151,821 1.5h 4.6d 45.7d 120.6d 0 book_staleness book g 102,771 1,963 88ms 1.1s 8.6h 112.9d 0 book_staleness book h 101,723 4,804 22ms 126ms 6.3h 120.6d 0 book_staleness book i 99,827 3,406 30ms 102ms 3.5s 102.0d 0 book_staleness book k 101,141 18,391 15ms 79ms 2.2h 102.0d 0 book_staleness last_trade_price c 41,858 37,269 6ms 22ms 381ms 6.2s 0 transport_latency_assumed last_trade_price g 47,506 1 88ms 362ms 8.5s 22.6s 0 transport_latency_assumed last_trade_price h 47,658 1,174 19ms 41ms 642ms 47.2s 0 transport_latency_assumed last_trade_price i 47,682 635 29ms 60ms 580ms 3.6s 0 transport_latency_assumed last_trade_price k 47,679 8,721 13ms 27ms 350ms 18.1s 0 transport_latency_assumed market_resolved c 737 654 5ms 2.6min 8.6min 9.0min 0 transport_latency_assumed market_resolved g 707 15 80ms 242ms 46.0s 46.1s 0 transport_latency_assumed market_resolved h 707 112 19ms 25.8s 48.5s 51.5s 0 transport_latency_assumed market_resolved i 707 25 28ms 92ms 42.2s 56.2s 0 transport_latency_assumed market_resolved k 707 64 13ms 30.5s 52.0s 55.3s 0 transport_latency_assumed new_market c 2,716 1,333 326ms 5.5min 6.4min 6.6min 0 transport_latency_assumed new_market g 2,030 248 325ms 31.3s 43.5s 1.2min 0 transport_latency_assumed new_market h 2,030 599 175ms 28.9s 46.7s 1.6min 0 transport_latency_assumed new_market i 2,030 799 143ms 31.7s 39.7s 1.5min 0 transport_latency_assumed new_market k 2,030 585 199ms 30.1s 40.5s 1.7min 0 transport_latency_assumed price_change c 79,408,707 72,316,718 5ms 13ms 288ms 11.1s 0 transport_latency_assumed price_change g 91,126,002 8,830 79ms 134ms 1.3s 22.6s 0 transport_latency_assumed price_change h 91,188,330 1,767,511 18ms 25ms 408ms 50.7s 0 transport_latency_assumed price_change i 91,216,198 1,052,934 27ms 38ms 193ms 4.1s 0 transport_latency_assumed price_change k 91,213,778 16,103,510 12ms 19ms 234ms 1.4min 0 transport_latency_assumed tick_size_change c 2,608 2,415 5ms 9ms 387ms 759ms 0 transport_latency_assumed tick_size_change g 3,028 not meas. 78ms 93ms 540ms 1.2s 0 transport_latency_assumed tick_size_change h 3,028 76 18ms 22ms 249ms 1.2s 0 transport_latency_assumed tick_size_change i 3,028 17 27ms 36ms 152ms 390ms 0 transport_latency_assumed tick_size_change k 3,028 520 12ms 17ms 277ms 8.7s 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/12/2026-09-27T12.parquet sha256sum 2026-09-27T12.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.