CLI Overview

Local Machine runtime inspection and execution from your terminal.

New here? Start with the five-step flow: break down the task, review the Goal Program, compile an ISA executable, run the APU, and retire checked results.

This reference covers the runtime underneath that flow. Approving goal intent does not authorize execution; approval must bind the exact executable image. Current v1 instructions run serially. Retirement does not commit, merge, or deploy your code.

Access

RepoToire is a commercial private beta. CLI binaries and setup guidance are provided directly during onboarding.

Quick Start

# Inspect Machine state
repotoire machine report .

# Emit an event into the runtime log
repotoire machine emit-event .

# Run a program flow
repotoire machine evolve .

Commands

Command	Description
`machine report`	Print pc, flags, registers, git fingerprints, and recent runtime state
`machine emit-event`	Append a structured event into `.machine/events.jsonl`
`machine evolve`	Run the next Machine program transition
`machine spawn`	Validate a worker packet and reserve write claims
`machine join`	Evaluate completion contracts, evidence, gates, and hazards
`machine doctor`	Check local runtime health and adapter configuration
`machine clean`	Remove generated runtime caches that are safe to rebuild

Machine Model

Git history is durable memory. The working tree is a write buffer. Git publication happens outside the Machine ISA.

Reports

# Human-readable report
repotoire machine report .

# JSON report for CI or automation
repotoire machine report . --format json

# Event stream inspection
tail -f .machine/events.jsonl

Common Workflows

Daily Development

# Check the runtime before starting
repotoire machine report .

# Run the next explicit program step
repotoire machine evolve .

# Verify gates before writeback
repotoire machine report . --format json

CI/CD Integration

# Emit machine report for policy evaluation
repotoire machine report . --format json > machine-report.json

# CI decides which gates block the build
jq '.verification.gates' machine-report.json

Provider Adapter Integration

# Spawn a worker packet for a provider adapter
repotoire machine spawn claude worker.json

# Join after evidence is returned
repotoire machine join worker-42

Configuration

Beta onboarding maps the runtime to your repo, trusted binary path, command policy, and adapter settings.

# Inspect local runtime health
repotoire machine doctor .

Trust Boundaries

Commands are explicit. Networked operations require visible intent. Provider adapters preserve the Machine contract instead of defining it.

Machine ISA

The stable instruction vocabulary is LOAD, TEST, IMPL, VERIFY, JOIN, BNZ, TRAP, and HALT.

Exit Codes

Code	Meaning
0	Success
1	General error
2	Verification gate or trap blocked progress