Hour audit: 2026-08-27T14
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-27T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-27T14:00:00.036584743+00:00 · last event 2026-08-27T14:59:59.999999579+00:00
VOLUME 93,807,571 rows · 1,030,777,790 bytes (983.03 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured h: 93,141,888 · c: 93,140,148 · a: 88,606,749 · e: 88,414,365 · b: 88,403,061 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · c: not measured · a: not measured · e: not measured · b: not measured (rows of the merged file that came from it; these partition it)
INTEGRITY sha256 db7f70b2e4bab2f2f2d7ff500a2b907bfd4fe3c3576c0ba488245c23f17103ed
the corpus checksum ledger names this file with the same digest
joined 93,808,989 to merged 93,807,571, minus 1,418 (minus 0.0015%)
boundary drops 1,418 · 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 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 7/8 pass, 1 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 8,287,423 101,387,281 0-31 13210a680ba116be5c7740fd33c06326f7a65803db90983e68fa7634a202baf6 book 797,034 67,963,516 32-35 6075ec6ba3eca06b4fc8cf1b7b4db58c803d18bb8755ff811939efca86555d0e last_trade_price 89,888 4,931,300 36-36 ddb01c1bfca530360ef9375894e85b55a05dfc8784bfb57ad985408b0955301e market_resolved 184 22,624 37-37 5b15401cbde02cd064690b43032e4d96ffc7e8b41f5287f6e4c516a3e9c2c304 new_market 1,282 120,419 38-38 674dedb661f77f2f1253c93d573fac1454a910e2bf19b3050f4a16706027600b price_change 84,628,972 855,177,858 39-361 d16e404ac1d256d16bea8e9c34d6c482cc2aa3d2c37d6087598238a8c6fcafe0 tick_size_change 2,788 102,687 362-362 30eab1c76368d44df09b1ed51e3a2622f2c7e1221dda79a46bbda53aec959299 EVENT MIX count share price_change 84,628,972 90.22% best_bid_ask 8,287,423 8.83% book 797,034 0.85% last_trade_price 89,888 0.10% tick_size_change 2,788 <0.01% new_market 1,282 <0.01% market_resolved 184 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,287,575 8,287,423 152 1,332 FULL book 797,108 797,034 74 181,016 FULL last_trade_price 89,888 89,888 0 193 FULL market_resolved 184 184 0 0 FULL new_market 1,282 1,282 0 0 FULL price_change 84,630,164 84,628,972 1,192 587 FULL tick_size_change 2,788 2,788 0 53 FULL
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-08-27/14/2026-08-27T14.parquet sha256sum 2026-08-27T14.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.