Module server 

Command Server Implementation

The Command server implements the command lifecycle:

• CommandRegistry is the SOURCE OF TRUTH for all metadata (state, timestamps, etc.)
• KV stores ONLY operational data (params/response blobs, indices, leases)

Re-exports

pub use crate::dispatchers::CommandDispatcher;

pub use crate::dispatchers::NullCommandDispatcher;

pub use axum_handlers::create_axum_router;

pub use axum_handlers::CommandPayloadResponse;

pub use axum_handlers::HasCommandServer;

pub use axum_handlers::StorePayloadRequest;

pub use command_registry::delivery_mode_for;

pub use command_registry::select_command_target;

pub use command_registry::validate_command_name;

pub use command_registry::validate_command_target_id;

pub use command_registry::CommandAccessContext;

pub use command_registry::CommandEnvelopeData;

pub use command_registry::CommandMetadata;

pub use command_registry::CommandRegistry;

pub use command_registry::CommandStatus;

pub use command_registry::InMemoryCommandRegistry;

pub use command_registry::ResolvedCommandTarget;

Modules

axum_handlers

command_registry

Command registry abstraction for command server

storage

Structs

CommandServer

Core command server implementation.