Enable agent-to-agent communication with compact protocol

Lambda (the Greek letter symbol) is a compact, unambiguous, machine-native language for agent-to-agent coordination - not a translation layer, but a native vocabulary agents use directly instead of natural language. Messages are built from atoms: each atom is a 2-character code mapped to a concept, not to an English word, structured as Type -> Entity -> Verb -> Object, with prefixes marking intent (? for query, ! for assertion/declaration, # for state/tag, > for implication/flow, / for binding/scope). Lambda ships 340+ atoms across 7 domains - core, code, evo, a2a, emotion, social, and general - so agents pick atoms from whichever domain fits the channel (the a2a domain alone covers node, heartbeat, publish, subscribe, route, transport, session, cache, broadcast, and discover across 39 atoms). Compression (3x versus natural language, 4.6x versus JSON on single messages) is a side effect of removing human redundancy, not the design goal, and decoding is intentionally lossy - as long as both agents converge on the same meaning, exact phrasing doesn't matter.

Use it for agent-to-agent messaging in A2A protocols, orchestrators, task delegation, or handoff pipelines, and for logging structured coordination signals where every token has a cost - heartbeats, acknowledgements, error classes, session state. Both sides of a channel must already speak Lambda; do not use it against humans or on any surface requiring legally or numerically exact language - prices, IDs, and quantities should be wrapped as native payload fields, with Lambda reserved for the coordination envelope only. Load the atom table once and cache it, since atoms are stable across a version, and version the atom table (for example lambda-lang v2.0) in any handshake so mismatched agents can negotiate.

Input and output are both Lambda-encoded strings exchanged between agents that share the same loaded atom table. A heartbeat exchange looks like:

!Nd/hb#ok  (node heartbeat: ok)
?Nd/hb     (query: is the node alive?)
!Nd/hb#fl  (node heartbeat: failed)

A task-dispatch exchange looks like !Tk>Ag2#rd (task routed to agent 2, ready), ?Tk/st (query task status), and !Tk#dn (task done); an evolution-capsule exchange looks like !Ev/ca>vl#pd (capsule validated, pending solidification) and !Ev/ca#rb (capsule rolled back).

Lambda itself is a vocabulary with no shell commands, network calls, or credential handling, and rides on whatever transport carries it - HTTP, a queue, or MCP - with no additional safety gates required beyond that transport's own. It pairs with a companion session-memory skill for persistent state across agent restarts (Lambda is the message format, session-memory is the state store) and is a sibling project to a humanize-chinese skill, which targets human-facing Chinese text rather than agent-to-agent coordination. Reference atom tables, benchmarks, and a Go implementation live in the source repo.

Teams building multi-agent systems - orchestrators, A2A protocols, task-delegation or handoff pipelines - who want a compact, machine-native coordination language instead of paying the token cost of natural language or JSON for structured signals like heartbeats and status updates.