For Legal / General Counsel
AI creates obligations faster than contracts can follow.Evidence follows the decision, not the other way around.
Good Proof produces contract-grade verification evidence for AI-driven decisions — scope-limited, portable, and designed for dispute reconstruction.
Contract-grade evidence • Scope-limited claims • Portable audit trails • Dispute-ready records
Not a certification. Scope-limited verification.
Legal 60-Second Brief
Problem
AI-driven decisions create contractual, liability, and regulatory exposure without verifiable evidence chains.
Control
Status Link verification tied to contract-defined action classes and scope boundaries.
Output
Evidence Pack per decision — exportable for litigation, dispute resolution, and regulatory review.
Boundary
Produces verification evidence within defined scope. Does not provide legal advice or guarantee regulatory compliance.
Is this a fit?
Best fit
- Organisations where AI actions create contractual obligations, liability, or regulatory exposure
- Legal teams needing defensible evidence chains for dispute resolution or litigation
- In-house counsel requiring scope-limited verification claims for contract language
Not fit
- Teams seeking legal advice or regulatory compliance consulting
- Organisations wanting AI output quality assurance or accuracy certification
Done means: contractually-defined AI actions block automatically when status ≠ VALID.
Legal Outcomes
Contract-grade evidence
Every AI action produces an Evidence Pack admissible for contractual dispute resolution
Scope-limited claims
Verification claims are bounded — no overclaiming beyond defined action classes
Portable evidence chain
Evidence Packs exportable for litigation, arbitration, and regulatory proceedings
Dispute-ready records
Decision-time reconstruction available for counterparty disputes and appeals
How Verification Works
1
AI action triggers a contractually-defined decision class
2
Gate verifies Status Link against contract scope and authority
3
Policy evaluates status + scope + expiry against contract terms
4
Execute only if VALID — otherwise block and escalate to legal review
5
Log Gate Decision + evidence fields for dispute and audit trail
Failure Semantics
Explicit condition → state → action mapping
| Condition | State | Action |
|---|---|---|
| Verifier timeout | NOT_VERIFIED | Block/Escalate |
| TLS failure | NOT_VERIFIED | Block/Escalate |
| Domain mismatch | NOT_VERIFIED | Block/Escalate |
| Malformed response / signature failure | NOT_VERIFIED | Block/Escalate |
| WITHDRAWN | WITHDRAWN | Block |
| NEEDS_REFRESH | NEEDS_REFRESH | Escalate/Review |
| Out-of-scope / expired | NOT_VERIFIED | Block/Escalate |
What a Stamp Proves
Proves (within scope)
- Action class + Gate Decision at decision-time
- Verification timestamp with authority reference
- Scope boundaries defined in contract language
- Validity state at moment of execution
- Signer identity and verifier domain
- Evidence chain for dispute reconstruction
Does not prove
- Legal correctness of the AI decision outcome
- Regulatory compliance or certification
- AI model accuracy, bias, or output quality
- Contractual adequacy of scope definitions
- Liability allocation between parties
For disputes: Status Link = current verification state. Evidence Pack = decision-time record for reconstruction.
Status Triggers
NEEDS_REFRESH
- Contract amendment or scope change
- Regulatory requirement update
- Key rotation or credential refresh
- Counterparty change or novation
- Incident opened pending legal review
WITHDRAWN
- Contract termination or material breach
- Court order or regulatory directive
- Confirmed scope boundary violation
- Counterparty dispute requiring halt
- Critical vulnerability in verification pipeline
Evidence for Litigation & Audit
Fields per Gate Decision
evidence-fields.json
stamp_idaction_classdecisionstatusverified_atexpires_atverifier_domainsignerversionrequest_idreason_codefailure_mode
Designed for dispute reconstruction, regulatory submissions, and external arbitration.
Fits Into Your Legal Function
Compensating control, not replacement
Contract management systems and CLM platformsRegulatory compliance frameworksDispute resolution and arbitration processesData privacy and retention policiesCorporate governance and board oversight
What Legal Teams Ask
Is the evidence admissible in legal proceedings?
Evidence Packs are designed for decision-time reconstruction. They record verification state, scope, timestamps, and authority references. Admissibility depends on jurisdiction and proceedings — Good Proof provides the raw evidence chain, not legal opinion on admissibility.
How does scope limitation protect against overclaiming?
Every stamp is bounded to a defined action class and scope. The verification claim is explicit: 'within this scope, at this time, status was VALID.' Claims outside the defined scope are structurally impossible — there is no stamp for what was not verified.
Can we use clause pack language in our contracts?
Yes. The clause pack provides template language for contract schedules. It maps action classes to verification requirements with defined scope boundaries, failure semantics, and retention terms.
What happens when a contract is amended?
Contract amendments or scope changes trigger NEEDS_REFRESH on affected stamps. Verification blocks until re-verification under the updated scope. The change event is logged for audit.
"High-impact [ACTION CLASS] SHALL require a valid externally-verifiable Status Link as a condition of contractual reliance."
Verification path excludes raw PII/PHI payloads by default. Retention defined in Order Form.
"Reliance on AI-executed [ACTION CLASS] is contractually conditioned on VALID status at decision time (No Stamp → No Reliance)."
30-Day Sprint
One contract lane live with verification gating, evidence export, and dispute reconstruction.
1
Scope & contract mapping
Define 3 action classes, map to contract scope, establish evidence retention terms
2
Integrate gate
Wire Status Link verification into decision pipeline with contract scope checks
3
Dispute + failure testing
Test counterparty dispute reconstruction, failure semantics, evidence export workflow
4
Go-live report
Evidence chain validation, clause pack integration, retention compliance, rollout plan
Risk Reduced vs Residual
Risk reduced
- AI decisions without verifiable evidence for dispute resolution
- Overclaiming beyond defined verification scope
- Stale authorisation persisting after contract amendment
- Evidence gaps in regulatory or litigation proceedings
Residual (out of scope)
- Legal correctness of AI decision outcomes
- Regulatory compliance or certification guarantees
- Contract adequacy or scope definition quality
- Liability allocation between parties
Designed to produce defensible evidence chains, not to guarantee legal outcomes.
Assurance Governance (Optional by Lane)
Mind Chill Guardians
Human finality for high-value contractual exceptions
Conflict checks and reviewer rotation
Multi-review thresholds for material decision classes
Minimal disclosure with auditable traceability
Ready for contract-grade AI verification?
Definition of done: contractual AI actions block on status ≠ VALID.
Every AI decision without evidence is a dispute you cannot reconstruct.
Scope-limited verification. Not a certification.