Question 560
A production agent loads its prompt from a shared editable text file and behavior changes without review. What should be used?
Explanation
Correct Answer
Source control creates traceable changes and enables exact prompt restoration when an unexpected regression occurs.
Incorrect Answers
The alternative, Maintain an explicit template-variable schema and compatibility tests, belongs to a different technical condition: Different application versions use incompatible prompt variable names after a merge. There the source-specific mechanism or proof is: Prompt source changes can break caller bindings even when the generated prose appears linguistically valid. The condition asked about here is: A production agent loads its prompt from a shared editable text file and behavior changes without review. A suitable correction is Store production prompt templates as version-controlled files in Git; the targeted justification or result is: Source control creates traceable changes and enables exact prompt restoration when an unexpected regression occurs.
Use short-lived feature branches and resolve merge conflicts through code review. That operation would be relevant if: Two analysts change one prompt file simultaneously and one overwrites the other's safety edits. Its corresponding reason or verification is: Branch-based integration makes conflicting instruction edits visible instead of silently losing required policy clauses. However the problem in this question is: A production agent loads its prompt from a shared editable text file and behavior changes without review. The requirement instead calls for Store production prompt templates as version-controlled files in Git; the question-specific check is: Source control creates traceable changes and enables exact prompt restoration when an unexpected regression occurs.
Compare the deployed prompt artifact hash against the approved Git release artifact. A separate source case supports that approach when: Security reviewers want proof that the current production prompt still matches its approved repository revision. The supporting rationale or observable result is: Hash verification detects manual or accidental changes to model-visible instructions after review and promotion. This question describes a different issue: A production agent loads its prompt from a shared editable text file and behavior changes without review. Address it through Store production prompt templates as version-controlled files in Git, with the required justification or evidence: Source control creates traceable changes and enables exact prompt restoration when an unexpected regression occurs.