Self Motivation treats review logic as part of the public product. Readers should be able to see what route a page is trying to solve, why it belongs here, and when it should hand off instead of pretending every routine problem is motivational.
What gets checked before publication or refresh
- Published guides are expected to show a visible route purpose, correction path, and trust-page parity.
- Planning advice should stay inside weekly reset, mental reset, and friction-reduction scope rather than drifting into body-state claims.
- When a page changes the next step a reader should take, the update should be visible instead of hidden in a silent rewrite.
Public route types
- Weekly Reset Guide
- Habit Friction Audit
- Mental Reset Note
- Checklist Page
- Newsletter Landing
- Trust Page
- Update Stream Page
Duplicate and hidden-fallback review
- Legacy support pages, stale route shells, and duplicate trust surfaces should not stay crawlable just because they still return 200.
- Newsletter, homepage, updates, and trust routes should point to the same public structure instead of relying on shadow copies.
- Cross-domain handoffs are allowed only when the paired page solves the user problem more directly than the local route.
How scope boundaries are enforced
- Planning and follow-through guidance stays separate from therapy, medical care, and body-state recovery advice.
- If the bottleneck is really sleep, pain, low energy, panic, or another health-state issue, the page should hand off instead of making the local reset stricter.
- Broad generic motivation filler is removed rather than re-labeled as strategy.
Corrections and updates
Material fixes stay visible when a route target, trust page, or planning boundary changes the reader decision. Silent rewrites should not hide a changed handoff or duplicate cleanup.
Where ownership lives
Use Author / Team for public ownership and Editorial Policy for the site-wide rules on scope, monetization separation, and corrections.