Build with Muse
Muse is a content-addressed version control engine built for code, music,
and any structured state space. Every object has a sha256: ID.
Every commit is signed with Ed25519 — by an agent or a human. There are no
passwords, no JWTs, no merge conflicts that can't be taught to resolve
themselves.
The protocol is simple: implement six methods and any domain — MIDI sequences,
source code, genomic data, financial models — gets branching, merging,
time-travel, structured diffs, and conflict resolution for free. Agents are
first-class citizens: every commit carries agent_id,
model_id, and a cryptographic signature traceable to a single
HD wallet seed.
Getting Started
Install muse, authenticate with Ed25519, create your first repo, and run the core workflow.
01Foundations
Content-addressed object model, commit DAG, snapshots, branches, push/pull.
02Cryptographic Identity
HD Ed25519 keys, MSign auth, human→agent→org trust chains, quorum authorization, MPay.
03Domain Protocol
MuseDomainPlugin — six methods, any state space. Typed delta algebra, address-keyed Map merge.
04Code Intelligence
Symbol graph, blast radius, gravity, hotspots, entanglement, dead-code detection.
05Merge Engine
Three-level granularity, strategy × history matrix, --explain observability, local and proposal merge, Harmony integration.
06Harmony
Four-tier conflict resolution: policy, exact replay, semantic match, escalation.
07Agent Coordination
Work queues, claim/complete lifecycle, sharding, reservations, forecasting.
08MCP Tooling
Model Context Protocol server — tools, resources, elicitation, SSE streaming.
09Shelves
Working-tree checkpoints — intent types, resumability, domain state, handoff patterns.
10Wire Protocol
MsgPack over HTTP — presigned mpack push, fetch delta, refs.
11MuseHub API Reference
REST API, MSign authentication, rate limits, webhooks, pagination.
12Identity Profiles
Three-archetype profile system — Spectral Sigil, attestations, MPay ledger, agent genealogy.
13Mist Domain
Content-addressed, forkable, embeddable artifact shares. URL schema, artifact types, CLI, REST API, security model.
14Vision
Why Muse exists. Semantic vs binary diffs, independent-dimension auto-merge, domain agnosticism, and the AI-agent imperative.
15CRDT Primitives
Six lattice-based primitives — VectorClock, LWWRegister, ORSet, RGA, AWMap, GCounter — with full API reference and integration patterns.
16Security Reference
Fourteen layered guards: object-ID validation, path containment, ANSI injection, XML safety, HTTP hardening, identity store, and more.
Suggested reading paths
New to Muse? Pick a goal and follow the path. Every section can be read stand-alone, but the paths below give the fastest on-ramp to each use case.
| Goal | Sections |
|---|---|
| Evaluate Muse understand the core object model |
00 Getting Started → 01 Foundations → 02 Cryptographic Identity |
| Build a domain plugin extend Muse to a new state space |
01 Foundations → 03 Domain Protocol → 05 Harmony |
| Run agents coord, shelves, MCP tooling |
00 Getting Started → 06 Coordination → 07 MCP Tooling → 08 Shelves |
| Integrate via REST API MSign auth, repos, issues, webhooks |
02 Cryptographic Identity → 10 MuseHub API |
| Understand the wire protocol push/fetch frame format, presign, msgpack |
01 Foundations → 09 Wire Protocol |
| Host and share artifacts mist URLs, artifact types, CLI, REST API |
00 Getting Started → 12 Mist Domain |
| Set up an identity profile Spectral Sigil, attestations, agent genealogy |
02 Cryptographic Identity → 11 Identity Profiles |