π Obvious by Rose β Master page
Stop obvious observations from becoming another to-do list. πΉ
π― The job
Stop obvious observations from becoming another to-do list. The aim: less faff, more progress. The boss fight is still checking the result.
βοΈ How the approach works
Start with your goal, follow the documented steps, then inspect the result. You keep the final say on anything consequential.
β¨ Product-specific scope
- Identify routine next actions
- Suggest action rather than repeating the problem
- Avoid ceremonial reminders and trivial questions
- Respect permission gates before doing anything consequential
π§ͺ Example
Find the next safe step and explain exactly what can be actioned now.
π Boundaries and evidence
Recorded status: Early idea; scope overlaps other Petals. Availability labels describe the project record; they do not promise a public release.
Page art is illustration, not proof of a working interface.
β How to judge a good result
A good run gets you closer to the goal and changes nothing you did not approve. If the screen disagrees with this guide, stop and check the version.
πΉ Page art is decorative; it does not show the product UI.
