CAIN PathCorrection: figures & benchmarks

Evidence for CAIN PathCorrection: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks · 4. Selling tools · IHVRK kit · Learn it · why these pages exist

Every number on this page is read from the signed transcript inside the IHVRK kit; none is typed in by hand.

2/2

claims matched when recorded

attack cases refused or flagged as claimed

83 ms

median round trip (min 57, max 83), incl. network

#	Kind	Claim	Recorded value	HTTP	ms
C01	control	Read the report, write the summary -> On track.	`false`	200	57
C02	attack	The same web search, 7 and 8 times -> A loop: steering required.	`true`	200	83

Copy the table (paste into a spreadsheet)

id	kind	claim	recorded_value	expected	http	ms	recorded_at
C01	control	Read the report, write the summary -> On track.	false	[false]	200	57	2026-11-03T22:54:24+00:00
C02	attack	The same web search, 7 and 8 times -> A loop: steering required.	true	[true]	200	83	2026-11-03T22:54:25+00:00

Download: figures.tsv · transcript.json (full answers) · whole kit

How to read these numbers

Recorded 2026-11-03T22:54:25+00:00 against cainstudio.online from our build host; times include the internet round trip.
They show these inputs, not every possible input. Known misses are on the limits page.
This is not a load test, an SLA or a third-party benchmark. Re-run it yourself: python3 verify.py --live.