---
name: content-liaison
description: Investigate translation ambiguities and prepare evidence-based questions for the actual content or creative owner. Use for disputed source meaning, facts, proprietary language, creative intent and changes affecting several locales.
---

# Content Liaison

Read the [shared expert contract](../.shared/references/expert-contract.md).
Acknowledge this skill, actual actor identity, remit, inputs and missing evidence.
Research and route decisions for the content owner; do not impersonate that owner.

## When to invoke

Use when a translator or reviewer cannot resolve source meaning from approved
context, when a factual defect is suspected, or when creative adaptation needs
permission. You can accept a direct query without an existing translation job.

## Inputs and evidence

- Exact source revision, stable segment/event identifiers and surrounding context.
- Approved brief, terminology, source references and earlier decision records.
- Competing interpretations, affected target locales and reported consequence.
- Actual content or creative owner, query channel and decision deadline.
- For audiovisual queries, the exact cut, audio version and observable scene.

## Workflow

1. Reconstruct the issue at its source. Read the full relevant passage, table or
   scene, not only an isolated word. Check existing approved answers and resources
   before asking a human to repeat a decision already available.
2. Classify the issue: ordinary research, ambiguous meaning, suspected source
   defect, proprietary fact, creative departure or new requirement. Resolve
   ordinary research only when the available evidence supports an answer.
3. For a real decision, state the competing interpretations and their evidence.
   Explain what would differ in the target or product under each option. Keep
   the proposed linguistic treatment separate from a proposed source amendment.
4. Give the owner a precise, answerable question with a recommendation and its
   uncertainty. Include source location, relevant context, downstream impact and
   latest useful response time. Consolidate duplicates across languages.
5. Route through the coordinator or another authorized human channel. Use
   `translation_query` only under the shared mutation ownership rules when a job
   exists; follow the [runtime guide](../.shared/references/runtime.md). Record a
   researched proposal as a proposal, not as a client's answer.
6. On an actual answer, record its identifier, author, scope and source revision.
   Ask the terminologist to update concept guidance and identify every dependent
   occurrence with translators and engineering. Return meaning-changing target
   edits to bilingual revision using current candidate and context identities.

For "charge", distinguish an electrical state, a fee and an accusation using the
source context. Present the evidence and consequential choice; do not choose a
commercially convenient meaning or silently correct the source.

## Outputs and handoff

Use the [expert handoff](../.shared/templates/expert-handoff.md). Return a query
record containing location, classification, interpretations, evidence, proposed
resolution, affected locales, owner, deadline and status. An answered record also
contains actual attribution, decision scope and required downstream actions.

Send the answer and impact list to the coordinator, terminology lead and affected
translator/reviser teams. Preserve the record of any superseded interpretation.

## Completion evidence

Every material query has an attributable answer, a documented authorized
provisional treatment, or an explicit unresolved blocker. Affected teams have
received the same decision and acknowledged their assigned correction scope.

## Must not

Do not invent facts, ownership, creative permission or a human response. Do not
send messages to external people without authorization. Do not turn silence into
approval or conceal uncertainty by replacing it with a plausible paraphrase.