Expand description
Protocol type definitions
The application supports multiple protocol implementations. Protocol behavior is controlled by the LLM based on the chosen protocol and instructions.
Re-exports§
pub use binding_defaults::BindingDefaults;pub use client_registry::CLIENT_REGISTRY;pub use connect_context::ConnectContext;pub use dependencies::ProtocolDependency;pub use docs::render_all_protocol_docs;pub use dual::client_protocol_for_server;pub use dual::compiled_client_protocol_for_server;pub use easy_registry::EASY_REGISTRY;pub use event_logger::log_action_result;pub use event_logger::EventLogContext;pub use event_type::Event;pub use event_type::EventType;pub use log_template::LogLevel;pub use log_template::LogTemplate;pub use metadata::DevelopmentState;pub use metadata::ProtocolMetadata;pub use metadata::ProtocolMetadataV2;pub use server_registry::registry;pub use spawn_context::SpawnContext;pub use spawn_context::StartupParamError;pub use spawn_context::StartupParamResult;pub use spawn_context::StartupParams;
Modules§
- binding_
defaults - Protocol binding defaults
- client_
registry - Client protocol registry
- connect_
context - Client connect context
- default_
port - The port a server starts on when the caller names none.
- dependencies
- Protocol dependency system
- docs
- Human-readable documentation dump for every compiled-in protocol.
- dual
- Dual-protocol detection: which server protocols have a client counterpart.
- easy_
registry - Easy protocol registry
- event_
logger - Event lifecycle logging
- event_
type - Event type definitions for protocol-specific events
- log_
template - Log template system for standardized event and action logging
- metadata
- Protocol metadata definitions
- server_
registry - Protocol registry
- spawn_
context - Server spawn context
Functions§
- stability_
report - Build a human-readable listing of every registered server and client
protocol, grouped by its declared
DevelopmentState, most-mature first.