Add the synthetic-town fixture contract for Records - #71
Merged
Conversation
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
1 participant
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.
What
Adds an additive, deterministic fictional-municipality fixture contract to Townlight Core while preserving the existing Brookfield testing API.
The canonical v1 fixture provides independently authored, fully synthetic Records data; explicit provenance, redistribution, watermark, no-network, and no-personal-data constraints; closed schemas and cross-reference validation; search, PII, workflow, and human-approval ground truth; per-artifact hashes and a pinned whole-fixture golden SHA; and adversarial privacy, provenance, reference-integrity, and tampering tests.
Why
Townlight Records needs reproducible system-level testing before real municipalities are available. Existing faux-Longmont files are not suitable for public redistribution, and live scraping is intentionally outside this tranche.
Verification
Scope and limits
No Longmont or Longmont Public Media content is copied or scraped. No production data is auto-seeded. This contract is the foundation for later desktop and Python cross-implementation golden tests; it does not by itself make Records beta-ready.