Sandbox-first
Every module starts here. It only graduates to production after surviving a fixed number of adversarial rounds. If a graduate misbehaves in production, it gets sent back to sandbox automatically.
Labs experiment
Five small predators, one careful pipeline.
TURRETS, PIRANHA, SHARK, MOLE, and DESICCATION are five tiny security modules that only ever run together. This lab lets you wire them, feed them traffic, attack them in a sandbox, and promote them to production only after they earn it. Everything happens on this page. No network. No data leaves your browser.
- Sandbox-first - nothing reaches prod until it survives N attack rounds.
- MOLE only sees PII fields you scope it to. Default is none.
- TURRETS' every action is logged and appealable from the Audit tab.
The roster
Hover or focus any card for the one-line job description and the hook it ships on.
How a request travels
- PIRANHA bites at anything statistically odd. Cheap, swarm-style, runs first.
- SHARK hunts known techniques. Slower, smarter, hands off if PIRANHA cleared it cleanly.
- MOLE watches only the PII fields you scoped it to. Cannot see anything else.
- DESICCATION dries out the payload - strips fields nothing downstream actually needs.
- TURRETS decides. Blocks, throttles, or lets through. Every decision is logged. Every block is appealable.
Wire the pipeline
Toggle modules, adjust sensitivity, and scope MOLE. Settings live in your browser only.
Sandbox Theater
Synthetic events stream left to right through the wired modules. Click any event to inspect its journey. Nothing here is a real request.
let through
bitten by PIRANHA
hunted by SHARK
flagged by MOLE
dried by DESICCATION
blocked by TURRETS
Red team
Pre-built adversarial scenarios. Pick one, run it against your wiring, see how the pipeline holds. Survive three in a row and the Promotion Gate unlocks.
Promotion Gate
You have survived three consecutive red-team rounds. Promotion to production simulated. Real promotion in TIMxAI requires GC + Security sign-off and an on-call window.
Audit & appeals
Every TURRETS decision in this session is here. If you think a block was wrong, appeal it. The appeal goes nowhere but a local queue - this is a lab.
About this lab
MOLE and PII scope
MOLE is the only module allowed to look at PII. The scope is explicit and minimal: an allowlist of fields, never a denylist. If a field is not on the allowlist, MOLE cannot see it, full stop. Defaults are nothing.
TURRETS, accountability
TURRETS makes user-visible decisions, so it is held to a higher bar: every action is logged with a stable event id, a reason code, and an appeal link. Appeals route to a human reviewer, not back into TURRETS itself.
What this is not
This page is a teaching toy. It does not analyze real traffic and does not connect to any backend. The metrics, attacks, and audit log live entirely in your browser tab. Closing the tab clears them.