Module error 

The canonical control-plane error taxonomy.

One definition point for every error code a dig-node control method emits, the ControlError envelope ({code, message, data:{code, origin}}), and the constructor both sides use so every error carries a machine-branchable data.code (UPPER_SNAKE) and data.origin.

The numeric values are the SAME published wire contract as dig-node’s meta::ErrorCode and the canonical dig-rpc -320xx control range — they never change once assigned. A client keys its UX off data.code (the stable symbol), never the human message.

Code	Variant	Origin	Meaning
-32700	ParseError	shell	request body was not valid JSON
-32600	InvalidRequest	shell	not a single JSON-RPC object
-32601	MethodNotFound	boundary	control method is not resolved
-32602	InvalidParams	node	missing/malformed params
-32000	DispatchFailed	shell	the node failed to dispatch
-32030	Unauthorized	shell	called without a valid control token
-32031	NotSupported	shell	control op unsupported on this build
-32032	ControlError	shell	control op failed at runtime

Structs

ControlError

A control-plane error, serialized as the JSON-RPC error object ({code, message, data:{code, origin}}).

ControlErrorData

The machine-branchable inner data on a control error: the stable symbol + its origin.

Enums

ControlErrorCode

A canonical control-plane error code.