Three passes
Rereading should not be chaotic. It works better as a small analysis ritual.
- First pass: what was clear immediately.
- Second pass: what became clearer later.
- Third pass: which one step is still relevant.
archive
rereading
Revisit a scroll
An old scroll can become more useful after a day, week, or month when the user returns with a question for themselves, not fate.
User need
The user wants to understand what stayed alive after time passed.
Calm promise
Give a rereading format: what to highlight, what to compare, what to let go.
Archive as value
The archive makes a paid product not a one-time screen, but a personal library of recurring themes.
- The scroll should be easy to reopen.
- It needs date, method, and short summary.
- Never expose private data in share cards.
Gentle nudges
- An old answer can be reread without a new payment.
- Mark recurring words, not only cards.
- Save one action after each reread.
What to avoid
- Do not lock archive without reason.
- Do not replace reread with a new checkout.
- Do not promise the old scroll must match events.
QA checklist
- Clear path to account/readings exists.
- Journal prompt exists after reread.
- Archive is explained as paid-product value.