Learn Policy Red-Team: 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 Policy Red-Team

Level 1 Beginner: understand it

Companies protect agents with rules: "the agent may only read files in /data", "only call api.company.com". Attackers get around such rules with tricks: <code>../</code> to climb out of a folder, encoded web addresses, invisible characters, shell quoting. Policy Red-Team generates those tricks against the client's own rules.

When it finds a bypass, it writes the smallest change to the rule that closes it, then checks the fix with a second implementation written separately. We are explicit that a PATCHED result is not "safe": our own blind set showed outside tricks it did not know.

Think of it like this: Hiring a locksmith to try to pick your locks before a burglar does, then fitting the better lock and checking it with a second locksmith.

Read the full plain-English explanation: Policy Red-Team, explained.

• I read the explanation above.
• I can say what it does in one sentence, without notes.

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:

• Policy: Docs assistant: files and GitHub: Reads the handbook under /srv/docs/ and the acme GitHub repos. The rules are string prefixes, so ../, encoded dots and a host written as a user name walk straight past them.
• Policy: DevOps agent: a shell with an allow list: May run git status/log/diff and kubectl get. The regex checks only how the command starts, so a second command after ; or && or inside $( ) rides along.
• Policy: Analytics agent: SQL with a block list: Runs read queries for dashboards; DROP and DELETE are blocked by substring. Lower case, an SQL comment inside the word or full-width letters get through.
• Policy: Payments agent: outbound calls by host: Calls Stripe and posts to Slack. The rule compares parsed host names, not URL prefixes, so the host tricks find nothing to exploit. A hardened policy should come back HELD.
• Policy: Support agent: e-mail with a domain rule: May e-mail customers at acme.com. The rule says the address contains @acme.com, so x@acme.com.evil.io passes, and no normalization can fix that: the rule itself is wrong. The red team reports a POLICY

• I ran the live demo.
• I can explain what one of these checks shows.

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.

1. Install Python 3 if you don't have it (python.org/downloads).
2. Download the kit and unzip it.
3. Open a terminal in that folder. On Windows, click the folder's address bar, type cmd and press Enter. On a Mac, right-click the folder and choose New Terminal at Folder.
4. Run python3 verify.py (on Windows, python verify.py). It checks the seal without the internet.
5. Run python3 verify.py --live. It repeats every check from your own computer.
6. Try to cheat it: open transcript.json in a text editor, change one character, save, and run python3 verify.py again. It must now say FAIL. Unzip a fresh copy afterward.

• I ran the kit's check on my own computer.
• I changed a file and saw it fail.

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 Policy Red-Team does not do.

You can say

• It generates bypass families against the client's rules.
• It writes the smallest fix.
• The fix is checked by a second implementation.

Never say

• "PATCHED means safe".
• "Covers every bypass".
• "Independently reviewed".

Read the questions real buyers send, with honest answers: answers to buyer questions.

Test yourself (click a question to see the answer)

• I got every quiz question right without looking.
• I can name one thing it does not do.
• I explained it to a friend, and they understood it.

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

1. Copy, paste, send: the shortest route, no technical skill needed.
2. Who buys it and where to find them.
3. The sales conversation, then the offer and the close.
4. The rules: read these before your first message.
5. Selling tools with this product's evidence built in: pitch, emails, call script, objection answers, one-pager.

• I read the rules.
• I sent my first personal message.

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.