AAL2 Synthetic QA Evidence

SCRIMED separates protected AAL2 execution evidence from buyer-proof release approval.

This package records the first protected AAL2 synthetic QA evidence posture, required test categories, retained packet visibility, audit status, and a clear go/no-go recommendation without weakening clinical, PHI, security, reimbursement, or production authority boundaries.

Download Evidence Brief Inspect API Smoke Readiness Brief Smoke Readiness API Execution Console Buyer Proof Release Protected Workspace

Statusprotected-aal2-synthetic-qa-evidence-package-ready

Run stateprotected-aal2-human-run-required

RecommendationNO-GO-buyer-proof-release

Demo postureGO-controlled-synthetic-demo

Packet visibleno

Audit signals0

Test categories9

PHI enteredno

Smoke preflightaal2-smoke-readiness-preflight-ready-no-secret

Strict smokehuman token required

Boundary

First protected human-reviewed AAL2 synthetic QA workflow evidence package covering synthetic clinical/workflow QA categories, hard authority boundaries, no-secret metadata, audit visibility, and Buyer Proof Release status.

SCRIMED AAL2 Synthetic QA Run Evidence records the first protected human-reviewed AAL2 synthetic QA evidence posture. It does not bypass human AAL2, store credentials, store PHI, touch production systems, trigger live patient workflows, perform autonomous clinical action, certify HIPAA/SOC/FDA/security status, guarantee reimbursement, approve connectors, approve buyer proof release, or authorize live clinical care.

date2026-06-22

consoleoperator-aal2-run-required

releaselocked-retained-packet-required

packetpending-human-aal2-run

AAL2 smoke readiness

Strict protected smoke is prepared, but remains blocked until a fresh human AAL2 token and target feature flag are present.

ready

Workspace slug

The operator flow supports SCRIMED_WORKSPACE_SLUG and defaults to atlas-synthetic-evaluation for synthetic smoke testing.

Set SCRIMED_WORKSPACE_SLUG only when running against a different authorized synthetic tenant.

blocked-until-human-aal2

Short-lived AAL2 bearer token

The app never prints or embeds token material. The local helper accepts clipboard, prompt, or session-file input and writes only to gitignored local environment when requested.

Generate a fresh authorized tenant-admin, pilot-lead, or reviewer session token and run the token helper immediately before strict smoke.

target-runtime-required

Role verification

Protected APIs verify tenant role and AAL2 state at runtime; this readiness packet does not assert operator authorization.

Run the strict smoke against the protected target so Supabase/Auth/RLS can verify the token and role.

operator-action-required

Durable-store feature flag

Protected writes intentionally stay disabled unless SCRIMED_EXECUTION_ATTEMPT_DURABLE_STORE_ENABLED is true on the target app.

Enable SCRIMED_EXECUTION_ATTEMPT_DURABLE_STORE_ENABLED=true only for the authorized synthetic smoke target.

target-runtime-required

Protected Supabase runtime

Durable-store record, replay, and review disposition depend on protected Supabase RPCs and deny-by-default RLS.

Verify the target deployment has the durable-store migrations applied before strict smoke.

target-runtime-required

Stored-vector registration role

Stored-vector RPC smoke requires authenticated registration through the protected target and must not run as public anonymous code.

Run npm run smoke:scrimed-stored-vector-rpc:strict after the same short-lived AAL2 token is accepted.

validated

No-secret output

Readiness APIs, briefs, docs, and contract checks must not include JWT-like strings, bearer-token material, Supabase service role keys, PHI, or credential fragments.

Keep all token movement limited to local environment variables, .env.local, secure prompt input, or clipboard handoff.

ready

Strict smoke commands

Nonsecret preflight and strict durable-store/stored-vector commands are present as npm scripts and are covered by the nonsecret contract suite.

Run the readiness preflight before strict smoke and keep failed protected writes fail-closed.

Operator commands

Use only the no-secret preflight and short-lived local token handoff path for strict AAL2 smoke.

safe commands

4

npm run smoke:aal2:readiness
npm run smoke:aal2:token -- --prompt-token --write-env-local
npm run smoke:aal2:durable-store:strict
npm run smoke:scrimed-stored-vector-rpc:strict

guardrails

5

No PHI, patient identifiers, payer member identifiers, imaging, claims, or live records are accepted.
No autonomous diagnosis, treatment, prescribing, patient outreach, payer submission, billing submission, or EHR writeback is authorized.
The preflight does not weaken AAL2, tenant role checks, Supabase RLS, durable-store authorization, or protected API verification.
Token-like values must be redacted in logs and never committed to source, docs, tests, or chat output.
A failed or missing token keeps strict smoke blocked instead of falling back to public execution.

fail-closed modes

5

Missing SCRIMED_BEARER_TOKEN fails closed before authenticated strict smoke.
Expired, malformed, or non-JWT token material fails closed during local preflight or protected API verification.
Valid token with an unauthorized role is rejected by protected role checks.
Disabled durable-store target returns disabled/fail-safe status instead of accepting protected writes.
Unauthenticated public requests to protected record/replay/review paths remain fail-closed.

Required categories