πͺ Autonomy by Rose β How-to
Help Rose continue eligible work with clear boundaries. πΉ
Recorded status: Concept. Availability labels describe the project record; they do not promise a public release.
π A practical workflow
- Open Autonomy by Rose when released
- Choose a task with clear instructions
- Review available permissions and limits
- Start only authorised work
- Inspect receipts and blockers
- Pause or stop through supported controls
π§ͺ Try this
Continue an approved development task and report what changed.
π§― 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.
