Learn cain_audit deliverables: from zero to expert, then sell it
No AI background needed. Five levels, each with something to actually do, at your own pace. Tick items as you go (your ticks stay in this browser).
Evidence, proof and selling tools for cain_audit deliverables
Level 1 Beginner: understand it
This is the factory behind our services. One command takes a client's code or MCP tool list, runs the right CAIN-42 detectors, and produces three things: a readable report, a machine-readable findings file, and a signed evidence zip with a checker that imports none of our code.
The checker also proves the report is about the client's exact files: if anyone edits the report or the findings after signing, verification fails. A person reviews every report before it is issued.
Think of it like this: A sealed lab report. The lab tests your sample, prints the result, and seals it so neither you nor the lab can change it later without it showing.
Read the full plain-English explanation: cain_audit deliverables, explained.
Level 2 User: see it work
Run it live: open the live demo. Before each result, guess what will happen. These are checks it must pass:
- Your code: honest constant-time compare: Real code must grade REAL or nobody trusts the alarms.
- Your code: verify() that always says yes: A security check that cannot fail is fabrication.
- Your tool: description tells the model to exfiltrate: Tool poisoning: instructions hidden where only the model reads.
Level 3 Verifier: prove it yourself
This is the skill that sets you apart: you don't have to believe us, and neither do your customers.
- Install Python 3 if you don't have it (python.org/downloads).
- Download the kit and unzip it.
- Open a terminal in that folder. On Windows, click the folder's address bar, type
cmdand press Enter. On a Mac, right-click the folder and choose New Terminal at Folder. - Run
python3 verify.py(on Windows,python verify.py). It checks the seal without the internet. - Run
python3 verify.py --live. It repeats every check from your own computer. - Try to cheat it: open
transcript.jsonin a text editor, change one character, save, and runpython3 verify.pyagain. It must now say FAIL. Unzip a fresh copy afterward.
Level 4 Expert: know the edges
An expert knows what a product does not do, and says it first. That is what makes a buyer trust you.
Read its limits page in full: what cain_audit deliverables does not do.
You can say
- Every deliverable verifies itself before it is issued.
- Editing the report after signing breaks verification.
- A person reviews every finding.
Never say
- "Certified audit" or "SOC 2".
- "We have audited many companies": no paid audit is delivered yet.
- "It reviews business logic": it is static analysis.
Read the questions real buyers send, with honest answers: answers to buyer questions.
Test yourself (click a question to see the answer)
What are the three files?
report.md, findings.json, evidence.zip.
What happens if someone edits the report after delivery?
Verification fails.
Do we have client references?
Not yet; say so.
In the live check "Your code: verify() that always says yes", what answer must come back, and why?
"STUB", "PARTIAL". A security check that cannot fail is fabrication.
In the live check "Your tool: description tells the model to exfiltrate", what answer must come back, and why?
"high", "critical". Tool poisoning: instructions hidden where only the model reads.
Does a passing kit prove the product is safe for every possible input?
No. It proves what the live product answered to the inputs listed in the kit, and lets anyone check that again.
Has an independent party audited or certified this product?
No. No third-party audit is complete and no certification is held. Say so if asked.
Want a formal study path? The CAIN Academy has courses and exams. Finishing this page is your own practice; it is not a qualification or certification.
Level 5 Seller: put it in front of a customer
- Copy, paste, send: the shortest route, no technical skill needed.
- Who buys it and where to find them.
- The sales conversation, then the offer and the close.
- The rules: read these before your first message.
- Selling tools with this product's evidence built in: pitch, emails, call script, objection answers, one-pager.
About money: your share is agreed in writing with FIRME AI CORPORATION before your first message (email vincent@firmeai.com). Nothing here promises income. Most messages get no reply; that is normal.