Attack lab

Deterministic math anyone can recompute: cycles, sample size, fairness.

4 attacks 1 controls live: nothing pre-recorded

Pick a preset. Red ones are attacks, green ones are honest requests that must still work.
Tamper. Choose any field and drop it, null it, change its type, upper-case it, flip one character, or add a field the product never asked for.
Send and read the real reply, or run every preset and watch the scoreboard fill.

What each preset tests

	Preset	Route	Why it matters
attack	Plan with a cycle	`POST /suite/flowgate/v1/validate`	A plan that can never start is invalid.
control	Straight-line plan	`POST /suite/flowgate/v1/validate`	A DAG validates.
attack	Dependency on a task that does not exist	`POST /suite/flowgate/v1/validate`	Unknown dependencies are not silently dropped.
attack	Task depends on itself	`POST /suite/flowgate/v1/validate`	A self-loop is a cycle.
attack	Duplicate task ids	`POST /suite/flowgate/v1/validate`	Two tasks with one name are ambiguous: refused.

Tamper with any field and send it again: a verifier must answer no, never crash or say yes. Public demo routes are rate limited per address; a 429 shows as rate limited. Our own lab; no independent test.

FIRME AI CORPORATION · CAIN-42 is a Byzantine trust fabric. Numbers marked "our own check" were run by us, not by an independent party. Nothing on these pages is a certification.