One True Name: How Data Contracts Keep Systems Honest

Episode six of our recommender deep-dive leaves the algorithm's brain and explores its plumbing. When a basketball game ends, three systems fire—editorial publishes a recap, video publishes highlights, scoring publishes the final score. Each speaks a different schema. How do they become one unified event the feed can rank? Through data contracts: written promises between teams about what data flows and when. Joey explores the mechanics using Earthsea's concept of true names—and what breaks when those contracts fail. The recommender doesn't crash. It quietly learns the wrong thing. And that's worse. 00:00:00 - The Plumbing Problem: Three Systems, One Event 00:03:01 - Earthsea and True Names: The Le Guin Metaphor 00:08:10 - What Breaks in the Sports Feed 00:11:41 - Silent Failure: When the Plumbing Lies 00:13:12 - Feature Stores and the Model --- Sources & further reading: • Chad Sanderson and Adrian Kreuziger, *An Engineer's Guide to Data Contracts — Pt. 1*, Data Products Substack, 2022-10-05 — — contract definition, contracts as code, CI enforcement, FORWARD mode.: https://dataproducts.substack.com/p/an-engineers-guide-to-data-contracts • Bitol / LF AI & Data, Open Data Contract Standard README (v3.2.0 at check) — — definition, version, license, sections (also https://bitol-io.github.io/open-data-contract-standard/latest/).: https://github.com/bitol-io/open-data-contract-standard • Confluent, Schema Evolution and Compatibility — — modes, BACKWARD default and rewind rationale, upgrade order.: https://docs.confluent.io/platform/current/schema-registry/fundamentals/schema-evolution.html • Apache Kafka, Introduction — — events, partitions, per-key ordering, retention.: https://kafka.apache.org/intro • Confluent, Kafka Message Delivery Guarantees — — at-least-once default, idempotent producer, transactions.: https://docs.confluent.io/kafka/design/delivery-semantics.html • AWS, Kinesis Data Streams Terminology and concepts — — shards, partition keys, 24h default retention.: https://docs.aws.amazon.com/streams/latest/dev/key-concepts.html • AWS, Handle duplicate records — — producer vs consumer retries, embedded primary key.: https://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-duplicates.html • Tyler Akidau, Streaming 101: The world beyond batch, O'Reilly Radar, 2015-08-05 — — event vs processing time, skew, watermarks.: https://www.oreilly.com/radar/the-world-beyond-batch-streaming-101/ • Akidau et al., The Dataflow Model..., PVLDB Vol. 8, 2015 — — late/retracted data, correctness-latency-cost trade-off (listing only; full PDF not read).: https://research.google/pubs/the-dataflow-model-a-practical-approach-to-balancing-correctness-latency-and-cost-in-massive-scale-unbounded-out-of-order-data-processing/ • Martin Zinkevich, Rules of Machine Learning, Google for Developers — — skew definition and causes, Rule #29.: https://developers.google.com/machine-learning/guides/rules-of-ml • Del Balso and Hermann, Meet Michelangelo: Uber's Machine Learning Platform, Uber Engineering, 2017-09-05 — — feature store, shared training/serving pipeline.: https://www.uber.com/blog/michelangelo-machine-learning-platform/ • Feast, Point-in-time joins — — point-in-time correctness, backfill leakage.: https://docs.feast.dev/getting-started/concepts/point-in-time-joins • All fetched on 2026-10-15. This podcast episode was fully generated by AI — research, script, voices, and production. Built with Claude, Piper TTS, and automated pipeline tooling.