Platforms

Ouro HX is how an app treats people, and Ouro AX is how it treats agents. Neither cares much what the app is written in, so they travel: one core of tokens and standards, and a platform kit wherever someone has packed a bag.

Where they live

A platform gets its own repository and pins a release of Ouro UI core, the part that holds on any platform. Today core holds Ouro HX's tokens, what Ouro HX's components promise as claims, and Ouro AX for Apple's claims; Ouro HX's design language and web's Ouro AX standard move in later.^core-today A platform takes core's files from a release tag, never from a branch, and its CI checks that they arrived unchanged.^pinning

• Ouro HX & AX for web lives in ourostack/ouro-ui: the components, the AX kit for command lines, HTTP and MCP, and this site.^web-home
• Ouro HX & AX for Apple is a Swift package for iPhone, iPad and Mac, with Siri as the agent at the door.
• Ouro HX & AX for Android and for Windows are spare rooms with the lights on, waiting for a builder.
• Ouro HX & AX for your platform is the door we left open for whatever comes next.

Which core they meet

For web

Release checked: v1.3.3^web-release

The core it meets: core v0.3.0, for its tokens^web-core

Core's parity check compares its web stylesheets with web's, byte for byte.^web-core

For Apple

Release checked: v0.3.4^{apple-release}

The core it meets: core v0.3.0^apple-core

The release's core-provenance.json names the tag and each file's SHA-256, and CI checks the hashes.^apple-core

For Android

Release checked: none yet

The core it meets: none yet

Build it

For Windows

Release checked: none yet

The core it meets: none yet

Build it

Core's newest release, v0.3.0, has added Ouro AX for Apple's claim set and Ouro HX's component claims since v0.1.0, each as data.^core-v0.3.0

Building one

Start with the guide for platform builders: the contract a platform meets, and how a pull request with a link to your work becomes ouro-ui-<platform>.