repopact 2.0.1__tar.gz → 2.0.2__tar.gz

{repopact-2.0.1 → repopact-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repopact
-Version: 2.0.1
+Version: 2.0.2
 Summary: A repository-native standard for durable agent work: binding invariants, evidence-gated work items, and drift audits.
 License: Apache-2.0
 Project-URL: Homepage, https://github.com/ForgeWireLabs/repopact
@@ -22,15 +22,15 @@ cannot be silently weakened.
 > The repository is the pact: authority, intent, evidence, and history that survive every
 > session.
 
-`pip install repopact` · Apache-2.0 · current release **2.0.1**
-([changelog](decisions/0021-preflight-mandatory-and-provenance.md)).
+`pip install repopact` · Apache-2.0 · current release **2.0.2**
+([changelog](decisions/0022-release-2.0.2-installed-seed-lookup.md)).
 
 ## How it relates to `AGENTS.md`
 
 `AGENTS.md` (and `CLAUDE.md`, editor rules) tell an agent *what to do* — they're
 instructions, plain Markdown, with no enforcement. RepoPact is the layer **above** them:
 
-> `AGENTS.md` tells the agent what to do. RepoPact proves it didn't quietly undo it.
+> `AGENTS.md` tells an agent how to behave. RepoPact enforces and records whether the work respected the contract.
 
 RepoPact's distinguishing primitive is the **binding invariant** — a declared guarantee with
 a rationale, an escalation path, and (where its logical type permits) a machine enforcer.
@@ -83,6 +83,14 @@ repopact dashboard
 [`AGENTS.md`](AGENTS.md), then [`governance/charter.md`](governance/charter.md) and
 [`governance/workflow.md`](governance/workflow.md).
 
+Alternative implementations can run the published conformance suite:
+
+```powershell
+python scripts/run_conformance.py --command "your-validator --root {repo}"
+```
+
+See [`CONFORMANCE.md`](CONFORMANCE.md) and [`conformance/`](conformance/).
+
 ## Adopt an *existing* repository
 
 For a project that already has CODEOWNERS, CI workflows, and nested `AGENTS.md` contracts,
@@ -102,7 +110,7 @@ idempotent.
 
 ## 2.0: mandatory preflight + provenance-typed records
 
-Decision [`0021`](decisions/0021-preflight-mandatory-and-provenance.md) (supersedes 0018):
+Decision [`0021`](decisions/0022-release-2.0.2-installed-seed-lookup.md) (supersedes 0018):
 
 - **Mandatory preflight (default on).** No work begins until a work item exists and
   propagates through the pact; `repopact new` stamps the marker. Existing repos grandfather
@@ -132,7 +140,7 @@ holds a [formal model](research/formal-model.md) (the L0–L5 kernel, the typed
 lattice, the adoption trilemma), the pre-registered [experiment protocol](research/protocol.md)
 and [benchmark protocol](research/benchmark-protocol.md) (hypotheses H1–H13, falsification
 criteria, [threats to validity](research/threats-to-validity.md)), a [findings
-register](research/findings.md), and a full [paper draft](research/paper.md).
+register](research/findings.md), and the current [paper](research/paper.md).
 
 **PactBench** — the runnable benchmark suite (pre-registered tasks measuring whether RepoPact
 enforcement reduces silent guarantee drift, with a model-agnostic harness and an S5 drift

{repopact-2.0.1 → repopact-2.0.2}/README.md

@@ -1,144 +1,152 @@
-# RepoPact
-
-RepoPact is a **repository-native governance kernel for durable agent work**. It keeps the
-load-bearing state of a project — intent, authority, evidence, decisions, and drift — as
-typed, version-controlled records in the filesystem, so a new contributor or agent can
-recover where things stand *without* a prior conversation, and so the guarantees that matter
-cannot be silently weakened.
-
-> The repository is the pact: authority, intent, evidence, and history that survive every
-> session.
-
-`pip install repopact` · Apache-2.0 · current release **2.0.1**
-([changelog](decisions/0021-preflight-mandatory-and-provenance.md)).
-
-## How it relates to `AGENTS.md`
-
-`AGENTS.md` (and `CLAUDE.md`, editor rules) tell an agent *what to do* — they're
-instructions, plain Markdown, with no enforcement. RepoPact is the layer **above** them:
-
-> `AGENTS.md` tells the agent what to do. RepoPact proves it didn't quietly undo it.
-
-RepoPact's distinguishing primitive is the **binding invariant** — a declared guarantee with
-a rationale, an escalation path, and (where its logical type permits) a machine enforcer.
-That, plus evidence-gated completion and a filesystem state machine, is what turns a folder
-convention into a contract. `repopact adopt` ingests an existing `AGENTS.md` rather than
-replacing it (decision [`0020`](decisions/0020-launch-positioning-layer-above-agents-md.md)).
-
-## Core loop
-
-```text
-intent -> scoped authority -> work item -> implementation -> evidence -> audit -> history
-```
-
-![RepoPact core loop over a filesystem state machine](docs/assets/repopact-flow.svg)
-
-## Primitives
-
-1. **Charter & invariants** — principles (judgment) and binding invariants
-   (escalation-gated) in `governance/`.
-2. **Frozen surface** — paths and symbols that require operator approval (`--ack`) to change.
-3. **Scopes & roles** — layered `AGENTS.md` contracts plus a role/scope map in
-   `governance/owners.json`.
-4. **Work items** — narrative `README.md` + machine-readable `work-item.json` with
-   evidence-linked acceptance criteria. **Mandatory preflight** (2.0): a work item must be
-   recorded *before* implementation begins (`repopact new` stamps the marker).
-5. **Evidence** — immutable run manifests under `evidence/runs/`.
-6. **Decisions & policies** — durable choices (`decisions/`) and operating rules
-   (`governance/policies/`) whose rationale outlives any single work item.
-7. **Provenance** (2.0) — every record is `concrete`, `provisional`, or `inferred`.
-   `adopt` emits provisional/inferred records (honest, not fabricated); `doctor` ratchets
-   them to `concrete` as real evidence arrives. See *2.0 changes* below.
-8. **Reconciliation** — audits and a *generated* dashboard surface drift and review
-   staleness rather than hand-maintaining it.
-
-## Install & quick start
-
-```powershell
-pip install repopact                # the CLI + reference validator, from PyPI
-repopact init --target ../your-repo # seed a valid RepoPact in a new repo
-cd ../your-repo
-repopact new work-item "Title of the work"   # stamps records (incl. the preflight marker)
-repopact validate
-repopact dashboard
-```
-
-`repopact` dispatches `init`, `adopt`, `validate`, `new`, `dashboard`, `spec`,
-`check-frozen`, `import-plan`, and `doctor`. Records are validated against `schemas/*.json`
-(structure) and by the validator (cross-record semantics; decision
-[`0003`](decisions/0003-validate-records-against-json-schemas.md)). Begin with
-[`AGENTS.md`](AGENTS.md), then [`governance/charter.md`](governance/charter.md) and
-[`governance/workflow.md`](governance/workflow.md).
-
-## Adopt an *existing* repository
-
-For a project that already has CODEOWNERS, CI workflows, and nested `AGENTS.md` contracts,
-`adopt` maps those existing signals into RepoPact records without overwriting anything:
-
-```powershell
-repopact adopt --target ../existing-repo --dry-run   # preview the plan, write nothing
-repopact adopt --target ../existing-repo             # create records, then validate
-repopact doctor                                      # diagnose + repair drift; migrate on upgrade
-```
-
-CODEOWNERS becomes scopes and roles; each `.github/workflows/*` becomes a binding-gate policy
-(plus invariant `INV-2` and a frozen-surface entry); every nested `AGENTS.md` is registered as
-a contract; git history seeds a first **inferred** evidence run, and the adoption record is
-recorded as **provisional** — honestly typed, not a fabricated "completed" claim. Adoption is
-idempotent.
-
-## 2.0: mandatory preflight + provenance-typed records
-
-Decision [`0021`](decisions/0021-preflight-mandatory-and-provenance.md) (supersedes 0018):
-
-- **Mandatory preflight (default on).** No work begins until a work item exists and
-  propagates through the pact; `repopact new` stamps the marker. Existing repos grandfather
-  their pre-2.0 items automatically — `adopt`/`init` set a preflight epoch and `doctor`
-  migrates on upgrade. *This is a breaking change*: run `repopact doctor` after upgrading.
-- **Provenance typing** (`concrete` / `provisional` / `inferred`, default `concrete`). This
-  is the principled escape from the *adoption trilemma*: `adopt` emits provisional/inferred
-  records so the result is both **valid** and **faithful** (reconstruction is labelled, not
-  faked). Completion still requires `concrete` evidence; `doctor` ratchets when it arrives.
-
-## Status is a filesystem transition
-
-Work moves between `work/active`, `work/blocked`, `work/deferred`, and `work/completed`; its
-`work-item.json` status must match its directory. Moving a work item never deletes its
-reasoning, decisions, or evidence links.
-
-## Derive over declare
-
-Anything computable from source records is generated, not authored by hand (the dashboard,
-audit-freshness views, and the derived blocks of `SPEC.md`). Only genuine sources are
-hand-maintained. See policy `001`.
-
-## Evaluation, formal model & the Proving Ground
-
-RepoPact is developed against its own evidence, not assertion. The `research/` lab notebook
-holds a [formal model](research/formal-model.md) (the L0–L5 kernel, the typed invariant
-lattice, the adoption trilemma), the pre-registered [experiment protocol](research/protocol.md)
-and [benchmark protocol](research/benchmark-protocol.md) (hypotheses H1–H13, falsification
-criteria, [threats to validity](research/threats-to-validity.md)), a [findings
-register](research/findings.md), and a full [paper draft](research/paper.md).
-
-**PactBench** — the runnable benchmark suite (pre-registered tasks measuring whether RepoPact
-enforcement reduces silent guarantee drift, with a model-agnostic harness and an S5 drift
-harness) — lives in the **[RepoPact Proving
-Ground](https://github.com/ForgeWireLabs/repopact-proving-ground)**, a throwaway-but-real
-project that consumes RepoPact from PyPI and is driven across every primitive, including cases
-designed to break it. RepoPact defines the *protocol* (`research/`); the Proving Ground hosts
-the runnable suite. *RepoPact defines the pact; the Proving Ground tests whether the pact
-holds under agent pressure.*
-
-## Ecosystem
-
-RepoPact is the work-governance layer of [ForgeWire Labs](https://github.com/ForgeWireLabs) —
-inspectable agentic infrastructure (*inspect the work, bound the authority, preserve the
-evidence*). It composes with Fabric (execution governance) and ForgeLink (human-agent
-communication governance), but is independently useful on its own.
-
-## License & version
-
-Apache-2.0 ([`LICENSE`](LICENSE), decision [`0002`](decisions/0002-license-apache-2.0.md)).
-The spec version is in [`VERSION`](VERSION); templates for every record type live in
-[`templates/`](templates/).
+# RepoPact
+
+RepoPact is a **repository-native governance kernel for durable agent work**. It keeps the
+load-bearing state of a project — intent, authority, evidence, decisions, and drift — as
+typed, version-controlled records in the filesystem, so a new contributor or agent can
+recover where things stand *without* a prior conversation, and so the guarantees that matter
+cannot be silently weakened.
+
+> The repository is the pact: authority, intent, evidence, and history that survive every
+> session.
+
+`pip install repopact` · Apache-2.0 · current release **2.0.2**
+([changelog](decisions/0022-release-2.0.2-installed-seed-lookup.md)).
+
+## How it relates to `AGENTS.md`
+
+`AGENTS.md` (and `CLAUDE.md`, editor rules) tell an agent *what to do* — they're
+instructions, plain Markdown, with no enforcement. RepoPact is the layer **above** them:
+
+> `AGENTS.md` tells an agent how to behave. RepoPact enforces and records whether the work respected the contract.
+
+RepoPact's distinguishing primitive is the **binding invariant** — a declared guarantee with
+a rationale, an escalation path, and (where its logical type permits) a machine enforcer.
+That, plus evidence-gated completion and a filesystem state machine, is what turns a folder
+convention into a contract. `repopact adopt` ingests an existing `AGENTS.md` rather than
+replacing it (decision [`0020`](decisions/0020-launch-positioning-layer-above-agents-md.md)).
+
+## Core loop
+
+```text
+intent -> scoped authority -> work item -> implementation -> evidence -> audit -> history
+```
+
+![RepoPact core loop over a filesystem state machine](docs/assets/repopact-flow.svg)
+
+## Primitives
+
+1. **Charter & invariants** — principles (judgment) and binding invariants
+   (escalation-gated) in `governance/`.
+2. **Frozen surface** — paths and symbols that require operator approval (`--ack`) to change.
+3. **Scopes & roles** — layered `AGENTS.md` contracts plus a role/scope map in
+   `governance/owners.json`.
+4. **Work items** — narrative `README.md` + machine-readable `work-item.json` with
+   evidence-linked acceptance criteria. **Mandatory preflight** (2.0): a work item must be
+   recorded *before* implementation begins (`repopact new` stamps the marker).
+5. **Evidence** — immutable run manifests under `evidence/runs/`.
+6. **Decisions & policies** — durable choices (`decisions/`) and operating rules
+   (`governance/policies/`) whose rationale outlives any single work item.
+7. **Provenance** (2.0) — every record is `concrete`, `provisional`, or `inferred`.
+   `adopt` emits provisional/inferred records (honest, not fabricated); `doctor` ratchets
+   them to `concrete` as real evidence arrives. See *2.0 changes* below.
+8. **Reconciliation** — audits and a *generated* dashboard surface drift and review
+   staleness rather than hand-maintaining it.
+
+## Install & quick start
+
+```powershell
+pip install repopact                # the CLI + reference validator, from PyPI
+repopact init --target ../your-repo # seed a valid RepoPact in a new repo
+cd ../your-repo
+repopact new work-item "Title of the work"   # stamps records (incl. the preflight marker)
+repopact validate
+repopact dashboard
+```
+
+`repopact` dispatches `init`, `adopt`, `validate`, `new`, `dashboard`, `spec`,
+`check-frozen`, `import-plan`, and `doctor`. Records are validated against `schemas/*.json`
+(structure) and by the validator (cross-record semantics; decision
+[`0003`](decisions/0003-validate-records-against-json-schemas.md)). Begin with
+[`AGENTS.md`](AGENTS.md), then [`governance/charter.md`](governance/charter.md) and
+[`governance/workflow.md`](governance/workflow.md).
+
+Alternative implementations can run the published conformance suite:
+
+```powershell
+python scripts/run_conformance.py --command "your-validator --root {repo}"
+```
+
+See [`CONFORMANCE.md`](CONFORMANCE.md) and [`conformance/`](conformance/).
+
+## Adopt an *existing* repository
+
+For a project that already has CODEOWNERS, CI workflows, and nested `AGENTS.md` contracts,
+`adopt` maps those existing signals into RepoPact records without overwriting anything:
+
+```powershell
+repopact adopt --target ../existing-repo --dry-run   # preview the plan, write nothing
+repopact adopt --target ../existing-repo             # create records, then validate
+repopact doctor                                      # diagnose + repair drift; migrate on upgrade
+```
+
+CODEOWNERS becomes scopes and roles; each `.github/workflows/*` becomes a binding-gate policy
+(plus invariant `INV-2` and a frozen-surface entry); every nested `AGENTS.md` is registered as
+a contract; git history seeds a first **inferred** evidence run, and the adoption record is
+recorded as **provisional** — honestly typed, not a fabricated "completed" claim. Adoption is
+idempotent.
+
+## 2.0: mandatory preflight + provenance-typed records
+
+Decision [`0021`](decisions/0022-release-2.0.2-installed-seed-lookup.md) (supersedes 0018):
+
+- **Mandatory preflight (default on).** No work begins until a work item exists and
+  propagates through the pact; `repopact new` stamps the marker. Existing repos grandfather
+  their pre-2.0 items automatically — `adopt`/`init` set a preflight epoch and `doctor`
+  migrates on upgrade. *This is a breaking change*: run `repopact doctor` after upgrading.
+- **Provenance typing** (`concrete` / `provisional` / `inferred`, default `concrete`). This
+  is the principled escape from the *adoption trilemma*: `adopt` emits provisional/inferred
+  records so the result is both **valid** and **faithful** (reconstruction is labelled, not
+  faked). Completion still requires `concrete` evidence; `doctor` ratchets when it arrives.
+
+## Status is a filesystem transition
+
+Work moves between `work/active`, `work/blocked`, `work/deferred`, and `work/completed`; its
+`work-item.json` status must match its directory. Moving a work item never deletes its
+reasoning, decisions, or evidence links.
+
+## Derive over declare
+
+Anything computable from source records is generated, not authored by hand (the dashboard,
+audit-freshness views, and the derived blocks of `SPEC.md`). Only genuine sources are
+hand-maintained. See policy `001`.
+
+## Evaluation, formal model & the Proving Ground
+
+RepoPact is developed against its own evidence, not assertion. The `research/` lab notebook
+holds a [formal model](research/formal-model.md) (the L0–L5 kernel, the typed invariant
+lattice, the adoption trilemma), the pre-registered [experiment protocol](research/protocol.md)
+and [benchmark protocol](research/benchmark-protocol.md) (hypotheses H1–H13, falsification
+criteria, [threats to validity](research/threats-to-validity.md)), a [findings
+register](research/findings.md), and the current [paper](research/paper.md).
+
+**PactBench** — the runnable benchmark suite (pre-registered tasks measuring whether RepoPact
+enforcement reduces silent guarantee drift, with a model-agnostic harness and an S5 drift
+harness) — lives in the **[RepoPact Proving
+Ground](https://github.com/ForgeWireLabs/repopact-proving-ground)**, a throwaway-but-real
+project that consumes RepoPact from PyPI and is driven across every primitive, including cases
+designed to break it. RepoPact defines the *protocol* (`research/`); the Proving Ground hosts
+the runnable suite. *RepoPact defines the pact; the Proving Ground tests whether the pact
+holds under agent pressure.*
+
+## Ecosystem
+
+RepoPact is the work-governance layer of [ForgeWire Labs](https://github.com/ForgeWireLabs) —
+inspectable agentic infrastructure (*inspect the work, bound the authority, preserve the
+evidence*). It composes with Fabric (execution governance) and ForgeLink (human-agent
+communication governance), but is independently useful on its own.
+
+## License & version
+
+Apache-2.0 ([`LICENSE`](LICENSE), decision [`0002`](decisions/0002-license-apache-2.0.md)).
+The spec version is in [`VERSION`](VERSION); templates for every record type live in
+[`templates/`](templates/).

repopact-2.0.2/VERSION

@@ -0,0 +1 @@
+2.0.2

{repopact-2.0.1 → repopact-2.0.2}/pyproject.toml

@@ -31,10 +31,11 @@ py-modules = [
   "track_import",
   "takeover",
   "doctor",
-  "new",
-  "check_frozen_surface",
-  "frontmatter",
-]
+  "new",
+  "check_frozen_surface",
+  "frontmatter",
+  "run_conformance",
+]
 
 [tool.setuptools.package-dir]
 "" = "scripts"
@@ -45,5 +46,5 @@ version = { file = "VERSION" }
 # Seed content shipped so `repopact init` works from an installed wheel. These
 # reference the canonical top-level files (one source of truth — no duplication).
 [tool.setuptools.data-files]
-"share/repopact/schemas" = ["schemas/*.json"]
-"share/repopact/templates" = ["templates/*"]
+"share/repopact/schemas" = ["schemas/*.json"]
+"share/repopact/templates" = ["templates/*"]

repopact-2.0.2/schemas/conformance-manifest.schema.json

@@ -0,0 +1,34 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "conformance-manifest.schema.json",
+  "type": "object",
+  "required": ["suite_version", "fixtures_root", "cases"],
+  "properties": {
+    "suite_version": {"type": "string", "pattern": "^[0-9]+\\.[0-9]+\\.[0-9]+$"},
+    "spec_version_file": {"type": "string"},
+    "fixtures_root": {"type": "string", "minLength": 1},
+    "cases": {
+      "type": "array",
+      "minItems": 1,
+      "items": {
+        "type": "object",
+        "required": ["id", "path", "expect", "rules", "description"],
+        "properties": {
+          "id": {"type": "string", "minLength": 1},
+          "path": {"type": "string", "minLength": 1},
+          "overlay_on": {"type": "string", "minLength": 1},
+          "expect": {"enum": ["accept", "reject"]},
+          "expected_message": {"type": "string"},
+          "rules": {"type": "array", "items": {"type": "string"}, "minItems": 1},
+          "description": {"type": "string", "minLength": 1}
+        },
+        "allOf": [
+          {
+            "if": {"properties": {"expect": {"const": "reject"}}},
+            "then": {"required": ["expected_message", "overlay_on"]}
+          }
+        ]
+      }
+    }
+  }
+}

{repopact-2.0.1 → repopact-2.0.2}/scripts/init_repo.py

@@ -11,6 +11,7 @@ from __future__ import annotations
 import argparse
 import json
 import shutil
+import site
 import sys
 from datetime import date, timedelta
 from pathlib import Path
@@ -26,13 +27,16 @@ MODULES = (
 
 def _seed_dir(name: str) -> Path:
     """Locate seed content (schemas/templates) in a checkout or an installed wheel."""
-    checkout = CHECKOUT / name
-    if checkout.is_dir():
-        return checkout
-    installed = Path(sys.prefix) / "share" / "repopact" / name
-    if installed.is_dir():
-        return installed
-    raise FileNotFoundError(f"cannot locate seed '{name}' (looked in {checkout} and {installed})")
+    candidates = [
+        CHECKOUT / name,
+        Path(sys.prefix) / "share" / "repopact" / name,
+        Path(site.USER_BASE) / "share" / "repopact" / name,
+    ]
+    for candidate in candidates:
+        if candidate.is_dir():
+            return candidate
+    looked = ", ".join(str(candidate) for candidate in candidates)
+    raise FileNotFoundError(f"cannot locate seed '{name}' (looked in {looked})")
 
 
 def _write(path: Path, text: str) -> None:

{repopact-2.0.1 → repopact-2.0.2}/scripts/repopact.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repopact
-Version: 2.0.1
+Version: 2.0.2
 Summary: A repository-native standard for durable agent work: binding invariants, evidence-gated work items, and drift audits.
 License: Apache-2.0
 Project-URL: Homepage, https://github.com/ForgeWireLabs/repopact
@@ -22,15 +22,15 @@ cannot be silently weakened.
 > The repository is the pact: authority, intent, evidence, and history that survive every
 > session.
 
-`pip install repopact` · Apache-2.0 · current release **2.0.1**
-([changelog](decisions/0021-preflight-mandatory-and-provenance.md)).
+`pip install repopact` · Apache-2.0 · current release **2.0.2**
+([changelog](decisions/0022-release-2.0.2-installed-seed-lookup.md)).
 
 ## How it relates to `AGENTS.md`
 
 `AGENTS.md` (and `CLAUDE.md`, editor rules) tell an agent *what to do* — they're
 instructions, plain Markdown, with no enforcement. RepoPact is the layer **above** them:
 
-> `AGENTS.md` tells the agent what to do. RepoPact proves it didn't quietly undo it.
+> `AGENTS.md` tells an agent how to behave. RepoPact enforces and records whether the work respected the contract.
 
 RepoPact's distinguishing primitive is the **binding invariant** — a declared guarantee with
 a rationale, an escalation path, and (where its logical type permits) a machine enforcer.
@@ -83,6 +83,14 @@ repopact dashboard
 [`AGENTS.md`](AGENTS.md), then [`governance/charter.md`](governance/charter.md) and
 [`governance/workflow.md`](governance/workflow.md).
 
+Alternative implementations can run the published conformance suite:
+
+```powershell
+python scripts/run_conformance.py --command "your-validator --root {repo}"
+```
+
+See [`CONFORMANCE.md`](CONFORMANCE.md) and [`conformance/`](conformance/).
+
 ## Adopt an *existing* repository
 
 For a project that already has CODEOWNERS, CI workflows, and nested `AGENTS.md` contracts,
@@ -102,7 +110,7 @@ idempotent.
 
 ## 2.0: mandatory preflight + provenance-typed records
 
-Decision [`0021`](decisions/0021-preflight-mandatory-and-provenance.md) (supersedes 0018):
+Decision [`0021`](decisions/0022-release-2.0.2-installed-seed-lookup.md) (supersedes 0018):
 
 - **Mandatory preflight (default on).** No work begins until a work item exists and
   propagates through the pact; `repopact new` stamps the marker. Existing repos grandfather
@@ -132,7 +140,7 @@ holds a [formal model](research/formal-model.md) (the L0–L5 kernel, the typed
 lattice, the adoption trilemma), the pre-registered [experiment protocol](research/protocol.md)
 and [benchmark protocol](research/benchmark-protocol.md) (hypotheses H1–H13, falsification
 criteria, [threats to validity](research/threats-to-validity.md)), a [findings
-register](research/findings.md), and a full [paper draft](research/paper.md).
+register](research/findings.md), and the current [paper](research/paper.md).
 
 **PactBench** — the runnable benchmark suite (pre-registered tasks measuring whether RepoPact
 enforcement reduces silent guarantee drift, with a model-agnostic harness and an S5 drift

{repopact-2.0.1 → repopact-2.0.2}/scripts/repopact.egg-info/SOURCES.txt

@@ -3,6 +3,7 @@ README.md
 VERSION
 pyproject.toml
 schemas/audit-finding.schema.json
+schemas/conformance-manifest.schema.json
 schemas/evidence-run.schema.json
 schemas/frozen-surface.schema.json
 schemas/invariants.schema.json
@@ -19,6 +20,7 @@ scripts/new.py
 scripts/plan_import.py
 scripts/repo_model.py
 scripts/repopact_cli.py
+scripts/run_conformance.py
 scripts/takeover.py
 scripts/track_import.py
 scripts/validate_repo.py

{repopact-2.0.1 → repopact-2.0.2}/scripts/repopact.egg-info/top_level.txt

@@ -9,6 +9,7 @@ new
 plan_import
 repo_model
 repopact_cli
+run_conformance
 takeover
 track_import
 validate_repo

repopact-2.0.2/scripts/run_conformance.py

@@ -0,0 +1,112 @@
+"""Run the published RepoPact conformance suite.
+
+The runner materializes each fixture as an isolated temporary repository, injects
+the canonical schemas from this checkout, runs a RepoPact implementation, and
+compares the result with conformance/manifest.json.
+"""
+
+from __future__ import annotations
+
+import argparse
+import json
+import shutil
+import subprocess
+import sys
+import tempfile
+from dataclasses import dataclass
+from pathlib import Path
+
+
+ROOT = Path(__file__).resolve().parents[1]
+MANIFEST = ROOT / "conformance" / "manifest.json"
+
+
+@dataclass(frozen=True)
+class CaseResult:
+    case_id: str
+    passed: bool
+    detail: str
+
+
+def load_manifest(path: Path = MANIFEST) -> dict:
+    with path.open(encoding="utf-8") as handle:
+        data = json.load(handle)
+    if not isinstance(data, dict):
+        raise ValueError(f"manifest must be a JSON object: {path}")
+    return data
+
+
+def _copy_overlay(src: Path, dst: Path) -> None:
+    for path in src.rglob("*"):
+        if path.is_dir() or path.name == "meta.json":
+            continue
+        target = dst / path.relative_to(src)
+        target.parent.mkdir(parents=True, exist_ok=True)
+        shutil.copy2(path, target)
+
+
+def materialize_case(root: Path, fixtures_root: Path, case: dict) -> Path:
+    repo = root / "repo"
+    overlay_on = case.get("overlay_on")
+    if overlay_on:
+        shutil.copytree(fixtures_root / str(overlay_on), repo)
+        _copy_overlay(fixtures_root / str(case["path"]), repo)
+    else:
+        shutil.copytree(fixtures_root / str(case["path"]), repo)
+    shutil.copytree(ROOT / "schemas", repo / "schemas")
+    return repo
+
+
+def run_command(command: str, repo: Path) -> subprocess.CompletedProcess[str]:
+    rendered = command.format(repo=str(repo))
+    return subprocess.run(rendered, shell=True, text=True, capture_output=True)
+
+
+def evaluate_case(case: dict, command: str, fixtures_root: Path) -> CaseResult:
+    case_id = str(case["id"])
+    with tempfile.TemporaryDirectory(prefix=f"repopact-conformance-{case_id}-") as tmp:
+        repo = materialize_case(Path(tmp), fixtures_root, case)
+        proc = run_command(command, repo)
+    output = "\n".join(part for part in (proc.stdout, proc.stderr) if part)
+    expect = case.get("expect")
+    if expect == "accept":
+        passed = proc.returncode == 0
+        detail = "accepted" if passed else f"expected accept, exit={proc.returncode}: {output.strip()}"
+        return CaseResult(case_id, passed, detail)
+    expected = str(case.get("expected_message", ""))
+    passed = proc.returncode != 0 and expected in output
+    detail = (
+        f"rejected with '{expected}'"
+        if passed
+        else f"expected reject containing '{expected}', exit={proc.returncode}: {output.strip()}"
+    )
+    return CaseResult(case_id, passed, detail)
+
+
+def run_suite(command: str, manifest_path: Path = MANIFEST) -> list[CaseResult]:
+    manifest = load_manifest(manifest_path)
+    fixtures_root = manifest_path.parent / str(manifest.get("fixtures_root", "fixtures"))
+    return [evaluate_case(case, command, fixtures_root) for case in manifest.get("cases", [])]
+
+
+def main() -> int:
+    parser = argparse.ArgumentParser(description="Run the RepoPact conformance suite")
+    parser.add_argument("--manifest", type=Path, default=MANIFEST)
+    parser.add_argument(
+        "--command",
+        default=f'"{sys.executable}" "{ROOT / "scripts" / "validate_repo.py"}" --root "{{repo}}"',
+        help="Implementation command template; {repo} is replaced with the fixture repo path.",
+    )
+    args = parser.parse_args()
+
+    results = run_suite(args.command, args.manifest.resolve())
+    failed = [result for result in results if not result.passed]
+    for result in results:
+        status = "PASS" if result.passed else "FAIL"
+        print(f"{status} {result.case_id}: {result.detail}")
+    print(f"\n{len(results) - len(failed)}/{len(results)} conformance cases passed.")
+    return 1 if failed else 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

{repopact-2.0.1 → repopact-2.0.2}/tests/test_conformance.py

@@ -1,9 +1,9 @@
-"""Conformance corpus test (work item 006, issue #4).
+"""Conformance corpus test (work items 006 and 019).
 
-Validates the fixtures under tests/fixtures/: the valid baseline must be accepted,
-and each invalid overlay must be rejected with its declared message. Fixtures do
-not vendor schemas; the canonical schemas/ are injected here so a fixture can never
-pass against a stale schema copy (no drift).
+Validates the published suite under conformance/: the valid baseline must be
+accepted, and each invalid overlay must be rejected with its declared message.
+Fixtures do not vendor schemas; the canonical schemas/ are injected here so a
+fixture can never pass against a stale schema copy (no drift).
 """
 
 from __future__ import annotations
@@ -15,12 +15,17 @@ import tempfile
 import unittest
 from pathlib import Path
 
+import jsonschema
+
 ROOT = Path(__file__).resolve().parents[1]
 sys.path.insert(0, str(ROOT / "scripts"))
 
 from validate_repo import validate  # noqa: E402
 
-FIXTURES = ROOT / "tests" / "fixtures"
+import run_conformance  # noqa: E402
+
+MANIFEST = ROOT / "conformance" / "manifest.json"
+FIXTURES = ROOT / "conformance" / "fixtures"
 VALID = FIXTURES / "valid"
 INVALID = FIXTURES / "invalid"
 
@@ -39,6 +44,22 @@ def build_repo(dst: Path, overlay: Path | None = None) -> Path:
 
 
 class ConformanceTests(unittest.TestCase):
+    def test_manifest_is_structurally_valid(self) -> None:
+        manifest = json.loads(MANIFEST.read_text(encoding="utf-8"))
+        schema = json.loads((ROOT / "schemas" / "conformance-manifest.schema.json").read_text(encoding="utf-8"))
+        jsonschema.Draft202012Validator(schema).validate(manifest)
+        self.assertEqual((ROOT / "VERSION").read_text(encoding="utf-8").strip(), manifest["suite_version"])
+        for case in manifest["cases"]:
+            self.assertTrue((FIXTURES / case["path"]).exists(), case["path"])
+
+    def test_manifest_matches_reference_suite(self) -> None:
+        results = run_conformance.run_suite(
+            f'"{sys.executable}" "{ROOT / "scripts" / "validate_repo.py"}" --root "{{repo}}"',
+            MANIFEST,
+        )
+        self.assertTrue(results, "no conformance cases found")
+        self.assertEqual([], [result.detail for result in results if not result.passed])
+
     def test_valid_fixture_is_accepted(self) -> None:
         with tempfile.TemporaryDirectory() as tmp:
             repo = build_repo(Path(tmp) / "repo")

repopact-2.0.1/VERSION

@@ -1 +0,0 @@
-2.0.1