Quality gates
SCRIMED keeps execution moving by replacing blockers with explicit, safer quality gates.
Local verification, GitHub Actions, Vercel deployment, executable synthetic validation, interoperability conformance, fixture change review, workflow execution evidence, deny-by-default controls, and readiness checks form the current active quality path.
active
Vercel deployment
active gate
Primary deploy gate while the site is being built and verified.active
Synthetic clinical scenarios
active gate
Executable workflow validation without live patient data.active
Demo and pilot proof packets
active gate
Buyer-facing guided demos and structured pilot programs that bind executable synthetic proof to metrics, governance gates, buyer inputs, and production exclusions.active
Protected pilot workspace contract
active gate
Tenant-authenticated workspace APIs, durable synthetic session schema, row-level isolation, append-only audit functions, proof packet exports, and fail-closed activation gates.active
Tenant-admin sales operations
active gate
AAL2 tenant-isolated opportunity management, due-action cadence, audited commercial artifacts, vendor-neutral CRM handoff, assessment invitations, and append-only sales activity evidence.active
Executable TrustOS governance
active gate
Deterministic request governance plus an AAL2-protected tenant Decision Ledger with append-only decisions, Clinical Trace, reviewer dispositions, outcome signals, and audited governance packets.active
Production architecture contract
active gate
Typed, testable architecture contract across Agent Runtime, Context Engine, Trust Engine v2, Model Router, Evaluation Engine, ClinSecOps, and deterministic Workflow Engine.active
Enterprise readiness and claims control
active gate
Central control plane for legal, security, privacy, brand, governance, marketing, PR, sales, advertising, approved claims, prohibited claims, accountable owners, and launch gates.active
Interoperability standards control plane
active gate
Standards registry, profile targets, conformance evidence, terminology governance, and explicit pre-live requirements for healthcare connectors.active
Synthetic interoperability conformance evaluations
active gate
Executable FHIR R4 and US Core, SMART App Launch, and DICOMweb synthetic test kits with evidence artifacts and retained live-use blockers.active
Integration contracts
active gate
Standards-bound interface boundary before FHIR, HL7 v2, DICOM/DICOMweb, X12, pricing, or synthetic connectors are implemented.active
Integration fixture validation
active gate
Synthetic request and expected-response fixture coverage, safeguard mapping, and diff fingerprints before live connector implementation.active
Fixture change review
active gate
Expected-output fingerprint approval before workflows, agents, or connectors depend on fixture changes.active
Synthetic workflow execution
active gate
Staged module workflow execution readiness mapped to agent workflows, fixtures, quality gates, result fixtures, and Watchtower traces.active
Workflow execution result fixtures
active gate
Deterministic synthetic result fixtures for staged workflow outputs, traces, review states, and blocked actions.active
Workflow result validation
active gate
Validation diff gate comparing result fixtures against expected outputs, Watchtower traces, blocked actions, and review-state requirements.active
Workflow promotion review
active gate
Synthetic-only promotion approval records before any staged workflow can move toward production connectors or automation.active
Governed execution API contracts
active gate
Contract-only request, response, precondition, audit, observability, and denied-capability boundary before governed execution APIs are implemented.planned
Identity and access readiness
Deny-by-default governed execution endpoints remain the active replacement until production identity and access are approved.
Decision register for production identity provider, tenant isolation, role permissions, patient-context authorization, service authentication, consent, break-glass access, audit linkage, and regional identity controls.active
Execution attempt envelope and replay contract
Protected workflow execution remains blocked until durable attempt storage, customer authority, connector approval, PHI controls, and production review workflow are approved.
Metadata-only execution-attempt envelopes with deterministic idempotency, replay metadata, model-route telemetry, human review gates, audit linkage, failure recovery, and no-PHI scorecards.active
Execution attempt durable store
Protected workflow execution remains blocked until the migration is applied, authenticated AAL2 smoke passes, model/tool registries are approved, customer authorization exists, and production connectors are approved.
Tenant-scoped, no-PHI durable attempt metadata, idempotency TTL, locking, replay lookup, regional retention, immutable events, and protected human-review disposition APIs.planned
Runtime safety readiness
Deny-by-default governed execution endpoints remain the active replacement until runtime acceptance, throttling, and emergency shutdown controls are approved.
Decision register for runtime safety envelope, throttle policy, abuse signals, connector containment, emergency shutdown, Watchtower escalation, override rules, restoration protocol, and synthetic safety drills.active
Governed execution deny stubs
active gate
Deny-by-default execution endpoints that reject workflow execution before request-body parsing, attempt creation, connector access, workflow mutation, or patient-facing action.active
Denied execution audit boundary
active gate
Metadata-only audit envelope, evidence headers, and never-capture policy for denied governed execution attempts.planned
Audit persistence readiness
Metadata-only denied execution audit boundaries remain the active replacement until persistence is approved.
Decision register for durable denied-event audit storage, retention, access, encryption, incident response, regional residency, and Watchtower alerting.active
Hub readiness checks
active gate
Operational readiness visibility for product, API, and integration foundations.active
Master operating context
active gate
Company doctrine, decision framework, Atlas boundary, FaithCore boundary, and quality standard before product expansion.active
Agent workflow registry
active gate
Permission, input, output, audit-event, guardrail, interoperability, and human-review scope before specialized agent execution.active
GitHub Actions CI
active gate
Independent CI gate for deterministic install, dependency audit, lint, typecheck, and production build.active
QA evidence ledger
active gate
Dated release, smoke, token-policy, fail-closed, limitation, and manual AAL2 gate evidence surface for buyer-safe proof review.planned
Live clinical integrations
Synthetic conformance evaluations, fixtures, contracts, and explicit live blockers remain the active gate until production integration work is approved.
Future partner connector implementation and production validation after identity, consent, audit, security, profile, certification, and acceptance requirements are approved.