Translation/reframing adapts content between audiences by preserving semantic accuracy (what is true) while changing presentation (how it's communicated). Four fidelity types:
1. Semantic fidelity (MUST preserve): Core facts, relationships, constraints, implications remain accurate
2. Tonal fidelity (adapt): Formality, emotion, register change to match audience expectations
3. Emphasis fidelity (adapt): What's highlighted vs. backgrounded shifts based on audience priorities
4. Medium fidelity (adapt): Structure, length, format change for different channels/contexts
Example: Technical incident postmortem → Customer status update
Original (Engineers): "Root cause: race condition in distributed lock manager under high concurrency (>5000 req/s). Null pointer dereference when lock timeout occurred before callback registration. Fix: added CAS operation with retry logic, deployed canary to 5% traffic, monitored for 2 hours before full rollout."
Translated (Customers): "What happened: Service slowdown on Jan 15, 2-3pm affecting checkout for some users. Root cause: Timing issue in our system under high traffic. Status: Fixed, monitored, and fully deployed. Prevention: Added safeguards to prevent similar timing issues."
What changed: Technical detail reduced, jargon removed, impact/status emphasized, customer concerns prioritized (what happened, is it fixed, will it happen again). What preserved: Timing, affected functionality, root cause category, resolution status.
Translation/reframing（内容翻译与重构） 指在受众间调整内容时，保留语义准确性（核心事实）同时改变呈现方式（沟通形式）。包含四种保真类型：
1. Semantic fidelity（必须保留）: 核心事实、关联关系、约束条件、隐含信息需保持准确
2. Tonal fidelity（可调整）: 语气、情感、语体需调整以匹配受众预期
3. Emphasis fidelity（可调整）: 内容的突出重点与背景信息需根据受众优先级调整
4. Medium fidelity（可调整）: 内容结构、篇幅、格式需适配不同渠道/语境
示例：技术事件复盘→客户状态更新
原文（面向工程师）： "Root cause: race condition in distributed lock manager under high concurrency (>5000 req/s). Null pointer dereference when lock timeout occurred before callback registration. Fix: added CAS operation with retry logic, deployed canary to 5% traffic, monitored for 2 hours before full rollout."
转换后（面向客户）： "事件说明：1月15日2-3点服务响应缓慢，影响部分用户结账流程。问题根源：高流量下系统出现时序问题。当前状态：问题已修复，且完成全量部署并持续监控。预防措施：已添加防护机制避免同类时序问题再次发生。"
调整点： 移除技术细节与行话，突出影响与状态，优先关注客户关切点（发生了什么、是否已修复、是否会再次发生）。保留点： 事件时间、受影响功能、问题根源类型、解决状态。