Build with Muse

Muse is a content-addressed version control engine for structured state. Where Git versions lines of text, Muse versions what the content means: for source code that is its functions, classes and imports, so history, diffs and merges can be followed symbol by symbol. Every object has a sha256: ID, and hub API requests are authenticated with MSign Ed25519 request signatures — no passwords, no JWTs.

The domain protocol is six methods — snapshot, diff, merge, drift, apply and schema. Implement them and the engine supplies the rest: the commit DAG, branching, checkout, history and merge-base finding. Source code is the primary domain today; a MIDI plugin is maintained but off by default, and state spaces such as genomic data or financial models are each one new plugin away.

Agents are first-class. Commits record agent_id and model_id when an agent supplies them. Once you have an identity on the repository's hub (Getting Started), signing is one switch — muse commit --sign, or commit.sign = true in config — and without one, a signing commit stops instead of writing an unsigned commit. A signed commit carries an Ed25519 signature, and its ID binds the signer's public key. Recurring conflicts can be taught: when the same conflict comes back, muse merge replays the resolution you recorded, and muse harmony engine adds declarative policies and similarity matching, then records an escalation for whatever is left for a human or an agent to resolve.