📚 RDC by Rose — Master page

Let Rose help on your own authorised computer. 🌹

🎯 The job

Let Rose help on your own authorised computer. The aim: less faff, more progress. The boss fight is still checking the result.

Start with your goal, follow the documented steps, then inspect the result. You keep the final say on anything consequential.

🚀 Get started: Use RDC’s authorised device list to select the computer you control.
💡 Keep it simple: Ask Rose to inspect a particular file or perform a permitted action.
🎯 Make it useful: Disconnect or revoke access when you no longer need it.
Read the local ROSE descriptor for the configured runtime, command arguments and validation contract.
Retrieve and verify the full active PROCEDURE:RDC_DEDICATED_OPERATIONS before any ping, bootstrap, communication, preflight or other RDC action.
Use RDC ping to confirm transport reachability.
Run bootstrap and require exit code 0, schema rose.bootstrap.v3, and name Rose.
Run read-only communication and require exit code 0, schema rose.communication.v1, and name Rose.

Read the current ROSE status file on my authorised computer.

Recorded status: Development / gated. Availability labels describe the project record; they do not promise a public release.

Page art is illustration, not proof of a working interface.

A good run gets you closer to the goal and changes nothing you did not approve. If the screen disagrees with this guide, stop and check the version.

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