yaront111

7 ms·

1.
by yaront111 8mo ago
That’s a sharp observation. You’re partially right CAP (our protocol) handles the structural canonicalization. We use strict Protobuf/Schematic definitions, so if an agent sends a messy JSON that doesn't fit the schema, it’s reje
2.
by yaront111 8mo ago
try this for security and scale cordum.io
3.
by yaront111 8mo ago
i just built Cordum.io .. should give u 100% deterministic security open sourced and free :)
4.
LangChain, AutoGen, CrewAI, Temporal: What breaks when you need governance?
1 points by yaront111 8mo ago|0 comments
5.
by yaront111 8mo ago
i built deterministic 100% solution cordum.io
6.
by yaront111 8mo ago
Thank u ! would love feedback and helping hand !
7.
by yaront111 8mo ago
Here is a 100% deterministic solution Cordum.io
8.
by yaront111 8mo ago
Exordex is a great tool for the CI/CD pipeline to test agents. Cordum is the Runtime Kernel that enforces those policies in production. Ideally? You use Exordex to test that your agent works, and Cordum to guarantee it stays safe.
9.
by yaront111 8mo ago
Great question. This is actually a core design principle of the Cordum Agent Protocol (CAP). It’s definitely a *structured rejection*, not a silent fail. Since the LLM needs to "know" it was blocked to adjust its plan, the kernel
10.
by yaront111 8mo ago
It is overkill for a demo. But for my production environment, I need an external safety layer. I can't rely on 'prompt engineering' when real data is at stake.
11.
Show HN: I built a firewall for agents because prompt engineering isn't security(github.com)
7 points by yaront111 8mo ago|7 comments
12.
by yaront111 8mo ago
Really appreciate the feedback to improve:)
13.
Show HN: I built a "sudo" mechanism for AI agents(github.com)
2 points by yaront111 8mo ago|2 comments