lesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contractslesson 3 of 5 · schema drift and dataset contractsschema drift and dataset contracts
Mid-quarter, the upstream app starts sending your label-critical churned field as the strings "yes"/"no" instead of booleans. Your contract fires on every batch. What's the right response?