Quality gates
SCRIMED keeps execution moving by replacing blockers with explicit, safer quality gates.
GitHub Actions remains a hardening item, while Vercel deployment, executable synthetic validation, fixture change review, synthetic workflow execution, execution-result fixtures, result validation, promotion review, governed execution contracts, identity and access readiness, execution-attempt readiness, runtime safety readiness, deny-by-default execution endpoints, denied-execution audit boundaries, audit persistence readiness, integration fixture validation, readiness checks, and integration contracts 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
Integration contracts
active gate
Interface boundary before FHIR, HL7, claims, 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.planned
Execution attempt readiness
Deny-by-default governed execution endpoints remain the active replacement until execution attempts can be deduplicated, persisted, audited, and safely replayed.
Decision register for attempt identity, idempotency, durable attempt state, concurrency, retry, failure quarantine, runtime-safety handoff, privacy boundaries, and regional attempt compliance.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.bypassed
GitHub Actions CI
Vercel deployment plus executable synthetic validation are the current active quality path.
Secondary build verification once workflow visibility and lockfile support are available.planned
Live clinical integrations
Synthetic fixtures and contract pages remain the gate until live integration work is explicitly approved.
Future connector validation after synthetic scenarios and contracts are stable.