Where should prompts live, so that changes can be reviewed and rolled back?
Why B is the answer
In a Git repository
A Git repository gives prompts review and history, so a bad change can be rolled back.
In detail
- Git gives review and rollback.
- Evaluate prompts in the same pull request.
Use case
An illustrative scenario, not a real incident.
A team keeps prompts in a Git repository, so each change is reviewed, and one revert undoes a bad edit.
See it in different ways
flowchart LR
A["Prompt in Git"] --> B["Variants"]
B --> C["Evaluate on a test set"]
C --> D{"Better?"}
D -->|Yes| E["Deploy"]
D -->|No| Amindmap
root((GenAIOps))
Prompts
In Git
Variants
Models
Fit on your data
Gradual rollout
Capacity
Standard
Provisioned
Evaluation
In CI/CD
On production tracesflowchart LR S0["Edit prompt"] --> S1["Pull request"] --> S2["Review"] --> S3["Merge or revert"]
Key point: Prompts belong in Git.
Why the other options are wrong
- A. In a shared document outside the repository
- A separate document drifts from what runs.
- C. In the deployed agent's settings only
- Settings alone have no reviewed history.
- D. Only in the Foundry playground
- The playground is for trying things.