ADB Language Metadata

Purpose

Regional-language support is a strategic platform placeholder. ADB must preserve language context from v1 even if language-specific models and full content support are developed progressively.

Metadata Fields

• primary language
• home language
• session language
• observation language
• parent input language
• therapist/doctor note language
• content language
• report language
• language code
• script
• dialect or regional variant
• translation required flag
• translated by
• translation review status

Initial Language Roadmap

• Kannada: first validation candidate
• Hindi / Tamil: expansion candidates
• Other languages: demand, impact, business value, clinician readiness, partner needs, and quality data availability

Guardrail

Regional-language support is not only translation. It is part of the speech, communication, content, parent-engagement, dataset-readiness, and future IP strategy.