Repository navigation
First packaged release: proof-studio becomes the tamper-scenario and benchmark
studio around the vendored rigforge core.
Added
proof_studiopackage: scenario model and manifest loading, deterministic
planted-failure vector builders, the strict verify runner (integrity, HMAC
signature, claim binding), per-class catch report, and theproof-studioCLI
(run,list,build-vectors).- Planted-failure vectors (control, tampered_artifact_hash,
forged_signature_no_key, replay_attack) with thescenarios.ymlmanifest,
fulfilling the vector plan intests/failures/README.md. The JSON vectors
are generated deterministically byproof-studio build-vectorsand are
gitignored;proof-studio runrebuilds them before verifying. - Test suite (
tests/): scenario and vector tests, runner tests including the
gate-can-fail cases, CLI and vector-reproducibility tests, packaging
invariants, README truth lint. pyproject.tomlpackaging (name, version, MIT license, authors, classifiers,
dependencies,devandmcpextras, console script, ruff config).- Community files:
CODE_OF_CONDUCT.md, this changelog, issue templates, a pull
request template,CITATION.cff, and.github/dependabot.yml. - CI runs the studio suite with coverage across Python 3.11 to 3.13 plus the
generated vectors, and keeps the vendored rigforge test job.
Changed
- README rewritten to a distinct purpose: the studio around rigforge, with
rigforge named as the core library, a "What it proves" table of runnable
checks with measured results, a mermaid flow, and the honest replay limits.
The four front-page hero assets are reduced to one demo GIF. docs/architecture.mddocuments the real design (scenario model, strict
policy, vector lifecycle, outcome classification);docs/evaluation-strategy.md
lists the real gates.scripts/smoke.shrunsproof-studio runbefore the core demo.mcp/server.pyresolves the platform helper fromRIG_LOOPorPATHinstead
of a hardcoded home-directory path.
Built by Mike Rodgers · rodgersintelligence.com