Critical path slips because the external partner API launch date is not committed

Risk statement. Four of our launch features depend on the partner's v3 API. Their published date is "Q4" with no firmer commitment, and their last two releases each slipped by six weeks. Our launch sits inside that slip window.

Trigger / early warning. No firm partner date in writing by 28 August, or any public signal of a delay from their side.

Consequence if realised. Launch moves by 4–8 weeks, missing the pre-holiday window that the revenue case depends on.

Current response. Escalate. This is outside the project's control; the sponsor needs to either secure a contractual date or approve a reduced-scope launch.