Specimens are redacted, format-only exemplars. Not client data. Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.

Evidence Pack

Stamped IDA Evidence Pack (Specimen)

The fileable snapshot. Forwardable. Citable. Dispute-ready.

PDFs are great for filing. Status Links keep them current. The IDA Evidence Pack is the snapshot you can put in front of someone else.

APPEND-ONLY

MINIMAL DISCLOSURE

TIME-STAMPED SNAPSHOT

What this is

•A time-stamped snapshot produced at issuance (or decision time) that can be forwarded, filed, and cited
•Designed for procurement, disputes, audit sampling, committees
•Contains scope + evidence window + status-at-time + signer reference
•Includes append-only history pointer (withdrawal ≠ erasure)

What this is not

•Not the live verifier (that's the Status Link)
•Not a raw data dump
•Not prompts, logs, telemetry, or internal case files
•Not a guarantee of outcome correctness
•Not "compliance certification"

Why buyers ask for this

"In the real world, trust isn't a dashboard. It's what you can forward."

"Counterparties can't log into your perimeter."

"PDFs and screenshots don't prove current validity."

"Disputes happen after policies, models, and evidence change."

The IDA Evidence Pack is the snapshot; the Status Link is the live state. You need both.

Two artifacts, one standard

Status Link (authoritative now)

•Live validity state: VALID / NEEDS_REFRESH / WITHDRAWN / EXPIRED / NOT_VERIFIED
•Fail-closed: unreachable = NOT VERIFIED
•Used for gates, automation, contracts, runbooks

"Do we rely on this right now?"

IDA Evidence Pack (snapshot then)

•Time-stamped, forwardable PDF snapshot
•Built for filing, disputes, procurement, audit
•Append-only history pointer

"What was true at decision time?"

One Stamp produces both.

Specimen Preview

Redacted example (format only). Values and fields vary by programme and lane.

IDA Evidence Pack (PDF Snapshot)

{
  "stamp_id": "GP-STAMP-2026-████",
  "scope_summary": "████████████████",
  "evidence_window": {
    "from": "████-██-██T██:██:██Z",
    "to": "████-██-██T██:██:██Z"
  },
  "status_at_time": "VALID",
  "signer": "████████",
  "issued_at": "████-██-██T██:██:██Z",
  "append_only_pointer": {
    "version": "3",
    "chain_ref": "sha256:████████████"
  }
}

Excluded by default

Prompts / model inputs
Raw logs / traces
PII / PHI / sensitive payloads
Internal identifiers

Programme-gated access available when required (auditable trail).

How buyers use this

Procurement / Vendor Due Diligence

Steps:

1.Request the IDA Evidence Pack specimen
2.Confirm scope + evidence window
3.Confirm signer authority reference
4.File PDF in procurement record
5.Insert contract clause referencing Status Link + IDA Pack

Output: "Filed artifact" + "contract-referenceable proof object"

Disputes & Appeals

Steps:

1.Counterparty cites IDA pack snapshot (what was true then)
2.Counterparty checks Status Link (what is true now)
3.If status is NEEDS REFRESH/WITHDRAWN → stop relying and request re-verification

Output: "Dispute bundle" that survives time + change

Audit Sampling

Steps:

1.Auditor samples events
2.Pull IDA pack for each sampled stamp_id
3.Check scope boundaries, evidence window, signer reference
4.Record verification timestamp + artifact hash/ID

Output: "Audit trail with citable artifacts"

Third-party Review Without System Access

Steps:

1.Reviewer receives PDF (IDA pack)
2.Reviewer checks Status Link for live status
3.Reviewer logs verify result

Output: "Verification outside your perimeter"

Decision rule

VALID

→ File + rely within scope (subject to expiry)

NEEDS REFRESH

→ Do not rely until re-verified

WITHDRAWN

→ Stop relying immediately (history remains)

NOT VERIFIED

→ Treat as unverified; block/escalate

What happens when things change

NEEDS REFRESH triggers

•Policy/rule pack change
•Model/version change
•Workflow/tool boundary change
•Evidence window expiry
•Signer authority rotation
•Security incident affecting the lane

WITHDRAWN

Stop relying immediately.

Withdrawal ≠ erasure. The append-only history is preserved. The IDA pack snapshot remains as "what was true then."

If you're relying on a withdrawn stamp, treat it as NOT VERIFIED.

Fail-closed behavior

If verification cannot be performed (timeout, unreachable, error), treat as NOT VERIFIED.

Minimal disclosure by default

The pack proves the decision object and governance scope, not the underlying sensitive payload.

Programme-gated access available when required, logged, auditable.

What stays out by default:

Candidate data / claim files / PHI
Raw prompts / tool traces
Internal system identifiers

Procurement-ready clause (template)

"For any defined high-impact decision, Provider shall produce and maintain a Good Proof Stamp with an active Status Link and a corresponding IDA Evidence Pack. Actions taken with status NOT VERIFIED, NEEDS REFRESH, or WITHDRAWN shall be treated as unverified."

Not legal advice. Template language for legal review.

FAQs

Forwardable proof. No portal access required.

The IDA Evidence Pack is the snapshot you can put in front of someone else. File it, forward it, cite it.

Book a Stamp Sprint Back to Specimens

Status Link specimen →Stamp Spec page →Evidence Vault →

Specimens are redacted, format-only exemplars. Not client data. Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.

Stamped IDA Evidence Pack (Specimen)

What this is

What this is not

Why buyers ask for this

Two artifacts, one standard

Status Link (authoritative now)

IDA Evidence Pack (snapshot then)

Specimen Preview

Excluded by default

How buyers use this

Procurement / Vendor Due Diligence

Disputes & Appeals

Audit Sampling

Third-party Review Without System Access

Decision rule

What happens when things change

NEEDS REFRESH triggers

WITHDRAWN

Minimal disclosure by default

What stays out by default:

Procurement-ready clause (template)

FAQs

Is this a certification?

Does this expose prompts/logs/PII?

Can we use this only for certain decision classes?

What happens after expiry?

Will counterparties accept it?

How does it pair with Status Link?

Forwardable proof. No portal access required.

Stamped IDA Evidence Pack (Specimen)

What this is

What this is not

Why buyers ask for this

Two artifacts, one standard

Status Link (authoritative now)

IDA Evidence Pack (snapshot then)

Specimen Preview

Excluded by default

How buyers use this

Procurement / Vendor Due Diligence

Disputes & Appeals

Audit Sampling

Third-party Review Without System Access

Decision rule

What happens when things change

NEEDS REFRESH triggers

WITHDRAWN

Minimal disclosure by default

What stays out by default:

Procurement-ready clause (template)

FAQs

Is this a certification?

Does this expose prompts/logs/PII?

Can we use this only for certain decision classes?

What happens after expiry?

Will counterparties accept it?

How does it pair with Status Link?

Forwardable proof. No portal access required.