POLICY CONSISTENCY
Public claims should change together when product reality changes.
Consistency checks compare current public declarations across policy/architecture contracts. They do not replace legal review, security review, accessibility testing or editorial judgment.
PASS
accounts-not-live
Change trigger: Account/auth launch.
PASS
personalization-not-live
Change trigger: Saved or personalized smell-profile launch.
PASS
recommendations-not-live
Change trigger: Public recommendation feature launch.
PASS
privacy-no-personal-search-profile
Change trigger: Personal search history/profile or personalized ranking.
PASS
rights-no-blanket-license
Change trigger: Publication of an explicit data/content license.
PASS
source-corrections-explicit
Change trigger: First public correction notice.
PASS
runtime-budgets-clean
Change trigger: Architecture budget increase or interactive runtime addition.
PASS
translations-not-live
Change trigger: First translated/localized public route.
/data/policy-consistency.json
JSON ↗Machine consistency report
Cross-contract checks and change triggers.