Version pinning
The practice of specifying and holding a fixed, exact model build rather than a general model name, so that the version you tested is the version you run and a vendor update cannot change your system's behavior without your knowledge. Version pinning is a precondition for reproducibility and for defending an answer after the fact.
Defined in 4 GAGE programs, which carry 5 distinct definitions of it. The wording above is taught in Certified AI Governance Professional (CAIGP).
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The practice of specifying and holding a fixed, exact model build rather than a general model name, so that the version you tested is the version you run and a vendor update cannot change your system's behavior without your knowledge. Version pinning is a precondition for reproducibility and for defending an answer after the fact.
The practice of specifying an exact, immutable version identifier for a dependency or data artifact, rather than allowing a system to automatically resolve to "latest," which closes the window an attacker would otherwise have to insert a newer, malicious version under the same name.
The practice of recording the specific Git commit hash at which a demo video or published artifact was produced, and noting it in the README. Version pinning creates an audit trail that prevents confusion when the code evolves after the demo is recorded.
Locking an AI process to a specific vendor model version rather than "latest," so a vendor's update cannot silently change your process's behavior without your knowledge.
The negotiated right to remain on a named model version for a defined period rather than being force-migrated, buying time for re-evaluation and redeployment; vendors resist indefinite pinning because serving old versions has real costs.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- Your lineage map under attack: the red team finds the gap you papered over · Adversarial Data Governance, Certified AI Data Governance Professional (CADGP)
- Prompts, context, and why the same model gives different companies different answers · Build Before You Govern, Certified AI Governance Professional (CAIGP)
- The AI contract: the clauses that protect you when the vendor's model fails · Shipping AI and Surviving the Incident, Certified AI Governance Professional (CAIGP)
- Process Governance and Continuous Improvement · Process and Operations Redesign, Certified AI Transformation Professional (CATP)
- Demonstrate, document, and defend: your first portfolio piece · Capstone: Build and Program a Simulated Mobile Robot, Foundations of Robotics and Physical AI
Where it shows up at work
A definition is where Version pinning starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Turns controls into enforceable obligations: data use, change notice, audit rights, incident duties, subcontractors, IP, exit and deletion.
One lesson on this page teach it as a primary outcome.
Designs decision rights, committees, intake, approval tiers and escalation so routine uses move and consequential uses get reviewed.
One lesson on this page teach it as a primary outcome.
Sets performance metrics, thresholds and review triggers after launch, and treats a model change, a vendor update or new data as a reason to re-check.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Vendor Risk Managerneeds it at depth
- AI Regulatory Counselneeds it at depth · 14 open postings this week
- Third-Party Cyber Risk Managerneeds it at depth
- Third-Party AI Risk Analystneeds working knowledge
- Chief AI Officerneeds it at depth
- Chief Compliance Officer, AI compliance editionneeds it at depth
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: GDPR Article 28; EU AI Act value-chain obligations; NIST AI RMF GOVERN; ISO/IEC 42001 Clause 5.
One interview question about it
Which contract terms would you insist on before a vendor's model touches customer data, and what happens when the vendor changes the model?
Asked of candidates for contract terms that allocate ai risk. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- Legal and paralegal work carries it as work you can show: Contract terms are your product.
- A law degree (JD, LLB or LLM), no AI work yet carries it as a claim to back up: Contract terms that move risk are a first-year subject.
- Model risk, credit risk and quantitative analysis carries it as a claim to back up: Performance monitoring thresholds are familiar.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.