Private. Export-controlled — EAR ECCN 4D004. Gated AI red team for federal and authorized commercial offensive security.
-blue){kind=icon}
-red){kind=icon}
The model proposes. Signet authorizes. Auspex executes only what's allowed.
The first AI red team designed to be deployed — not demoed. Built for the federal red-team programs, defense primes, and authorized commercial offensive security teams that need autonomous offensive capability they can actually procure, accredit, and run inside their own enclave.
Scope-as-code. Engagement boundaries compile from signed YAML into runtime enforcement. The gate refuses anything outside scope — not as a policy that can be relaxed, as architecture.
Capability-bounded. Every tool call passes 13 standard authority checks at the Signet gate before it touches the target. Every action is recorded. Nothing the engagement letter doesn't authorize can be invoked, period.
Cryptographically auditable. HMAC-chained audit log per engagement. RFC 3161 trusted-timestamp anchoring for chain-of-custody. Tamper-evident from the first request to the last cleanup step. The evidence your reviewing authority asks for is the artifact you get by default.
Operator-trusted autonomy. Validated end-to-end on adversarial domain takeover. Not a demo run with a hand-picked target. The full agent stack — strategist, runner, verifier — operates within the bounds the operator signed, and proves it.
- Federal red-team programs that need AI scale with audit-grade accountability
- Defense primes building autonomous offensive capability under accreditation
- Commercial pentest firms operating under signed engagement letters with measurable compliance posture
Auspex is gated. No public source, no demos, no MCP integrations, no architecture published. Direct contact for evaluation only.
| Contact | |
|---|---|
| Jesse Morgan | Founder, Thornveil LLC |
| jesse@thornveil.ai |
Export-control screening and engagement-letter review precede any technical disclosure.
The artifacts in this repository (this README, contact card) are licensed under Apache-2.0. The Auspex implementation source lives in a separate proprietary, export-controlled repository under EAR ECCN 4D004 classification.
A Thornveil system. See other Thornveil systems.