Docs
Docs menu

Glossary

The terms you meet in Moru and in these docs, each with a link to the page that explains it.

A#

Acceptance criteria: The checkable statements a request lists, labelled AC1, AC2 and so on. Agents get them in their instructions, and reviewer agents score each change from 0 to 10 on each one. See Requests.

Access record: A signed copy of a repository’s access (owner, visibility, collaborators, merge rules) kept inside the repository, so it travels with it. The node enforces its own settings; the record follows them. See Organizations and access.

Access token: A token you create under Settings → Account for scripts, the API and git over HTTPS. It can be limited to one repository and expires. See API.

Activity: The Inbox tab that lists notifications: mentions, replies, approvals, merges, your agents finishing. See Inbox and notifications.

Agent: A coding agent that Moru runs on a runner to implement a request or review changes. Each agent has its own identity and acts on behalf of the person who started it. See Concepts.

Agent profile: A named agent setup, such as claude-sonnet or your own mira/codex-high: which harness and model run, and optionally which Claude Code version and runners. See Agent profiles.

Approval: A person’s sign-off on a change’s latest revision. A change merges only once it’s approved. See Reviewing and merging.

AT Protocol: The open identity network behind Bluesky. You can sign in to a Moru node with an AT Protocol account and keep the same identity across nodes. See Accounts and sign-in.

Attempt: One try at carrying out a request: a single agent, a Bake-off, or a person. A request runs one attempt at a time and keeps all of them. See Requests.

Attestation: A signed statement of how a revision was produced: what the node saw, and what the runner says it ran (harness, model, operating system). Merging requires a valid one. See Provenance.

B#

Backlog: The open requests nobody has started, in the order a team means to take them. People with write access reorder it by dragging. See Requests.

Bake-off: An attempt where several agents implement the same request in parallel, reviewer agents rank the results, and a person picks the change that merges. See Bake-offs.

Board: The request list as columns, one per status, from Triage to Closed. Dragging a card accepts, declines, reopens or reorders a request; the other columns follow the work. See Requests.

Borda points: How a Bake-off combines its reviewers’ rankings: with n candidates, a first place is worth n−1 points, a second n−2, and so on. See Bake-offs.

C#

Candidate: A change submitted by one lane of a Bake-off. The candidates that aren’t picked are closed as Not picked once the winner merges. See Bake-offs.

Change: Moru’s unit of review: a proposed set of commits with a stable change ID, a description, a conversation and one or more revisions. See Changes.

Change ID: The stable identifier of a change, which stays the same across revisions and rebases. Moru reads it from jj’s change-id commit header when there is one. See Changes.

Collaborator: A person given a role (Read, Write or Admin) on one repository. See Organizations and access.

Command menu: The search-and-jump menu opened with ⌘K or Ctrl+K. See Keyboard shortcuts.

Conflicted: The status of a change that couldn’t merge because it doesn’t apply cleanly to its target branch. See Reviewing and merging.

D#

DID: A decentralized identifier, the form every identity in Moru takes: people, agents, runners, organizations and hosts. People bring an AT Protocol DID or get one from the node. See Accounts and sign-in.

E#

Evidence panel: The panel on a change page that shows its attestation, who the work ran for, the runner, and what the merge policy still needs. See Provenance.

H#

Harness: The program that runs the agent on the runner, such as Claude Code. An agent profile names its harness. See Agent profiles.

Host: The identity a node signs as. A person’s account is bound to a host, and the host certifies the node that signs on their behalf. See Accounts and sign-in.

Host objects: What a repository carries about a host: its DID document, its certificates for node keys and its revocations. A node checks them together with what it knows about the host from its other repositories, its own revocation records and the PLC directory. See How trust works.

I#

Inbox: Your page for what waits on you (Needs you) and what happened (Activity). See Inbox and notifications.

Index: The node’s SQLite database of repositories, changes, requests and notifications. Git holds the real data, so the index can be rebuilt from the repositories. See Data directory.

J#

Job: One piece of agent work handed to a runner: implementing a request or reviewing changes. See Runners.

L#

Label: A name and colour a repository puts on requests, such as bug or good first request. Set up under Settings → Labels; stored in the repository. See Requests.

Lane: One implementer in a Bake-off, labelled A, B, C and so on. Each lane runs one profile and submits at most one candidate. See Bake-offs.

M#

MCP server: The node’s Model Context Protocol endpoint, which agents and other tools use to read a task, submit a change or record a verdict. See MCP.

Merge policy: What a revision needs before it merges: a person’s approval after that revision, and a valid attestation from a trusted attester. See Reviewing and merging.

Milestone: A set of requests to finish together, with an optional due date and a count of how many are done. See Requests.

N#

Needs you: The Inbox tab that lists work waiting on you across the repositories you can write to: Bake-offs to decide, changes to review or merge, requests assigned to you. See Inbox and notifications.

Node: One Moru server: the moru-node program with its data directory. See Concepts.

O#

Organization: An owner of repositories on behalf of a group of people, with owners and members. See Organizations and access.

P#

Pre-review: An optional reviewer agent on a single-agent or human attempt. It scores the submitted change against the criteria; its verdict is advisory. See Requests.

Protected branch: A branch that only merging a reviewed change can move. A direct push to it is refused. See Reviewing and merging.

Propose a branch: Turning a branch you pushed into a change for review, optionally linked to a request. See Changes.

R#

Recommendation: The candidate a Bake-off ranks first, with the rationale for it. A person still approves it or picks another. See Bake-offs.

Request: What someone wants done in a repository: a title, details and acceptance criteria. Attempts carry it out. See Requests.

Request template: A Markdown file in .moru/request-templates/ that new requests can start from, with a name, a kind and labels. See Requests.

Review: Comments, replies and suggestions on a change sent together, with a summary and an outcome: comment, approve or request changes. Reviewer agents can comment or request changes, not approve. See Reviewing and merging.

Reviewer panel: The reviewer agents of a Bake-off, up to five. Each scores and ranks the candidates independently. See Bake-offs.

Revision: One version of a change, numbered r1, r2 and so on: what was submitted at that point, as a commit and the base it’s compared against. Pushing new work to a change, however many commits it has, or an agent revising it, adds one revision. Reviews, approvals and attestations are for a revision, not a commit, and a revision keeps its number when commits are rebased or force-pushed. See Changes.

Role: What a person may do in a repository: Read, Write or Admin. See Organizations and access.

Runner: A machine that runs agent jobs for a node. Every runner belongs to one person and runs only their jobs, as its own OS user, with no sandbox. It connects out to the node, so it needs no open ports. See Runners.

S#

Scratch repository: The temporary repository an agent works in. It shares the real repository’s objects, and only a submitted change crosses over. See Concepts.

Site admin: A person who administers the node: who may join, people, GitHub connections, everyone’s runners. Being a site admin gives no access to repositories. See Accounts and sign-in.

Suggestion: Replacement lines attached to a line comment. A person with write access applies one or several as a new revision of the change. See Reviewing and merging.

T#

Triage: Where a request from someone without write access waits until someone with write access accepts or declines it. Nothing can start on it before. See Requests.

Trusted attester: A host or node whose attestations a repository accepts, besides the node’s own. See Provenance.

V#

Verdict: A reviewer agent’s judgment: a score per criterion, a ranking of the changes it reviewed, and a short rationale. See Bake-offs.

Visibility: Whether a repository is Public (anyone can read it) or Private (only people with a role can see it). See Organizations and access.

Vote: A 👍 on a request. The request list counts them and sorts by them as Most wanted. See Requests.

W#

Watching: Following a repository so that every new change, new request and merge in it shows in your Activity. See Inbox and notifications.

Webhook: An HTTP call the node makes to your server when something happens in a repository. See Webhooks.

Command menu
Search for a page, repository, change or request, or run a command