The parts

Workspace: Your organisation’s place in Arbituro: its people, projects, agents, connections, plan and audit log.
Project: A body of work with its own members, brief, board and rules. Its key, such as WEB, starts every job’s key.
Job: One piece of work, such as WEB-12, with an objective, an owner, dates, and often an agent.
Acceptance criteria: What finished means for a job. Each one is decided by a person, by a CI check, or by an approved message being sent.
Agent: Does the work on jobs, on an AI model, with only the access people give it. Every workspace starts with one, named Scout.
Run: One stretch of an agent’s work on a job: it plans, asks questions, waits for approvals, and files its result.
Result: What a run delivers: a document, a one-page memo, a slide deck, a draft pull request or a GitHub issue.
Judge: The person who accepts or rejects a job’s result. By default, the job’s owner.
Approval: A person’s yes to something an agent wants to send or change. An agent sends nothing through a connection without one.
Connection: An account such as Gmail, Slack or Salesforce. Its owner decides which agents may read or draft through it, and who approves.
Knowledge: Documents a project publishes for its agents to read and cite.
Record: Every action by people and agents, on each job, in What happened, and in the workspace’s audit log.

The life of a job

Someone files a job. A person writes what needs doing, or it arrives from an import or a project’s request form. See Jobs and Bring work in.
An agent takes a first look. The project’s agent reads the job and the project’s brief, changes nothing, and suggests acceptance criteria. A person accepts the ones that are true. See Acceptance criteria.
The agent works. When a first run could send something outside, it plans before it works, and the job’s owner approves the plan. As it works it asks questions, and every change or message it proposes waits for a person’s approval, given at the time or, for some changes, in advance. See Runs and deliverables and Approvals.
It delivers a result. The result is filed on the job, and the judge reviews it against the acceptance criteria, then accepts it or sends it back with a reason.
Each criterion is decided. The person a criterion names ticks it, a CI check settles it on a linked pull request, or an approved message settles it when it is sent. Agents never tick criteria.
The job is done. A person moves it to a finished status. A project’s rules can require a sign-off or a condition first.

Every step is in the job’s record, with who or what did it.

A few parts of Arbituro have names of their own on screen:

Something missing or wrong? Email support@arbituro.com.