Skip to main content

Run agents as a local machine.

Repotoire gives agents a small, inspectable computer: explicit programs, reserved write claims, verified gates, and precise traps before writeback.

Request beta accessRead the architecture
Repotoire Station · Signal Path

GOAL ▸ “tokenize GuidedFlow.css against the App.css design tokens”

START HERE ▸ src/

LOADdeterministic_evidence_decodeTESTIMPLVERIFYCOMMITHELDtrust_level: unknown

Hover or tap a stage to inspect its evidence.

Readout
lane: microtoken_budget: 8000time_ms: 900000cache_missworkflow_calibration_untrained

Real capture · repotoire 0.1.0-beta.6 · . · 2026-07-27

Inspect the raw packet
## Machine packetentered: trueselected_lane: microrecommended_lane: microtoken_budget: 8000time_ms: 900000trust_level: Unknown ### Runtime units- workflow_decide: executed- deterministic_evidence_decode: executed- bounded_context_fetch: planned- focused_verifier: planned ### Reason codes- cache_miss- workflow_calibration_untrained
Real run · repotoire agent run --goal "tokenize GuidedFlow.css against the App.css design tokens" . · repotoire 0.1.0-beta.6 · 2026-07-27

1.0 Load

Repotoire boots on your repository and loads real state. This is the runtime contract an agent receives — not a chat transcript.

Runtime Contract
Runtime contract: plain agent chat versus Repotoire
Runtime contractPlain agent chatRepotoire
Instruction setPrompts and intentionsLOAD · TEST · IMPL · VERIFY · COMMIT
Durable memoryWhatever changed locallyCommitted git history only
Parallel workersUntracked overlapScoreboard with RAW/WAR/WAW hazards
Completion proofAssistant says doneEvidence packets plus gate verdicts
Stale contextDiscovered latePrecise trap before writeback

2.0 Test

Verification is named first. The Machine records what will decide the outcome before it changes anything, so “done” is a gate verdict rather than an assertion.

  1. Declare the gates

    Name the tests, typecheck, and lint that decide done — before any worker touches a file.

  2. Reserve write claims

    Workers reserve the paths they will edit; overlaps surface as RAW/WAR/WAW hazards on the scoreboard.

  3. Bound the lane

    The Machine picks a lane and sets token and time budgets up front, so scope is explicit before execution.

3.0 Impl

Provider adapters let Claude, Codex, MCP tools, and local runners execute worker packets while Repotoire holds the stable contract: write claims, evidence packets, gates, and precise traps.

The brief beside this is real output from the front door — the lane it selected, the evidence status, and the next safe action the adapters are cleared to take.

Agent Execution Brief
status: quick_checklane: microevidence_status: partialsummary: Machine selected the lightweight fast path inside the same trust boundarynext_action: start_lanenext_action_detail: Start here: inspect src/ and confirm the touched scope before editing
Real run · repotoire agent run --goal "tokenize GuidedFlow.css against the App.css design tokens" . · repotoire 0.1.0-beta.6 · 2026-07-27

4.0 Verify

Gates run and the evidence is judged. A agent-processor runtime for development work reports what it may and may not claim — trust is a stated level, not a vibe.

Proof
trust_level
unknown
Allowed actions
perform the scoped micro-lane task
Forbidden inferences
do not treat cache hits, provider success, or worker claims as correctness proof
do not claim proof, merge safety, or unattended completion from this brief
Real run · repotoire agent run --goal "tokenize GuidedFlow.css against the App.css design tokens" . · repotoire 0.1.0-beta.6 · 2026-07-27

Underneath: machine programs, source-pipeline evidence, precise traps, and MCP adapters. Only verified gates and explicit commands move code into durable git history.

5.0 Commit

Commit Gate

Only verified gates move code into durable git history.

Repotoire is in private beta for teams that want explicit, inspectable development workflows — without handing their repository to a hosted scheduler.

Request beta accessRead the architecture

Questions, answered plainly.