Skip to content

Add benchmark proof links to the README proof section #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
YuuGR1337 wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −0
Open

Add benchmark proof links to the README proof section #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,14 @@ shows the same AI eval gate inside this repository:
[blocked run](https://github.com/AzurLiu/falsiflow/actions/runs/26708459093),
then [ready run](https://github.com/AzurLiu/falsiflow/actions/runs/26708472653).

Benchmark proof: the same downstream AI eval
[PR #1](https://github.com/AzurLiu/falsiflow-downstream-ai-eval-demo/pull/1)
demonstrates the `claim_check_blocked` →
`claim_check_ready` transition behind
[Benchmarks Should Fail Builds](docs/launch_articles/benchmarks_should_fail_builds.md).
Falsiflow validates benchmark evidence-package readiness, not benchmark
correctness or model quality.

For copy-paste downstream smoke repos that intentionally fail on placeholder
evidence, then pass after source-backed rows are added, use
[examples/downstream_ai_eval_smoke](examples/downstream_ai_eval_smoke),
Expand Down