In spec, it passes.
Out of spec, it never leaves.
The shield is the layer between your agent and its tools: every action checked against a spec you define. Deterministic, auditable, versioned. In development — design partners test it early.
The two modes
Red mode — the scanner
Automated injection scans on your agent, continuously. Methods evolve around the clock — so does the scanner.
Blue mode — the runtime
The proxy in front of your tools: in spec → allow, out of spec → block + log. Deterministic, no LLM in the decision loop.
Declarative rules
Versioned in your repo. If we disappear, you keep everything — no black box.
Inspectable journal
Every allow/deny decision logged with its cause and provenance — the line that names where the intent came from.
Design partners
Early clients run the prototype on their stack at a preferential rate, in exchange for feedback.
For whom, when
- Teams that already ran a red team or diagnostic — the layer will deploy their conclusions
- Agents touching customer data or irreversible actions
- Those who want control without lock-in: readable rules in their repo
- Sign up to be notified at launch