RepoPact 3.1.3

Downloadable Workbench installers release. Backward-compatible: no schema, protocol, CLI subcommand semantics, lifecycle, or provenance compatibility break from 3.1.2.

What's in this release

• Downloadable Workbench installers, attached below for the first time: Windows NSIS (.exe) and MSI (.msi) installers, a Linux .deb package, and a signed Android release APK. WI062 previously proved these build/install/launch correctly, but none were ever publicly attached to a release until now.
• Windows/macOS artifacts are unsigned (an explicit cost/time decision, not an oversight) — expect a SmartScreen/Gatekeeper warning on first run.
• Android is signed with RepoPact's own release key (not affiliated with Google Play) — enable "install unknown apps" to sideload.
• Mandatory documentation-impact closure (decision 0065, opt-in, epoch-grandfathered): work items can now declare documentation_impact at completion; disabled by default, no effect on existing adopters.

See decision 0066 for the full rationale.

pip install --upgrade repopact

Platform	Artifact
Windows	RepoPact-Workbench-3.1.3-x64-setup.exe or RepoPact-Workbench-3.1.3-x64.msi
Linux (Debian/Ubuntu)	RepoPact-Workbench-3.1.3-amd64.deb
Android	RepoPact-Workbench-3.1.3-android-universal.apk

RepoPact 3.1.2

Corrective patch release. Backward-compatible: no schema, protocol, CLI subcommand semantics, lifecycle, or provenance compatibility change from 3.1.1.

What's in this release

• repopact --version: a conventional top-level version flag, sourced from the existing governed package identity. Exits 0 without requiring a subcommand.
• Package/native-engine identity hardening: the Workbench type generator (generate-types.mjs) no longer defaults CARGO_TARGET_DIR to a shared machine-wide temp directory, eliminating a cross-checkout build-cache corruption risk; local Python package and native repopact-engine build identity are reconciled and verified to agree.
• Validation/release-state reconciliation: fixes to the conformance suite's Python compatibility comparator (severity filtering) and its assurance-overclaiming heuristic (negation-aware phrase matching), plus test-portability fixes found while cross-verifying on Linux.

No new governance capability or compatibility line is introduced. See decision 0064 for the full rationale, and decision 0063 for 3.1.1's corrective history.

pip install --upgrade repopact

RepoPact 2.1.0

Minor release: the proposed work lifecycle state.

• New lifecycle state proposed and work/proposed/ directory: captured candidate work that does not grant implementation authority (decision 0023).
• New semantic rule: active/completed work items may not depend on proposed ones (SPEC §4.3).
• repopact new work-item "Title" --status proposed; init creates work/proposed/.
• Conformance suite_version 2.1.0 with two new cases: a valid proposed item and a rejection overlay for active-depends-on-proposed.
• Release rationale and evidence: decision 0024.

No existing 2.0.x repository becomes invalid; the record language change is additive.

RepoPact 2.0.0

RepoPact 2.0 — mandatory preflight by default and provenance-typed records.

Breaking changes

• Preflight is mandatory by default. No work begins until a work item is created and
  propagated through the pact; repopact new stamps the marker automatically. Existing
  repos grandfather their pre-2.0 items — adopt/init set a required_from_date epoch,
  doctor migrates on upgrade. (Decision 0021 supersedes 0018.)
• Provenance-typed records (concrete / provisional / inferred, default concrete)
  on work items and evidence runs. adopt now emits provisional records backed by
  inferred evidence — resolving the adoption trilemma in the implementation (Closed
  and Faithful), not merely relaxing it. doctor ratchets provisional → concrete as
  real evidence arrives. L2 enforces admission (P1), completion-requires-concrete (P2),
  and consistency (P3).

Also in this line

• Comparative benchmark suite scaffolding: PactBench (24 pre-registered tasks across six
  security classes + adversarial evidence-fabrication and context-injection), 10 real
  fixtures, a runnable S5 drift harness, and a model-agnostic harness with a subprocess
  RealRunner. Full paper draft + figure mockups under research/.

Migration: run repopact doctor after upgrading to grandfather pre-2.0 work items.
Full suite: 91 tests passing (2 honest skips for open obligations O-4/O-6).

RepoPact 1.4.0

RepoPact 1.4.0 — full adoption lifecycle.

Adds the complete onboard→retire toolchain: adopt (brownfield onboarding), import-plan (todos, checklists, section roadmaps, GitHub issues, and tracking/ governance folders → work items / decisions / audit findings), doctor (diagnose & repair drift), and takeover (retire a fully-migrated legacy method — archive or delete).

Proven on three independent real adopters (forgewire, Flask, SkillForge Academy) plus the greenfield proving ground. First PyPI release.

pip install repopact

RepoPact 1.0.0

First stable release.

RepoPact is a repository-native operating system for durable agent work: binding invariants, scoped authority, evidence-gated work items, and drift audits kept inside the repo.

1.0 is backed by adopter evidence (see research/):

• Greenfield: an independent proving-ground CLI adopted RepoPact from the wheel and held five of six pre-registered hypotheses; the two defects found were fixed (work item 007).
• Brownfield: repopact adopt brought the real forgewire repo (4569 commits, 19 nested contracts, 7 CODEOWNERS scopes, 4 CI gates) under RepoPact non-destructively, and the result validates (work item 008).

See decision 0007 for the 1.0 rationale. Install: pip install repopact-1.0.0-py3-none-any.whl (PyPI publish to follow).

RepoPact v0.1.0-alpha

First public, intentionally-alpha release of RepoPact — a repository-native standard for durable agent work.

RepoPact governs its own development, so this repository is both the product and the evidence: real invariants, a frozen surface, work items with acceptance criteria, evidence runs, decisions, and a reconciliation finding.

Highlights

• The pact: binding invariants with escalation, distinct from principles.
• Adoption: python scripts/init_repo.py --target ./your-repo bootstraps a valid repo; templates + scripts/new.py stamp records.
• Normative SPEC.md with a generated record-type catalog and conformance section; validate_repo.py is the reference implementation.
• Diátaxis docs: tutorial, concepts, how-to guides.
• Derive over declare: dashboard and SPEC catalog are generated; CI fails if they drift.

Why alpha

Days old and not yet validated by external adopters. Confidence is not evidence — VERSION is 0.1.0 and 1.0 waits for real-world use. See decision 0005.

Start with docs/adopt-repopact.md and SPEC.md. Questions welcome in Discussions; good first issues are labeled.