πΉ Overview Β· π Instructions
Candidate Β· unreleased. Follow only controls confirmed in a supported build. Proposed steps are not proof that a feature is available.
π Auto-Correct by Rose β How to Use It
Give your AI a friendly nudge when it stops following your preferred rules.
πΉ Status: Candidate, internally labelled Etta. This guide distinguishes observed controls from proposed workflows.
π What is it?
Give your AI a friendly nudge when it stops following your preferred rules.
π Letβs get started
- Expand the Auto-Correct card
- Read the answer and identify a specific formatting or instruction problem
- Choose Send Correction if you want to submit a correction
- Optionally enable Auto Append Correction
- Check that your original message is preserved
- Review the next answer to see whether it improved
β¨ Give it a go
Correct a response that forgot your requested short bullet-point format.
πΈ Screenshots to put on the page
- π· Screenshot 1: Development screenshot showing Auto-Correct by Etta / Send Correction.
- π· Screenshot 2: Auto Append Correction toggle.
These are placement notes, not invented screenshot URLs. Add the actual approved website media links when available.
π‘ My little tips
- πΉ Start small and try one simple example first.
- π Check what actually happened rather than trusting a status label alone.
- πΎ Keep important work and settings saved before experimenting.
π Worth knowing
Customer-facing name is Auto-Correct by Rose. Automatic detection of memory degradation is a product goal, not proven by the screenshots.
π All done!
Thatβs it! Keep it simple, have a play, and let Rose do the useful bits. πΉ
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.
See the Auto-Correct by Rose evidence status on its description page.
Troubleshooting
- The Petal is not listed: check the availability label above and confirm the relevant candidate is enabled in your supported session.
- A control in this guide is missing: use only controls visible in your installed version. These steps describe the evidenced or proposed workflow; they are not a promise that every interface control is present.
- The result is unexpected: pause and inspect what changed before trying again. Keep the original work until the result is verified.
Auto-Correct: anticipated troubleshooting
These are planning notes for an unreleased concept, not verified controls or live support instructions.
- The correction control is missing: this is an internal candidate and the live catalogue has an Etta-branded entry; do not assume a public Rose control exists.
- The next answer repeats the problem: compare the specific correction with the new answer; do not assume a permanent preference changed.
- The correction is vague: describe one missed requirement and the exact desired result, then review any proposed revision.
Auto-Correct: common questions
Is this publicly released as a Rose Petal? No release is verified; the current draft labels it an internal candidate and notes the Etta catalogue mismatch.
Does a correction permanently edit instructions or memory? That behaviour is not established by the available evidence.
Frequently asked questions
Is this Petal released? Use the status shown on this page. Concept, planned, candidate and development labels do not mean a public release is available.
Are the steps exact for every installation? No. Follow the controls available in your supported build and the release notes for that build.
Installation, compatibility and availability
Release status: Candidate Β· unreleased / availability unverified. No installation steps or supported platform are provided unless a verified release is announced. This guide records the intended workflow, not an available control.
Setup: no verified installer, prerequisites, configuration or permission flow is documented here. Do not follow speculative installation steps.
Compatibility and requirements: not verified.
Troubleshooting
No release-specific faults or recovery steps are verified while this Petal remains unreleased. Check its availability first; if you think this page is wrong, contact support.
Frequently asked questions
Can I use this Petal now?
Availability is not verified; the status above describes the current evidence.
Does this page promise a release date?
No. It records the intended workflow and known evidence gaps.
Privacy, permissions and safety
Do not provide secrets or sensitive data to a concept workflow. Data handling, storage and permissions must be confirmed from an implemented build before release.
Release status and evidence
Status: Candidate Β· unreleased / availability unverified. This guide is not release evidence. Confirm availability on the Petal overview; no supported release is asserted here.
Support and feedback
Send a question, correction or suggestion to support@kingding.co.uk.
