CAIN-42 is in Public Beta. Expect changes, and do not rely on it as your only control for anything critical. What beta means
CAIN-42 CAIN Studio

CAIN-42 · announcement · October 2026

CAIN-42 checks its own code every 42 seconds.

Day and night, every 42 seconds, CAIN-42 turns its own tools on itself: it looks at every file of its codebase, re-scans anything that changed for code that fakes a result, and publishes the check, chained to the one before it. You are watching it happen. Run the live tools ↓

Connecting to the live self-check…

—checks run so far
—since the last check
—until the next check (about)
—files looked at on every check

Live tools · no account needed

Don’t take our word for it. Run it.

Four live tools on production routes. Each shows exactly what the server returned.

1 · Re-verify the 42-second chain in your browser

Downloads the latest 120 checks and recomputes every SHA-256 hash and link on your own machine, then measures the real interval between checks.

2 · Run FALSEWORK on your own code

The detector behind the 42-second check. Pick a sample or paste any Python; FALSEWORK reports code that fakes a result. Nothing you paste is executed.

3 · KEYSTONE’s signed fixes

Every KEYSTONE run is a signed record: what FALSEWORK found, what the AI changed, whether an independent test failed on the old code and passed on the new, and the Ed25519 signature. Open one and re-verify it live.

Loading the signed ledger…

4 · The campaign on CAIN-42’s own code

FALSEWORK and KEYSTONE pointed at CAIN-42 itself: the proved fixes that went into the repository, and every finding, searchable.

All the evidence, across CAIN-42

What happens every 42 seconds

  1. A timer on the CAIN-42 host wakes FALSEWORK, CAIN-42’s detector for code that fakes a result.
  2. FALSEWORK looks at every Python file of CAIN-42 and re-scans the ones that changed: results typed in instead of computed, verdicts returned without a check, errors silently swallowed, leftover placeholders.
  3. Each file is graded REAL, PARTIAL or STUB, and the totals are published at once.
  4. The check’s record is SHA-256 chained to the one before it, so a skipped or edited check shows.

When FALSEWORK flags something, KEYSTONE takes over: an AI proposes a fix, and the fix is applied only once sandboxed tests fail on the old code and pass on the new.

Check it yourself

The live status is a public file. Fetch it twice, 42 seconds apart, and watch the check number move:

curl -s https://cainstudio.online/evidence/keystone-codebase-scan-live.json

Running since — · current chain head —

The signed record of the first full run, with every check in order and an offline verifier that recomputes every number, is at /evidence/keystone-codebase-scan-2026-10-15/. Full results: cainstudio.online/#codebase-scan.

Tell someone

If a codebase can prove it is checked every 42 seconds, yours can be too. Share this page:

Post on X Share on LinkedIn Submit to Hacker News Email it

Want the same for your agents? Start free · CAIN-42 home