Module · MLOps Engineer
Data Quality & Labeling
Contracts that fail the build, and labels that humans can actually agree on.
TOPIC 01
Contracts & Checks
State what the data must look like, and let the pipeline fail when it does not.
What you'll practice
- Write a Data Contract — guided · beginner
- Report the Quality of a Run — practice · intermediate
A command you'll meet
cat ~/data/contracts/users.yamlA contract nobody enforces is a wish. Open the task below for the full walkthrough.
Hands-On Tasks in This Topic (2)
Write a Data Contract
A contract states the columns a table must have and the rules those columns must follow. Write the contract for the users table.
Report the Quality of a Run
A contract produces a verdict. Write the report that says how many rows were scanned, how many broke the contract and whether the run may continue.
TOPIC 02
Labeling & Ground Truth
Labels are a human product - define them, review them, and measure agreement.
What you'll practice
- Write Labeling Guidelines — practice · intermediate
A command you'll meet
cat ~/data/labels/guidelines.mdIf two annotators disagree, the model will not save you. Open the task below for the full walkthrough.