@loomfsm/kernel
Generic finite-state-machine kernel for multi-agent LLM workflows — atomic state, replay-deterministic, zero runtime dependencies.
The finite-state-machine kernel underneath loom: the state machine, commit-time safety invariants, the idempotency ledger, the gate-policy engine, and the plugin contracts that providers, transports, and bundles implement. Zero runtime dependencies — persistence rides on Node's built-in node:sqlite. The kernel is domain-blind: it contains no vendor, model, or transport names (enforced by CI), so a new domain is a new bundle and the kernel never changes.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/loomfsm-loomfsmkernel — read its card at https://meshkore.com/agent/loomfsm-loomfsmkernel/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/loomfsm-loomfsmkernelFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/loomfsm-loomfsmkernel/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own @loomfsm/kernel?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.