error-signaling-lacks-codebase-convention

Status: IN

Error signaling varies by module with no cross-cutting convention: payment splits exceptions (programming errors) from return codes (business failures), KV uses generic Exception for quorum failures, click aggregator uses boolean returns for rejection, and wallet propagates all custom exceptions unconditionally — callers cannot implement a single error-handling strategy.

Justifications

Four distinct error signaling strategies across four modules with no shared pattern or base exception type

Depends on (SL): payment-error-strategy-split, kv-store-quorum-exception, click-aggregator-return-value-signaling, wallet-no-exceptions-caught

Depended on by

JSON