sched

sched Durable workflow orchestration in Go. Write workflows as plain functions and the engine takes care of persistence, retries, signals, timers, and replay across restart and worker failure. Inspired by Temporal and Cadence. Single Go SDK, single binary, Postgres plus Redis. Apache 2.0. Status: alpha, working toward v0.1.0. See BACKLOG.md for a current breakdown of what is shipped, what is in progress, and what is planned. The full design lives in docs/PRD.md. Why State survives anything. Every workflow transition is persisted to Postgres before the RPC returns. Engine restart, worker crash, network blip: the workflow resumes. Replay on yield. Workflow functions are deterministic over their event history. When a worker dies the engine re-dispatches the task; the function re-runs against the same history with recorded commands turned into no-ops. The standard Temporal-style model, minus the platform. Small to operate. No coordinator, no sidecar. Active-passive HA is a Postgres advisory lock. Observability is a /metrics endpoint and an OTLP exporter. Architecture Three processes, two stateful dependencies. Engine.