Project Comparison

Use comparison workflows to identify:

• Missing keys
• Locale gaps
• Inconsistent copy between product surfaces

Comparison Dimensions

• Coverage: which locales are incomplete
• Consistency: same key, conflicting phrasing across projects
• Freshness: keys changed in one project but not in related projects

Suggested Review Process

1. Select two related projects
2. Compare shared namespaces (auth.*, dashboard.*)
3. Export mismatch report
4. Create follow-up tasks for missing or inconsistent keys

Release Gate Recommendation

Run comparison before each release candidate to reduce copy regressions.

Pair this with scheduled exports for periodic quality checks.