Proposal: URML (substrate-neutral robot intent) cross-citation for STM32Cube — mixed-license clarification ask + multi-series scope question

[idoco2003]

Hi @STMicroelectronics team,

Proposing a URML v0.1 capability-manifest cross-citation for STM32Cube over STMicroelectronics/STM32CubeF4. URML (Universal Robot Language, Apache-2.0) is an open spec for substrate-neutral robot intent.

STM32 is one of the two most-deployed MCU families in robotics; URML's manifest declares STM32 board class spanning the F4 / H7 / U5 / G0 / G4 / WB / WL / WBA series. Mixed-license posture is the gating fact: ST's repos carry a mix of permissive (BSD-3-Clause, MIT, Apache-2.0) and proprietary-with-redistribution-license components. URML's adapter-grade reuse depends on per-surface clarity. Multi-series scope is the second question: this RFC anchors on STM32CubeF4 but the discussion likely belongs at a higher-level org surface if you have one.

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/0182-stmicroelectronics-stm32cube-outreach.md

Questions worth STMicroelectronics maintainer input on:

1. License clarification. Can the STM32Cube repos get explicit per-surface SPDX declarations? Which subdirectories are BSD-3-Clause / MIT / Apache-2.0 vs proprietary-with-redistribution?
2. MCU substrate manifest fields. URML's v0.1 has no mcu_class: stm32_* enum entries. Spec RFC queued. Manifest field expectations from ST's perspective (series identifier, Cube version pin, middleware declarations)?
3. Mixed-license-surface declaration. Should URML's manifest declare per-component license boundaries explicitly?
4. Multi-series scope. Should URML engagement live per-series-repo (F4 / H7 / U5 etc.) or at a higher-level umbrella?
5. Adapter home. Cross-citation only (recommended pending license clarification), URML repo (reference/edu-runtime/STM32CubeAdapter), or ST-maintained?
6. Conformance listing. Would STMicroelectronics consider a README link to URML's compatible-runtimes registry once a working cross-citation ships?
7. 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.