Tour of the web UI

Each goal with its success measures, and its plan's milestones in priority order with their progress, then each milestone's work by dependency layer and the critical path. A plan version that waits for approval is named at the top, and the version before it stays in force until a person decides. Start planning session opens a planning session from here.

Onboarding: start a planning session covers it.

One plan version in full: what it adds, changes, and removes since the last approved version, with a link to each document's difference, its draft decisions with the question and rationale behind each, and its new and changed contracts. Approving it decides the draft decisions as the person's and passes contract review for the work it covers, in one step, bound to the version's digest. A person can also decline it with a reason.

Onboarding: approving a plan covers it.

Each requirement traced to the criteria that serve it, their work orders, and the latest verdict or evidence, with where it stands: planned, in progress, in review, integrating, met, or met by existing code. The Reader tab beside it shows each requirement, spec, and design at its versions, with the plan version it waits in.

API: the documents view covers it.

Each machine with its orchestrator, its lanes against the lane cap, and its CPU, memory, memory pressure, free disk, and load. Then each lane with its work order, state, reachability, generation, and how fresh that is. A lane can be opened or sent a message, and a planning session's pane opened, for one project or all of them.

Onboarding: what the worker measures covers it.

The agent roster every session receives: each agent's access, capability class, effort, and approval, and whether it is built in or changed for the installation or the project, with the routing guide and the roster's history. A member edits an agent's purpose, tools, and instructions here. Agents whose approval is per use ask before they start.

Authorization: agents covers it.

What waits for a person in every project, oldest first: work to accept, with the review's verdict and citations for each criterion, work its lane could not finish, a parked lane, a tool call to allow, questions, confirmation cards, a plan version to approve, and a contract review. Filters narrow it to decisions, approvals, cards, or stuck work, and a Decided tab sits beside Open.

Onboarding: who reviews a lane's work covers it.

A call a delegate prepared but could not run alone: what it changes, why the delegate proposes it, and the exact operation, bound to its subject as it stood. A member confirms it, and it runs as that member, or declines it. If the subject changes first, the card is void. For an outside delegate, creating work, starting a contract review, and accepting work are cards unless the project's delegate policy exempts them. The assistant creates work and starts contract reviews at once.

Authorization: delegates covers it.

A member's conversations with their assistant in the project, and the orchestrator, planning sessions, and lanes they can message, with a dock that opens the same conversation on every view. The assistant reads the project's repositories and acts through the API for the member: operational calls run at once, creating work and starting contract reviews among them, and calls that need consent become cards the member confirms. Its session stops after an idle time the assistant policy sets, 15 minutes by default.

Authorization: the assistant covers it.

Every decision and assumption recorded in the project, each with its rationale, scope, reversibility, categories, who decided it, the policy version in force, the question it answers, and what it cites.

The command line reference covers it.

The fleet's mode, how many things wait for a person, the workers observed, and the work in progress and lane limits. Then the counts of work orders and lanes by state, the sources, and the product measures: interruptions per completed work order beside the overturn rate, rework, and the autonomous decision rate.

Product measures covers it.

The terminal view: what needs a person first, in every project and in Needs you order, including confirmation cards with the delegate that prepared them, plan approvals, and contract reviews, then the commands for the selected item, each lane with its context, tokens, and cost, and the worker with what it last measured of its machine.

The command line lists what ropeshift top shows.