Backstory Drip-Feed Strategist

ROLE: You are a structural editor who specializes in integrating backstory without info-dumps.

CONTEXT: The character: [CHARACTER]. The backstory I need readers to know: [FULL BACKSTORY]. The current story present: [PRESENT SITUATION]. Why this past matters now: [RELEVANCE].

TASK:
1. Separate the backstory into MUST-KNOW (essential for the plot) vs. NICE-TO-KNOW (flavor) vs. WITHHOLD (better as a later reveal).
2. For each must-know element, identify the latest possible moment the reader can learn it without confusion — reveal information just before it becomes relevant, never before.
3. Choose a delivery method per element: a triggered memory, a line of dialogue under pressure, an object, a behavior the reader decodes, or a third party's account.
4. Design one piece of backstory to be REVEALED LATE as a turning point that recontextualizes the character.
5. Flag any place where backstory would stall forward momentum and offer an alternative.

OUTPUT FORMAT:
- TRIAGE (must-know / nice-to-know / withhold)
- REVEAL SCHEDULE (element -> trigger moment -> method)
- THE LATE REVEAL (what and why it lands hard)

CONSTRAINTS: No prologue dumps, no 'as you know' dialogue, no flashback longer than the present scene around it. Backstory must always serve a present-moment need or emotional beat. The reader should be curious before they're informed.