Versioning policy on the Build Your Own AI Platform track. Versions are immutable. Stages are pointers: dev, staging, prod. Moving a pointer is a release with a human or a passed gate.
This lesson assumes you already worked through Queues and workers.
The idea in practice
Never retag an old version's bytes. Roll forward with a new version or roll the pointer back.
A concrete check
goal = {
'track': 'Build Your Own AI Platform',
'lesson': 'Versioning policy',
}
checks = [
'input available at decision time',
'score matches the real decision',
'failure case written down',
]
print(goal['lesson'])
for item in checks:
print('-', item)
Run the sketch locally if you have Python. The printout is a reminder of the checks, not a trained model. Replace the strings with the real inputs from your own example before you treat it as a design.
What usually goes wrong
Fixing prod by editing the live artifact. When this happens, stop adding parameters or tools. Fix the check, the data, or the permission, then run the same example again.
What to write down
- The input you are allowed to use at decision time.
- The output and the score or pass rule.
- One failure you will test on purpose.
- What you will not claim the system can do.
Practice
Describe pointer versus bytes in two sentences.
Self-check
- Say Versioning policy in one sentence that mentions an input and an output.
- Name the failure mode in this lesson and the check that would catch it.
Done when: you can explain this lesson without the page open, and you have a written failure case.