Updated
RepoPact gives AI coding agents and human reviewers a shared local contract for software work: what exists, what is ready, what proof was captured, what changed in review, and what should happen next.
Workflow evidence that lives with the code.
Abstract
RepoPact keeps actionable work, sequences, reviews, validation, decisions, handoffs, run records, snapshots, and archives in repository-owned files.
Generated boards and packets are projections; the repo artifact graph remains authoritative.
What it captures
- Work items and work sequences
- Validation records and durable proof refs
- Review rounds, decisions, and handoffs
- Archive snapshots and lineage
Agents get exact next actions.
Abstract
RepoPact exposes compact JSON and role-scoped commands so agents can ask what to read, what state they are in, and which command is safe to run next.
Agents do not have to treat prose or dashboards as source of truth.
What it returns
- Required reads before a state transition
- The current role and workflow state
- Safe next commands with exact arguments
- Machine-readable output by default
Every PR can carry its proof.
Abstract
Validation records, durable proof refs, review findings, decisions, handoffs, and archive lineage flow into a generated Work Packet for PRs, audits, and local review.
Packet output is useful because the repository records remain the authority behind it.
What travels with work
- Validation proof and command outcomes
- Review findings and repair history
- Human or agent decisions
- Handoff context and archive lineage
Execution can evolve without losing the audit trail.
Abstract
RepoPact does not force one universal execution process.
Versioned workflow extensions let execution happen in the right tool or agent flow, then adapters capture normalized run events, chronology, snapshots, and proof into RepoPact’s evidence model.
What stays stable
- Normalized run events
- Execution chronology
- Snapshots tied to workflow state
- Proof captured into the evidence model
Who it’s for
- Teams using AI coding agents inside Git repositories.
- Reviewers who need proof, findings, repair history, and handoff context.
- Platform and engineering leads who want local-first governance without starting from a hosted project-management system.
- Agent-heavy teams that need workflow evidence to survive across runs, reviewers, and handoffs.
Technical specs
The workflow surface.
RepoPact is in development as a local-first Rust CLI centered on repository-owned workflow records.
- Runtime
- Rust CLI
- Primary command
./repo-pact- Storage
repo-pact-work/in the managed repository- Public surfaces
- Default JSON ·
--agent· selected--humanrenderings - Evidence model
- Work Items · Work Sequences · Reviews · Decisions · LOG · VAL · Run Events · EW Chronology · Snapshots · Work Packets
- Core posture
- Local-first; no hosted database, account, or telemetry required by the core workflow
- Status
- In development