nobulexdev

4 ms·

1.
by nobulexdev 7mo ago
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 g
2.
by nobulexdev 7mo ago
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
3.
by nobulexdev 7mo ago
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/no
4.
by nobulexdev 7mo ago
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 a
5.
by nobulexdev 7mo ago
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&#x27
6.
by nobulexdev 7mo ago
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 indepe
7.
by nobulexdev 7mo ago
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 wit
8.
by nobulexdev 7mo ago
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 e
9.
by nobulexdev 7mo ago
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 pl
10.
by nobulexdev 7mo ago
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, d
11.
Show HN: I'm 15. I mass published 134K lines to hold AI agents accountable(github.com)
6 points by nobulexdev 7mo ago|23 comments