The text below is an extract of the current draft RFC. To access the full RFC or join the discussion, please contact the InnoFabric Working Group via the Participate in InnoFabric page.

RFC-0002: XRN usage by InnoFabric

InnoFabric RFC Series — Part of the InnoFabric Standards Track

Status: Draft 01
Version Date: 2026-02-18
Intended Status: Proposed Standard
Authors: InnoFabric Working Group (IWG-CloudId)
ISC Reviewer: TBD

1. Scope and Purpose

This document defines how InnoFabric uses XRNs to achieve interoperability, automation, and sovereignty-aware operation across providers and independently developed components.

RFC-0001 defines the syntax, fields, and normalisation rules for XRNs. This document defines the operational usage model for those XRNs within InnoFabric, including:

how XRNs are created and assigned,
which actors have naming authority in each architectural domain,
how XRNs are interpreted consistently by all components,
how shared semantics are enforced through a concrete system component,
and how the XRN namespace evolves over time.

The InnoFabric Registry is the practical system component that implements and enforces this XRN usage model.

Together, RFC-0001 and RFC-0002 define XRNs not merely as identifiers, but as the primary integration contract of the InnoFabric cloud operating system.

2. Uniform Naming as a Foundational Principle

InnoFabric is designed as a federated, multi-provider system composed of independently developed components operating across organisational, technical, and sovereignty boundaries.

Such a system cannot rely on:

provider-local identifiers,
implicit naming conventions,
undocumented semantics,
SDK-level assumptions.

Instead, InnoFabric relies on uniform, registry-backed naming as its primary integration mechanism.

Uniform naming enables:

interoperability between independently developed components,
portability of workloads, policy, and automation,
stable semantics across time despite internal change,
strict separation between control, substrate, and hardware concerns.

Without an authoritative and enforced naming system, these properties cannot be achieved.

Further sections

The remainder of the current working draft is not included in this published extract.

Additional sections covering the later specification material have been omitted for the present web version.

For access to the fuller draft or to participate in the InnoFabric IWG, please use the Participate in InnoFabric page.