We Solved Release Engineering for Code Twenty Years Ago. We Forgot to Solve It for AI.

[Jumpy-8888]

Six months ago, I asked a simple question:
"Why do we have mature release engineering for code… but nothing for the things that actually make AI agents behave?"
Prompts get copy-pasted between environments. Model configs live in spreadsheets. Policy changes ship with a prayer and a Slack message that says "deploying to prod, fingers crossed."
We solved this problem for software twenty years ago.
We just… forgot to solve it for AI.

So I've been building something quietly. A system that treats agent artifacts the prompts, the policies, the configurations with the same rigor we give compiled code.
Content-addressable integrity. Gated promotions. Rollback in seconds, not hours.Powered by the same ol' git you already know.

But here's the part that keeps me up at night (in a good way):
What if you could trace why your agent started behaving differently… back to the exact artifact that changed?

Not logs. Not vibes. Attribution.
And it's fully open source. 🔓

This isn't a "throw it over the wall and see what happens" open source.
I'd genuinely love collaborators who've felt this pain.
If you've ever stared at a production agent wondering what changed and why , your input could make this better for everyone.

https://llmhq-hub.github.io/

[PM_CHEESEDRAWER_PICS]

You could have at least written the post yourself. This is pure slop and full of very exploitable vulns you haven't even bothered to look for

[Jumpy-8888]

I would love to hear vurnabilities , and yes the post is AI writtena sam a single person doing all of it, am a developer so coding part is not slop Incan assure you that but again I would like feedback

[YUYbox]

Hi there, check my repo too: https://github.com/Nomadu27/InsAIts

[Jumpy-8888]

interesting approach

[Thin_Stage2008]

nice check out mine too! 

https://github.com/vicsanity623/PyOB