---
title: "Contract-triad governance for the registry"
slug: "contract-triad"
type: recipe
locale: en-US
canonical: "https://www.coremodels.io/recipe/confluent/contract-triad"
updatedAt: "2026-08-27T01:42:16+03:00"
---

# Contract-triad governance for the registry

Avro, JSON Schema and Protobuf in one governed estate: coverage gaps stay visible.

Govern a mixed-format registry honestly: Avro subjects parse fully (records, enums, optionality, cross-subject references), JSON Schema subjects parse at depth 1 (properties, required, enum, format), and Protobuf subjects are inventoried with the protobuf-unparsed finding on every audit: the coverage gap never fades from memory. The loop closes with registry-ready .avsc generation from the governed model.

## Articles

- [Anatomy of a Governed Streaming Estate: How the Confluent Connector Maps Subjects into the Graph](https://www.coremodels.io/connector/confluent/t5-deep-dive)
- [The Meaning Gap Under Every Kafka Topic](https://www.coremodels.io/connector/confluent/h1-need)