Using Moru
Provenance
What the node records about how each revision was made, how to read the Evidence panel, how to check it with moru-node verify, and whose attestations a repository trusts.
When a revision reaches a change, the node records what it saw about how that revision was made and signs it. This record, the attestation, is stored with the change in the repository, so it travels with the repository and can be checked anywhere, offline. A change can’t be merged unless its latest revision has a valid one (see merge rules).
What an attestation says#
For an agent’s revision, the node records:
- the change, the revision number, the repository, and the commits from the base to the revision;
- the agent that submitted it, and the person it worked for;
- the task, and the runner that leased the job;
- what the node asked for: the agent profile, the model, and the Claude Code version if it was pinned;
- when the job was queued, leased, started and submitted.
The runner adds its own claim, signed with the runner’s key: the harness and its version, the SHA-256 of the Claude Code binary it ran, the model, the machine’s operating system, and when it started by the runner’s clock. The node can’t check what a runner says about itself. What it can check is the signature, so if a claim is false, it shows which runner made it.
For a revision a person pushed, the node records who pushed it and which commits, and that no agent or runner was involved.
The attestation is an in-toto statement, with the predicate type https://moruforge.com/agent-run/v0.2, in a DSSE envelope signed with the node’s key.
The Evidence panel#
The Evidence panel on the right of every change page shows the attestation for the revision you’re looking at.
- Attestation verified means the signature checks out, the attestation is about this revision’s commit, and its signer is trusted here. Otherwise the panel says Not verified and why, such as “no attestation” or “untrusted signer”.
- Seen by the node is the node’s own record: the agent and on behalf of whom (or “pushed it themselves” for a person), Asked for (the profile and model), Claude Code (“not pinned: the runner chose” when the profile didn’t pin it), Leased by (the runner), Task, Ran, Commits, and Signed by, with whether the signer is a trusted node here.
- Reported by followed by the runner’s name is the runner’s signed claim: Harness, Binary, Model, Sandbox and Started. Runs on current runners say “no sandbox (macOS)” or “no sandbox (Linux)”: the runner ran the agent directly on that machine. Older runs say which sandbox they ran in, and the Image row shows the agent image of a Docker run.
- Status history lists approvals and other status changes, with who made them and at which revision.
- Merge policy shows the merge rules for the latest revision.
In the revision list, a shield next to a revision means its attestation verified.
Check a change with moru-node verify#
To check a change’s attestations from the command line, without the web UI, run moru-node verify on the node with the repository and the change ID. The Evidence panel shows the
exact command for each change.
moru-node --data /var/lib/moru verify acme/timetable kzvpqrstuwxyzkzvpqrstuwxyzkzvpqr With the Docker image, run it in the container:
docker exec moru moru-node verify acme/timetable kzvpqrstuwxyzkzvpqrstuwxyzkzvpqr It prints one line per agent attestation: ok, untrusted (a valid signature by a signer this
node doesn’t trust) or FAIL, then the revision, the commit, the signer and the reason for
any failure. Under each, it prints what the node saw, what it asked for, and what the runner
says:
ok r1 3f9c2a7b1d4e signer=did:key:z6Mk… trusted=true
node saw: agent did:key:z6Mk… on behalf of did:plc:…, task t-…, leased by runner mira-laptop (did:key:z6Mk…)
node asked for: harness claude, model claude-sonnet-5-5
runner says (signed, not checkable by the node): …
verified: every revision of kzvpqrstuwxyzkzvpqrstuwxyzkzvpqr has a valid, trusted attestation If any revision lacks a valid, trusted attestation, it ends with NOT verified and exits
with status 1, so you can use it in scripts. An attestation trusted through another host
gets a trusted via host line naming it.
The same checks are available from the API at GET /api/v0/repos/<owner>/<name>/changes/<change-id>/verify (see API).
CI results#
When a CI job for a change’s revision ends, the node signs a second kind of attestation
and stores it in the change beside the first: predicate type https://moruforge.com/ci-run/v0.1, about the revision’s commit. It records the
workflow file (by path and blob ID), the job and its matrix values, the trigger, the
person the run was for, the runner with its owner and the owner’s role on the repository
when the runner took the job, the names of the secrets the job was given (never their
values), when it was queued, started and finished, and the outcome: succeeded, failed, timed_out or cancelled. The runner’s own signed claim is inside it, as for
an agent’s run. A job that used containers also lists their images with their digests
(the job’s container, its services and Docker actions); for an image built from a
Dockerfile, the digest is its image ID. The runner reports these after pulling, when
the job ends, so they’re the runner’s word, like the outcome; its claim is
signed before the pull and doesn’t name them.
Jobs that never reached a runner (skipped, or cancelled while queued) get none. Runs for pushes and manual starts write nothing into the repository: they’re kept on the node only.
moru-node verify lists CI results after the agent attestations, one line each:
ci ok r2 3f9c2a7b1d4e checks/test (os=linux): succeeded, counted signer=did:key:z6Mk…
ran on a runner of did:plc:… (role write), job … counted means the result counts toward the repository’s required CI jobs. A result from a runner whose owner
didn’t have write access is shown and marked not counted, with why. CI lines don’t
change verify’s exit status. The API’s verify has them under ci_checks.
Trusted attesters#
An attestation only counts if its signer is trusted. A node always trusts itself: its own key and its host. Attestations from other nodes, for example in a repository imported from another node, show as untrusted until you trust that node’s host. Until then, a change whose latest revision depends on them can’t be merged.
Get the other node’s host DID by running moru-node host there. It prints the host’s DID
and kind. Then trust it in one of two places:
For one repository: on the repository’s Settings → Trusted attesters, a repository admin pastes the DID and clicks Add. This list is part of the repository’s signed access record, so it moves with the repository.
For the whole node: a node admin adds the DID to
trusted-attesters.jsonin the data directory, a JSON list:["did:plc:abcdefghijklmnopqrstuvwx"]The node reads the file each time it checks an attestation, so no restart is needed.
Trusting a host trusts the node keys it vouches for in that repository, during the time it
vouched for them. moru-node verify then marks those attestations trusted via host.
A key the host has revoked stops counting from the revocation’s time, even in a copy of the repository that doesn’t carry the revocation, as long as this node knows of it. The panel then says “revoked by … from …”, with “(known to this node)” when the repository itself lacks it. See How trust works.
See Backups for what to keep safe.