Governed workload demo
A guided click path for showing how a health-system team catalogs a workload, runs it on local compute, traces lineage, verifies governance, and keeps PHI inside its own boundary.
Register the governed asset
Open the Catalog surface, draft the workload from English, and review the versioned tools, schemas, guardrails, purpose, and signoff roles before registration.
Bind to local runtime
Inspect the workload definition and its model/provider binding. In production this points at the customer's local vLLM endpoint or managed in-boundary model service.
Follow the workload execution
Open the synthetic run, inspect input, output, tool calls, latency, signoff state, and replay controls as a single lineage trail.
Prove policy and audit integrity
Load the hash chain to show tamper-evident audit entries for invoke, tool calls, policy enforcement, and awaiting-signoff state.
Close with the customer boundary
Close with deployment posture: service readiness, storage, model endpoint status, DSR exports, and customer-boundary evidence are visible to platform operators.
Build clinical workflow apps on top of this platform.
TheraSyn can support full clinical workflow applications, but the platform wedge stays clear: customer teams build workflow apps on top of the governed catalog, compute, lineage, and policy plane.