feat: enforce regulated content boundaries - #3
Merged
Conversation
What changed: - Added conservative regulated and YMYL inference from bundle category, title, aliases, and tags. - Backfilled explicit professional-review boundaries on 323 public registry records. - Made enrichment add inferred risk metadata and canonical validation reject detected risk signals without it. - Added inference regression tests to the public repository validation workflow. - Ignored generated Python bytecode artifacts. Why: - Consequential legal, medical, financial, employment, privacy, security, safety, and compliance content must not rely on editors remembering a manual warning. - Explicit metadata gives the website a stable, reviewable professional-reliance boundary for every detected public record. Verification: - Automatic inference tests passed. - Canonical validation completed with 0 errors and 18 pre-existing relationship warnings. - All 277 public compliance bundles have explicit risk metadata. - No public record with an inferred risk signal is missing content_risk metadata. - Semantic registry review found only 323 risk additions and four truthful word-count refreshes. Notes/Risks: - Inference is intentionally conservative and may display a not-reviewed boundary on some tool or operational pages whose use can affect consequential decisions. - The 35 excluded draft records are not backfilled until they become publication candidates.
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.
Summary
Verification
content_riskSEO impact
No sitemap, robots, canonical, or indexability-policy changes.