microduck_rl
microduck_rl Security and Operations: Keep Simulation and Hardware Safe
Govern robot assets, checkpoints, telemetry, control interfaces, operator approvals, and incident recovery.
What you will learn
- Map environment, simulator, and runner
- Run a reproducible simulation
- Identify sim-to-real gates
Before you start
- Basic Git and command-line usage
- Comfort reading a project README
You can explain the project, run its documented first step, and decide what to verify before adopting it.
Key takeaways
- Simulation credentials and hardware controls are different trust zones.
- Watchdogs and stops must be independent.
- Telemetry and checkpoints need retention and incident plans.
Protect assets and data
Robot CAD/assets, sensor traces, checkpoints, and videos may be sensitive. Isolate workers, restrict access, encrypt storage, and keep credentials out of configs and logs.
Use the pinned source evidence, record versions and assumptions, and ask a qualified reviewer to validate the result before adopting it.
Constrain actions
Training code should not reach hardware by default. Separate simulation, export, and control networks; require allow-listed interfaces, actuator limits, watchdogs, and operator approval for trials.
Recover
Monitor divergence, crashes, runaway actions, disk growth, and stale checkpoints. Rehearse stop, revoke, quarantine, restore, and deletion with an independent emergency stop.
Use the pinned source evidence, record versions and assumptions, and ask a qualified reviewer to validate the result before adopting it.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Inventory assets, interfaces, credentials, and owners.
- 2
Isolate simulation and hardware networks.
- 3
Gate export/control with limits and approvals.
- 4
Monitor, stop, quarantine, and restore.
Copy-ready example
simulation worker -> bounded policy
export -> reviewed adapter + limits
control link -> watchdog + emergency stop
incident -> stop/revoke/quarantine/restoreFrequently asked questions
Can a policy process own the emergency stop?
No. Use an independent, qualified stop mechanism controlled by the robot safety system/operator.
Should checkpoints be public?
Only after reviewing asset licenses, telemetry privacy, and potential misuse.
Sources
- microduck_rl repositorySource checked 2026-08-31