How to read these presets
A preset narrows the review surface without pretending the platform changed underneath.
- Start with the narrowest believable surface for the journey you are checking.
- Move to the wider baseline only when adjacent routes materially affect the result.
Platform preset
Use this when you need the broadest route inventory, account edges, and release rehearsal coverage in one pass.
- Use this when route adjacency, account edges, and release-rehearsal coverage all matter in one pass.
- Expect a higher noise floor: it is broad on purpose, not the cleanest way to isolate one narrow problem.
Publication demo
Use this for editorial discovery, detail-page reading, and embedded update capture around articles.
- Focus on list-to-detail continuity, reading comfort, and restrained conversion support.
- Remember that the narrower editorial view can hide issues that only appear in the wider shell.
Catalogue demo
Use this for browse-to-detail journeys where taxonomy, support content, and retention prompts all need to work together.
- Review browse-to-detail continuity, taxonomy depth, and supporting content together.
- Treat this as a route rehearsal for browsing journeys, not as a substitute for the full baseline.
Conversion demo
Use this when you want the smallest route set that still proves value messaging, trust, and the update capture flow.
- Keep attention on the homepage update module and the primary capture flow.
- Use this preset to prove the action cleanly, then widen the scope if adjacent routes materially affect the result.
What the presets do not change
Presets change review context, while capabilities still decide route access, shell links, and seeded depth.
- A capability changes behaviour. A preset changes review context.
- Keep the capability contract separate from the demo shortcut and the seeded depth behind it.