🪄 Backup by Rose — How-to

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

Recorded status: Planned; backup coverage unverified. Availability labels describe the project record; they do not promise a public release.

🚀 A practical workflow

1. List the files or conversation artifacts you would want a future backup plan to cover. This draft does not scan or inventory them.
2. Record destination, retention and access requirements as open design questions; no destination or retention policy is verified.
3. Specify what evidence would prove a future copy completed and can be read.
4. Describe how a future restore would be reviewed and tested on a separate copy before changing existing data.
5. Keep originals in place; this page provides no backup or restore control and confirms no existing copy.

🧪 Try this

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

🧯 If the result looks wrong

Stop. Keep the original. Compare the result with your request; don’t press retry and hope the goblins have learned manners. See Troubleshooting for Petal-specific checks.

Use these steps only if the matching controls exist in your build. A planned feature is not a hidden quest item.

🌹 Page art is decorative; it does not show the product UI.