Proposal: URML (substrate-neutral robot intent) cross-citation for Theia — and a license-clarification ask

[idoco2003]

Hi @rai-opensource Theia team,

Proposing a URML v0.1 capability-manifest cross-citation for Theia over rai-opensource/Theia. URML (Apache-2.0) is a substrate-neutral spec for robot intent: typed primitive vocabulary + capability manifest + static validator.

Theia is a vision foundation model for robotics; URML's manifest declares which vision-foundation-model class is active so adapters can consume Theia's feature representations without re-implementing the model surface.

License-clarification ask is the gating fact: the repo's license is listed as "Other" by the GitHub API. An explicit OSI declaration (Apache-2.0 / MIT / BSD-3-Clause) would unlock Apache-2.0 downstream reuse; until clarified, URML's framing stays at cross-citation depth.

This is proposal-only, part of URML's Move #11 outreach (15 net-new VLA / foundation-model RFCs in this wave).

Full RFC: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0148-rai-theia-outreach.md

Questions worth maintainer input on:

1. License clarification. Can rai-opensource/Theia get an explicit OSI license declaration?
2. Vision-foundation-model substrate manifest fields. Manifest expectations for input modality, output representation class, downstream consumer interface?
3. Bridge home. Cross-citation only (recommended pending license), URML repo (reference/vla-bridge/), or RAI-maintained?
4. Conformance listing. README link to URML's compatible-runtimes registry once a working cross-citation ships?
5. 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.