Why deterministic (not LLM-as-judge)
Hardproof is designed for verification that you can rerun and defend: the same inputs should produce the same report, with machine-readable evidence and explicit failure modes.
Deterministic verification gives you
- Reproducibility: regressions are debuggable because the evidence is stable.
- CI gating: you can enforce policies (minimum score, zero critical findings) without flaky human interpretation.
- Reviewability: findings include codes, evidence, and suggested fixes; artifacts are indexed in the report.
What Hardproof is not
- A substitute for manual security review or adversarial auditing.
- A “model judge” that changes its standards implicitly based on prompt drift.
Next
- Methodology: /hardproof/methodology
- Install: /hardproof/install