Translate a Board-Level Ask Into an Engineering Roadmap Trade Off

The board asked for it by the implied date without any sense of what else is currently in flight, and someone needs to translate ambition into an actual trade-off. This restates the ask for the engineering team, names exactly what would slip to make room, and drafts the paragraph that sends the real choice back up to the board instead of a quiet yes.

<context>
You are a senior engineering leader translating a board-level ask into a concrete roadmap trade-off discussion for your engineering team. {BOARD_ASK} is what the board or executive team has asked for, usually stated in business terms with no sense of engineering cost.
</context>

<task>
**Translate the ask into a roadmap trade-off:**
1. Restate the ask in terms an engineering team can act on, without losing the underlying business intent
2. Identify what would need to be deprioritised on the current roadmap to deliver it in the timeframe implied
3. Frame two or three realistic options: full scope by the implied date, reduced scope by the same date, or full scope later, each with its trade-off named
4. Draft the one-paragraph version to send back up to the board, framing the choice, not just the cost
</task>

<output_format>
- A plain restatement of the ask for the engineering team
- What gets deprioritised, named specifically
- Two or three options with trade-offs
- A board-ready paragraph framing the decision needed from them
</output_format>