# SCRIMED QA Buyer Proof Release Brief

Status: manual-aal2-qa-buyer-proof-release-gate-ready
Release decision: locked-retained-packet-required
Buyer Diligence export allowed: no
Protected verification required: yes

## Boundary
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.

## Current Decision
- Buyer-safe claim: SCRIMED remains activation-ready; retained manual AAL2 QA proof cannot be used in buyer diligence until the protected release gate passes.
- Next action: 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.

## Required Evidence
- protected Manual QA Evidence packet SHA-256
- protected packet audit event UUID
- workflow run ID and run URL
- synthetic target or workspace label
- human AAL2 no-secret operator attestation
- temporary token deleted or rotated
- Proof Promotion ready-for-buyer-diligence decision
- Activation Seal sealed-for-buyer-diligence decision
- Claim Guard safe or retained-packet-gated language result
- protected Buyer Diligence packet route
- external distribution remains separately gated
- clinical, PHI, reimbursement, certification, connector, and production authority remain blocked

## Release Criteria
- Retained protected packet visible (blocked): No protected packet SHA-256 is visible to the release gate. Next: Persist safe metadata through protected Manual QA Evidence after the human AAL2 run.
- Proof Promotion permits buyer diligence (blocked): Proof Promotion state: pending-retained-packet. Next: Use /qa-run-control, complete one human AAL2 synthetic QA workflow, persist the no-secret packet, then promote after packet hash visibility.
- Activation Seal allows buyer use (blocked): Activation Seal state: unsealed-human-aal2-required. Next: 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.
- Claim Guard keeps language bounded (passed): Claim Guard state: requires-retained-packet. Next: Complete Launch Kit, validate dispatch through Human Run Packet, validate through Completion Bridge, persist protected metadata, then confirm Proof Promotion before using this claim.
- External authority remains separately gated (passed): External distribution, public claims, live clinical care, PHI processing, reimbursement, certification, connector, and production authority remain false. Next: Route external-use claims through qualified release, legal, privacy, security, clinical, reimbursement, regional, connector, and customer go-live controls.

## Hard Stops
- bearer token or refresh token submitted
- API key, password, credential, or production secret submitted
- PHI, patient identifier, payer member identifier, medical record, claim, image, or regulated clinical content submitted
- public release requested without qualified approval
- live clinical care authorization claimed
- PHI processing authorization claimed
- HIPAA, SOC 2, security, FDA, regional, or legal approval claimed
- reimbursement certainty or payer submission authority claimed
- production connector approval claimed
- autonomous diagnosis, treatment, patient outreach, or clinical execution claimed

## Blocked Claims
- SCRIMED is authorized for live clinical care
- SCRIMED can process production PHI
- SCRIMED is HIPAA certified or SOC 2 certified
- SCRIMED guarantees reimbursement or payer approval
- SCRIMED has FDA, regional regulatory, or legal approval
- SCRIMED production connectors are approved
- SCRIMED can autonomously diagnose, treat, submit claims, or contact patients
- public claims can reference retained AAL2 proof without qualified review

## Routes
- Public page: /qa-buyer-proof-release
- Public API: /api/qa-evidence/buyer-proof-release
- Protected release route: /api/pilot-workspaces/{workspaceSlug}/qa-evidence/buyer-proof-release
- Buyer Diligence packet: /api/pilot-workspaces/{workspaceSlug}/buyer-room/packet
- Activation Seal: /qa-activation-seal
- Proof Promotion: /qa-proof-promotion
- Claim Guard: /qa-claim-guard

## Next Recommended Build Step
After the approved human AAL2 run is persisted, run the protected Buyer Proof Release gate, then export Buyer Diligence only when the gate returns ready-for-protected-buyer-diligence-export.