Skip to main content
MRS-S is the canonical storage format for complete, archival-quality scores. It is optimized for semantic fidelity, human readability, and validation. See: /MRS-Specification-RFC#4-mrs-s-the-canonical-storage-format

Role in MRS Architecture

Agents read MRS-S fragments in Working Set Envelopes. Agents write MRS-Ops operations. The orchestrator applies operations to canonical score state.

Top-level Structure

Key Characteristics

Stable UUID Identifiers

Every measure, event, and span carries a stable UUIDv7 identifier:
  • :id — Stable identity for all internal references
  • :number / beat — Display/structural position for human navigation

Player-Instrument Model

Players own instruments; instruments appear in measure content:

Orchestrator-Computed Derived Fields

In MRS-S storage, :at (absolute position) is optional. The orchestrator computes it:
This is a change from earlier versions: agents no longer provide :at in operations; the orchestrator computes it.

All References Use UUIDs

Span endpoints, working set scopes, overlay regions—everything references by UUID:

Canonical Rational Syntax

All temporal positions use exact rationals:
Decimal literals (2.5) are NOT permitted.

File Types

  • MIME type: application/vnd.mrs+sexpr
  • Extensions: .mrs or .mrs-s
  • Encoding: UTF-8 (no BOM)