
The forwardable, time-stamped artifact produced by a Good Proof Stamp — built for procurement, disputes, and audit.
VALID
→ proceed (check Status Link)
NEEDS REFRESH
→ re-verify before relying
WITHDRAWN
→ stop relying (IDA = history)
NOT VERIFIED
→ fail-closed
Status Link = what's true now. IDA Evidence Pack = what was true then.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
EUEU AI Act enforcement begins — high-risk AI systems now require conformity assessments (Feb 2025)│
UKUK publishes AI Safety Institute guidance on frontier model evaluations│
USANIST AI 600-1 released — GenAI risk profiles now standardised│
APACSingapore MAS issues advisory on AI-driven financial decision accountability│
AFRICASouth Africa POPIA enforcement targets automated decision-making systems│
MIDDLE EASTUAE ADGM publishes responsible AI framework for financial services│
EUEU AI Act enforcement begins — high-risk AI systems now require conformity assessments (Feb 2025)│
UKUK publishes AI Safety Institute guidance on frontier model evaluations│
USANIST AI 600-1 released — GenAI risk profiles now standardised│
APACSingapore MAS issues advisory on AI-driven financial decision accountability│
AFRICASouth Africa POPIA enforcement targets automated decision-making systems│
MIDDLE EASTUAE ADGM publishes responsible AI framework for financial services│A Good Proof Stamp produces both. They serve different purposes.
Make the gate machine-checkable, not meeting-checkable.
Previously referred to as Proof Packs in some programmes. Now standardised as IDA Evidence Packs.
Authoritative now
Snapshot then
One Stamp produces both. The Status Link remains authoritative for current validity.
One is for systems and counterparties to check now. The other is for humans to file and cite later.

For high assurance programmes, status change events can be anchored to Good Proof LIVE Ledger for tamper evident timestamp finality.
Anchoring never exposes prompts, logs, PII, or internal identifiers by default.

Every Stamped IDA Evidence Pack includes:
Accessible via canonical verify route (or programme-gated access when required)
PDF export available for filing (programme-scoped)
Pack references the append-only record/version; receipt digest is published to the receipted history.
Track changes over time
verify.goodproof.mindchill.ai
90 days (configurable 30-365 days)
These are the default Status Link verify fields (authoritative now). The IDA Evidence Pack is the time-stamped snapshot referenced by the Status Link.
{
"stamp_id": "GP-2026-0142-XK9",
"status": "VALID",
"scope": "hardship_determination",
"expires_at": "2026-06-15T00:00:00Z",
"verified_at": "2026-01-08T14:32:00Z",
"signer": "guardian_panel_uk_01",
"version": "v3",
"verify_url": "https://verify.goodproof.mindchill.ai/GP-2026-0142-XK9"
}stamp_idUnique identifier for the StampstatusVALID / NEEDS_REFRESH / WITHDRAWN / EXPIRED / NOT_VERIFIEDscopeAction class + explicit boundariesexpires_atEvidence window endverified_atTimestamp of verificationsignerAuthority reference: system or guardian panelversionAppend-only referenceverify_urlCanonical verification URLExcluded by default: prompts, logs, PII, internal identifiers. Programme-gated access is available for authorised verifiers with an auditable access trail.
IDA Evidence Pack snapshot includes (redacted by default): scope summary, qualifiers, evidence window, status-at-time, signer reference, and version pointer.
What this is — and isn't.
The IDA Evidence Pack is automatically generated when a Stamp is issued.
Scope boundaries + evidence windows
No Stamp / NOT VERIFIED / NEEDS REFRESH / WITHDRAWN → block or escalate.
No Stamp → No Ship.
Automatic snapshot creation tied to the verification
Exceptions, disputes, scoped human finality with anti-rubber-stamp controls
Beyond the first verification, the artifact compounds operational value.
Proof that travels outside your perimeter by link.
Templates reduce bespoke reporting and meeting time.
Refresh cycles keep claims defensible as systems change.
Append-only history reduces dispute ambiguity and cost.
Once accepted, approvals get faster and repeatable.
You don't buy another dashboard. You get an artifact your organisation can cite.
Different roles, same artifact. Need → How the IDA helps.
Need: Contract-referenceable artifact
Helps: Verification rights; clause mapping
Learn moreNeed: Hostile scrutiny readiness
Helps: Append-only history; withdrawal semantics
Learn moreNeed: Ship autonomy safely
Helps: Appealable decisions; repeatable verification
Learn moreSame artifact. Different lane scopes.
Programme scoped. Rollout based. No guaranteed outcomes.
Without complexity. Built for hostile scrutiny.
If verification cannot be performed (network unreachable, timeout, error), the default response is NOT VERIFIED. Systems should block or escalate—never assume validity.
High-assurance programmes may use an offline signed snapshot for limited-time continuity; the Status Link remains authoritative.

Questions about the IDA Evidence Pack.
Define your high-impact action classes. Require the Stamp. Let the Status Link do the rest.
Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.