A target lifecycle governs changes to prompts, model configurations, and retrieval configurations from draft through testing to active, then deprecates the replaced version. It keeps untested changes out of production while preserving an audit trail. section 8.2
A production-oriented lifecycle separates experiment metadata from artifact ownership:
- Register a target by referencing its name and version in the owning Model Service or Data Service rather than duplicating artifact content. section 8.2
- Run the target against an evaluation dataset and attach an EvaluationSummary containing overall, per-metric, and test-case results. section 8.1
Prompt-version promotion
Register a new prompt version in the Model Service, register the same name and version as a PROMPT experiment target, describe the intended change, and run evaluation against the candidate and current version. Compare quality scores before promoting the candidate. section 8.2
