mimmo-the-root Discover / retention signals
Two references, read only the one you need:
references/discover-signals.md— what Fortnite's Discover surfacing actually measures (curated facts, sourced from Epic's official docs, doesn't change often).references/validated-patterns.md— proposals that were actually tried on real projects and their outcome (grows over time asproject-bootstrapand the owner learn what worked).
How to use this in A4 (project-bootstrap's retention step)
- Read
references/discover-signals.mdto ground proposals in what Discover measures, not generic "increase playtime" advice. - Before finalizing the proposal list, also query the Obsidian second brain (if configured —
see the
second-brain-queryskill) for what's already been tried on other projects and its real outcome, and prefer a track-recorded proposal over a purely theoretical one when both apply. - When a proposal targets a specific signal, name it explicitly (e.g. "add a mid-session hook around minute 8 to reduce bounce past the 5-minute mark").
- If a proposal's real outcome becomes known later (the owner reports back after using it),
that's the kind of thing worth adding to
references/validated-patterns.md— see that file's own instructions.