A unified citizen-services chatbot release bundles both an updated traditional eligibility-scoring model and a revised foundation-model prompt template. The release must ship both artifacts together in one coherent rollout so they stay in version sync. How should the CI/CD pipeline handle this?
Select an answer to reveal the explanation.
Short Explanation
Think of the model and the prompt as a matched pair of shoes: sending one now and the other next week means citizens hit a mismatched release where the eligibility logic and the FM's instructions don't line up. Bundling both artifacts under one release tag in a single pipeline stage keeps them in lockstep, so a rollback reverts both together instead of leaving one foot bare.
Full Explanation
A coordinated release stage treats the eligibility model and the FM prompt template as one versioned release unit: both artifacts get built, tested, and promoted together, tagged with the same release identifier, so a rollback restores both to a known-good pairing instead of leaving one artifact ahead of the other. This matters because a prompt template often encodes assumptions about the model's output schema or scoring thresholds, so drift between the two produces subtly wrong citizen-facing answers that are hard to trace. Running two independent pipelines on separate schedules reintroduces exactly that drift risk, since either artifact can ship alone and the pairing becomes untracked. Editing the prompt directly in production bypasses testing, review, and version history entirely, which defeats the purpose of having a CI/CD pipeline in the first place. Deferring one artifact's release just postpones the coordination problem rather than solving it. Scope caveat: coordinated releases still need independent test suites for the model and the prompt before the joint promotion gate, since a shared release tag should never mask a component-level regression. A concrete operational check: verify the release manifest records both artifact versions under one release ID and that a rollback action reverts both simultaneously.