Locus

Technical reference

Locus Room package format

This reference includes the Room transport envelope, authorable Package-v2 fields, schemas, reproducible examples, packer, and validator.

Import paths. Import a View from one 2:1 JPEG, PNG, or HEIC image. Import a Room from an archive containing a Room and, optionally, its paired View and Experience.

Specifications

Room archive and content formatEnvelope layout, Room and optional pairing metadata, asset profiles, budgets, hashes, validation, and update rules.Authoring guideSupported View input, editable Room package structure, and failure cases.Browse reference files on GitHubReview changes and download plain-text sources.

Schemas and tools

Archive JSON SchemaThe strict transport envelope.Provenance JSON SchemaCreator, source, rights, credits, and modification history.ValidatorValidates archive bytes, manifests, referenced assets, limits, images, lighting EXRs, and USDZ before import.PackerRegenerates integrity fields and refuses to publish an invalid or overwritten archive.

Supported Room examples

Start with the complete Demo Room to try a real, furnished workspace. It is a Room-only archive, so Locus can pair it with any compatible View in your library.

Download Demo RoomA Locus-authored two-floor workspace with two work seats and two desks · 7.7 MB ZIP.

The smaller authoring fixtures below contain generated 16 × 8 PNG data, a tiny structural USDZ, strict provenance, Package-v2 manifests, and canonical integrity fields. They contain no private room, paid provider output, account data, or proprietary launch media.

Room-only authoring fixtureOne tiny Room with a self-contained USDZ; import it with Import a Room.Room with a paired ViewOne tiny Room, one View, and their explicit Virtual Space Experience; import the bundle with Import a Room.

The source builder also emits a View-only archive as a validator fixture. Import a custom View from a direct image.

Authority and licensing boundary

The shipping Locus importer is the installation authority. The public validator is intended to catch authoring and CI failures before import, but a future app version can enforce additional compatibility or platform checks.

Publishing these documentation and tool files does not publish the private Locus app source, disclose its implementation, or state that the application has adopted an open-source license.