This Page Tests an Ending; It Does Not Teach the Whole Ending System
The canonical Ending and Resolution pages own how endings are constructed. This page owns the final question: does this ending survive a closure stress test?
The stress test is:
Closure → Loose End Scan → Reader State → New-Risk Check → Stop.
Page Contract
This page owns: testing whether an ending is sufficiently closed and safe to submit.
This page does not own: resolution construction, reflective insight or generic “conclusion techniques”.
1. Test the Central Closure
Ask one direct question:
Has the main event that drove the composition actually reached a new stable state?
If the answer is no, do not add decorative reflection yet. The ending still has a structural problem.
2. Scan Only Load-Bearing Loose Ends
Not every detail introduced earlier deserves explicit closure. Focus on threads that affect the story’s logic.
| Thread | Does it need closure? |
|---|---|
| Main conflict | Yes |
| Decision consequence | Usually yes |
| Important relationship shift | If it changes the final state |
| Decorative object | Only if it was made causally important |
| Background detail | Usually no |
3. Test the Reader’s Final State
After the ending, can the reader answer:
- What changed?
- What consequence now holds?
- What relationship or state is different from the beginning?
- Is the story still relevant to the topic?
If the reader cannot reconstruct the new state, the ending may be emotionally expressive but structurally incomplete.
4. Run the New-Risk Check
Many weak endings are damaged by a late attempt to make them “more impressive”.
Before adding anything new, ask whether it introduces:
- a new character;
- a new conflict;
- a new timeline;
- a new moral claim unsupported by the story;
- a new image that needs explanation.
If yes, the addition may reopen the composition rather than close it.
5. “Link Back to the Introduction” Is Not a Mandatory Rule
A circular return can work when it reveals a changed state. It should not be treated as an official PSLE requirement or a compulsory ingredient in every ending.
Use it only when the return carries meaning.
6. Reflection Is Optional and Must Be Earned
If the story genuinely changed the character’s understanding, a brief reflection may belong. If the ending is already complete, a generic life lesson can weaken it.
Route reflection questions to the dedicated Reflection After Resolution page.
7. Do Not Invent a Fixed Conclusion Time
There is no need to present a fixed 10–15 minute conclusion allocation as an SEAB recommendation. Internal planning strategies can vary. The operational goal is to protect enough time to complete and safely check the whole response.
8. Use the Stop Rule
Stop editing when:
- the central event is closed;
- load-bearing consequences are recoverable;
- the reader can reconstruct the final state;
- remaining changes are preference rather than correction.
9. AI Use: Attack the Ending, Do Not Embellish It
During practice, eduKateAI can act as an adversarial reader: identify unresolved threads, ask what changed, or flag a new element introduced too late. It should not automatically append a moral or “powerful final sentence”.
The Ending Stress-Test Card
CLOSE — Is the main event actually resolved?
SCAN — Which loose ends are load-bearing?
READER — What final state can the reader reconstruct?
RISK — Does the proposed addition reopen the story?
STOP — End once the structure is sufficiently closed.
The Exit Condition
The stress test passes when the main event is closed, important consequences are recoverable, the reader understands the final state and further editing would add more risk than useful correction.