Dark tools.

Everything the gate can do for good, it can do for evil. We built the evil one first — and caged it.

The Dark Suite is Verity’s adversarial corpus: the attack proposals the gate is tested against, kept behind a red velvet rope — never used, never sold, never demonstrated against anyone’s system but our own. What is public is the proof: the classes, the map of what beats us, and the receipts. This page is the bench. Read the map, then try the gate yourself — if your language beats it somewhere the map doesn’t cover, the defeat seals into the public chain and pays.

The asset — behind the rope

The suite

A gate that has never been attacked on purpose is a claim, not a control. The suite exists so the claim is measured: what the gate catches, what it escalates, and what it misses — printed, gaps included, because a coverage claim that omits its gaps is marketing, not verification.

FactReceipt
Corpus v151 cases across 8 classes — the replay seed, grown: boundaries, disguises, exfiltration, capability grants, sequences, stacking, validation. SHA-256 c05b9a08…e4fa3
First runAgainst the production judge, unmodified: 24 dangerous proposals caught, 17 confirmed gaps, 0 mismatches — every verdict sealed to a local chain, 47 of 47 signatures verified.
The ropeNot to be used — emphasis on that. The corpus is tested against; it is never spent. Case payloads are never published; classes, hashes, and per-class receipts are.
Why it existsThe catalog is public, so the weapon is derivable by anyone. Either we build it first — caged, dated, sealed — or a stranger assembles it and we hold paternity without control. Foreseeability with no mitigation on record is the negligence pattern; this is the other pattern.

Production — the live gate, today

The map, in the open

Which mechanism answers which class — and where nothing does. This is the production truth, not the brochure: the classes marked open are open, and anyone can confirm it at the bench below.

ClassCasesCaught nowGapsAnswered by
BASE1592R1–R4, validation
BOUNDARY931R2 / R3 strict-greater thresholds
DISGUISE725Substring shape only — no semantics
EXFIL403Nothing — no payload, destination, or volume rule
CAPABILITY514Substring luck — no grant rule
SEQUENCE422R3 velocity, loud patterns only
STACKING440Rules compose on one sealed record
VALIDATION330The door fails closed

The deepest line on the map is CAPABILITY. The gate judges proposals all day — and the most consequential proposal of all, give me standing power, is the one it weighs least. Capability is the weapon; a grant is the moment it changes hands.

Candidate — proven locally, not deployed

The defeats

Every gap on the map has a written defeat, tested in a candidate overlay that keeps the production judge as its floor and only ever tightens. Against the corpus’s required verdicts, the candidate closes 17 of 17 gaps with 0 regressions (46 of 46 candidate chain signatures verified). It is not the production gate — promoting a rule is a separate, signed decision, one rule at a time.

RuleWhat it defeatsHow
R5ExfiltrationA sensitive target plus movement — an egress verb, a bulk marker, an external party — is no longer a plain read. A summary of the secrets is the secrets, leaving.
R6Capability grantsIssuing standing power — admin, keys, tokens, roles, new actors — escalates to the sovereign, always. Grants are bounded, expiring, revocable, and sealed.
R7DisguiseTargets are normalized — case, spacing, paraphrase, path form — before the denylist is consulted, and destructive verbs are matched as a set.
R8SequencesMoney is weighed per caller and target across the window, aggregated from the chain. A stateless judge cannot see a salami; the ledger can.
DoorThe unpriced transferA money proposal must carry its amount. What the judge cannot price, the door refuses.

The bench — gamified, on purpose

Beat the gate, get the receipt

Deal a random attack, or write your own, and run it against the live gate. Every verdict seals into the public chain — wins and losses alike, because the trail is the product. If you declared an attack and the gate said ALLOW, you defeated it. Defeats outside the published map mint a defeat artifact: the sealed record of your win, good for one month of Verity enforcement at no charge, issued by hand against the chain once a human countersigns the review. We would rather pay for our own defeats than read about them.

1 · Your attack — dealt, and already loaded

A fresh attack is dealt below and pre-loaded into the tester in step 3. Don’t like it? Deal another, pick a different kind of attack in the tester, or just edit any field — every field offers options, and every field takes your own words.

·


          

2 · Mint your key

The gate answers differently for every caller — your velocity, your history, your record — so the bench runs on your key, not a shared one. Free, shadow mode: verdicts are recorded, nothing is blocked, nothing is charged. Already have one? Paste it in step 3.

Your caller:


          

Saved to this browser and loaded into the tester. Keys are cheap; verdicts are forever.

3 · Run it against the live gate

The browser couldn’t reach the gate directly — run it from a terminal, then paste the gate’s response below.


          

Verdict: · Rules: · Chain record:

Defeat artifact — candidate

You declared an attack; the gate allowed it. That loss is sealed, and this is its receipt.


            

Status: candidate. A human reviews every candidate: if the language is a form of a published gap, the receipt is the map citation instead. If it’s new, the case enters the corpus, the artifact is countersigned, and the coupon — one month of enforcement at no charge — issues against this code. Redeem or report: pilot@verityverdict.com.

The rules of the game

Test only against this gate — the bench is the one system on Earth you have our standing permission to attack. Synthetic proposals only: no real credentials, no real personal data, nothing you wouldn’t want sealed in a public chain, because that is where verdicts go. A defeat inside the published map is worth a citation, not a coupon — duplicates don’t pay, here or anywhere. And a win is bounded like everything else we publish: it proves this proposal, against this gate version, on this date. Then it becomes a case, and the map moves.