Expand description
Wire DTOs for driving a lash runtime across a process boundary.
Each domain module carries one slice of the protocol vocabulary
(llm, turn_input, turn_result, processes, triggers,
prompt, tools, observations, usage_activity,
registry_errors); the crate root re-exports all of them, which is the
established public API for direct consumers of this crate. The
cross-cutting protocol handshake (REMOTE_PROTOCOL_VERSION,
ensure_protocol_version) lives at the root itself.
Re-exports§
pub use llm::*;pub use observations::*;pub use processes::*;pub use prompt::*;pub use registry_errors::*;pub use tools::*;pub use triggers::*;pub use turn_input::*;pub use turn_result::*;pub use usage_activity::*;
Modules§
- llm
- LLM request/response envelopes: messages, attachments, tool specs, output specs, provider metadata, and schema-projection contracts.
- observations
- Session observation: cursors, resumable observation events, and live replay gap envelopes.
- processes
- Process lifecycle envelopes: start/cancel/signal/await/list requests and results, process records and summaries, event semantics, execution environments, and runtime invocation provenance.
- prompt
- Prompt-layer envelopes: templates, slots, and contributions.
- registry_
errors - The protocol error type, plus the remote tool-registry contract and its reopen-stability assertion.
- tools
- Tool grants: schemas, call-path bindings, activation, scheduling, and retry policies.
- triggers
- Trigger envelopes: occurrence emission, subscriptions, and registrations.
- turn_
input - Turn input envelopes: items, image blobs, per-turn protocol options, and the turn request.
- turn_
result - Turn result envelopes: the turn result itself, outcomes, stops, assistant output, usage/execution summaries, tool-call summaries, issues, and causal references.
- usage_
activity - Token usage accounting and the streaming turn-activity event vocabulary.