Hour audit: 2026-09-27T13
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-27T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T13:00:00.000011032+00:00 · last event 2026-09-27T13:59:59.999133574+00:00
VOLUME 107,106,359 rows · 1,149,189,243 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 105,700,739 · k: 105,692,504 · h: 105,644,649 · g: 105,547,333 · c: 92,364,945 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,327,965 (1.24%) · k: 18,571,707 (17.34%) · h: 2,431,355 (2.27%) · g: 25,226 (0.02%) · c: 84,750,106 (79.13%) (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 107,106,359 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b3aa8e3922a7c3f5eb318cf86d84ba4b18b31c1814519a9153ab972fa45aa675
the corpus checksum ledger names this file with the same digest
joined 107,111,722 to merged 107,106,359, minus 5,363 (minus 0.0050%)
boundary drops 5,363 · 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-27T17:26:37Z 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,253,010 116,692,446 0-39 8e6735e920a4771036018ce5d585259cdb612f1a757193ef19e9093ffcff8126 book 1,478,269 73,017,361 40-45 b098e97db7429896ced5bafc91b9a2f635d5acbf6328ab0dd91c7492aee7d7ba last_trade_price 55,027 3,207,764 46-46 cd4d320ebce8a81b750e8298a7787aa048f0551011ef9429db9e993fa066cf48 market_resolved 1,174 145,336 47-47 0e90ea64e11f04ea1af491386401f36a8a9bcc9c9a432d142223813a051bbf6c new_market 1,949 183,002 48-48 2d32477f8b76099bd2d455c96f65456a25149da9159cb9d1b13a3af0dd761721 price_change 95,313,786 954,605,292 49-412 d808423ffae03be283936d5df04388be968ee76ff533791593692e46098aacd1 tick_size_change 3,144 116,310 413-413 3692adc3b02d420b980a584ab3d485e2b8f14f4b577c3e8221f38d9f1a16b1d9 EVENT MIX count share price_change 95,313,786 88.99% best_bid_ask 10,253,010 9.57% book 1,478,269 1.38% last_trade_price 55,027 0.05% tick_size_change 3,144 <0.01% new_market 1,949 <0.01% market_resolved 1,174 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,253,146 10,253,010 136 2,138 FULL book 1,482,019 1,478,269 3,750 199,994 FULL last_trade_price 55,027 55,027 0 359 FULL market_resolved 1,174 1,174 0 98 FULL new_market 1,996 1,949 47 59 FULL price_change 95,315,216 95,313,786 1,430 1,880 FULL tick_size_change 3,144 3,144 0 65 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,850,684 8,150,549 5ms 12ms 162ms 4.2s 0 transport_latency_assumed best_bid_ask g 10,248,624 1,242 80ms 102ms 471ms 18.7s 0 transport_latency_assumed best_bid_ask h 10,250,965 205,374 18ms 24ms 211ms 48.0s 0 transport_latency_assumed best_bid_ask i 10,251,210 113,696 22ms 27ms 112ms 6.2s 0 transport_latency_assumed best_bid_ask k 10,251,239 1,782,149 12ms 18ms 129ms 9.8s 0 transport_latency_assumed book c 1,462,344 1,444,485 1.7h 4.7d 45.8d 120.6d 0 book_staleness book g 113,885 1,838 88ms 807ms 5.9h 102.1d 0 book_staleness book h 115,195 5,781 22ms 87ms 7.0h 102.0d 0 book_staleness book i 114,525 4,020 25ms 160ms 2.8h 102.0d 0 book_staleness book k 114,906 22,145 16ms 62ms 5.2h 102.0d 0 book_staleness last_trade_price c 47,349 42,138 6ms 24ms 290ms 2.2s 0 transport_latency_assumed last_trade_price g 54,311 14 89ms 373ms 9.7s 18.7s 0 transport_latency_assumed last_trade_price h 54,818 1,749 19ms 47ms 450ms 12.4s 0 transport_latency_assumed last_trade_price i 54,901 800 24ms 85ms 1.4s 2.3s 0 transport_latency_assumed last_trade_price k 54,844 10,326 14ms 33ms 341ms 7.3s 0 transport_latency_assumed market_resolved c 1,059 964 6ms 10.3min 16.1min 17.6min 0 transport_latency_assumed market_resolved g 804 not meas. 81ms 256ms 49.9s 49.9s 0 transport_latency_assumed market_resolved h 804 122 19ms 24.6s 55.1s 58.1s 0 transport_latency_assumed market_resolved i 804 8 22ms 158ms 51.5s 51.6s 0 transport_latency_assumed market_resolved k 804 80 13ms 13.2s 55.6s 57.7s 0 transport_latency_assumed new_market c 1,349 617 124ms 4.7min 12.1min 12.2min 0 transport_latency_assumed new_market g 1,147 178 310ms 32.2s 53.9s 1.6min 0 transport_latency_assumed new_market h 1,147 319 141ms 14.7s 54.1s 1.4min 0 transport_latency_assumed new_market i 1,147 443 98ms 19.7s 39.1s 1.7min 0 transport_latency_assumed new_market k 1,147 392 184ms 31.5s 52.6s 1.6min 0 transport_latency_assumed price_change c 81,999,276 75,108,644 5ms 14ms 172ms 4.2s 0 transport_latency_assumed price_change g 95,125,418 21,954 80ms 127ms 1.2s 18.7s 0 transport_latency_assumed price_change h 95,218,576 2,217,954 18ms 28ms 272ms 49.2s 0 transport_latency_assumed price_change i 95,275,008 1,208,974 22ms 31ms 215ms 6.2s 0 transport_latency_assumed price_change k 95,266,420 16,756,260 13ms 21ms 169ms 10.9s 0 transport_latency_assumed tick_size_change c 2,884 2,709 5ms 10ms 44ms 217ms 0 transport_latency_assumed tick_size_change g 3,144 not meas. 79ms 93ms 147ms 543ms 0 transport_latency_assumed tick_size_change h 3,144 56 18ms 22ms 93ms 4.9s 0 transport_latency_assumed tick_size_change i 3,144 24 22ms 28ms 127ms 243ms 0 transport_latency_assumed tick_size_change k 3,144 355 13ms 18ms 57ms 144ms 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/13/2026-09-27T13.parquet sha256sum 2026-09-27T13.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.