nobulexdev

You’re correct. The cryptographic chain proves “this middleware has processed this action and has recorded it,” not that the enforcement logic itself was correct or that the code running was what you think it was. Those are both different guarantees and I have been conflating them.

On “nothing too special about doing this with LLMs,” also fair. The primitives (policy enforcement, audit trails, non-repudiation) aren’t new. The bet is that AI agents will need these at a scale and standardization level that does not exist yet, and having it as a composable library matters when every framework (LangChain, CrewAI, Vercel AI SDK) is building agents differently. But the underlying cryptography isn’t novel.

That is exactly the direction I'm heading based on feedback from this thread. The core primitives (action-log, verifier, covenant DSL, parser) as a small, auditable package. Everything else — c2pa, otel, langchain, compliance adapters as a separate layer that builds on top.

You are right that auditability of the system itself is the goal. Its very hard to trust a trust layer you can't easily inspect. Appreciate you digging deep into the code.

Based off of all the feedback here, I have built a quick demo that shows the multi-party use case on why cryptography matters when a third party needs to verify compliance independently:

https://github.com/nobulexdev/nobulex/blob/main/demo/two-par...

Run it: npx tsx demo/two-party-verify.ts

Three steps: operator creates a covenant, claims compliance and then a regulator verifies the cryptographic proof without trusting the operator. That is the core of what Nobulex does. Everything else is tooling around this pattern. Appreciate the pushback, as it helped clarify what actually matters.

Very fair question. If you control the whole stack with your agent, your middleware and your logs, then cryptography doesn't add much. You already trust yourself.

But, it matters when there are multiple parties. An enterprise deploys an agent that can handle customer data. The customer wants proof the agent has followed the rules. The regulator wants proof that the logs were not just edited after an incident. Without cryptographic signatures and hash chains, the enterprise can just say "trust us." With them, the proof is independently verifiable.

It's just the difference between "we followed the rules" and "here's a mathematically verifiable proof we followed the rules." For internal use, it's an overkill. For anything with external accountability, that targets the point.

On "why not a CLI tool / smart contract,” for single-agent, single-system setups, you are completely right. Nobulex is for when a third party has to verify compliance independently across systems. But the current examples don't make that clear enough. On the code, yes, heavily AI-assisted. I designed the architecture, AI helped implement it. I am 15 and in school, no team. The project has been through many iterations over several months, not one month. On "solution in search of a problem,” maybe. What would you consider worth solving in this space?

Good question.

The Enforcement and verification serve for a different audience.

Enforcement will protect you as it stops your agent from doing something it shouldn't. Verification protects everyone else, as it lets a third party independently confirm that the enforcement actually happened, without trusting you. You say "my agent followed the rules," while the regulator says "prove it." The hash-chained logs and signed covenants are the proof. Without verification, it's just your word.

Your Gmail CLI is doing the right thing with manually restricting what the agent will be able to do and logging actions. Nobulex is more of the generalized version of that pattern.

The difference: your CLI controls one agent on one tool with rules you have hardcoded. Nobulex gives you signed, immutable constraints that third parties can verify independently. The logs are hash-chained so nobody (including you) can tamper with them after the fact. And the constraints are the cryptographically bound to the agent's identity.

If you are truly the only one who needs to trust your agent, your approach works fine. Nobulex matters when someone else needs to verify what your agent has done, a regulator, a customer and a counterparty.

You're right with the 134K point. The actual cryptographic kernel (covenant building, verification, hash-chaining) is just about 3-4K lines. The rest are just adapters, plugins and test harnesses. I should lead with that number. With enforcement, the covenant itself isn't the enforcement. Middleware intercepts tool calls before the execution and blocks the violations. But you're right that this only works for constraints you can express as rules. "No external calls" and "rate limit 100/hour" are enforceable. "Don't discriminate" is not — that's a fundamentally harder problem and I'm not pretending that it solves it. The small trustable core advice is truly good and probably what I should focus on next. Thank you.

Fair catch. Those are internal notes from all of my earlier iterations of the project. I should have cleaned the docs folder before pushing to a new repo. Removing them now. On the age thing: those notes have been written when I was just planning to let the work stand on its own. I had decided to include it because I figured being upfront is better than people finding out later and feeling misled. Either way, the code is the code — 134K lines, 6,115 tests, all on npm. Judge it on that.

I am 15 (sophomore in high school). I have been building Nobulex for the past several months, including 60 npm packages, 134K lines of TypeScript and 6,115 tests.

The problem: AI agents are making real decisions for loans, trades, hiring, diagnostics with zero cryptographic proof of what they have done or whether they followed any rules. The EU AI Act requires tamper-evident audit trails by August 2026. Nobody has infrastructure for this.

Nobulex is three things:

Agents will be able to sign behavioral covenants before they act (cryptographic commitments — "I will not do X")

Middleware enforces those covenants at runtime as violations are blocked before execution

Every action is logged in a hash-chained, merkle-tree audit trail that anyone can use and verify independently

The quickstart is 3 lines: const { protect } = require('@nobulex/sdk'); const agent = await protect({ name: 'my-agent', rules: ['no-data-leak', 'read-only'] });

npm install @nobulex/sdk

Everything is MIT licensed and on npm under @nobulex/*. Site: https://nobulex.com

Would love feedback on the architecture, the covenant model, or anything else. Happy to answer questions.