🪄 RDC by Rose — How-to
Let Rose help on your own authorised computer. 🌹
Recorded status: Development / gated. Availability labels describe the project record; they do not promise a public release.
🚀 A practical workflow
- Select the authorised device in RDC and use the device ID returned by RDC.
- Read the ROSE descriptor for the configured runtime, command arguments and validation contract.
- Retrieve and verify the full active RDC operations procedure before ping or any other RDC action.
- Confirm transport with RDC ping. This confirms reachability only.
- Validate ROSE with bootstrap and read-only communication, using the descriptor's schema and identity requirements.
- Run preflight with the complete original request verbatim.
- Report connected only after every required result succeeds; otherwise state the exact failed operation and result.
🧪 Try this
Read the current ROSE status file on my authorised computer.
🧯 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.