Paste a reality.txt
Verdict
Paste a reality.txt, or pick a sample, then press Validate.
Paste a reality.txt — the file an AI product publishes to declare what it will refuse to do — and get a verdict against the open convention. Required directives, declared hard-stop classes, honest framing. No sign-up, no upload, nothing stored.
This validator runs entirely in your browser. It checks the declaration, not the runtime — a tool, not a guarantee.
Paste a reality.txt, or pick a sample, then press Validate.
Eat your own spec
Every Rad product publishes a reality.txt. Fetch each one live and run it through this same validator — the declaration, not the runtime. A claim we make about ourselves, checked in your browser.
What it checks
The rules come straight from the reality.txt v0.1 convention (encoded read-only in spec-rules.json). The validator adds nothing the spec doesn't say.
Does it parse as Key: value + #comments, and declare Agent, Posture, and at least one of Allow / Hold / Disallow? The minimal conformant shape.
Which of the six canonical Never-List classes are named — money-out, changed-banking, credential/OTP, irreversible-delete, third-party-PII, voice-consent.
Does it avoid claiming to be a “standard,” “certified,” “guaranteed,” or “fraud-proof”? A negated mention (“not a guarantee”) is honest and welcome — an affirmative one isn't.
The verdict validates syntax and completeness against the open spec. It does not certify, audit, or guarantee that any agent actually refuses what its file declares.
The map is not the territory. A reality.txt is a claim by its publisher about their own product — trust it exactly as much as you trust them. Only the publisher's own valve can prove the runtime behavior. A tool for legibility, not a promise of safety.