Talosdev Archdiff: 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 Talosdev Archdiff: 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	`svc-talosdev-archdiff-20261103T233243`
Recorded	2026-11-03T23:32:43+00:00 against cainstudio.online
Claims	4
Zip SHA-256	`9c3edee0a465cfc17e974bc229ad3e614c12648ee563d13207d6a57443ed8fff` (also in SHA256SUMS)
Signing key fingerprint	`1cacdfc1fc2024b6bb4f8fb02c7c80f4a57f44c5adb11c507190781b5d613de3`, published on cainstudio.online · mcpgate.online · clawx.click

Verify it on your own machine

unzip cain42-ihvrk-svc-talosdev-archdiff.zip && cd cain42-ihvrk-svc-talosdev-archdiff
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	talosdev-archdiff (catalog service): the demo completes (ok) -> ok = every step succeeded; refused = the service answered and refused a step, as this demo shows on purpose.	`["ok"]`
C02	Step 1: POST /snapshot answers HTTP 200 -> This step succeeded in the reference run.	`[200]`
C03	Step 2: POST /snapshot answers HTTP 200 -> This step succeeded in the reference run.	`[200]`
C04	Step 3: POST /diff answers HTTP 200 -> This step succeeded in the reference run.	`[200]`

Evidence links you can give your customers

Kit download: /proof/bundle/ihvrk-kits/cain42-ihvrk-svc-talosdev-archdiff.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: /service/talosdev-archdiff
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 Talosdev Archdiff yourself:
1. Download the official CAIN-42 IHVRK: https://cainstudio.online/proof/bundle/ihvrk-kits/cain42-ihvrk-svc-talosdev-archdiff.zip
   SHA-256: 9c3edee0a465cfc17e974bc229ad3e614c12648ee563d13207d6a57443ed8fff
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/service/talosdev-archdiff
What it does not do: no written limits review yet; this kit shows the live service answered as recorded, not that every answer is right for every input

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. This product has no written limits review yet.