Aller au contenu principal

Separate Build, Release, And Run For AI Changes

Apply the Twelve-Factor build-release-run separation to AI app deployment inputs.

ai-app-deployment5 min read

AI deployment gets safer when every production answer can be traced back to a named release. The separation Twelve-Factor's build-release-run split is still relevant for AI apps. The build stage packages code and dependencies. The release stage binds that artifact to environment-specific config. The run stage executes the selected release. AI adds more release inputs, but it does not remove the need for separation. Prompts, model IDs, retrieval indexes, eval thresholds, tool allowlists, and safety rules are often changed through dashboards. That is convenient in the moment and expensive later. A production answer is the product of all those inputs…

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Nous contacter