🪶 How it composes
The stack.
Each layer is built on the layer below. spec-sync is the foundation. fledge and Merlin both sit on it. Showcases at the top (corvid-chat, Podo, Rita) pull from every layer at once.
Read it top to bottom
- 1. Showcases at the top are what people actually use: corvid-chat (federated E2EE chat, the full-stack demo), Podo (multi-platform weather app, the consumer surface), and Rita (the weather API backend). All three in development. None 1.0 yet.
- 2. Agent tools in the next layer are how AI participates: Merlin is the agent runner in active development (consumes fledge plugins, plus a lot more) and corvid-agent is the released platform sessions run on.
- 3. Primitives are the two general-purpose libraries: AlgoChat (encryption, six implementations) and fledge (the dev-lifecycle CLI. Crazy because plugins). Released, used in CI everywhere.
- 4. spec-sync is the foundation. Both fledge and Merlin are built on it. Markdown specs are the contract; drift between code and spec fails the build. The thing the whole stack depends on staying honest.
- 5. Algorand is the substrate. AlgoChat settles on it for on-chain transport; corvid-agent settles on it for memory + identity. Dashed lines on the diagram mark the chain edges.
Each layer depends on the layer below. That's the workshop-that-compounds bet in one diagram: every new primitive sharpens every layer above it.