Verifier
Local verification, no SaaS.
The MECHASSURE verifier runs locally against a bundle directory. It produces a deterministic report and never opines on the legal conclusion or coverage decision.
§ 1
Install and run
| 001 | # Install |
| 002 | $ pipx install mechassure-verify |
| 003 | |
| 004 | # Verify a bundle directory |
| 005 | $ mechassure verify ./bundle/ |
| 006 | reading manifest.json |
| 007 | checking artifact hashes [10/10] |
| 008 | validating legal-oreo-lr-0.1 ok |
| 009 | validating coverage_map ok |
| 010 | validating exclusions_map ok |
| 011 | validating risk_controls ok |
| 012 | emitting reports/mechassure_report.json |
| 013 | |
| 014 | MECHASSURE-READY: YES |
| 015 | COVERAGE DETERMINATION: NOT MADE |
| 016 | EVIDENCE RECORD VERIFIED: YES |
§ 2
What the verifier checks
- passManifest is present and parseable.
- passAll declared artifact hashes match file contents.
- passEvent log hash chain is continuous.
- passBundle receipt is present and signed.
- passLegal OREO sub-bundle satisfies legal-oreo-lr-0.1.
- passCoverage / exclusions / risk-control maps are present and parse.
- warnSubstantively-unresolved defeaters are flagged for insurer review.
- infoFinal status is reported as record-verified, not coverage-determined.
§ 3
What it never does
- It does not connect to a remote server.
- It does not score legal correctness.
- It does not recommend a coverage decision.
- It does not transmit bundle contents anywhere.