Sphinx — Durable Workflow Runtime

Durable Workflow Runtime

Sphinx

Orchestrate what happens next — durably, correctly, over time.

The durable workflow runtime. Long-running business flows, human tasks, timers, and crash recovery — all governed, all traceable, executing against pinned approved artifacts.

One-line summary

Durable execution — survives crashes, resumes from journal. Activation-time pinning of all authority versions. Human task — claim, escalation, SLA, dual approval.

Part of the Pommala governed platform stack — one architecture where every authority answers exactly one class of question.

What it is

The problem it solves

The durable workflow runtime. Long-running business flows, human tasks, timers, and crash recovery — all governed, all traceable, executing against pinned approved artifacts.

Orchestration engines that mix business rules, policy logic, and workflow execution in one place become impossible to govern and audit. Sphinx owns only what it should — workflow progression — and delegates everything else to the right authority.

Asset classes

Definition Plane

Workflow graph, transitions, node metadata, authority references. Validated and approved before activation. Authority bindings compiled and pinned at activation time.

Durability Plane

Append-only execution journal, checkpointed state, idempotency-keyed outbound calls. Crash-safe recovery without developer versioning logic.

Human Task Plane

Creation, claim, assignment, escalation, approval, override tracking. SLA-aware with dual approval support and full audit trail.

Capabilities