MRS-S: The Single Format
MRS uses one syntax for all operations. There is no separate “working format”—agents receive and return valid MRS-S. See:/mrs-s/overview and /MRS-Specification-RFC#4-mrs-s-the-canonical-format
File Types
- MIME type:
application/vnd.mrs+sexpr - Extensions:
.mrsor.mrs-s - Encoding: UTF-8 (BOM should not be used)
/MRS-Specification-RFC#14-mime-types-and-file-extensions
Minimal MRS-S Skeleton
- Every measure has
:id(UUID) and:number(display) - Every event has
:idand:at(absolute position)
/MRS-Specification-RFC#4-2-document-structure
Working Set Envelope for Agent Tasks
For agent operations, the orchestrator extracts a Working Set Envelope with context:- Scope uses UUIDs — not measure numbers
:display-hintprovides human-readable numbers- Context rings provide surrounding material
- Synopsis reference for global awareness
/working-set-envelope and /MRS-Specification-RFC#5-working-set-envelope
Agent Workflow (Extract → Edit → Replace)
- Extract: Create Working Set Envelope with UUID scope and context
- Send to agent: Agent receives valid MRS-S with context rings
- Agent returns: Valid MRS-S fragment for the modified scope
- Replace: Orchestrator does trivial substitution + validation
/extract-replace-protocol and /MRS-Specification-RFC#9-extract-replace-protocol