Ac Data Contracts

Treating a data feed as an interface with obligations: schema and semantics in a contract, freshness and completeness guarantees, schema evolution and the compatibility rules that decide who breaks, ownership and escalation, quality checks at the boundary, and the written contract record. It explains how to specify a dataset's guarantees; it never certifies a dataset's correctness and never replaces profiling. Use when asking "data contract", "schema registry", "data freshness", "completeness SLA", "data quality checks", "who owns this pipeline", "breaking schema change", "data model change", "upstream data changed". Not for database schema migrations (ac-database-changes), not for event schema evolution between services (ac-event-driven-architecture), not for evaluating an external vendor dataset (ac-alternative-data).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 3c0f261a7d

Frequently asked questions

npx get-skill add jiayaoqijia/ac-data-contracts