Specimens are redacted, format-only exemplars. Not client data. Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.
Signed verification responses backed by non-exportable keys (HSM/TPM) where programmes require it.
When "a URL said VALID" isn't enough, hardware finality makes reliance tamper-evident and independently verifiable.
Default lanes can use Status Link + IDA Pack. Hardware Finality is for programmes that require stronger reliance semantics.
One Stamp can produce all three (programme-scoped).
Redacted example (format only). Values and fields vary by programme and lane.
Signed Verify Response (Hardware-Backed)
{
"stamp_id": "GP-STAMP-2026-████",
"status": "VALID",
"verified_at": "████-██-██T██:██:██Z",
"signer_authority": {
"type": "HARDWARE_BACKED",
"key_id": "gp-hsm-prod-████",
"key_status": "ACTIVE",
"attestation": "NON_EXPORTABLE"
},
"signature": {
"alg": "ES256",
"kid": "gp-hsm-prod-████",
"sig": "████████████████████..."
}
}Programme-gated access available when required (auditable trail).
Fail-closed rule
If signature verification fails, key is unknown, response is malformed, or verification cannot be performed → treat as NOT VERIFIED.
Pain:
Need audit-grade reliance proof for high-value controls
What they do:
Verify signed response, file it with risk record
Output:
Insurer-acceptable artifact
Pain:
Sampling requires tamper-evident verification evidence
What they do:
Verify signature + log verified_at and key identity
Output:
Auditable sampling record
Pain:
Need independent verification without portal access
What they do:
Verify signed response + check Status Link for current state
Output:
Reliance they can defend
Pain:
"Who verified what, when" must be provable
What they do:
Attach signed verify response to the change ticket / runbook event
Output:
Change-control proof bundle
"For high-assurance programmes, Provider shall supply a hardware-backed signed verify response for defined high-impact actions. Any failure to verify signature or key identity shall be treated as NOT VERIFIED. Actions with NOT VERIFIED, NEEDS REFRESH, or WITHDRAWN shall be treated as unverified."
Not legal advice. Template language for legal review.
Hardware finality for programmes that need cryptographic proof of verification.
Specimens are redacted, format-only exemplars. Not client data. Not a certification. Scope-limited verification. Acceptance depends on counterparty/programme requirements.