What mekik gives your graph
Everything below comes from the mekik packages — @mekik/* on npm, Mekik.* on NuGet. Your graph stays pure ilmek.
One graph run = one turn
Point mekik at a compiled ilmek graph. Each user message drives one run; text, generative UI, tool traces and pauses stream back over one socket. The graph never learns it is being served.
Durable human-in-the-loop
A node calls mekik.approve and suspends. The pause lives in ilmek's checkpoint — with a durable checkpointer it survives a restart — and resumes exactly where it stopped, answered by a thread-scoped interrupt id.
Exactly-once side effects
mekik.tool journals each side effect through ctx.step. A resume re-runs the node from the top, but the tool it already ran is memoized — a refund never charges twice.
Generative UI streaming
Emit ui / text / event chunks with mekik.ui and mekik.text. They travel as genui frames carrying the same AIChunk shape chativa already renders inline.
Watermark resume
Persistent frames carry a per-conversation seq. Reconnect with your watermark and the server replays exactly what you missed — multi-tab and multi-device out of the box.
Two languages, one wire
TypeScript (reference) and .NET (port) speak byte-identical mekik/1, held to that promise by shared golden fixtures replayed through both mappers.
Agent Skills
Give a node a catalog of SKILL.md folders. The model sees names and descriptions, loads a skill's instructions on demand, and a skill's own tools are offered only once it is loaded.
Client tools
The frontend declares what its page can do — a date picker, a calendar — and a node calls it like a server tool, answered through the same durable pause.
MCP and A2A
Serve the graph as MCP tools or as an Agent2Agent peer, and bring other MCP servers' tools into an agent with the same traces, approvals and exactly-once.