We built something like this by hand without much difficulty for a product concept. We'd initially used LangGraph but we ditched it and built our own out of revenge for LangGraph wasting our time with what could've simply been an ordinary python function.
Never again committing to any "framework", especially when something like Claude Code can write one for you from scratch exactly for what you want.
We have code on demand. Shallow libraries and frameworks are dead.
This is one of the worst takes I've ever heard.
There's a reason industries have standards. If you replace established libraries with vibecoded alternatives you will have:
- less documentation
- less tested code
- no guarantees it's doing the right thing
- a dice roll for whether it works this time on this project
- a bad time in general
i noticed the same, so in the README, I describe `cord` as a protocol:
``` This repo is one implementation of the Cord protocol. The protocol itself — five primitives, dependency resolution, authority scoping, two-phase lifecycle — is independent of the backing store, transport, and agent runtime. You could implement Cord with Redis pub/sub, Postgres for multi-machine coordination, HTTP/SSE instead of stdio MCP, or non-Claude agents. See RFC.md for the full protocol specification. ```