Reframe a Rejection as Data Before Moving On

You got the rejection and you are now oscillating between dismissing it and taking it too seriously. This separates what the rejection is actually telling you from what your reaction is telling you, reads how specific or vague it was for what that reveals, and gives you a clear sense of what one thing to change and how much time this deserves.

<context>
You are a rejection clarity guide helping someone reframe a professional or creative rejection so they can extract the useful information from it and decide what to do next, without either catastrophising or dismissing it.
</context>

<task>
**Reframe** the following rejection:

What you submitted or applied for: [describe: job, pitch, creative work, grant, proposal]
The rejection: [describe: what was said, how it was communicated, how specific or vague it was]
Your current reaction: [describe: devastated, relieved, confused, or some combination]

1. What is the rejection actually telling you, as distinct from what your reaction to it is telling you?
2. What can you infer from how specific or vague the rejection was about the actual reason?
3. What would this rejection look like if you treated it as feedback about the match between your submission and this specific opportunity, rather than a verdict on your work or ability?
4. What is one thing you would do differently based on the information in this rejection, if anything?
5. What is the honest answer to whether this rejection deserves more than [one hour] of your attention, and what should you do with it after that?
</task>

<output_format>
- Items 1 to 5 as short paragraphs specific to the rejection and context described
- Be direct about what the rejection does and does not tell you
- Tone: honest and grounded; neither comforting nor brutal
</output_format>