From LinkedIn · · 1 min
The release button lives somewhere else
Some teams keep prompts in a separate service, and the application loads whichever version is marked production. Marking another version as production changes the assistant without a code deploy.
By Olha Shevchenko. Audits production systems on AWS and Node.js.
An AI assistant's answers can change on a day when nobody deploys code.
My prompt history is in Git. That's where I'd look first if someone changed the instructions.
But prompts can live in a separate service, too. The application loads whichever version is marked production. Someone marks another version as production. The next time the application fetches it, the assistant gets different instructions.
No code change required. Potentially quite a different assistant.
I can see the appeal: you can update instructions without redeploying the application. That also makes the prompt dashboard a place for production changes. Which is where my reviewer brain starts paying attention.
I'd want to see how a new prompt gets approved, who can make it live, and whether logged answers record the version they used. If code changes need approval but prompt changes can go straight to production, the release process has a gap.
The release button just lives somewhere else.