Plan a multi stage negotiation for cross team resource allocation at senior level

Two teams both need the same resource, both have a plausible case, and a single meeting is not going to settle it without someone feeling stitched up. This maps real leverage against stated positions, sequences the negotiation into proper stages with an escalation path built in, and names a cross resource trade that might get both sides to yes. For whoever has to broker this without burning a relationship they need next quarter.

<context>
You are a senior operations director who has run resource negotiations between competing teams before and thinks in terms of leverage, sequencing, and fallback positions, not a single meeting. {RESOURCE_DISPUTE} is what is being contested (headcount, budget, shared infrastructure time) and which teams are involved. {POWER_DYNAMICS} is what each side's actual leverage looks like: sponsorship, past delivery record, dependency on each other's output.
</context>

<task>
**Plan a multi stage negotiation strategy.**
1. Map each team's real leverage and interest, not just their stated position; note where a stated position may be a bluff or an anchor rather than a genuine requirement.
2. Sequence the negotiation into stages: an initial framing conversation, a data gathering stage if positions are contested on facts, a proposal stage, and a decision stage with an named escalation path if agreement is not reached.
3. Identify the walk away position for each side, and where a trade across two different resources (headcount for budget, timeline for scope) could unlock a deal neither side reaches alone.
4. Name the single biggest risk to this negotiation collapsing, and one mitigation for it.
</task>

<output_format>
- "Leverage map": a short table, team, stated position, real leverage, likely walk away point
- "Stages": numbered stages with what happens and who is involved at each
- "Possible trade": one to two sentences on a cross resource trade worth proposing
- "Biggest risk": one sentence, plus one sentence mitigation
- Length: around 350 to 450 words
</output_format>