{"id":"avro-schema-evolution-handles-version-mismatch","text":"Avro schema evolution correctly handles writer-reader version mismatches through mandatory dual-schema resolution (writer schema parses wire bytes, reader schema shapes output), with clean separation between structural schema errors at parse time and compatibility errors at resolution time.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["avro-writer-reader-dual-schema-resolution","avro-schema-error-vs-compatibility-error"],"outlist":["schema-registry-no-compat-enforcement"],"label":"Two base beliefs about Avro's schema handling form a positive evolution story, gated on the schema registry accepting any schema without backward/forward compatibility checks — incompatible schemas can be registered and deployed, bypassing the resolution mechanism's design intent"}],"dependents":[],"metadata":{},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"avro-schema-evolution-handles-version-mismatch","truth_value":"IN","reason":"SL justification valid","antecedents":["avro-writer-reader-dual-schema-resolution","avro-schema-error-vs-compatibility-error"],"label":"Two base beliefs about Avro's schema handling form a positive evolution story, gated on the schema registry accepting any schema without backward/forward compatibility checks — incompatible schemas can be registered and deployed, bypassing the resolution mechanism's design intent","outlist":["schema-registry-no-compat-enforcement"]},{"node":"avro-writer-reader-dual-schema-resolution","truth_value":"IN","reason":"premise"},{"node":"avro-schema-error-vs-compatibility-error","truth_value":"IN","reason":"premise"}]}}