Swati

every multi-agent framework I've seen makes the same assumption: coordination is an llm problem. good prompts, good memory, good routing - eventually they'll coordinate. that assumption is wrong.

coordination between independent processes is a distributed systems problem. when A sends to B, who guarantees B receives it? when three agents need to branch on the same decision, who guarantees they all take the same branch? no prompt answers these questions.

Swati answers them structurally. you write one TypeScript file describing the full protocol, who speaks, to whom, when, with what conditions. each role runs as a separate process. runtime projects that file down to each participant: every agent sees only its own steps, send always has a matching receive, branching decisions are broadcast so all roles take the same path.

tbh: it's deadlock-free by construction under normal execution. it doesn't handle adversarial agents or network partitions. if a role crashes, the others time out and fail cleanly. guarantee is structural, not adversarial.

you don't orchestrate agents. you describe the protocol once. protocol runs itself.

core is a conductor interpreter that walks a typescript choreography function and, per step, asks: does this belong to my role? if yes, execute it and append a signed entry to the log. if no, wait or skip. this is endpoint projection - a formal result from choreographic programming theory

before any run starts, all participants exchange a signed attestation containing the choreography's sha256. If any machine is running a different version, run aborts before any work is done - no silent mid-run mismatches. every action is logged as an ed25519-signed, hash-chained entry. swati verify replays the chain and checks every signature.

agents communicate over gensyn axl <> three separate nodes, genuinely distributed. choreography source and execution logs are stored on 0g. roles are discovered via ens(optional). SwatiRegistry.sol lets any participant verify onchain that they're running correct choreography with the correct peers.

every integration < transport, storage, llm, gate provider > is a swappable adapter. choreography file never changes; only the config does.