Module taxonomy 

The closed error taxonomy of spec 009, 3.6: each RemoteCode maps to exactly one spec 003 failure class, carries a default charge, and is written at the front of the failure detail as remote:<code> within the run record’s 256-byte detail.

Structs

RemoteFailure

A classified remote failure, before it becomes a report.

Functions

charge_for

The charge to report: the reported one when there is one, else the code’s default. A reported unknown counts as not reported.

classify_status

The code for an HTTP status (3.6 and 3.11); None for a success.

code_of_detail

The code a failure detail written by failure_detail begins with.

default_charge

The charge a code carries when the remote side reported none (3.6).

failure_class

The one failure class a code maps to (3.6, R-2).

failure_detail

remote:<code>, then : and detail when it is not empty, cut to 256 bytes on a character boundary (spec 003, 3.9.3).

is_local_only

Codes only the adapter itself can observe. A remote party that sends one is not trusted with it (it could zero a reported charge); adapters refuse such an answer as malformed_response.

is_refusal

True for the refusals whose default charge is observed{0} (3.6).

remote_end

Whether remote work may outlive a failure reported of the adapter’s own accord (spec 013, 3.1): when request bytes left the process, the charge is unknown because nothing established a final one, and the code is one where no confirmed end arrived. That covers a transport interrupted after sending and an unparseable answer, and also remote_deadline and remote_error without a charge: the remote side gave up or failed without confirming that its work and charges stopped.