One internal effect
The effect, step state, and successor transition commit in the same transaction. Epoch and expiry checks reject stale workers.
GO · POSTGRES · OPENTELEMETRY
Workers can fail.
The work should survive.
A durable workflow engine with fenced leases, atomic internal effects, bounded retries, and a console that shows what happened.
Recorded evidenceThis site presents saved runs and the recorded console. The
interactive Go/Postgres engine is not hosted here yet.
THE WORK'S ROUTEORDERED STEPS / DURABLE STATE
01 / MEASURED, NOT ESTIMATED
Raw campaign JSON ↗Synthetic workflows on a local development machine. These are not Vercel capacity measurements. Enqueue-to-first-claim uses database timestamps; HTTP request-to-handler-start was not measured.
Burst load sweep
Admission → all effects → drain| Workflows | Effects | Workflows / s | First-claim p99 |
|---|
Inspect actual workflow timings
First 80 rows in saved reconciliation| Idempotency key | Run | First claim |
|---|
02 / THE OPERATIONS CONSOLE
Recovery you can follow.
Login, recover a lost acknowledgement, pause dispatch, replay a failed step without repeating its completed prefix, and roll back a configuration.
Actual local screen recording. No simulated live counters.
03 / WHAT THE ENGINE GUARANTEES
SDK / console→Go API→Postgres↔Fenced workers
Visible failure
Retries have a budget. Exhausted work enters a dead-letter queue. Manual replay preserves completed prefix effects.
Precise boundaries
At-least-once execution. No exactly-once guarantee for arbitrary external HTTP, email, or payment effects.