Remove evidence-certification bookkeeping; keep the benchmark harness

.dialyzer_ignore.exs

@@ -37,7 +37,7 @@
    {286, 30}},
   # defensive clause for non-covered differential rows
   {"bench/imp/benchmark_truth/optimize_anything/upstream_differential.ex", :pattern_match_cov,
-   {228, 10}},
+   {227, 10}},
   # MapSet opacity on case-id sets typed through campaign JSON (col 21)
   {"bench/imp/benchmark_truth/rlm_campaign.ex", :call_without_opaque, {813, 21}},
   # MapSet opacity on case-id sets typed through campaign JSON (col 53)
@@ -108,8 +108,6 @@
   {"lib/imp/tracking/mlflow.ex", :call_without_opaque, {361, 8}},
   # defensive clause dialyzer pins to the module head (line 1)
   {"lib/mix/tasks/imp.benchmark.fast_slow.ex", :pattern_match, 1},
-  # MapSet opacity on the hop-id set from analysis JSON
-  {"lib/mix/tasks/imp.benchmark.hotpotqa_analysis.ex", :call_without_opaque, {159, 24}},
   # MapSet opacity on the run-index set from parity JSON
   {"lib/mix/tasks/imp.benchmark.parity.aggregate.ex", :call_without_opaque, {328, 24}},
   # raise-only helper: invalid_python!/1 exists to Mix.raise

.gitignore

@@ -12,16 +12,13 @@
 
 # Replaceable build and test material.
 /tmp/
-/benchmarks/data/
-!/benchmarks/data/
-/benchmarks/data/*
-!/benchmarks/data/musique-ans-mipro-current-v1.receipt.json
+# `mix imp.benchmark.fetch` writes split-sized dataset files here. Everything
+# else under benchmarks/data -- fixtures, manifests, provenance, build
+# scripts -- is tracked, so nothing a checkout needs is ignored.
+/benchmarks/data/*-[0-9]*.jsonl
 !/benchmarks/data/hotpotqa-validation-0-10.jsonl
-!/benchmarks/data/hotpotqa-validation-0-10.manifest.json
-!/benchmarks/data/HOTPOTQA_ATTRIBUTION.md
 
-# Disposable executions and resumable campaign state. Immutable accepted
-# evidence lives outside these roots under benchmarks/evidence/admitted.
+# Benchmark output. Every task writes its report under one of these roots.
 /benchmarks/runs/
 /benchmarks/checkpoints/
 /benchmarks/results/

CONTRIBUTING.md

@@ -26,19 +26,17 @@ run under `mix test test/learning_path_contract_test.exs`, and
 both green when changing public examples or notebooks.
 
 Provider-backed and research-scale tests are separate because they require
-credentials, external services, canonical datasets, or significant spend. See
-`docs/maintainers/RELEASE.md` and `docs/maintainers/EVIDENCE.md` before changing
-a provider, optimizer, benchmark, or fidelity claim. `.env.example` documents
+credentials, external services, canonical datasets, or significant spend.
+`.env.example` documents
 the supported live-test variables; keep real credentials in an ignored `.env`.
 
 ## Maintainer checks
 
-The benchmark-evidence and reproduction-registry tests are excluded from the
-default `mix test` run (tag `:evidence_infrastructure`). They validate the
-committed benchmark artifacts against full git history, the pinned DSPy Python
-environments (`scripts/setup_dspy_parity_env.sh` and friends), and in some
-lanes a `.env` with provider credentials — none of which a fresh clone has.
-To run them:
+Some benchmark and upstream-differential tests are excluded from the default
+`mix test` run (tag `:evidence_infrastructure`). They need the pinned DSPy
+Python environments (`scripts/setup_dspy_parity_env.sh` and friends), and in
+some lanes a `.env` with provider credentials — neither of which a fresh clone
+has. To run them:
 
 ```sh
 scripts/setup_dspy_parity_env.sh
@@ -47,20 +45,14 @@ scripts/setup_reference_test_env.sh
 EVIDENCE_INFRASTRUCTURE=1 mix test        # or: mix test --include evidence_infrastructure
 ```
 
-They also need a full (non-shallow) clone, because the source-binding
-validators resolve ancestor commit SHAs.
-
 ## Maintainer Authority
 
 Public behavior belongs to code, tests, and user documentation. Pinned upstream
-semantics belong to `benchmarks/authorities.json`; reproducible research
-protocols and retained results belong to `benchmarks/reproductions.json` and
-`benchmarks/evidence/`. Unfinished work is a pull request on a topic branch; there is no ticket file in this repository.
-
-`benchmarks/claims.json` is a scoped index for auditing unusually broad or
-comparative statements. It is not a release score. Read
-`docs/maintainers/AUTHORITIES.md`, `docs/maintainers/REPRODUCTIONS.md`, and
-`docs/maintainers/RESEARCH_PROTOCOLS.md` when changing those surfaces.
+semantics belong to `benchmarks/authorities.json`: the differential harness
+reads it before comparing Imp against upstream, and it fails closed when a pin
+drifts. Benchmark results belong to whoever ran the harness, in the report the
+task writes. Unfinished work is a pull request on a topic branch; there is no
+ticket file in this repository.
 
 ## Design Standard