Verification Object

Status Link (Specimen)

The procurement object: a link counterparties can check today.

A Status Link is the authoritative verification URL for a Good Proof Stamp.
It returns the current validity of a decision within scope and within an evidence window.

Decision rule: rely only if status = VALID. Anything else = do not proceed.

Fail-closed: unreachable/timeout = NOT VERIFIED

No login / no portal: counterparties verify by link

Reliance rule (what to do with the status)

VALID

→ Proceed within scope + before expiry

Reliance is authorized for this decision class.

NEEDS REFRESH

→ Block/escalate until re-verified

Something changed. Do not rely until status returns to VALID.

WITHDRAWN

→ Stop relying immediately

Withdrawal ≠ erasure. History preserved. Stop reliance now.

NOT VERIFIED

→ Treat as unverified; block or escalate

No stamp found, or verification failed.

If the Status Link cannot be verified (timeout/unreachable), treat it as NOT VERIFIED.

What this is

•A live, checkable URL returning current status of a Stamp
•The single source of truth for verification (not emails, not PDFs)
•Human-readable status page + machine-readable JSON
•Built for contracts, runbooks, tickets, and automated gates
•Works outside your perimeter (counterparties don’t need system access)

What this is not

•Not a static document or point-in-time attestation
•Not access to prompts, logs, PII, or sensitive payloads
•Not a guarantee of outcome correctness
•Not a compliance certification (acceptance depends on counterparty/programme)

What a counterparty actually checks

A. Status states

VALIDNEEDS REFRESHWITHDRAWNNOT VERIFIED

Only VALID authorizes reliance. Everything else = block or escalate.

B. Domain trust check (anti-spoofing)

Official verifier: verify.goodproof.mindchill.ai

If the domain does not match, treat as NOT VERIFIED.

Don't trust links. Type mindchill.ai/official to verify.

Counterparties may verify TLS certificate + issuer per policy.

C. Decision summary check

• Confirm scope_summary matches the decision class you are relying on
• Confirm expires_at is in the future

If scope does not match, treat as NOT VERIFIED.

Official verification endpoint (machine-readable)

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

GET https://verify.goodproof.mindchill.ai/{stamp_id}

{
  "stamp_id": "GP-STAMP-2026-████",
  "status": "VALID",
  "scope_version": "1.0",
  "scope_summary": "████████████████",
  "scope_hash": "sha256:████████",
  "expires_at": "████-██-██T██:██:██Z",
  "checked_at": "████-██-██T██:██:██Z",
  "signer": "████████",
  "verify_url": "https://verify.goodproof.mindchill.ai/GP-STAMP-2026-████",
  "fail_closed": true,
  "official_verifier": "verify.goodproof.mindchill.ai",
  "refresh_triggers": [
    "policy_change",
    "model_version_change",
    "data_boundary_change"
  ],
  "withdrawal_reason_tags": []
}

Logging recommendation:

Store stamp_id, checked_at, status, scope_version, expires_at, and the verifier domain.

How a counterparty relies on a Status Link (runbook)

Open the Status Link at goodproof.mindchill.ai/verify/{stamp_id}

Confirm domain + TLS certificate (policy-dependent)

Confirm status = VALID

Confirm scope_summary matches what you’re relying on

Confirm expires_at is valid for your reliance window

Record your verification (stamp_id + checked_at + status)

For automated gates: treat any non-VALID response as block/escalate.

Fail-closed behavior (non-negotiable)

If verification fails, times out, or returns an error → NOT VERIFIED
NOT VERIFIED means: do not execute / do not rely
This prevents silent reliance on stale, withdrawn, or spoofed approvals

Gate rule:

"If Status Link response != VALID → block or escalate."

NEEDS REFRESH means "re-verify before relying"

Triggers (examples):

• Policy/rules changed
• Model/version changed within scope
• Data boundary/evidence window changed
• Material correction or review initiated

WITHDRAWN means "stop relying immediately"

Conditions (examples):

• Material flaw discovered
• Fraud/misrepresentation or compromised integrity
• Scope invalidated by external event
• Guardian escalation outcome (programme-scoped)
• Consent withdrawal (where applicable)

Withdrawal propagates stop-rely semantics instantly. History remains append-only.

Status Link vs IDA Evidence Pack

Status Link

Authoritative now

Live validity you can check today

IDA Evidence Pack

Defensible then

Time-stamped snapshot you can file/cite

PDFs are great for filing. Status Links keep them current.

Procurement-ready clause (template)

“For any defined high-impact action, Provider shall obtain and maintain a Good Proof Stamp with an active Status Link. Actions taken with a status of NOT VERIFIED, NEEDS REFRESH, or WITHDRAWN shall be treated as unverified.”

Not legal advice. Template language for legal review.

Why this beats PDFs

PDFs don't stay true

Signed today says nothing about tomorrow. Status Links update in real time.

Portals don't travel

Counterparties can't log into your systems. A Status Link works anywhere.

Disputes require live validity

Reliance must be checkable at review time, not just when issued.

Revocation matters

WITHDRAWN stops reliance fast when risk changes. PDFs can't do that.

Start with one decision class. Gate it. Ship proof that travels.

Get a working Status Link gate + IDA specimen in 30 days.

Book a Stamp Sprint Back to Specimens

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