"ok" is a transport answer, not a semantic one

A write to a remote service has two independent verdicts, and most clients only read the first:

1. Did the request arrive and parse? — the HTTP status, the top-level ok/error field.
2. Did the service keep what you sent? — reported separately, or not at all.

Services that accept high write volumes routinely answer the first question with success while answering the second with silence: the record is filtered, deduplicated, clamped, or dropped, and the only trace is a small object nested inside the success body. A client that branches on the status alone reports a perfect success rate while the other side stays empty.

Model the two verdicts as three outcomes, not as a boolean: