Skip to content
ostrium-labsPublic

About

OpenPlay: an open package and runtime standard for portable games

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

OpenPlay

OpenPlay is an open, versioned contract for portable game packages and runtimes. A game ships one .opk package; a conforming runtime on Windows, Linux, macOS or Steam Deck can load it, present it and run it.

Status: design draft. The Core 0.1 specification, manifest schema, WIT contract and manifest validator exist. There is no reference runtime yet.

OpenPlay is not a console replacement and does not assume Sony, Microsoft or Nintendo will adopt it. Console support is a later profile that requires platform-holder participation. The first profile targets open desktop platforms where nobody can block adoption.

What it standardises

Layer OpenPlay Core 0.1
Package .opk: deterministic ZIP, openplay.json, content-addressed files
Logic WebAssembly module with a versioned WIT ABI
Rendering WebGPU-shaped command submission; clear + textured quad is the first conformance target
Input Raw keyboard, mouse and gamepad events
Audio Interleaved PCM stream at a declared rate
Storage Sandboxed save container with a quota
Capabilities Explicit required/optional negotiation, no ambient authority
Trust Package hashes, optional Ed25519 publisher signatures, untrusted WASM sandbox

What it is not

  • Not a store, launcher, DRM system or entitlement service.
  • Not an emulator or a compatibility layer for existing console binaries.
  • Not a replacement for console certification.
  • Not a new programming language or engine.
  • Not a promise that AAA console titles run unchanged.

Repository layout

Path Responsibility
docs/spec/ The normative OpenPlay Core 0.1 specification
docs/adr/ Design decisions and their consequences
schemas/ JSON Schema for openplay.json
wit/ WebAssembly Interface Types contract
crates/openplay-core Manifest types and validation
crates/openplay-cli openplay validate and openplay inspect
examples/hello-openplay Minimal manifest example

The repository conventions follow ostrium-labs/ferite: one Rust workspace, one lockfile, ADR-numbered decisions, Apache-2.0 and a design-first loop where the conformance corpus drives the runtime.

Build and test

The Rust toolchain is pinned in rust-toolchain.toml.

cargo build --workspace --locked
cargo test --workspace --locked
cargo run -p openplay-cli -- validate examples/hello-openplay/openplay.json

Profile 0

Profile 0 (core-0.1) targets Windows, Linux, macOS and Steam Deck. It requires:

  • a WASM game module and the openplay:core@0.1.0 ABI;
  • WebGPU-class rendering;
  • keyboard, mouse and gamepad input;
  • PCM audio output;
  • a sandboxed save container.

Android, browsers and consoles are explicitly out of scope for Profile 0. See docs/profile-0.md.

Relationship to Prospero

Prospero is a separate PS5 emulation project. OpenPlay is not an emulator, and an emulator is not part of the OpenPlay trust boundary. A future runtime could use an emulator as a legacy backend, but that would be a separate profile and would not make emulated console binaries conforming OpenPlay packages.

Licence

Apache-2.0. See LICENSE and NOTICE.

About

OpenPlay: an open package and runtime standard for portable games

Topics

Resources

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages