Will this Temporal workflow replay, retry and compensate the way you think it will?
Paste or drop the Python behind one durable process - the @workflow.defn classes, the
@activity.defn functions and the Worker - and its pyproject.toml. Your
browser reads every file and checks it: datetime.now(), random or an HTTP
call inside a workflow, an activity call with no timeout, a timeout given as a number, compensations run in
the order the steps ran, activities that retry forever or never heartbeat, a swallowed
cancellation, a loop that never continues as new, an activity no Worker registers. Free, before you sign in,
and nothing is uploaded. Then pick a lane: the audit gives exact edits for each finding, or
the fix lane writes the whole fixed files - and the page re-checks both.
The companies, hosts and values in the examples are invented. The first three are audits (the first also carries a saved fix run of its edited code, one click after the audit), the last two fix runs; each comes with a saved model reply, so you can see the whole page without signing in or spending a credit.
The audit rates determinism, activities, compensation and operations, confirms or dismisses every flag below, adds what rules cannot see (idempotency, retries of permanent failures, versioning of running executions), and gives exact before/after edits for each finding - which the page applies to your paste and re-checks.
What this does, and what it does not
The check is a reading of the text, not Python: nothing is imported or run, and no Temporal server is
contacted. Each file is lexed so strings and comments are never mistaken for code, its blocks are rebuilt
from indentation so each workflow class, method, loop, try and with has its exact extent, and each flag
carries the catalogue id it comes from and the line it points at. Workflow code here means the methods of
@workflow.defn classes; helpers they import from other modules, whether an external API is
idempotent, and how a change replays against executions already running are outside the check (noted,
not assumed). Replaying a recorded history with temporalio.worker.Replayer remains the
ground truth for non-determinism.
The paid lanes see your paste and the page's facts. Every quote and edit they return is checked against your paste, every edit and every returned file is put back and re-checked, and a reply that repeats a credential from your paste is called out. A paste stays in this browser unless you run a lane. Derived from the agent skill @wshobson/workflow-orchestration-patterns by Seth Hobson (wshobson/agents, MIT). Sources are listed in llms.txt.