Who Owns the Event Definition? The Registry Knows; the Org Doesn't
A compatibility check can block a breaking change. It can't name who's allowed to make one.
The event has a schema, a version, and a registry that enforces both. What it doesn't have is an owner who answers when a consumer breaks at 9 a.m.
The standards are arriving on schedule. Confluent's Schema Registry enforces compatibility modes so that, under backward compatibility, newer readers can still consume events written by older writers, and under forward compatibility, newer writers can produce events that older readers can still read. Separately, the Bitol project shipped the Open Data Contract Standard v3.0.0 in October 2024 and announced v3.1.0 on December 7, 2025, an incubation-level project under LF AI & Data, defining a contract's schema, quality, roles, and SLAs in one document.
Read the registry's own upgrade guidance and the ownership gap becomes a sequencing problem. Under backward compatibility, you must upgrade all consumers before you start producing new events. Under forward compatibility, you first upgrade all producers, then the consumers. Both instructions assume a single party can see every producer and every consumer of an event and choreograph them. In most orgs, no such party has been named, which is precisely why a standard now has a field for roles.
This is the quiet tell. A schema registry is a control that enforces a rule; a data contract is a document that records a decision. Buying the first and skipping the second is the streaming era's favorite move: the breaking change is blocked at the server, so everyone assumes the breaking change was governed. It wasn't. The registry knows the schema is incompatible. It has no idea who was allowed to change it, or who promised the team downstream that it wouldn't.
Watch for the day a producer flips compatibility to NONE to ship a deadline, or registers a v2 stream and quietly stops feeding v1. The compatibility check passes because someone turned it off, and the contract holds because no one signed one. The artifact that finally assigns an owner won't be the registry. It'll be the incident review that asks who approved this, and gets silence.
A schema registry enforces compatibility; it does not assign ownership. If you can't name the human who approves an event's schema change, you have a server, not governance.
Confluent Schema Registry enforces backward and forward compatibility between producers and consumers.
Registry guidance requires upgrading consumers before producers under backward compatibility, and producers before consumers under forward compatibility.
supports01Bitol released ODCS v3.0.0 in October 2024 and announced v3.1.0 on December 7, 2025, as an incubation-level project under LF AI & Data.
supports03A schema registry enforces compatibility rules but does not by itself assign a human owner or approver for an event's schema.
No notes yet. The margin is open.
Sign in to add a note. The margin is moderated — we keep it useful, not cruel.
An engineering convenience became a control point. A control point needs a controller.
Definition DriftA real standard for data contracts now exists. The argument it was supposed to settle has simply moved up a layer.
Owner MissingA right to access connected-product data arrives before anyone agrees what the fields mean.