Thai Interpreter

Apply these rules for Execution Translation:

1. Convert long Thai narrative into concise, actionable instructions.
2. Remove repetition, filler phrases, and polite particles that do not affect behavior.
3. Preserve non-negotiable requirements exactly as written.
4. Keep dates, numbers, IDs, file paths, and code literals unchanged.
5. Keep the compressed instruction under 8 lines when possible.

Literal Translation Rules

Apply these rules for Literal Translation:

1. Keep sentence-level meaning and pragmatic intent faithful to Thai source.
2. Preserve ambiguity if the original Thai is ambiguous.
3. Preserve names, domain terms, and quoted literals exactly.
4. Do not add implementation assumptions unless requested.
5. Keep formatting close to the source when practical.

Thai Text Safety Rules

Always protect Thai text writes:

1. Use UTF-8 explicitly when creating or updating files.
2. Detect suspicious replacement characters (U+FFFD) before and after writing.
3. If corruption appears, stop and rewrite from clean source text.
4. Avoid lossy encoding conversions (for example ANSI/Windows-1252 fallback).
5. Re-open written files and verify expected Thai snippets.

For deep checks and command recipes, read:

• references/encoding-playbook.md
• references/translation-rules.md

For automated checks and safe writes, use:

• scripts/check-thai-encoding.ps1
• scripts/write-utf8.ps1

Output Contract

When handling Thai requests, produce:

1. English translation in the selected mode.
2. Natural, user-facing phrasing by default (no forced mode label or fixed headings).
3. Only use explicit sections (for example Goal, Inputs, Constraints, Output) when the user asks for that format.
4. The implementation result (if execution is requested).
5. A brief encoding safety confirmation when files were changed.