ropeshiftInstall
MenuClose

Diagrams

Diagrams of how ropeshift works, in a light and a dark theme. Open any of them at full size.

How work flows. In this release: solo mode, one machine. Planned work becomes verified outcomes. A person is interrupted only when a person is needed. Ropewalk, plan to merge. 01, Plan: A person or a planning agent writes the plan and its contracts. 02, Contract review: Every question it can find, in one batch, before work starts. A dashed arrow labeled questions leads from Contract review to a box reading: You, only when needed. 03, Orchestrator: Claims ready work and starts lanes. 04, lanes in parallel. wo-12 Lane: One writer, one git worktree. wo-13 Lane: One writer, one git worktree. wo-14 Lane: One writer, one git worktree. 05, Review: Checks the work against contracts and requirements. A dashed arrow labeled sent back leads from Review to the lanes. 06, Merge: A pull request or git, at the merge authority level you choose. ropeshift.com.
How work flowsLight, full size (How work flows)Dark, full size (How work flows)
A question climbs a ladder. Never ask twice. Interrupt a person last. Five rungs, listed from the top. 5, A person. Ask: Only now is a person interrupted. An arrow labeled still open leads up to this rung. 4, A recorded assumption. Assume: Safe to assume? Record the assumption. An arrow labeled still open leads up to this rung. 3, A decision within policy. Decide: Inside your policy? Decide and record why. An arrow labeled still open leads up to this rung. 2, Open questions. Share: Already asked? Share it. Never ask twice. An arrow labeled still open leads up to this rung. 1, Existing decisions. Reuse: Answered before? Reuse the decision. ropeshift.com.
A question climbs a ladderLight, full size (A question climbs a ladder)Dark, full size (A question climbs a ladder)
Park, don't wait. A lane that cannot proceed saves its work and stops. It resumes when the answer arrives. One lane. Working: Writing code in its own worktree. Cannot proceed: Needs an answer it does not have. Parked: Work saved, no quota used. Answer arrives: From the ladder, or from a person. Resumes: Where it left off, with its work intact. The answer comes from the question ladder. A person is its last rung. ropeshift.com.
Park, don't waitLight, full size (Park, don't wait)Dark, full size (Park, don't wait)
FOUR PARTS, ONE ROPE. Four parts, one record of the work. 01 Work ledger: The system of record for execution: claims, outcomes, questions, decisions, and evidence. A local ledger per project; one installation holds many isolated projects. Works from repository files, with no tracker required. 02 Planning and decisions: A planning session turns your answers into requirements, documents, milestones, and contracts. Approved as one plan; adopt an existing project the same way. Contract review finds questions before work starts. A searchable record of every decision. 03 Supervised agents: One orchestrator per machine pulls work and exercises judgment. A daemon keeps each session healthy; a fence stops a holder that lost its claim from writing. Lanes run as the agent from a roster you edit. A review agent checks each finished lane. 04 Web UI: Needs you across every project, with confirmation cards. Roadmap, plans and plan approval, the planning pane, documents traced to work and verdicts. The floor of lanes, measures, and conversations with the assistant and agents. Each project's repositories, agent roster, settings, and audit. ropeshift.com
Four parts, one ropeLight, full size (Four parts, one rope)Dark, full size (Four parts, one rope)