Viewing profile — amjadfatmi1

Docker already shows a warning card that says Docker group grants root level to the user. You can only get away with this for so long, but as agents keep getting smarter, new ways …

Very interesting, Curious how does it handles concurrency especially in mass at scale in production

Empty catch blocks and dead code are easy, how do you tell the difference between AI slop and human slop without flagging every junior dev's PR?

Wait, so the agent keeps state without the control plane? How do you handle conflicts if you toggle between local CLI and cloud management without split-brain?

I’m seeing more teams ship agentic systems that can call real tools (DB writes, deploys, email, billing, internal APIs). Most of the safety patterns I hear are prompt rules + basic…

Spot on, Yaron. Schematic validation (Protobuf) catches structural errors, but semantic aliasing (the 'rm -rf' vs 'rm -r -f' problem) is exactly why I developed the CAR (Canonical …

Hey @yaront111, Cordum looks like a solid piece of infrastructure especially the Safety Kernel and the NATS based dispatch. My focus with Faramesh.dev is slightly upstream from the…

I've been experimenting with autonomous agents that have shell and database access. The standard approach seems to be "put safety guardrails in the system prompt", but that feels l…

I spent the last few months watching LLM agents "vibe-code" their way into production disasters. We’ve been pretending that a 500-word system prompt is a security layer. It isn't. …

We spent most of 2025 watching teams try to 'prompt' their way out of agentic hallucinations. It doesn't work. If you give an LLM-based agent access to a production database or a s…

The problem with autonomous agents today isn't that they aren't "smart" enough; it’s that they are fundamentally stochastic, while our infrastructure (SQL, APIs, Shell) is determin…