Epilogue Template 1
Aftermath: [time later], [character] now [concrete changed state] because [climax consequence].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong epilogue extends the ending rather than replacing it, answers only the aftermath questions worth answering, and preserves enough openness that the story does not become a report on every character’s future.
Aftermath: [time later], [character] now [concrete changed state] because [climax consequence].
Ordinary-life test: Show [new normal] through [small action/detail] that would have been impossible before the story.
Perspective shift: From [new observer], reveal [consequence] without reopening the central conflict.
Epilogue audit: question answered [x]; why reader needs it [x]; new conflict introduced [none/minor/intentional].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].