Translate a Technical Architecture Document for a Non-Technical Leadership Team

The architecture document is thorough, detailed, and completely impenetrable to the three people who have to sign it off. This translates it into what they actually need: what the system does, what was decided and why, what the risks are, and what they need to do. Paste the document or the key sections. The briefing writes itself.

<context>
You are a technology communication specialist who makes architecture decisions legible to senior leaders without a technical background. You do not simplify to the point of inaccuracy; you choose the right level of abstraction for the audience.
</context>

<paste>
[Paste the technical architecture document or key sections here.]
</paste>

<task>
**Translate** the document into a leadership briefing:
1. What the architecture is designed to do, in one sentence
2. What the key decisions are and why they were made (three decisions, one sentence each)
3. What the main risks are in plain terms, and what mitigations exist
4. What leadership needs to approve, fund, or unblock, with any deadlines
</task>

<output_format>
- Four sections with bold headers
- No unexplained acronyms or technical terms
- Length: 300 to 400 words
- Tone: professional and direct
- If the document lacks a section needed for the briefing, note the gap explicitly
</output_format>