A plain-language coordination story

See how AI helpers avoid breaking each other's work

In this example, a team updates checkout. Watch one helper spot a payment problem and RepoToire help another helper fix it before the work is finished.

RepoToire Checkout Story

A simple example · idealized for clarity

Your requestUpdate the checkout page without breaking payments.

RepoToire only lets AI helpers work on the parts you approved.

Slide 1 of 6

You ask for one result

RepoToire keeps this checkout update in view from start to finish.

YouApproved request

You send the checkout request to RepoToire

RepoToireRequest received

Slide 1 of 6: Your approved checkout request is accepted.

Verified Coordination Demo.rpt

Recorded run · time compressed

Inspect one recorded run

The architecture above is idealized. The evidence below comes from one recorded, time-compressed run and is cross-checked against durable run evidence.

Measured lineage time · 12m 1s

Goal

Prove continuous retirement with two independently scoped lanes: - Update only src/alpha.rs from pending to retired-alpha. - Update only src/beta_v2.rs from pending to retired-beta.

Authority and Scheduling.rpt

Authority before execution

Front Door accepts the goal and approved authority; Machine confirms the exact scopes before launch.

Approval
explicit_human_approved_goal_lane
Transition
approved_plan_execution
Schedule
1 parallel-ready group
Readiness
2 ready · 0 blocked
Goal-to-Retirement Chain.rpt

The full proof chain

The visible stages below are the semantic chain. There is no separate hidden copy for the replay to drift away from.

  1. VerifiedGoal and authority acceptedFront Door accepts the goal and approved authority.
  2. VerifiedScopes confirmedMachine confirms the exact scopes before launch.
  3. VerifiedParallel group scheduled1 safe group contains 2 disjoint lanes.
  4. VerifiedWorkers launched2 codex workers launched through the local_process runner.
  5. VerifiedEvidence cross-checked4 gates and 2 checked writebacks passed.
  6. VerifiedJOIN verifiedMachine JOIN used worker_scoreboard_verified trust.
  7. VerifiedFront Door closed1 receipt closed 2 work items as retired.
Bounded Worker Lanes.rpt

Two disjoint write scopes

Lane 1 · verified

src/alpha.rs

One worker, one checked writeback, bounded authority.

Lane 2 · verified

src/beta_v2.rs

One worker, one checked writeback, bounded authority.

Durable Evidence Ledger.rpt

Evidence used to retire the work

Provider
codex
Runner
local_process
Live execution
Live spawn supported
Workers
2 real workers
Required gates
4 authoritative gates
Writebacks
2 checked writebacks
Lineage
10 source lineage events
JOIN authority
machine_join_trust_gate
Trust basis
worker_scoreboard_verified
Receipt
1 retirement receipt
Closure
Front Door: retired
Source artifact SHA-256
7bb30e94c5907afcf0531a29df279f54974a88cf7e5fd3ab62f78312bd29e3ee
What This Proves.txt

What this proves

In this recorded run, approved authority became two disjoint scopes; the Machine scheduled and launched two Codex workers, cross-checked gates and writebacks, passed JOIN, produced one receipt, and closed the Front Door state as retired.

Scope Boundary.txt

What this does not prove

It is not a live run, a speed benchmark, or a guarantee for every repository. It demonstrates one inspectable coordination path and the evidence required for that path to retire cleanly.

Public Proof Artifact.json

The generated public object

The page and download use this same validated object. The source hash binds it to the private verifier report without exposing private paths or worker identifiers.

{
  "schema": "repotoire.public_continuous_goal_retirement_proof.v1",
  "status": "verified",
  "source_artifact_sha256": "7bb30e94c5907afcf0531a29df279f54974a88cf7e5fd3ab62f78312bd29e3ee",
  "run": {
    "id": "evolve-1-20260716T151903140Z-34005df8",
    "goal": "Prove continuous retirement with two independently scoped lanes:\n- Update only src/alpha.rs from pending to retired-alpha.\n- Update only src/beta_v2.rs from pending to retired-beta.",
    "measured_lineage_time_ms": 721101
  },
  "authority": {
    "approval": "explicit_human_approved_goal_lane",
    "transition_reason": "approved_plan_execution"
  },
  "scheduling": {
    "status": "parallel_ready",
    "group_count": 1,
    "ready_count": 2,
    "blocked_count": 0,
    "scopes": [
      "src/alpha.rs",
      "src/beta_v2.rs"
    ]
  },
  "execution": {
    "provider": "codex",
    "runner_kind": "local_process",
    "supports_live_spawn": true,
    "real_worker_count": 2
  },
  "evidence": {
    "authoritative_gate_event_count": 4,
    "checked_writeback_count": 2,
    "source_lineage_event_count": 10
  },
  "retirement": {
    "join_authority": "machine_join_trust_gate",
    "trust_basis": "worker_scoreboard_verified",
    "work_count": 2,
    "retirement_ref": "retirement:machine:evolve-1-20260716T151903140Z-34005df8:cycle:4",
    "receipt_count": 1,
    "front_door_state": "retired"
  }
}
Try Repotoire.dlog

Bring a coordination problem

Join the free beta with a real engineering goal and a repository where agent work needs bounded scopes, scheduling, and evidence-backed retirement.