Expand description
§IPC Message Types
Core message structures used by every IPC channel between Wind and Mountain.
Layout (one export per file, file name = identity):
IPCMessage::Struct- generic envelope with id, command, payload, timestamp, correlation id, priority.IPCCommand::Struct- command request with args and named params.IPCResponse::Struct- success/error response keyed by correlation id.MessagePriority::Enum- Low / Normal / High / Critical.
TODO: zero callers as of 2026-05-02. Used to be the planned shape for the Tauri-IPC envelope; superseded by the gRPC channel and direct Tauri events. Kept atomic so a future router can adopt it without re-deriving fields.
Modules§
- IPCCommand
- IPC command request: command name + positional
Args+ namedParamsmap + a priority. Built throughnewand theWithArg/WithParam/WithPrioritybuilder shims. - IPCMessage
- Standard IPC message: identifier, command name, JSON payload,
creation timestamp, optional correlation ID, and a priority. Built
through
newand theWithPayload/WithCorrelationId/WithPrioritybuilder shims. - IPCResponse
- IPC response: correlation ID, payload, success flag, optional error
string, and timestamp. Built through
Success/Errorconstructors that stamp the timestamp from the chrono UTC clock. - Message
Priority - Priority ladder used by
IPCMessage::StructandIPCCommand::Struct. Ordered so callers can compare with</>.DefaultisNormal.