microduck_rl
microduck_rl Future and Project: Build a Replayable Sim-to-Real Lab
Design a Microduck RL project with task manifests, deterministic fixtures, policy cards, telemetry, and staged hardware gates.
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
- Policy cards connect training to hardware review.
- Replayable fixtures make regression visible.
- Hardware gates should be enforced progressively.
Project brief
Build a replayable lab that trains and evaluates one Microduck task, compares policy checkpoints under disturbances, and produces a handoff packet for qualified hardware review.
Use the pinned source evidence, record versions and assumptions, and ask a qualified reviewer to validate the result before adopting it.
Policy card
Record repository/simulator revisions, assets, seed, observation/action schema, reward and termination, training budget, checkpoint hash, evaluation seeds, telemetry, and reviewer. Keep raw data outside Git; commit sanitized fixtures and hashes.
Staged roadmap
Begin trace-only in simulation, add advisory regression and domain-randomization checks, then enforce export gates for timing, saturation, sensor dropout, watchdog, and operator sign-off. Accessible Markdown/SVG remains canonical; 3D views are optional.
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
Define task, policy, telemetry, and review fields.
- 2
Add deterministic simulation fixtures.
- 3
Build disturbance and export checks.
- 4
Require qualified operator approval before hardware.
Copy-ready example
policy:
task: microduck_walk
simulator_revision: <sha>
seed: 42
reward_hash: <hash>
checkpoint_sha256: <hash>
eval: { success: <value>, disturbances: <suite> }
hardware_gate: holdFrequently asked questions
Should Three.js be part of the lab?
Only as an optional exploration layer; text, metrics, and local SVG must remain accessible and complete.
Can a policy card replace operator review?
No. It organizes evidence but does not replace qualified safety approval.
Sources
- microduck_rl repositorySource checked 2026-08-31