# SCRIMED Service Delivery Workbench Brief

Status: service-delivery-workbench-active
Updated: 2026-06-26
Service delivery offers: 7
Phases: 7
Work order templates: 8
Artifacts: 7
Activation gates: 8
Hard stops: 39

## Boundary
SCRIMED Service Delivery Workbench converts packaged offers into scoped work orders, delivery phases, acceptance criteria, buyer handoffs, proof routes, margin protections, and retained healthcare authority gates. It is a product and services execution control surface only. It is not a statement of work, contract approval, legal advice, accounting advice, tax advice, audited financial reporting, contractual SLA, uptime guarantee, managed-service commitment, customer permission, revenue guarantee, profit-margin guarantee, clinical validation, compliance certification, security certification, PHI processing authority, production connector approval, EHR writeback approval, payer submission approval, or live clinical care authorization.

This brief is not a statement of work, contract approval, legal advice, accounting advice, tax advice, audited financial reporting, contractual SLA, uptime guarantee, managed-service commitment, customer permission, revenue guarantee, profit-margin guarantee, clinical validation, compliance certification, security certification, PHI processing authority, production connector approval, EHR writeback approval, payer submission approval, or live clinical care authorization.

## Operating Rule
No SCRIMED service should move from buyer interest to delivery without a selected package, no-PHI intake, scope matrix, acceptance criteria, work-order template, proof route, margin control, and retained boundary.

## Service Delivery Offers
- Workflow Intelligence Assessment Delivery (ready-to-scope): Turn one to three operational pain points into a no-PHI workflow map, automation scorecard, evidence inventory, and next-package decision. Acceptance: All scoped workflows have owner, friction, evidence, and next action recorded; Buyer confirms no PHI or production credentials were provided; Recommendation is tied to a proof route and retained boundary Boundary: Operational intelligence only; no clinical advice, production automation, PHI processing, or guaranteed savings.
- Health Records Safety Assessment Delivery (active-delivery-template): Map safe record extraction, source attribution, patient-safety linting, interoperability standards, and live-data approval gates without accepting PHI. Acceptance: Every source type has a safety check and retained approval gate; Synthetic extraction path is separated from live-data path; Blocked actions are visible in the handoff Boundary: No-PHI extraction planning only; patient matching, production connectors, writeback, payer submission, and clinical action remain blocked.
- Interoperability Readiness Sprint Delivery (active-delivery-template): Prepare a standards-aware connector path, synthetic conformance evidence, and implementation sequence before production access is requested. Acceptance: Every target standard has evidence route, owner, and gate; No live endpoint dependency exists inside sprint scope; Production connector approval is separated from readiness work Boundary: Readiness and synthetic conformance only; production connector, PHI, security, privacy, and customer environment approval remain external gates.
- TrustOS AI Governance Audit Delivery (ready-to-scope): Create a governed AI adoption review with claims controls, oversight map, audit evidence plan, and approval-gate ladder. Acceptance: Claims are classified as approved, evidence-required, or prohibited; Human review ownership is explicit; Legal, security, clinical, and regulatory conclusions are routed to qualified reviewers Boundary: Governance readiness only; legal, regulatory, security, certification, and clinical authority require qualified external review.
- Synthetic Pilot Evaluation Delivery (protected-gated): Run governed synthetic workflow evaluation with workflow packets, Trust Cards, QA evidence, metrics, and protected-pilot recommendation. Acceptance: Synthetic scenarios are approved before execution; QA evidence and claim guard are complete before buyer proof language; Protected evidence release remains AAL2 gated Boundary: Synthetic evaluation only; no diagnosis, treatment, payer submission, patient outreach, live PHI, or production connector execution.
- Enterprise Proof and Deal Room Delivery (protected-gated): Package buyer-specific diligence, proof packets, release decisions, protected evidence-room boundaries, quote-to-contract inputs, and next action. Acceptance: Every external packet has release authority, recipient control, and access-log route; Custom claims are routed to Claim Guard; Contract and pricing commitments are separated from proof work Boundary: Diligence activation only; external sharing, customer permission, certification, signed contracts, and production activation remain gated.
- Continuous Review and Innovation Retainer Delivery (active-delivery-template): Operate agent-assisted accuracy review, evidence attribution, claims drift, security drift, incident learning, and internal innovation backlog with human approval gates. Acceptance: Human owner approves every remediation or public claim; Quantum or future research stays internal unless approved; Escalations become separately scoped work when implementation labor is required Boundary: Agent-assisted and internal-research cadence only; humans approve remediation, public claims, production changes, and innovation disclosures.

## Delivery Phases
- Qualify (ready-to-scope): Confirm buyer, sponsor, package, budget posture, no-PHI boundary, and decision owner before work is promised. Exit: Sponsor named; Scope lane selected; Boundary accepted Hard stop: Stop when sponsor, package, or no-PHI boundary is missing.
- Scope (active-delivery-template): Translate buyer interest into capped workflow count, deliverables, acceptance criteria, proof routes, and excluded work. Exit: Scope matrix approved; Acceptance criteria recorded; Excluded claims listed Hard stop: Stop when requested work requires contract, legal, finance, PHI, connector, or clinical authority approval.
- Kickoff (active-delivery-template): Set owner map, cadence, artifacts, review checkpoints, communication path, and escalation rules. Exit: Kickoff brief; Work-order board; Human-review owners Hard stop: Stop when buyer requests autonomous communication, calendar send, or unsupported SLA commitments.
- Configure (protected-gated): Prepare synthetic fixtures, task plans, evidence routes, TrustOS gates, and QA checks for scoped work orders. Exit: Fixture plan; Agent task map; QA checklist; Blocked action list Hard stop: Stop when live endpoints, production credentials, PHI, or patient identifiers are requested.
- Execute (protected-gated): Run scoped no-PHI work orders, collect evidence, route issues, and prevent claim expansion. Exit: Evidence packet; Issue queue; Acceptance memo candidate Hard stop: Stop when a result would imply diagnosis, treatment, reimbursement, certification, security approval, or production authorization.
- Review (external-review-required): Approve or block buyer-facing language, external packet release, business terms, security claims, and clinical implications. Exit: Release decision; Blocked claims; Qualified-review notes Hard stop: Stop when qualified review is missing for legal, security, finance, tax, clinical, regulatory, or certification language.
- Handoff (active-delivery-template): Deliver artifacts, confirm acceptance, route unresolved gates, and recommend next paid package or retainer. Exit: Buyer handoff packet; Expansion recommendation; Retained boundary register Hard stop: Stop when buyer asks for implementation expansion without change order, SOW, protected pilot, or license approval.

## Work Order Templates
- Buyer Discovery and No-PHI Intake (active-delivery-template): Scoped intake sheet. Hard stops: PHI in intake, No sponsor, Unsupported claim requested
- Scope Matrix and Acceptance Plan (active-delivery-template): Scope matrix. Hard stops: Uncapped scope, No acceptance criteria, Contract-like commitment without review
- Workflow and System Boundary Map (active-delivery-template): Workflow boundary map. Hard stops: Live endpoint dependency, No owner for clinical or data gate, No workaround for blocked action
- Synthetic Fixture and Evidence Plan (protected-gated): Synthetic evidence plan. Hard stops: PHI scenario, No evidence reference, No QA checkpoint
- Standards and Record Safety Crosswalk (active-delivery-template): Standards and safety crosswalk. Hard stops: Patient matching requested, EHR writeback requested, Payer submission requested
- TrustOS Claim and Authority Review (external-review-required): Claim and authority review memo. Hard stops: Legal advice requested, Certification claim requested, Clinical authority claim requested
- Buyer Proof Packet and Release Control (protected-gated): Buyer proof packet. Hard stops: No release decision, No recipient control, No AAL2 protected route
- Delivery Retro and Expansion Recommendation (active-delivery-template): Delivery handoff and expansion memo. Hard stops: Implementation expansion without SOW, Revenue guarantee requested, Unreviewed public claim

## Activation Gates
- No-PHI Intake Gate (active-delivery-template): Only synthetic, business-contact, workflow-scope, or metadata inputs are present. Fail closed: Reject input, remove sensitive content from scope, and route to protected/privacy review.
- Sponsor and Owner Gate (ready-to-scope): Sponsor, workflow owner, review owner, and decision owner are named. Fail closed: Keep request in nurture/onboarding until ownership exists.
- Scope and Acceptance Gate (active-delivery-template): Deliverables, acceptance criteria, excluded work, proof routes, and hard stops are recorded. Fail closed: Block delivery and return to scope matrix.
- Legal Finance Contract Gate (external-review-required): Qualified owners approve or route the language. Fail closed: Use readiness-only language and remove contract-like commitments.
- Claim Guard and Authority Gate (external-review-required): Claim is approved, evidence-required with controls, or blocked before release. Fail closed: Block language and route to qualified review.
- Protected Buyer Evidence Release Gate (protected-gated): AAL2 workspace, release decision, reviewer signoff, recipient attestation, lockbox, and access-log path exist. Fail closed: Share public-safe summary only or keep evidence internal.
- Connector and Live Data Gate (blocked-before-approval): Approved protected or production connector scope exists with qualified privacy/security/customer approvals. Fail closed: Use synthetic fixtures, standards mapping, and readiness-only workaround.
- Clinical Action Gate (blocked-before-approval): Formal clinical authority, intended-use, safety, regulatory, and customer approvals exist. Fail closed: Block clinical action and convert to synthetic planning or governance review.

## Artifacts
- Scoped Intake Sheet: Capture buyer, sponsor, target offer, workflow questions, and no-PHI boundary. Release rule: Internal and buyer-facing after no-PHI check.
- Scope Matrix: Tie deliverables to acceptance criteria, proof routes, excluded work, margin protections, and escalation triggers. Release rule: Buyer-facing only after delivery lead and business owner review.
- Work Order Board: Track tasks, owners, status, evidence links, hard stops, and human-review checkpoints. Release rule: Internal by default; buyer snapshot allowed when sensitive content is absent.
- Evidence Packet: Package synthetic fixtures, outputs, source attribution, TrustOS decisions, QA checks, and blocked actions. Release rule: Protected route or public-safe summary depending on buyer release decision.
- Claim and Authority Memo: Classify sales, buyer, investor, legal, financial, clinical, security, and regulatory language before external use. Release rule: External use requires authorized claim status or qualified-review completion.
- Acceptance and Handoff Memo: Close scoped work, record acceptance result, unresolved gates, buyer next action, and recommended expansion package. Release rule: Buyer-facing after delivery and claim review.
- Retainer and Internal Research Backlog: Route recurring review loops, innovation work, and future research assignments without public commitments. Release rule: Internal-only unless founder and qualified reviewers approve disclosure.

## Package Bindings
- Assessment Package: 7 work-order templates. Handoff: Synthetic Pilot Evaluation or Interoperability Readiness Sprint. Boundary: No live clinical care; No PHI; No legal, accounting, tax, security, or regulatory approval; No guaranteed savings
- Readiness Sprint Package: 6 work-order templates. Handoff: Synthetic Pilot Evaluation or Enterprise Proof and Deal Room Activation. Boundary: No certified compliance claim; No production connector approval; No regional approval claim; No implementation work without SOW
- Synthetic Pilot Package: 6 work-order templates. Handoff: Protected Enterprise Pilot or Enterprise Operating Layer License. Boundary: Synthetic only; No autonomous clinical action; No customer-value claim without permission; No protected evidence release without AAL2 gate
- Enterprise Activation Package: 6 work-order templates. Handoff: Multi-year enterprise operating license or strategic platform partnership. Boundary: No contract approval without executive and counsel review; No production activation without customer authority; No PHI without approved BAA/security controls; No margin or revenue guarantee
- Continuous Review Retainer: 5 work-order templates. Handoff: Enterprise operating cadence, renewal health packet, or internal research roadmap. Boundary: No managed SOC/MDR claim; No error-free AI claim; No autonomous production change; Quantum and frontier research stay internal until approved

## Live Service Activation Matrix
- Workflow Intelligence Assessment Delivery: status=public-demo-ready; deployment=public_route_ready; next=Keep this offer in public demo and qualification mode until scope, owner, review, and acceptance evidence are stronger.; production_authority=false
- Health Records Safety Assessment Delivery: status=no-phi-service-ready; deployment=no_phi_delivery_ready; next=Package a no-PHI delivery kickoff with owner map, work-order template, acceptance criteria, and claims-safe follow-up.; production_authority=false
- Interoperability Readiness Sprint Delivery: status=no-phi-service-ready; deployment=no_phi_delivery_ready; next=Package a no-PHI delivery kickoff with owner map, work-order template, acceptance criteria, and claims-safe follow-up.; production_authority=false
- TrustOS AI Governance Audit Delivery: status=public-demo-ready; deployment=public_route_ready; next=Keep this offer in public demo and qualification mode until scope, owner, review, and acceptance evidence are stronger.; production_authority=false
- Synthetic Pilot Evaluation Delivery: status=protected-pilot-candidate; deployment=protected_workspace_required; next=Prepare protected-pilot workspace plan and AAL2 release chain before any customer-specific evidence or execution.; production_authority=false
- Enterprise Proof and Deal Room Delivery: status=protected-pilot-candidate; deployment=protected_workspace_required; next=Prepare protected-pilot workspace plan and AAL2 release chain before any customer-specific evidence or execution.; production_authority=false
- Continuous Review and Innovation Retainer Delivery: status=no-phi-service-ready; deployment=no_phi_delivery_ready; next=Package a no-PHI delivery kickoff with owner map, work-order template, acceptance criteria, and claims-safe follow-up.; production_authority=false

## Hard Stops
- No PHI, patient identifiers, production credentials, or live endpoints in public intake.
- No delivery starts without named sponsor, owner, scope, package, and acceptance criteria.
- No buyer-facing value, ROI, clinical, reimbursement, certification, or security claim without qualified review.
- No contract, SOW, pricing, revenue-recognition, accounting, tax, or payment promise without qualified business review.
- No protected evidence release without AAL2 workspace, reviewer signoff, release decision, recipient control, and access-log path.
- No production connector, EHR writeback, payer submission, patient outreach, diagnosis, treatment, or live clinical workflow.
- No public quantum, autonomous-remediation, managed SOC/MDR, attack-proof, or error-free AI claim.
- No custom implementation expansion unless a change order or separately scoped work order exists.
- Stop when sponsor, package, or no-PHI boundary is missing.
- Stop when requested work requires contract, legal, finance, PHI, connector, or clinical authority approval.
- Stop when buyer requests autonomous communication, calendar send, or unsupported SLA commitments.
- Stop when live endpoints, production credentials, PHI, or patient identifiers are requested.
- Stop when a result would imply diagnosis, treatment, reimbursement, certification, security approval, or production authorization.
- Stop when qualified review is missing for legal, security, finance, tax, clinical, regulatory, or certification language.
- Stop when buyer asks for implementation expansion without change order, SOW, protected pilot, or license approval.
- PHI in intake
- No sponsor
- Unsupported claim requested
- Uncapped scope
- No acceptance criteria
- Contract-like commitment without review
- Live endpoint dependency
- No owner for clinical or data gate
- No workaround for blocked action
- PHI scenario
- No evidence reference
- No QA checkpoint
- Patient matching requested
- EHR writeback requested
- Payer submission requested
- Legal advice requested
- Certification claim requested
- Clinical authority claim requested
- No release decision
- No recipient control
- No AAL2 protected route
- Implementation expansion without SOW
- Revenue guarantee requested
- Unreviewed public claim