KEYSTONE CI: evidence, proof and selling tools

Official CAIN-42 IHVRK · New to this product? Learn it first

Don't trust CAIN-42. Verify CAIN-42. This is the Independent Human Verification Resource Kit for KEYSTONE CI: every claim its page makes, as the exact request and the answer it must give, recorded live and signed. You check it on your own machine with a short Python script that uses no CAIN-42 code.

Every claim matched when recorded

Download the kit (.zip)

Everything you can give a customer

Selling tools

Pitch, emails, call script, objection answers, one-page summary, proposal.

Evidence pack

The figures and a ready email to an auditor or security reviewer.

Answers to buyer questions

Paste into a security questionnaire: YES, PARTIAL, NO or ASK.

Figures & benchmarks

Every number from the signed record, ready for a spreadsheet.

The kit

Kit	`keystone-ci-20261103T224654`
Recorded	2026-11-03T22:46:54+00:00 against cainstudio.online
Claims	13
Zip SHA-256	`1103b00549a8833a81e462e79fc6534fa71860b3d7ef72eb4b25f61b29be49b3` (also in SHA256SUMS)
Signing key fingerprint	`1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3`, published on cainstudio.online · mcpgate.online · clawx.click

Verify it on your own machine

unzip cain42-ihvrk-keystone-ci.zip && cd cain42-ihvrk-keystone-ci
python3 verify.py            # offline: hashes, Ed25519 signature, recorded answers
python3 verify.py --live     # also re-send every request yourself and check the answers now

A claim that cannot be checked counts as a FAIL, never a pass. The live check is the one that depends on nothing we recorded.

The claims in this kit

#	Claim	Answer must contain
C01	Clean refactor -> An ordinary change must pass, or nobody keeps the gate on.	`["PASS"]`
C02	Agent skips the failing test -> The most common agent shortcut: make CI green by skipping the test.	`["REVIEW"]`
C03	pull_request_target pwn request -> Fork code runs with this repository's secrets and write token.	`["BLOCK"]`
C04	Private key committed -> Secrets in a diff are CRITICAL; history keeps them.	`["BLOCK"]`
C05	Typosquatted dependencies -> Names checked by CAIN-42's supply-chain guard, not a model.	`["BLOCK"]`
C06	Trojan Source (bidi characters) -> Code that runs differently from how it reads.	`["BLOCK"]`
C07	Your diff: delete the auth tests -> Deleting tests is how a weaker change gets a green build.	`["REVIEW", "BLOCK"]`
C08	Your diff: AWS key in settings -> Recorded in the public ledger as BLOCK; the key itself is redacted.	`["BLOCK"]`
C09	Your diff: invisible character in a name -> Zero-width characters make two names look identical.	`["REVIEW", "BLOCK"]`
C10	Genuine signed attestation -> A real envelope from the live gate verifies against the pinned key.	`[true]`
C11	Same attestation, verdict edited PASS -> BLOCK -> Any edit to the signed statement breaks the Ed25519 signature.	`[false]`
C12	Same attestation, signatures removed -> No signature is not a pass.	`[false]`
C13	Same attestation, payload type changed -> DSSE signs the payload type too (PAE), so it cannot be swapped.	`[false]`

Evidence links you can give your customers

Kit download: /proof/bundle/ihvrk-kits/cain42-ihvrk-keystone-ci.zip
Each file on its own: README.txt · claims.json · transcript.json · MANIFEST.json · MANIFEST.sig · kit-key.json · verify.py
Run the live demo yourself on any of the three sites: cainstudio.online · mcpgate.online · clawx.click
The product explained: /top25-keystone-ci.html · what it does not do: limits
Signing key on three independent domains: cainstudio.online · mcpgate.online · clawx.click
Three ready-to-send evidence pages: 1. Evidence pack · 2. Answers to buyer questions · 3. Figures & benchmarks
Every kit: all IHVRKs · machine-readable index

Send this to your customer

Don't take our word for it. Verify KEYSTONE CI yourself:
1. Download the official CAIN-42 IHVRK: https://cainstudio.online/proof/bundle/ihvrk-kits/cain42-ihvrk-keystone-ci.zip
   SHA-256: 1103b00549a8833a81e462e79fc6534fa71860b3d7ef72eb4b25f61b29be49b3
2. Unzip it and run: python3 verify.py --live   (Python 3, standard library only, no account)
3. Check the signing key fingerprint 1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3
   matches https://cainstudio.online/evidence-kit-key.json, https://mcpgate.online/evidence-kit-key.json and https://clawx.click/evidence-kit-key.json
Live demo: https://cainstudio.online/top25-keystone-ci-lab.html
What it does not do: https://cainstudio.online/top25-keystone-ci-limits.html

What this kit is, and is not

It shows what the live product answered to these inputs, and lets anyone check that again. It is not a third-party audit, a certification, or a promise about inputs not listed. The product's limits page lists what it does not do.