Product measures

Ropeshift computes its product measures from the ledger and nothing else, so they work with no telemetry pipeline, on one machine, with nothing configured. ropeshift measures prints them, the web UI's operations view shows the last 7 days, and the daemon copies them out as ropeshift.measure.* metrics every 5 minutes, to the local telemetry store and to an exporter when one is configured. Each read covers every page of the event log and the records of review calibration.

The north star and its counterweights#

The north star is human interruptions per completed work order. Interruptions alone reward an agent for never asking, so every surface shows the north star beside the overturn rate, rework, and the autonomous decision rate.

A rate with nothing under it has no value, and every surface says so instead of printing zero.

Definitions#

A window runs back from now, 7d by default. Work in progress is a count of now, and every other measure counts what happened inside the window.

Review agreement#

Whenever a member accepts or sends back work whose current attempt has verdicts from a review, ropeshift keeps a calibration record in the same transaction. A pull request the person merges on the forge, at a level where the person decides, counts as accepting the work it lands, and its record names the pull request in its reason and no member, because the forge's account is not one. At person_approves, approving the merge of a reviewed commit counts as accepting it, and denying it as sending it back. The record names the work order, the review, and the commit digest the review read, and it holds the outcome and the verdict on each criterion the member saw, the member's decision, whether the member agreed, the member's reason when one was given, the repository, and the merge authority level in force. It is evidence and nothing else: no calibration, and no rate computed from it, ever changes a repository's merge authority. Only a member raises or lowers the level.

A review's outcome reads from its verdicts: pass when every criterion passed, fail when any failed, and cannot_judge otherwise.

Three things write no record: a decision of the control plane itself, such as accepting reviewed work at review_approves or sending a failed review back by rule; work no review judged; and a member deciding while the review is still open. A defect found later in work accepted after a pass, recorded as the rework of a done work order, writes a disagreement against that earlier verdict, bound to the same commit digest.

Review agreement is read for the workspace and for each repository, over the last 30 days and over all time, ending at the report's window. It does not follow the report's own span, because a week of agreement says little. Each repository is listed with the merge authority level in force now, so the record reads beside the level it is evidence for.

A review fails work back to a lane by rule until its rounds are used up, so a person meets a failed verdict only at the bound on review rounds. Failures overridden therefore count accepts at that bound.

ropeshift repository show prints the same figures for one repository, and the web UI's operations view shows them in its measures section.

Capacity intervals#

A worker's reports are not kept, so the control plane records from each one when the worker's running lanes stand at one of its lane caps: max_lanes or max_lanes_per_sign_in. The lanes stand at a cap when they reach it or pass it, counted as admission counts them, and a cap of 0 caps nothing. A capacity interval names the worker, the cap, and its value, and holds the first report that saw the cap, the last, and its end, each by the control plane's clock less the report's age.

An interval that stands ends, as far as anyone can read, at the last report that saw it, so a worker that stops reporting ends its intervals at its last heartbeat. Recording takes no revision and appends no event, as keeping the report does, and a report of a session that is no longer current records nothing. The intervals live in the installation database beside the workers they describe.

Change size#

When a lane ends with a commit, its worker records with the lane's result what the lane's branch changed between the base commit its claim named and its final commit: the files changed and the lines added and removed. It reads them from the repository's history with git diff --numstat, detecting renames, so a moved file is one changed file, and a binary file counts as a changed file with no lines. Recording them with the result keeps them independent of a checkout and of a branch deleted after a merge.

The control plane keeps the change size on the lane's branch artifact. A lane with no base commit, a lane that made no commit, and a worker that could not measure the change record none, which is not a change of nothing. GET /v1/work-orders/{id}/acceptance returns it as each artifact's change, with files, added, and removed, and ropeshift work acceptance prints it after the branch's commit.

Delivery records#

Ropeshift derives where each work order's time went from its events, with no model, and keeps a delivery record for every change and rework work order that reaches done, failed, or canceled. The daemon's delivery fold reads what each project's log added every --delivery-tick, from a cursor it keeps, and re-derives each work order an event ends. Its first run reads the log from the start, so it backfills every work order that ended before it.

A timeline covers a work order's time from its first ready to its end with no gap and no overlap, in segments of one kind each:

A wait belongs to the party whose act ended it, so a wait a member ended is always person and never agent time. Each segment names its rework round, its lane, and the act that ended it.

A delivery record holds what an estimate matches on: kind, size, the roster agent and its capability class, the repository and its merge authority level, and the number of criteria. It also holds the model, milestone, plan, outcome, rounds, the time in each segment kind, each wait for a person, the tokens and estimated cost of every lane that served the work order, its review lanes included, and the change size of its last branch. Its four durations are elapsed time, from the first ready to the end; delivery time, which leaves out every wait for a lane; lane time, while a lane of it or of one of its reviews was claimed or running; and person time.

Capacity intervals and change sizes are recorded only from the release that added them. A record whose work began before the fold's first run says so with lane_cap_known false, and a record without a change size has none, which is not a change of nothing. The capability class and merge authority level are read when the record is made. A new version of the derivation drops every timeline and record and folds the log again.

Experience records#

The ledger keeps one experience record per lane and one per decision. Each holds the policy version in force, the settings the action ran on, the options considered, and what was chosen, and its outcome is filled in once, which may be long after the action. Nothing else ever changes a record.

A work order's size is what its contract declares, small, medium, or large, and unknown when it declares none.