DID
Decentralized identifiers. Who is this agent? Cryptographic binding to keys and lineage.
Your humans have paper trails. Your AI agents don't. Wrap any LangChain agent in three lines — every action becomes signed, hash-chained, independently verifiable evidence.
THE PROBLEM
AI agents are starting to move money, make trades, and handle procurement. But right now there's no way to prove what they actually did. MCP handles tool connections. A2A handles messaging between agents. AP2 handles payments. But nobody handles proof that the agent actually followed its rules. That's what we built.
Until now.
SIX PRIMITIVES
Together, these turn “policy” from a promise into a proof.
Decentralized identifiers. Who is this agent? Cryptographic binding to keys and lineage.
What will it do — and won’t do? Signed, immutable constraints. Only narrowable, never loosened.
Verifiable credentials. Prove identity and compliance without revealing internals.
Every action logged. Tamper-evident. Audit trail that anyone can verify.
Same inputs, same result. Independent, deterministic verification—no trust in the verifier.
Skin in the game. Violations are costly. Stake at risk aligns behavior with commitments.
HOW IT WORKS
SEE IT FAIL CLOSED
TWO-TIER GUARANTEE
Middleware runs in a TEE. Policy bypass is prevented inside the enforcement boundary (TEE + attestation assumptions).
Assumptions & threat model: We assume the TEE is uncompromised and correctly attests its identity. The enclave intercepts all agent actions before execution; forbidden actions never reach the host. If the enclave is compromised, an attacker could bypass enforcement — attestation lets you verify which software is running. See the Spec for details.
Stake at risk. Slashing on breach. Rational agents don’t violate when the cost exceeds the gain.
WHY NOBULEX
| Guardrails / policy engines | Proof-of-Behavior (Nobulex) | |
|---|---|---|
| Enforcement | Best-effort; can be bypassed | Signed commitments; pre-execution middleware |
| Verification | Trust the operator | Third-party verifiable; anyone can audit |
| Consequences | Policy violation = incident | Tamper-evident proof; cryptographic evidence of breach |
REGULATORY DEADLINES
Every major AI compliance framework requires tamper-evident audit trails. Regular logs won't pass.
June 30, 2026
Colorado AI Act
Accountability requirements for AI systems making consequential decisions. First U.S. state-level AI law.
August 2, 2026
EU AI Act Article 12
Requires tamper-evident automatic event logging for high-risk AI systems. Penalties up to €15M or 3% of global revenue.
November 2026
NAIC AI Evaluation
Nationwide AI evaluation tool for insurance. Carriers must prove agent compliance across every claim touched.
WORKS WITH
AWS AgentCore
MCP-native — auto-discoverable in Agent Registry
Microsoft AGT
Proof layer for governance toolkit
Google A2A
Behavioral attestation for Agent Cards
LangChain
Drop-in compliance callbacks
TRACTION
FOR DEVELOPERS
import { createDID, parseSource, EnforcementMiddleware } from '@nobulex/core';
// 3 lines to add proof-of-behavior enforcement
const agent = await createDID();
const spec = parseSource(`covenant MyAgent { permit read; forbid write; }`);
const mw = new EnforcementMiddleware({ agentDid: agent.did, spec });
PRICING
EU AI Act Article 12 · Colorado AI Act · NIST AI Agent Standards Initiative
Free
$0
For testing & evaluation
Team
$99/mo
For teams shipping AI agents
Enterprise
Custom
For regulated industries