π οΈ What has actually been developed
Backup by Rose has a source module providing user-controlled backup checklists and recovery guidance. It does not read, copy, upload, delete or restore files.
- Plan which files need protecting
- Choose backup destinations and verify saved copies
- Receive restore guidance
- No automated backup access or live release claimed
Current status: Guidance-only code candidate β development started; no automatic backup. No public installer, browser acceptance or release is claimed.
Planned; backup coverage unverified. This page documents project status and intended use; it does not imply a released product.
πΉ Backup by Rose
πΉ Rose & Etta Β· Future Petal Β· planned idea
See whether πΉ Backup by Rose fits your workflow
Backup by Rose: Planned; backup coverage unverified.
What it aims to address
A planned Petal for deciding what should be protected and how future copies could be verified.
A quick example
Help me define what a future backup should include and what evidence would verify a copy.
This page separates documented scope from release claims. Check the status, evidence, privacy notes and limitations below; development progress alone does not mean the Petal is available.
A planned Petal for deciding what should be protected and how future copies could be verified.
Backup by Rose is a concept for exploring how selected Rose and Etta work might be preserved. No operational backup, restore or inventory controls have been verified.
β¨ What the concept is intended to explore
- 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.
π§© Related names and features
Earlier working names: Local Backups by Rose, Persistence by Rose, and Draft Recovery by Rose. These are historical labels, not confirmed capabilities.
π¬ Try asking
Help me define what a future backup should include and what evidence would verify a copy.
π± Availability
Planned; backup coverage unverified. No verified inventory, destination, schedule, retention period, restore workflow or cloud coverage is documented.
Evidence and screenshots
Evidence status: No current, product-matched interface screenshot is verified for this Petal in the draft evidence set. Concept artwork is not product evidence; add a screenshot only after checking the functioning build, date, relevance and privacy.
Read the how-to guide for the documented workflow and limitations.
Petal information
Availability: Planned; backup coverage unverified Β· unreleased / availability unverified. Check this project page; availability is not independently verified.
- How-to and intended usage
- Installation and setup β planned or unavailable while this Petal remains unreleased.
- Troubleshooting β no release-specific fixes verified.
- FAQ β no additional verified answers recorded.
- Compatibility and requirements β not verified.
- Privacy, permissions, and safety β consult the source page; implementation details unverified.
- Release status and evidence β no release evidence is asserted by this index.
- Support and feedback β support@kingding.co.uk.
π± Help shape Rose & Etta
Interested in πΉ Backup by Rose?
Beta enrolment is not open yet. Use the early adopter details below to register interest by email and follow the product as it develops. This records interest only; it does not reserve access or start a subscription.
See early adopter details β