Playground

Paste a .omir Bundle, validate it against the R1 schemas, and see its entities and relationships as a graph — entirely in your browser.

Coming soon — and on purpose, client-side. The playground will run the reference validator in your browser (the Rust omir-validate crate compiled to WebAssembly). Nothing you paste leaves your machine — a real privacy property for a memory format. The validator now exists as a working CLI; the remaining step is the WASM build.

Validate today, from the CLI

Until the in-browser validator ships, the same conformance checks run from the command line. The reference validator (omir-validate, Apache-2.0) checks structural validity, reference integrity, and the version marker, and emits a human or JSON conformance report.

# from the repository root
cd validator
cargo run -- ../examples/minimal-bundle.omir

#   structural ............. pass   (5 entries: 2 Entity, 1 Episode, 1 MemoryRecord, 1 Relationship)
#   reference integrity .... pass   (7 of 7 references resolved)
#   version presence ....... pass   (Bundle=R1, 5/5 entries meta.omirVersion=R1)
#
# RESULT: PASS  —  Core conformant ✓  (badge-eligible)

# machine-readable report for CI / badge automation:
cargo run -- ../examples/minimal-bundle.omir --format json

Try it against the deliberately broken fixtures in examples/invalid/ to see what rejection looks like (a dangling reference, a score out of range, a bad enum, an undeclared field) — each exits non-zero with a located finding.

What the in-browser version will add

Paste & validate — drop a .omir document in, get the conformance report instantly, with findings anchored to the offending JSON path.
Graph view — entities as nodes (sized by salience), relationships as edges (weighted by strength), so a Bundle is legible at a glance.
Zero upload — the WASM validator runs locally; your memory never touches a server.

See Conformance for the exact rules the validator enforces, and Guides to build your first Bundle.