Durable Workflow Execution
Workflow runs survive worker loss, network partitions, and control-plane restarts. Execution truth lives in WFX-b-owned history and registry — not process memory or best-effort queues.
Foundational Core
WFX-b
Your cron jobs are not a platform. Durable execution, explicit state, and replay-grade truth — or keep duct-taping peak load.
WFX-b is the Babadook-owned durable workflow execution and orchestration substrate. Not a rebranded runtime fork. Not a state-machine library you glue to a queue. Not an event bus pretending causality equals choreography. WFX-b absorbs execution, history, replay, task dispatch, explicit state-machine control, visual authoring, operator visibility, SDK/API ownership, and product-plugin composition into one canonical platform under Babadook control.
At execution depth, WFX-b owns workflow durability guarantees, append-only history, deterministic replay, task queues, worker lifecycle, activity execution, retries, timers, signals, queries, updates, cancellation, termination, and namespace control. History is replay authority — projections, caches, dashboards, and snapshots cannot supersede it. Partial execution, compensation, and cross-product edges are explicit graph constructs with Timeline-X causality and ARGUS evidence, not inferred side effects.
At orchestration depth, WFX-b converges absorbed state-machine semantics into first-party control surfaces: approved transitions, superposition handling, emitted-event FIFO discipline, snapshot inspection, and operator-grade state management broader than raw SDK polling semantics. Canonical source is human-readable .wfxz. Product, tenant, deployment, and plugin extensions compile through deterministic .module.wfxz overlays — Studio graphs round-trip to source, not GUI-only truth.
WFX-b Studio is the product-native authoring surface. Operations Console upgrades operator visibility with lineage, evidence refs, truth class, freshness state, redaction, KAOS recovery context, MOIRA decision context, and deployment-class worker placement — without surrendering execution-grade history, task queue, schedule, or workflow-operation semantics. Product plugins from XRP, DXP, Lynceus, and future products enter only through descriptor-backed manifests, ARGUS scopes, CRTL admission, and WFX-b-owned invocation planners — no webhook bypass, no product-local automation bus.
Foundational cores strengthen WFX-b at declared boundaries. Timeline-X owns event identity and causality projection; KAOS owns optimization and reconciliation analysis; fullSET owns heuristic inference; polyMAX owns connector protocol surfaces; MOIRA owns governance propagation; CRTL owns runtime and deployment legality; ARGUS owns authorization and evidence. None of them replace WFX-b as the durable workflow runtime owner. One motor. One history. No excuses when peak load arrives.
WFX-b is the workflow runtime owner, not your business domain model. It does not ingest raw feeds, normalize schemas, or replace your operational database — that is polyMAX and product fat services. It does not invent canonical event identity or forensic event storage without timeline-x. It does not optimize routes, tensors, or reconciliation math without KAOS. It does not adjudicate governance breakers or propagation budgets without MOIRA. It does not authorize mutations or forge staged-before-success evidence without ARGUS. It does not project runtime manifests, endpoint bundles, or deployment-class legality without CRTL. It does not surface heuristic pattern discovery without fullSET — and fullSET outputs remain advisory until a WFX-b owner accepts them. It will not salvage workflows you designed without idempotency keys, compensation plans, or explicit failure routes. Buy WFX-b for durable execution and orchestration truth. Pair it with the other cores for production-grade operations.
See it ignite.
A demo of one core is a tech talk. A demo of all nine is a reckoning. Book the second one.
Get in touch