
For defined high-impact AI decisions, Good Proof provides externally verifiable, fail-closed controls with exportable decision-time evidence.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Internal reviews and model cards are insufficient for high-impact reliance.
Status Link verification at decision time for defined high-impact actions.
Exportable Evidence Pack (JSON/CSV) for audit and regulator requests.
Supports defensibility; does not guarantee regulatory approval or model correctness.
| Condition | Returned State | Default Action |
|---|---|---|
| Timeout / network unreachable | NOT_VERIFIED | Block/Escalate |
| TLS / certificate failure | NOT_VERIFIED | Block/Escalate |
| Domain mismatch / redirect | NOT_VERIFIED | Block/Escalate |
| Malformed / unauthenticated response | NOT_VERIFIED | Block/Escalate |
| WITHDRAWN status returned | WITHDRAWN | Block + stop-rely |
| NEEDS_REFRESH status returned | NEEDS_REFRESH | Escalate/Review |
| VALID but out-of-scope / expired | NOT_VERIFIED | Block/Escalate |
If escalation path is unavailable, default action is BLOCK.
Cryptographically-signed verification artifact issued per decision
Live URL returning current verification status (VALID / NEEDS_REFRESH / WITHDRAWN / EXPIRED / NOT_VERIFIED)
Time-bound scope for decision verification
verify.goodproof.mindchill.ai (HTTPS only; host must match; redirects forbidden)
Exportable, timestamped record with minimum fields
Human sign-off on exceptions/appeals with conflict-checked independence

Managing audit and counterparty expectations
Status Link = reliance state now. Evidence Pack = fileable decision-time record.
Minimum fields per decision
MAY include evidence_window_start and evidence_window_end (programme-defined).
JSON, CSV (PDF summary optional)
No PII/PHI by default
"How do you verify AI decisions?"
→ Status Link + evidence window + scope. Each high-impact decision is verified at runtime against an externally-verifiable Status Link.
"What happens when verification fails?"
→ Fail-closed → NOT_VERIFIED → block/escalate. Systems must not proceed on unverified decisions.
"What can you produce on request?"
→ Exportable audit evidence (JSON/CSV) + specimens. All minimum fields are captured and reproducible.

One lane live with fail-closed gating, Status Link verification, and exportable Evidence Pack.
Define audited process + action classes + evidence requirements
Status Link verification + audit logging + export endpoints
Timeout/TLS/domain/malformed tests + refresh/withdrawal drills
Evidence specimen + documentation + rollout plan
Pass/fail at go-live
If criteria fail, Buyer may withhold reliance for the affected action class.
Monitoring, Change Management, Logical Access, System Operations
Logging/Monitoring, Access Control, Communications Security, Supplier Relationships
AC, AU, CM, SC, SI
Mapping only; not a certification claim.
Good Proof is scope-limited verification. A VALID status confirms scope compliance under lane rules—not outcome correctness or regulatory approval.


Human finality for compliance edge cases
Definition of done: your workflow blocks on status ≠ VALID.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.