Independent project / In development
RepoToire
A runtime for AI coding agents.
An agent can propose a change. Deciding what may execute, what counts as success, and when to stop needs a clearer contract.
- Rust
- Quint
- Code intelligence
- Runtime prototype
Inside the runtime
I’m building a Rust runtime around an instruction set for coding agents. Codebase context informs a Goal Program; a compiler turns that program into an executable. Approval is tied to that exact image before the runtime admits it.
One compiled repair sequence
LOAD → TEST → IMPL → VERIFY → BNZ → HALT
These are instructions. Each one runs through the five stages shown here. TEST runs a repository check; VERIFY dispatches an agent to verify the work. BNZ can return to IMPL within a fixed retry limit.
Conformance tests replay Quint traces against the Rust runtime and compare the execution stage, instruction, and Machine state.
Ask me about RepoToireYour goal + current codebase context
- Goal ProgramTargets, constraints, success criteria
- Compiler → executableValidated instructions and repository checks
- Human approvalBound to this executable’s exact image hash
Read the next instruction.
The runtime reads the program counter and latches an instruction from the approved executable. Later stages check that they are still using the same image.
Input: approved executable + program counterEach instruction passes through these five stages. This diagram explains the design; it is not a live execution trace.