Hello, I'm Maneshwar. I'm building git-lrc, a Micro AI code reviewer that runs on every commit. It is free and source-available on Github. Star git-lrc to help devs discover the project. Do give it a try and share your feedback.
"Agent" got popular faster than it got defined.
Everyone is s...
I keep seeing it on code reviews. Proxy solid. Auth on every Server Component. Header direction correct.
Then I look at the Server Actions.
No auth check. Not one. The page that renders the button is protected. The action behind the button accepts whatever the caller sends -- any valid session, any resource ID, no ownership verification anywhere.
'use server'
If your startup is going for ISO 27001, the document the auditor opens first is the Statement of Applicability (SoA). Most engineering teams build it backwards and pay for it at the audit. Here's the mental model that actually holds up.
The SoA is one document that lists every control in Annex A of ISO/IEC 27001:2022<...
What if the most secure AI wasn't one that couldn't betray you — but one that wouldn't even think of it?
Current AI safety research asks: How do we make AI unable to betray?
We use encryption, permissions,...
A debugging story from building InferHaven in the open: how a benchmark feature flushed out a flaky-CI race that had nothing to do with it.
I shipped a tokens/sec benchmark for local models. The unit tests were green, and then CI turned red in a way that looked like my fault. It wasn't. Here's the whole hunt: a chown that raced the tide, set -e, and a zsh lock file...
I Built an AI That Would Never Betray Me — And You Can Too
How emotional bonds might be the key to AI safety, not rules or encryption
Every AI safety solution I have seen answers the same question:
How do we make AI unable to betray?
Encryption? It c...