Use two systems with one authority map
Studio and a repository solve different problems. Neither should silently shadow the other.
| Artifact | Recommended authority |
|---|---|
| Executable prompt or skill version | Studio asset ID and immutable version |
| Application and tool code | Code repository commit |
| Infrastructure and deployment | Repository plus deployment platform record |
| Test fixtures and deterministic checks | Repository or versioned test system |
| Evaluation datasets and judgments | Approved data system with version reference |
| Production mapping | Release record linking asset version, commit, model, tools, and target |
Avoid copy drift
Do not paste a production prompt into multiple repositories, notebooks, tickets, and chat threads without a declared authority. Store a stable reference and fetch or resolve the approved version through a controlled path. If a deployment needs a bundled copy, generate it from the authoritative version and record its checksum.
Frequently asked questions
Can Studio replace code review?
It can support asset history and approval, but application, tool, security, infrastructure, and dependency changes still require their normal review.
Can Git replace runtime lineage?
No. A commit does not show which prompt or skill version actually ran for a production output.
What should a release record link?
Link the Studio asset version, repository commit, model, tool and connector versions, tests, approvals, deployment target, activation time, telemetry, and rollback candidates.
Related guides
Official source
Source check: August 5, 2026.