Agent frameworks built for developer productivity treat audit as an afterthought — observability dashboards, token counts, latency traces. None of this satisfies a regulator asking 'prove to me that this AI recommendation was grounded in verified data and approved by an accountable human.'
The Vauban Agent SDK makes cryptographic accountability the default, not the exception. Every run produces a RunProofCertificate: a signed, Poseidon-hashed decision chain anchored on-chain, independently verifiable without access to Vauban infrastructure. HITL (Human-in-the-Loop) approvals are themselves cryptographically signed, so the approval chain is as auditable as the action chain. Brain Protocol integration means every knowledge entry consulted by an agent carries its own provenance — no hallucination can silently enter the decision chain without leaving a cryptographic trace.
Supply chain: every published SDK tarball is Sigstore-signed with a Rekor transparency log entry. You can verify the build provenance, the SBOM, and the OIDC identity of the signing workflow before deploying to a regulated environment.
Key capabilities
- → RunProofCertificate per agent run — signed, on-chain-anchored, independently verifiable
- → HITL approval with cryptographic receipts — accountable human-in-the-loop by design
- → Brain Protocol memory integration — every knowledge retrieval provenance-tracked
- → MCP-native — compatible with any MCP server in the Vauban ecosystem and beyond
- → Supply-chain-signed via Sigstore — SBOM + Rekor bundle per published tarball