Status: IN
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.
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
Depends on (SL): avro-writer-reader-dual-schema-resolution, avro-schema-error-vs-compatibility-error