Skip to main content

Evidence and Gates

This route previously documented the old diff analyzer. In the current Machine architecture, the important question is not "what finding changed?" but "is this worker's evidence fresh enough to write back?"

Local Loop

# 1. Inspect runtime state
repotoire machine report .

# 2. Run the next program transition
repotoire machine evolve .

# 3. Review evidence and gate verdicts
repotoire machine report . --format json

What To Inspect

  • .machine/state.json for pc, flags, registers, counters, and trap state.
  • .machine/events.jsonl for runtime events and worker activity.
  • Worker packets for task intent, write claims, and completion contracts.
  • Verification verdicts before JOIN and COMMIT.
  • Scoreboard hazards before writeback.

CI Usage

repotoire machine report . --format json > machine-report.json
jq '.verification.gates' machine-report.json

CI should evaluate team-approved gates and fail only on the runtime states your team has chosen to block.

See Also