QA Buyer Proof Release

SCRIMED now has a single protected go/no-go gate before retained QA proof enters Buyer Diligence.

Buyer Proof Release ties retained Manual QA Evidence, Proof Promotion, Activation Seal, and Claim Guard into one decision. Public checks remain candidate-only; protected workspace verification is required before Buyer Diligence references retained manual AAL2 synthetic QA proof.

Download Release Brief Inspect Public API Execution Console Human Run Packet Completion Bridge Activation Seal Proof Promotion Claim Guard Protected Workspace

Statusmanual-aal2-qa-buyer-proof-release-gate-ready

Decisionlocked-retained-packet-required

Buyer exportblocked

Protected checkrequired

Rules5

Evidence fields12

Hard stops10

Blocked claims8

Current decision

SCRIMED remains activation-ready; retained manual AAL2 QA proof cannot be used in buyer diligence until the protected release gate passes.

Complete the human AAL2 run, persist no-secret metadata, then verify Proof Promotion, Activation Seal, Claim Guard, and this release gate before Buyer Diligence export.

SCRIMED QA Buyer Proof Release decides whether protected buyer diligence may reference retained no-secret manual AAL2 synthetic QA evidence. Public checks validate candidate metadata only. Protected release requires tenant-governed AAL2 access, visible retained packet metadata, Proof Promotion, Activation Seal, Claim Guard, and unchanged clinical/PHI/security/reimbursement boundaries.

protected/api/pilot-workspaces/{workspaceSlug}/qa-evidence/buyer-proof-release

packet/api/pilot-workspaces/{workspaceSlug}/buyer-room/packet

publiccandidate validation only

Release criteria

Buyer proof release stays locked until protected retained evidence and language gates align.

blocked

Retained protected packet visible

No protected packet SHA-256 is visible to the release gate.

Persist safe metadata through protected Manual QA Evidence after the human AAL2 run.

blocked

Proof Promotion permits buyer diligence

Proof Promotion state: pending-retained-packet.

Use /qa-run-control, complete one human AAL2 synthetic QA workflow, persist the no-secret packet, then promote after packet hash visibility.

blocked

Activation Seal allows buyer use

Activation Seal state: unsealed-human-aal2-required.

Complete Launch Kit, validate dispatch through Human Run Packet, validate through Completion Bridge, persist protected no-secret metadata, confirm Proof Promotion, then run Claim Guard before buyer use.

passed

Claim Guard keeps language bounded

Claim Guard state: requires-retained-packet.

Complete Launch Kit, validate dispatch through Human Run Packet, validate through Completion Bridge, persist protected metadata, then confirm Proof Promotion before using this claim.

passed

External authority remains separately gated

External distribution, public claims, live clinical care, PHI processing, reimbursement, certification, connector, and production authority remain false.

Route external-use claims through qualified release, legal, privacy, security, clinical, reimbursement, regional, connector, and customer go-live controls.

Required evidence