📚 Backup by Rose — Master page

A planned Petal for deciding what should be protected and how future copies could be verified. 🌹

🎯 The job

A planned Petal for deciding what should be protected and how future copies could be verified. 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 which project files or conversation artifacts future coverage should include.
• Record destination and retention requirements before any implementation is promised.
• Specify what evidence would show that a future copy completed and can be read.
• Plan how any future restore would be reviewed and approved before it changes existing data.

🧪 Example

Help me define what a future backup should include and what evidence would verify a copy.

🛑 Boundaries and evidence

Recorded status: Planned; backup coverage unverified. 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.