Repository navigation
Contract the fields your metrics read, and check them where the data lands - #38
Merged
Merged
Conversation
h3qing
force-pushed
the
schema-drift-and-data-contracts
branch
2 times, most recently
from
September 16, 2026 08:26
a584ef9 to
e15abcc
Compare
An upstream change that breaks a query announces itself the same day. A change that only alters meaning says nothing: a new value in a status field, cents that become dollars, a column that starts arriving empty. The number moves and the query stays green. There is a newer form of the same failure: an AI assistant keeps notes about a field, the field changes, and the notes keep answering. This page contracts the handful of fields each metric reads, checks them where the data lands, and treats the assistant's memory as part of the contract. Sixteen references added.
h3qing
force-pushed
the
schema-drift-and-data-contracts
branch
from
September 17, 2026 03:18
e15abcc to
3089c04
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An upstream change that breaks your query tells you the same day. A change that only alters meaning tells you nothing: a new value in a status field, cents that become dollars, a column that starts arriving empty. The number moves and the query stays green. There is a newer form of the same failure. An AI assistant keeps notes about a field, the field changes, and the notes keep answering.
This page contracts the handful of fields each metric actually reads, and checks them where the data lands in your warehouse rather than in the producer's pipeline. A table lists what must stay true about each field and the check that fails when it stops being true, from
not_nullto a re-run of the hand-checked questions on closed periods. The assistant's memory is part of the contract and changes in the same commit as the field. The template carries the field list, the structural and semantic checks, the reaction plan, and the agent prompts.Files:
docs/modules/01-ai-data-quality/schema-drift-and-data-contracts.mdtemplates/01-ai-data-quality/schema-contract-control-plan.mdREFERENCES.mdllms.txt,CONTENT_BACKLOG.md,DECISIONS.md,docs/modules/01-ai-data-quality/README.md,templates/README.md