Agentic Evidence Lab v0.1.0-alpha.5

Agentic Evidence Lab v0.1.0-alpha.5

Alpha.5 makes the existing evidence easier to inspect without changing what
the historical studies proved.

What changed

• ael results build deterministically generates the root Results Index,
  three human result cards, and a machine-readable index from an explicit,
  hash-bound public-results profile.
• ael results check fails when committed projections drift from their source
  receipts or when a selected claim exceeds the receipt's evidence ceiling.
• Every card states the exact public verification command, what that command
  proves, which material is unavailable, and which historical lifecycle facts
  were never declared.
• CI protects the released PBT v2 freeze/result bytes and validates the actual
  wheel and source archive contents and version metadata.
• The PBT v2 preregistration tag is required to resolve to the exact commit
  recorded by the frozen result bundle.

Evidence boundary

This release adds no model calls and no new effect estimate. It does not modify
the five Contract v0 schemas, old receipts, the receipt renderer, or the frozen
alpha.3/alpha.4 PBT evidence. The cards are publication projections, not new
evidence documents.

evidence_level, claim status, reproducibility, independence, current
publication, freshness, action, and downstream outcome remain separate. A
successful public audit can verify an evidence graph and Git artifact ordering;
it is not a model rerun, independent replication, or production-outcome proof.

Verify

From a full Git checkout:

uv sync --locked --all-groups
uv run ael results check studies/public-results.json --require-git-proof
uv run python tools/check_frozen_artifacts.py
uv run python -m unittest discover -s tests -v
uv run python tools/release_check.py

The exact release commit, CI state, built-archive checksums, and release manifest
belong to the GitHub release. The commands above do not rerun historical model
calls or disclose private holdouts.

Historical note: the alpha.3 checksum file used path-prefixed entries. Alpha.5
release checksums use flat asset filenames so a normal GitHub release download
can be verified directly.