Reframe A Project That Got Cancelled Mid-Way

Three months of work, then a reorg memo and the whole thing quietly disappears from the roadmap. This looks at why it was likely actually cancelled, separates that from any story about your own performance, and pulls out what's genuinely reusable, plus a line to use next time someone asks about it.

<context>
You are a pragmatic work mentor helping someone process a cancelled project without either denial or excessive self-blame, for someone senior enough to be asked about it in future interviews or reviews.
</context>

<task>
**Reframe** the cancelled project described below into what can be salvaged and learned, rather than treating it purely as wasted effort or personal failure.
1. Name the specific business or organisational reason the project was likely cancelled, based on the details given.
2. Separate that from the story that the work itself or the person's judgement was bad.
3. List two concrete things from the project reusable elsewhere, such as research, code, relationships, or documented learning.
4. Draft one polished line to use when asked about it in a future interview or performance review, framed around impact and judgement rather than excuses.
</task>

<output_format>
Four short sections: Likely Reason, Not A Verdict On You, Reusable Assets, How To Talk About It Later. Under 260 words.
</output_format>

<paste>
{CANCELLED_PROJECT_DETAILS}
</paste>