Skip to content
v0.2.0 · Draft GitHub ↗ Apply for review →
↳ Governance · charter · process

An open standard, governed in public, on a published roadmap.

URML moves through five phases from a single-author draft to a fully-governed public standard. The spec, the RFCs, the decision history, and the charter are public from day one. The mark is not in use, and will not be until Phase 4.

Read GOVERNANCE.md ↗ CORE_COMMITMENT.md ↗
Where we are
0
Pre-public draft
ACTIVE

Single-author spec + reference implementation under public review. WG chairs and direct code contributions open in Phase 1.
§1 · Roadmap

Five phases. Boundaries are explicit; gates are public.

PHASE 0 NOW

Pre-public draft

now

Solo author in public. Spec + reference implementation under review. Discussions open.

PHASE 1

Public draft

next

Direct code contributions open. CONTRIBUTING.md in force; DCO enforced in CI.

PHASE 2

Working group formed

later

Charter ratified. WG chairs seated. First externally-authored RFC merged.

PHASE 3

v1.0 spec frozen

later

Breaking changes require RFC + WG supermajority. Conformance suite frozen with the spec.

PHASE 4

Certification program

later

“URML-Certified” mark introduced. Independent labs run conformance. Trademark policy ratified.

GATE CRITERIA FOR EACH PHASE TRANSITION ARE PUBLISHED IN GOVERNANCE.MD
§2 · Working groups

Four working groups. Four chair seats open.

Chairs are seated from organizations actively building or governing robots. Applications open at end of Phase 0, via GitHub Discussions.

Primitives WG

CHAIR SEAT OPEN

Add / deprecate intent verbs. Profile extensions.

Discuss in the open ↗

Compliance WG

CHAIR SEAT OPEN

Policy DSL · regulator liaison · jurisdictional overrides.

Discuss in the open ↗

Substrate WG

CHAIR SEAT OPEN

Reference adapters: ROS 2 · PX4 · OPC UA · vendor SDKs.

Discuss in the open ↗

Profiles WG

CHAIR SEAT OPEN

home · drone · industrial · educational · research.

Discuss in the open ↗
CHAIR INTEREST

Register interest in a WG chair seat.

Seats are seated at end of Phase 0. This is non-binding interest, reviewed in the open. One-year terms, renewable, no fee, conflict-of-interest disclosure required.

NON-BINDING · NO TRACKING · SAME-ORIGIN ONLY
§3 · RFC index

Every decision, in the open, with rationale.

Forty spec RFCs accepted or implemented, one open. Every RFC has an author, a state, and a public comment period. The per-target Outreach RFCs (the large remainder of ~609 docs) are tracked separately in the outreach ledgers.

NumberTitleStatus
RFC-0001 RFC process accepted RFC-0002 Initial Layer-2 primitive vocabulary implemented RFC-0003 US federal alignment as the default accepted RFC-0004 Compliance policy enforcement accepted RFC-0005 Structured HBOM parsing (Pass 5) implemented RFC-0006 Connectivity & link-loss safety contract implemented RFC-0007 Manufacturer go-to-market implemented RFC-0008 Community discussions implemented RFC-0009 Legged & humanoid mobility implemented RFC-0010 Whole-body / bimanual manipulation implemented RFC-0011 Educational profile accepted RFC-0012 Research profile accepted RFC-0013 Industrial Layer-2 primitives (pick_from / place_at / swap_tool) implemented RFC-0014 Substrate conformance contract implemented RFC-0015 Control-program invocation (call_program) open RFC-0016 Real-time / cyclic manifest block implemented RFC-0017 Digital-I/O actuation (set_output) implemented RFC-0018 Minimal-MCU capability subset implemented RFC-0019 AUTOSAR Adaptive substrate implemented RFC-0020 Autoware AV substrate (plan_path / follow_trajectory) implemented RFC-0021 On-device LLM bridge implemented RFC-0022 Warehouse domain profile implemented RFC-0039 Sensor schema v0.2 iteration implemented RFC-0260 language block — Layer-4 NL infrastructure implemented RFC-0262 licensing block — per-component license + boundary implemented RFC-0268 deployment block — commercial-use gate implemented RFC-0286 Multi-robot fleet addressing & synchronized execution implemented RFC-0290 Frame-transform graph (SE(3)) implemented RFC-0291 UTM-style geometric cross-robot deconfliction implemented RFC-0304 Permissive translation alternative implemented RFC-0381 validation block — simulation-fidelity hints implemented RFC-0382 monitorable_properties — temporal-logic safety core implemented RFC-0383 learned_policy — training-envelope declaration implemented RFC-0384 whole_body — structure + stability limits implemented RFC-0385 substrate.ipc — zero-copy IPC sub-substrate implemented RFC-0469 realtime.acyclic — SDO / mailbox regime implemented RFC-0477 substrate.clock — time-sync regime implemented RFC-0478 substrate.bringup — ordered init / recovery implemented RFC-0518 base-level mobility bounds (velocity-controlled base) implemented RFC-0586 dexterous (multi-fingered) hand declaration implemented RFC-0615 declared_areas + perception.object_detection implemented
§4 · Process

How an RFC actually passes.

STEP 1
Idea
GitHub Discussions
STEP 2
Proposal issue
Tagged proposal
STEP 3
RFC draft
PR to docs/rfcs/
STEP 4
WG review
Reviewer + chair
STEP 5
Public comment
7 days min
STEP 6
Vote
WG supermajority
VOTING RULES

Supermajority of seated chairs.

  • Quorum 3 of 4 WG chairs present.
  • Threshold 75% of present chairs approve.
  • Veto Any chair vetoes with a written objection; opens a 14-day re-vote.
  • Tie Phase 0/1: maintainer breaks tie. Phase 2+: rejected by default.
CONFLICT OF INTEREST

Disclosed, not avoided.

Chairs disclose any material interest in an RFC outcome (employment, equity, contracts, government affiliation) before the vote, publicly in the RFC PR thread.

Any decision affected by an undisclosed conflict is voided. DCO sign-off (not a CLA) keeps contribution provenance clean for a future entity split.

§5 · Marks & commitments

No mark in use. That's a feature.

Trademark posture

Through Phase 3, a registry listing does not grant any mark, badge, or right to claim certification. A federal-validation self-report is a reproducible factual artifact, not a third-party mark.

The "URML-Certified" mark is reserved for Phase 4, when independent labs run conformance and trademark policy is ratified.

Read TRADEMARK.md ↗
CORE COMMITMENTS · IMMUTABLE
  • Spec stays Apache-2.0
    Forever. See CORE_COMMITMENT.md.
  • Conformance stays free
    Anyone can run it, no cost, no gate.
  • No vendor lock-in
    Substrate-agnostic by construction.

Help govern the standard.

Express interest in a WG chair seat → Open an RFC