Skip to content

Add reproducible validator studies with MateProbe compatibility replay - #1

Merged
pablomate4b merged 11 commits into
mainfrom
study/validator-audit-evidence
Sep 29, 2026
Merged

pablomate4b merged 11 commits into
mainfrom
study/validator-audit-evidence

Conversation

@pablomate4b

@pablomate4b pablomate4b commented Sep 29, 2026 •

Copy link
Copy Markdown
Member

The technical report now includes controlled validator comparisons and retrospective reproductions of public bugs. This integrates that evidence with the current MateProbe a4 namespace and preserves all frozen a3 study sources, protocols, inputs, captures and reports unchanged.

The controlled study covers 144 pairs under eight authored validator profiles. Detailed Python assertions and the audit agree on all 1,152 classifications; boolean-only accounting loses attribution for 96 wrong-ID rejections, while valid controls expose 24 regressions. The historical study screens ten candidates and executes four comparisons; an explicitly documented compatibility follow-up reproduces three fixes across jsonschema and Marshmallow. The selected IDN case remains unsuccessful, and all setup failures, corrections, versions, locks and artifact hashes remain available.

Current users can run python benchmarks/study_replay.py --output /tmp/mateprobe-study-replay. A scoped import bridge runs the original hash-checked drivers against MateProbe. Result comparison permits only explicit library-version metadata changes; changes to outcomes, evidence or report membership fail. CI separately verifies byte-identical replay with the published historical a3 package, compatibility with published MateProbe a4, and the current checkout. Documentation distinguishes these replays from fresh third-party executions and provides an isolated a3 environment for historical commands.

Validation:

  • 172 tests pass, including original study checks and compatibility/tampering regressions.
  • Ruff lint/format and strict mypy pass; both distributions build.
  • The synthetic benchmark passes and all eight selected source mutants are killed.
  • All three studies reproduce byte-for-byte with installed a3 and match with published MateProbe a4 apart from explicit version metadata.
  • Documentation builds and validates 2,999 local links.
  • Frozen study evidence and runner source bytes are unchanged from the original PR head.

No core library behavior, published version, or frozen a2 evidence changes. These author-run studies support reproducible evidence accounting, not greater detection power than careful pytest, natural-language truthfulness, independent adoption, or measured authoring-cost savings. The paper makes those limitations explicit.

@pablomate4b pablomate4b changed the title Add reproducible validator comparison study and historical fix evidence Introduce MateProbe branding and reproducible validator audit study Sep 29, 2026
@pablomate4b pablomate4b changed the title Introduce MateProbe branding and reproducible validator audit study Add reproducible validator studies with MateProbe compatibility replay Sep 29, 2026
@pablomate4b
pablomate4b marked this pull request as ready for review September 29, 2026 22:56
@pablomate4b
pablomate4b merged commit 8d887d6 into main Sep 29, 2026
19 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-29T22:57:09.015514Z ef71096 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant