Packages

squid_mesh

0.1.0-alpha.1
0.1.1 retired 0.1.0 0.1.0-beta.3 0.1.0-beta.2 0.1.0-beta.1 0.1.0-alpha.7 0.1.0-alpha.6 0.1.0-alpha.5 0.1.0-alpha.4 0.1.0-alpha.3 0.1.0-alpha.2 0.1.0-alpha.1

Durable workflow runtime for Elixir applications.

HexDocs

Current section

Files

Jump to
Readme
12 Versions
5 Dependencies
Dependants
Files
Activity
squid_mesh docs adr 0001-runtime-boundaries.md
Raw

docs/adr/0001-runtime-boundaries.md 

# 0001 - Runtime boundaries



## Status



Accepted



## Context



Squid Mesh needs to provide durable workflow semantics without becoming a

standalone platform or re-implementing lower-level background execution

infrastructure.



## Decision



Squid Mesh owns:



- declarative workflow structure

- payload validation

- run state, step state, and attempt history

- transitions, retries, replay, cancellation, and inspection



Squid Mesh delegates:



- durable job execution and delayed scheduling to Oban

- step behavior execution to Jido

- durable state storage to Postgres through the host application's repo



## Consequences



- the public API stays focused on workflow concepts rather than job internals

- host applications reuse existing `Repo` and `Oban` infrastructure

- Squid Mesh does not need to become a separate service

- some runtime guarantees depend on step-level idempotency at external boundaries