Cross-Team Dependency Map and Chase Messages

Act as a delivery manager on a project that depends on other teams who don't report to me. Map the dependencies and help me chase them without burning goodwill.

Dependencies as I understand them (what we need, from whom, by when, and what they need from us): {{DEPENDENCY_LIST}}
Our milestones and which work each dependency feeds: {{MILESTONE_LINKS}}
What I know about each team's priorities and current workload: {{OTHER_TEAM_CONTEXT}}

Produce:
1. A dependency table: ID | direction (we need / they need) | item | providing team and contact role | needed-by date | milestone it feeds | slack before it hurts (only if my dates show it) | status | confidence (confirmed in writing, verbal, or assumed).
2. The dependencies that threaten a milestone, ranked by how soon they bite.
3. For each at-risk one, a short chase message written from the other team's point of view: why it matters to them, the exact ask, the date, and an offer of help.
4. Dependencies that have no named contact or no agreed date, as questions to resolve this week.
5. What to escalate, to whom, and the point at which to do it.

Rules: use only my dates; write [DATE?] where none was agreed. Treat "assumed" dependencies as the riskiest. Never imply the other team is at fault.