# SCRIMED QA Activation Seal Brief

Status: manual-aal2-qa-activation-seal-ready
Decision state: unsealed-human-aal2-required
Seal allowed: no
Buyer use allowed: no

## Boundary
SCRIMED QA Activation Seal checks whether manual AAL2 synthetic QA evidence can be treated as buyer-diligence-ready. Public checks can validate no-secret candidate completeness only; actual sealing requires protected workspace packet visibility. This does not execute passkey ceremonies, store tokens, store PHI, replace counsel, certify security or compliance, authorize live clinical care, guarantee reimbursement, approve production connectors, or grant production clinical authority.

## Current Decision
- Buyer-safe claim: SCRIMED has a no-secret activation path, but the QA Activation Seal remains unsealed until protected packet evidence is visible.
- Next action: 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.

## Required Evidence
- fresh human AAL2 workflow run
- explicit synthetic target
- Completion Bridge accepted no-secret candidate
- protected Manual QA Evidence packet SHA-256
- append-only packet audit event UUID
- workflow run ID and run URL
- temporary token deleted or rotated
- Proof Promotion ready-for-buyer-diligence decision
- Claim Guard current-state language check
- clinical, PHI, reimbursement, security-certification, connector, and production claims blocked

## Rules
- Protected packet required (hard-stop): A retained packet SHA-256 visible from protected Manual QA Evidence. Pass: Protected workspace packet list contains the packet hash. Fail closed if: Only a public preview hash or operator assertion is available.
- Audit event required (hard-stop): Append-only packet audit event UUID from the protected workspace. Pass: Audit event and packet metadata reference the same manual QA run. Fail closed if: The audit event is missing, synthetic target is ambiguous, or IDs do not match.
- No secrets or PHI (hard-stop): Only workflow ID, run URL, timestamp, target ID, safe object UUID, packet hash, and audit UUID. Pass: No token, credential, PHI, payer member data, source contract, URL artifact, report, or approval document is present. Fail closed if: Any field contains secret-like, PHI-like, credential-like, or regulated identifiers.
- Proof Promotion decision required (required): Proof Promotion state ready-for-buyer-diligence. Pass: Promotion allows only retained packet metadata and keeps production claims blocked. Fail closed if: Proof Promotion is pending, under review, or not visible.
- Claim Guard required (required): Claim Guard confirms current language does not overclaim retained proof or production authority. Pass: Buyer language stays bounded to synthetic QA evidence and retained packet metadata. Fail closed if: Language implies legal approval, certification, live clinical care, PHI authority, reimbursement certainty, or connector approval.
- Human AAL2 provenance required (required): Operator attestation no-secrets-no-phi-aal2-human-run and token disposal attestation temporary-token-deleted-or-rotated. Pass: The run was deliberate, human initiated, scoped, synthetic, and the temporary token was removed. Fail closed if: The workflow was unattended, scheduled, broad-targeted, or token disposal is not attested.
- Clinical and production authority blocked (hard-stop): Separate external approvals for clinical, legal, privacy, security, reimbursement, regional, connector, and customer go-live authority. Pass: Activation Seal remains limited to buyer diligence for governed synthetic QA. Fail closed if: Anyone treats QA evidence as clinical, PHI, payer, reimbursement, certification, connector, or production authorization.

## Hard-Stop Claims
- live clinical care authorized
- PHI processing authorized
- HIPAA certified
- HIPAA compliant
- SOC 2 certified
- security certified
- FDA cleared
- FDA approved
- reimbursement guaranteed
- production connector approved
- autonomous diagnosis authorized
- autonomous treatment authorized
- patient outreach authorized
- payer submission authorized

## Routes
- Launch Kit: /qa-launch-kit
- Completion Bridge: /qa-completion-bridge
- Claim Guard: /qa-claim-guard
- Proof Promotion: /qa-proof-promotion

## Next Recommended Build Step
Use QA Activation Seal after protected Manual QA Evidence persistence to confirm packet visibility, Proof Promotion readiness, Claim Guard language, and blocked production authority before Buyer Diligence export.