# Translation Context Packet

Package source references, screenshots, user flow, product behavior, variables, constraints, terminology, evidence, and ambiguity decisions for translators.

## Usage note

Assemble this packet for the exact source version being translated and remove secrets, live personal data, and unnecessary production access. Context should help a translator understand the user’s moment and the product’s behavior, not overwhelm them with unrelated files. Resolve source defects before handoff or label each open question with an owner and release consequence.

## How to use this template

1. Lock the source version and map every asset or string ID to its user flow, state, placement, and owner.
2. Add safe annotated visuals, source references, product behavior, audience, terminology, and material claim evidence.
3. Explain variables, plurals, protected syntax, layout behavior, media, links, and localized dependencies.
4. Record ambiguities in a shared question log and resolve source defects before translation where possible.
5. Version the packet, notify translators of changes, and archive the approved context with review and release evidence.

## Blank template

### Packet overview

- **Project and packet ID:** [Stable identifier]
- **Packet version and date:** [Version and YYYY-MM-DD]
- **Source locale and version:** [Locale, commit, build, or file]
- **Target locales:** [List]
- **User audience and situation:** [Who, when, and why]
- **Content type and risk:** [Product, help, campaign, policy, or another]
- **Localization owner:** [Name and contact]
- **Source content owner:** [Name and contact]
- **Implementation contact:** [Name and contact]
- **Question deadline and release:** [Dates]
- **Access and privacy limits:** [Safe preview and prohibited data]

### Asset and flow manifest

- **Asset or screen ID:** [Stable reference]
- **Source file or URL:** [Location]
- **Annotated screenshot or preview:** [Safe reference]
- **Prior user step:** [What just happened]
- **Current state and behavior:** [What the product shows or does]
- **Available next actions:** [Controls and destinations]
- **Related strings or media:** [IDs]
- **Hidden or alternate states:** [Error, loading, empty, success, permission, or other]
- **Layout and accessibility context:** [Order, label association, caption, alt purpose]
- **Source evidence:** [For claims, numbers, or instructions]

### String context record

- **String ID and exact source:** [Enter]
- **Content role:** [Heading, label, button, status, message, metadata, or other]
- **Audience relationship and formality:** [Enter]
- **Meaning and intended outcome:** [Plain explanation]
- **Approved terminology:** [Termbase links]
- **Variables and sample render:** [Token, type, meaning, and example]
- **Plural, gender, or agreement behavior:** [Rules]
- **Protected syntax:** [Code, command, product name, filename, or URL]
- **Character or timing constraint:** [Reason and tested boundary]
- **Permitted adaptation:** [Examples, order, unit, idiom, or none]
- **Known ambiguity:** [Question and owner]

### Handoff and change control

- [ ] Screenshots and source files describe the same version.
- [ ] No live personal, confidential, credential, or secret data is exposed.
- [ ] Fragmented strings and token-order risks were reviewed with implementation.
- [ ] Claims, terminology, links, and related assets have usable references.
- [ ] Questions have owners, shared answers, and release consequences.
- **Question log:** [ID, question, answer, owner, date, affected strings]
- **Source changes after handoff:** [Before, after, reason, affected IDs]
- **Translator acknowledgment:** [Name and date]
- **Final packet approver:** [Name, version, and date]
- **Archive location:** [Enter]