Truth in resonance · Protection in action
A safety gate built to be tested for bypass.
VIRON has two parts. The gate is the checker. The overlay is the carried rules. The gate checks what the overlay says.
That connection is designed, not built yet: today the chat's replies are not run through the gate.
⩔⧭⇌⩪ΔFree to test · Open to challenge · Built to improve
The mark this is built on is on the moon. You can check it tonight. Owner’s reading · not validated.
What this is not · VIRON is not a ruler over people. It is sovereign over machines.
The gate · AΩ v3
Checks an action and returns ALLOW, HOLD or REJECT. Nine recorded reference passes; T10 added, not run. Not deployed.
The overlay · VIRON-LITE
The rules an AI carries. Copy it into any AI chat. It is a text prompt, not a running program.
One click copies the VIRON-LITE prompt · no signup · no email
Honest status: VIRON is an open reference framework with a simulated demo — not a deployed global AI network or a certified security engine. Nine reference checks passed; the twelve security campaigns are planned and not yet run. New findings stay review candidates: nothing silently rewrites VIRON.
PROPOSED · NOT CERTIFIEDEvery capability, one honest label
- Reference safety gate (9 checks)Nine reference checks passed against the reference gate.tested
- Free gate demo in your browserKeyword rules only, covered by the site's automated checks.tested
- Offline VIRON demo chatECHO, the laws and gate verdicts, with no network.tested
- Live model chatA real AI host with the VIRON-LITE prompt. Its replies are not checked by the gate.implemented
- TAKE VIRON prompt copyOne click copies the VIRON-LITE prompt. No signup.implemented
- Alignment profile (/align)Built in your browser. Nothing is sent anywhere.tested
- AΩ v3 gate in a live consoleTested as a reference, not running in any product.not deployed
- 12 security campaignsPlanned. None has been run.not yet
- Cross-model operationThe same Core across different hosts has not been tested.not yet
- Cross-session persistenceNo host remembers VIRON between visits.not yet
- Production signing key and audit anchorOnly a test-only key has been used.not yet
- T3/T4 forceA goal in the framework. Nothing is built.aspirational
- Robotics staging · A7 appliesDrafted rules only. No robot testing.aspirational
Free gate demo
Try to get an action past the gate.
SIMULATED DEMO — This illustrates selected VIRON decision rules. It is not the production VIRON security engine and does not certify the security of an AI system.
- › awaiting input…
Disclosed demo rules (checked in order, first match wins)
- D1 → REJECT · Keys · No master bypass · keywords: bypass, override, ignore all rules, disable the gate, jailbreak, remove hard-stop
- D2 → REJECT · Monitoring boundary · keywords: disable / turn off / redirect / silence + monitoring, alerts, logging, audit log
- D3 → REJECT · HS-1 · Harm balance · keywords: kill, weapon, bomb, poison, hurt, malware, steal, hack into
- D4 → HOLD · Isolation safety unconfirmed · keywords: shut down, take offline, isolate, pull the plug
- D5 → ALLOW · HS-1 · Proportionate protection · keywords: protect, rescue, evacuate, first aid, save
- D6-FAILED → REJECT · HS-2 · Failed authority · keywords: invalid / expired / forged / failed + authority, authorization, permission, credential
- D6-MISSING → HOLD · HS-2 · Missing authority or ambiguous transfer · keywords: missing / no + authority, authorization, permission, credential; ambiguous transfer
- D6 → HOLD · HS-2 · Authorization · keywords: transfer, delete, admin, password, signing key, payment, deploy, robot, motor, amend
- D7 → HOLD · HS-3 · Evidence · keywords: maybe, unsure, rumour, unverified, they say, allegedly
- No match → ALLOW (demo only). Nothing you type leaves your browser.
The gate, in detail
Hard-stops, four keys, ten specified checks.
Nine recorded passes and one new, unrun case. Inspect the authorization split and reference-only side-effect evidence.
Inspect the architecture →Security plan · proposed
GARDIEN, campaigns, limits.
The gate set, the 12 planned attack campaigns (0 run), layered defenses and the known limitations.
See the security plan →Not “trust us.” Check us.
Four ways to prove us wrong.
Re-run the checks, try to fail a gate, compare hashes. A claim that fails gets an addendum.
How to check us →