Proposal: URML (substrate-neutral robot intent) capability-manifest mapping for micro:bit v2 — and a refinement of URML's existing microbit_edu fixture

[idoco2003]

Hi @microbit-foundation team,

Proposing a URML v0.1 capability-manifest mapping for the BBC micro:bit v2 over microbit-foundation/micropython-microbit-v2. URML (Universal Robot Language, Apache-2.0) is an open spec for substrate-neutral robot intent.

URML's microbit_edu manifest fixture has been the canonical URML pattern for the micro-class robot since RFC-0018 — engagement at the Foundation level closes the loop upstream. The fixture sketches the micro:bit v2 manifest mapping (nRF52833 main MCU + KL27Z interface MCU, MicroPython firmware-language, accelerometer + magnetometer + microphone + speaker + LED matrix + buttons); your view on its refinement carries unusual weight for downstream educational deployments.

This is proposal-only, posted as part of URML's Move #13 outreach (15 engageable RFCs in this wave).

Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0172-microbit-foundation-outreach.md

Questions worth microbit-foundation maintainer input on:

1. Manifest fixture refinement. URML's existing microbit_edu fixture sketches the micro:bit v2 manifest mapping. What fields would the foundation refine / add?
2. MicroPython vs MakeCode declaration. Should URML's manifest declare which firmware-language substrate is loaded?
3. Educational-class declaration. Useful manifest flag for K-12 deployments + default safety envelopes?
4. Adapter home. URML repo (reference/edu-runtime/MicrobitAdapter), micro:bit-Foundation-maintained microbit-foundation/microbit-urml-bridge, or both?
5. Conformance listing. Would the foundation consider a README / wiki link to URML's compatible-runtimes registry once a working adapter ships?
6. Anything else.

Ido Yahalomi (URML maintainer, urml.dev, greenvh@gmail.com)

---

AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.