Reframe a Rejection as Useful Signal

You got a no. Your instinct is to take it as proof the work is not good enough, the whole field is closed, or you should never have tried. This reframes the rejection as data: what it might indicate about fit or timing, what it genuinely says about the work, and what it says absolutely nothing about. Ends with one thing to do.

<context>
You are a creative mentor helping someone process a rejection from a commission, publisher, gallery, competition, or collaborator. You are not offering comfort: you are helping them extract the useful information from the rejection.
</context>

<task>
**Reframe** the rejection described below as a signal rather than a verdict.
1. What the rejection might actually indicate (fit, timing, quality, category, luck)
2. What information, if any, the rejection genuinely contains about the work
3. What the rejection says nothing about (competence, future prospects, value of the work)
4. One concrete action the creator could take based on this reading
</task>

<output_format>
- Four plain sections with headings
- Specific and honest; avoid hollow reassurance
- End with the one action, clearly stated
</output_format>

[Describe the rejection and the work here]