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

[idoco2003]

Hi @microsoft psi team,

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

The URML-fit framing is temporal-streams substrate declaration. URML's manifest declares sensors individually; PSI provides the cross-sensor temporal-alignment + offline-replay infrastructure that downstream URML adapters can compose with. The manifest would declare temporal_streams_substrate: microsoft_psi to make the PSI binding observable.

License-clarification ask is the gating fact: the repo's license is listed as "Other" by the GitHub API. An explicit OSI declaration would unlock Apache-2.0 downstream reuse.

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/0150-microsoft-psi-outreach.md

Questions worth maintainer input on:

1. License clarification. Can microsoft/psi get an explicit OSI license declaration?
2. Temporal-streams substrate manifest fields. Clock class, replay-mode declaration, cross-sensor sync semantics?
3. Bridge home. Cross-citation only (recommended pending license), URML repo, or Microsoft-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.