An admin console on the Build Your Own AI Platform track. Admins need to see versions, gates, quotas, and the off switch. They do not need a shell on the trainer. Dangerous buttons require confirmation and an audit row.
This lesson assumes you already worked through Billing and showback.
The idea in practice
Every promote, rollback, and quota change writes who did it.
A concrete check
goal = {
'track': 'Build Your Own AI Platform',
'lesson': 'An admin console',
}
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
An admin page that can delete a tenant with one click and no log. 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
List four admin actions and which ones write an audit row. All of them should.
Self-check
- Say An admin console 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.