Skip to main content

Module message

Module message 

Source
Expand description

The canonical conversation shape.

One definition, in core, so that every layer agrees: a Python step, the Rust provider, the schema validator, the journal, and the report renderer. Provider-specific wire formats are converted at the edge (in soma-llm), never leaked inwards.

This exists because of what the failure data says. Across 1600+ annotated multi-agent traces (MAST, NeurIPS 2025), ~37% of failures are inter-agent misalignment — context lost at a handoff, formats that don’t line up. A shared message type plus a schema that can say “this edge carries messages” moves a chunk of that from runtime surprise to compile error.

Structs§

Message
One turn in a conversation.
Messages
A conversation: an ordered list of turns.

Enums§

ContentBlock
One piece of a message’s content.
Role
Who produced a message.