- Clarity over cleverness
- Small, reversible changes
- Explicit costs, domain-first thinking
- History is part of the product
- Keep routine updates short, direct, and conversational.
Against the three libs in post 59, Squid Mesh is closer to a Phoenix/OTP business workflow runtime than to a minimal durable-function engine.
Absurd and TensorZero durable are mostly “write normal code, checkpoint steps into Postgres.” Estuary Flow automations is closer to a persistent control-plane task actor system. Squid Mesh is more explicit: workflow DSL, durable run facts, step state, transitions, approvals, recovery policy, inspection, replay, and host-app integration.
| Area | Squid Mesh | Absurd | TensorZero durable | Estuary Flow automations |
|---|
A workflow run becomes a durable workflow agent. The agent owns orchestration state for one run: current projection, runnable steps, dependency readiness, pause/resume/cancel decisions, and terminal status. It does not “do” step work directly. It records durable intent and coordinates dispatch.
A dispatch agent owns queue-side execution intent: scheduled attempts, claims, leases, heartbeats, retries, completion, and stale worker recovery.
IntentLedger can then become the default durable executor underneath that dispatch side, while Squid Mesh keeps the executor boundary pluggable.
| defmodule MiddleEarth.Workflows.RingQuest do | |
| use SquidMesh.Workflow | |
| workflow do | |
| trigger :leave_shire do | |
| manual() | |
| payload do | |
| field :ring_bearer, :string, default: "Frodo" | |
| field :snack_count, :integer, default: 7 |
| ;;; $DOOMDIR/config.el -*- lexical-binding: t; -*- | |
| ;; Place your private configuration here! Remember, you do not need to run 'doom | |
| ;; sync' after modifying this file! | |
| ;; Some functionality uses this to identify you, e.g. GPG configuration, email | |
| ;; clients, file templates and snippets. It is optional. | |
| (setq user-full-name "Todd Pickell" | |
| user-mail-address "todd@tap-software.com") |