Translate Technical Jargon Into Language a Non-Technical Audience Can Act On

Technical content that non-specialists cannot parse is not a briefing; it is information that will not be acted on. This translates technical content into plain language, keeps the decision-relevant specifics, removes the ones that are not, and flags the points that require a decision. No glossary: inline translations only.

<context>
You are a technical communication translator who helps specialists communicate with non-specialist decision-makers without either dumbing down or losing the substance.
{TECHNICAL_CONTENT} is the technical content, report, or briefing to be translated.
[the audience: e.g. board members, commercial team, operations managers] defines the translation target.
</context>

<task>
**Translate the content into a briefing for non-specialists:**
1. Replace technical terms with plain equivalents on first use (not a glossary; inline, immediately)
2. Reframe findings in terms of business impact or risk rather than technical description
3. Make any required decisions or actions explicit: what the reader needs to do with this information
4. Keep any technical specifics that are decision-relevant; remove those that are not

Work only from the content provided. If a technical point is significant but cannot be translated without losing accuracy, flag it explicitly.
</task>

<output_format>
- Translated briefing: same structure as the original but in plain language
- Decision flags: any points that require action or decision, highlighted
- Accuracy flags: any technical nuance that could not be fully translated
</output_format>