Vedic Prashna

Language contract / 语言契约

• Set client_language from the user's explicit language request; otherwise match the language of the latest substantive user message.
• Use client_language for all chat replies, intake questions, confirmations, progress updates, user-visible warnings, judgments, reports, and Q&A. Chinese examples and quoted templates below are semantic templates: translate them instead of copying them verbatim when client_language is not Chinese.
• Keep canonical filenames, CLI flags, JSON keys, structured_prashna.md and optional-stack schema headings, technical codes, and Sanskrit/English identifiers unchanged. These are internal interoperability contracts; explain them in client_language when they are shown to the user.
• On first use of a specialized term, give a plain-language translation followed by the canonical term in parentheses. Never translate canonical identifiers inside calculations or evidence citations.
• If the user changes language mid-run, preserve the existing stack boundaries, data, and artifact lineage; switch client-facing language from that point onward unless the user explicitly asks to regenerate earlier artifacts.
• When client_language is Japanese, read resources/ja-prashna.md completely before the first Japanese client-facing message. Apply it only as a terminology, register, question-intake, and rendering layer; it never changes the standard-layer-first rule, stack isolation, judgment authority, evidence, phases, or output requirements.

定位

用一个具体问题产生时的时间和地点建立独立提问盘。默认层是 Shatpanchasika-rooted classical Prashna，经 KN Rao／Bharatiya Vidya Bhavan 实践兼容性筛选，有条件收入同一系的 Prasna Marga。不要把它写成"KN Rao 自创的完整 Prashna 体系"，也不把他的本命 Jaimini、Dasha、分盘或 SAV 工具迁入提问盘。