Claude Code as a Machine adapter
Let Claude execute worker packets while RepoToire owns machine programs, source-pipeline evidence, precise traps, and MCP adapters. The provider can change; the program, evidence, gates, and traps stay stable.
repotoire machine spawn claude worker.json✓ write claims reserved✓ evidence packet receivedVERIFY -> flags.Z=1, trap=noneJOIN -> hazards=0
How it works
Machine reserves write claims
RepoToire validates the worker packet, records git fingerprints, and reserves the files the worker may touch.
Claude executes bounded work
The adapter runs Claude inside the completion contract and returns evidence to the source pipeline.
JOIN evaluates gates
RepoToire checks evidence, hazards, and verification verdicts before any explicit writeback step.
What you get
Worker packets
Claude receives a bounded packet with task intent, write claims, and completion contract.
Source-pipeline evidence
Context, changes, and verification outputs are captured as reviewable artifacts.
Explicit command trust
Commands are previewed and policy-gated before work can affect the repo.
Precise traps
Stale evidence and failed gates stop writeback with a clean restart point.
Stable Machine semantics
The adapter can change without changing opcodes, gates, hazards, or writeback rules.
Controlled teardown
Adapter configuration can be removed without altering unrelated tool settings.
Configure Adapter
repotoire machine report .✓ state loaded from .machine/state.jsonrepotoire machine spawn claude worker.json✓ packet accepted, write claims reservedJOIN: gates passed, hazards=0
5.0 Commit
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.