falsify
Fix the pass bar before the test runs. PRML is an open spec and CLI that hashes and timestamps evaluation criteria (SHA-256, RFC 3161) so anyone can check them later. Python, JS, Go, Rust.
- 8
- Python
- MIT
- 6 h ago
The maintainer has not written a description at the source.
Repo falsify-dev/.github, read from GitHub 1 min ago. falsify-dev has not joined Take My Repo.
falsify-dev/.github is a public repo on GitHub by falsify-dev. It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it. It has 0 stars and last changed on 2026-10-12. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-19.
Open the repository to look at the files.
Open on GitHubfalsify-dev/.github is a public repo on GitHub by falsify-dev. Its maker has not written a description.
It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-10-12. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Field manual for the PRML v0.1 specification. 13 patterns, 4 anti-patterns, 4 working examples. CC0.
Do AI agents ask for the evidence that would change their verdict? Synthetic evaluation-claim cases, runner, raw responses and report (Apart AI x Epistemics Sprint, Nov 2026)
Verify PRML (Pre-Registered ML Manifest) commitments in CI. Block merges on tampered or regressed eval claims.
MLflow plugin: automatic PRML manifest hash tagging for runs. Pre-Registered ML Manifest evidence layer.
PRML pre-registration for Giskard scenario results: commit an eval claim to a SHA-256 before the run, then verify the result against it.